Infusion Safety Monitor

Pharmacokinetic steady-state: sub-therapeutic → therapeutic → TOXIC as predicted plasma concentration crosses the therapeutic window. Guards continuous-infusion dosing.

Category	Medical
Template ID	infusion-safety-monitor
Definition	infusion_safety_monitor v1.0
States	4 (initial: subtherapeutic; terminal: stopped)
Transitions	4
Operators composed	MED_STEADY_STATE, MED_DOSAGE, MED_HALF_LIFE, KO42
Audit clock	on · tick rate 1

What it's for

• ICU infusion safety
• Anaesthesia depth control
• Narrow-therapeutic-index drugs

States

State	Role
subtherapeutic	initial
therapeutic	intermediate
toxic	intermediate
stopped	terminal

Transitions

From	To	Operator	Fires when	Proof	Trigger / actions
subtherapeutic	therapeutic	MED_STEADY_STATE	input.plasma_conc >= input.therapeutic_min	required	—
therapeutic	toxic	MED_DOSAGE	input.plasma_conc > input.therapeutic_max	required	—
therapeutic	subtherapeutic	MED_HALF_LIFE	input.plasma_conc < input.therapeutic_min	required	—
toxic	stopped	KO42	input.infusion_halted == true	required	—

Operators it composes

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

• MED_STEADY_STATE
• MED_DOSAGE
• MED_HALF_LIFE
• 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/infusion-safety-monitor

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

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.