Cardiac Rhythm Watch

NM30 (x(t)=A·cos(ωt+φ)) tracks beat-to-beat rate excursion: sinus → arrhythmia → alert when the rhythm leaves its declared envelope for too many beats. A physics-grade rhythm watchdog — not a diagnosis.

Category	Medical
Template ID	cardiac-rhythm-watch
Definition	cardiac_rhythm_watch v1.0
States	4 (initial: sinus; terminal: acknowledged)
Transitions	4
Operators composed	NM30, KO42
Audit clock	on · tick rate 1

What it's for

• Wearable ECG rhythm gating
• Telemetry-bed arrhythmia flags
• Holter post-processing

States

State	Role
sinus	initial
arrhythmia	intermediate
alert	intermediate
acknowledged	terminal

Transitions

From	To	Operator	Fires when	Proof	Trigger / actions
sinus	arrhythmia	NM30	input.rate_excursion_bpm > input.excursion_tolerance_bpm	required	—
arrhythmia	sinus	NM30	input.rate_excursion_bpm <= input.excursion_tolerance_bpm	required	—
arrhythmia	alert	NM30	input.sustained_beats > input.alert_beats	required	—
alert	acknowledged	KO42	input.clinician_ack == true	no	—

Operators it composes

Each transition fires a registry operator through the master equation (compute → prove → verify). This template composes:

• NM30
• 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/cardiac-rhythm-watch

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

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.