ZeqEmail

SMS, VoIP, email, mesh, satellite.

• Protocol ID — zeq-email
• Category — Communications
• Endpoint — POST /api/comms/email
• Auth — api-key
• Rate limit — 20/min
• Version — 1.287.0
• Precision — ≤0.1% (KO42-enforced)

What it does

Pulse-verified email dispatch. DKIM/SPF/DMARC compliant with Zeqond timestamp headers for cryptographic send-time provenance.

Signature

Request

POST /api/comms/email

Param	Type	Required	Default	Description
to	string	✓	—	Recipient email address.
subject	string	✓	—	Email subject line.
body	string	✓	—	HTML or plain-text body.
format	string		"html"	'html' or 'text'.

Response

{ messageId, status, zeqondStamp, deliveryHash }

Runnable example

curl -sS -X POST \
  -H "Authorization: Bearer $ZEQ_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "to": "<value>",
  "subject": "<value>",
  "body": "<value>",
  "format": "html"
}' \
  "https://api.zeq.dev/api/comms/email"

Integrate

1. Domain solver — compose with KO42 + two additional operators from the matching family for pulse-coherent results.
2. Digital twin — pipe sensor data into this protocol every Zeqond to keep the model phase-locked with the system.
3. Alert threshold — flag results whose error_pct exceeds 0.1% as out-of-spec events for the operations layer.

Seeds

• Near — wrap /api/comms/email in a language SDK so builders can call it in three lines.
• Medium — publish a reference integration demonstrating ZeqEmail alongside a real workload, with pulse-aligned metrics.
• Far — propose ZeqEmail as an open reference standard so other runtimes can implement it verbatim against the Zeq paper.

Papers

• Zeq paper — https://doi.org/10.5281/zenodo.18158152
• Framework paper — https://doi.org/10.5281/zenodo.15825138

Middleware active. Kernel on the 1.287 Hz HulyaPulse. Awaiting next Zeqond.