ZeqEmail

NET_CLUSTERING watch — connected → degraded → dropped when latency_ms crosses your thresholds; auto-logged with a ZeqProof per transition. Pulse-verified email dispatch. DKIM/SPF/DMARC compliant with Zeqond timestamp headers for

Category	Network & Comms
Template ID	zeq-email
Definition	zeqemail v1.0
States	4 (initial: connected; terminal: restored)
Transitions	4
Operators composed	NET_CLUSTERING, KO42
Audit clock	on · tick rate 1

What it's for

• ZeqEmail
• Threshold monitoring
• Audited latency_ms alerting

States

State	Role
connected	initial
degraded	intermediate
dropped	intermediate
restored	terminal

Transitions

From	To	Operator	Fires when	Proof	Trigger / actions
connected	degraded	NET_CLUSTERING	input.latency_ms > input.latency_ms_watch	required	—
degraded	dropped	NET_CLUSTERING	input.latency_ms > input.latency_ms_alert	required	—
degraded	connected	NET_CLUSTERING	input.latency_ms <= input.latency_ms_watch	required	—
dropped	restored	KO42	input.acknowledged == true	no	—

Operators it composes

Each transition fires a registry operator: the operator's closed-form solver runs, then the result is proved and verified (compute → prove → verify). The verbatim equation is recorded on the audit row as master_equation_block. This template composes:

• NET_CLUSTERING
• KO42

Browse the operators at /operators/; the building blocks a transition calls are the framework's protocols. KO42 is the always-on substrate operator; physics operators carry proof_required: true, so each fire runs the full compute → prove → verify path and lands a verifiable proof digest on your entangled state.

Deploy it

Inspect the full definition, then deploy it onto your state machine. Every fire is Zeqond-stamped onto your entangled state.

# 1. Inspect — the full definition (states, transitions, operators) as served
curl -sS https://zeqsdk.com/api/contracts/templates/zeq-email

# 2. Deploy onto your machine (auth: session; body carries your machine slug)
curl -sS -X POST https://zeqsdk.com/api/contracts/templates/zeq-email/deploy \
  -H "Content-Type: application/json" \
  -b "<your session cookie>" \
  -d '{"slug":"<your-machine>"}'
# → 201 { "ok": true, "contract": { "id": "…", "currentState": "connected", … },
#         "template_id": "zeq-email" }

The deploy path runs the same two-stage validation as the canonical create route (ContractDefinitionSchema.parse + validateContractDefinition against the live registry), writes the creation row onto your entangled state, and schedules the first fire. From there, drive transitions with POST /api/chain/<your-machine>/contracts/<id>/transition or let any triggers fire them autonomously.

Next

• Contract IDE — author, preview, and deploy contracts (this template is in the Templates tab).
• State Contracts — the full contract model: conditions, triggers, pre/post actions, lifecycle.
• Templates Library — every ready-to-deploy contract, grouped by category.
• Protocols — the named building blocks a transition composes.