Renal Dose Adjuster

MED_GFR + MED_CLEARANCE: normal → reduce-dose → hold as estimated renal function falls, preventing accumulation of renally-cleared drugs.

Category	Medical
Template ID	renal-dose-adjuster
Definition	renal_dose_adjuster v1.0
States	4 (initial: normal; terminal: resumed)
Transitions	4
Operators composed	MED_GFR, MED_CLEARANCE, KO42
Audit clock	on · tick rate 1

What it's for

• Nephrology dosing
• Elderly polypharmacy
• Contrast-agent safety

States

State	Role
normal	initial
reduce_dose	intermediate
hold	intermediate
resumed	terminal

Transitions

From	To	Operator	Fires when	Proof	Trigger / actions
normal	reduce_dose	MED_GFR	input.gfr_ml_min < input.reduce_threshold	required	—
reduce_dose	hold	MED_CLEARANCE	input.gfr_ml_min < input.hold_threshold	required	—
reduce_dose	normal	MED_GFR	input.gfr_ml_min >= input.reduce_threshold	required	—
hold	resumed	KO42	input.renal_recovered == true	required	—

Operators it composes

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

• MED_GFR
• MED_CLEARANCE
• 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/renal-dose-adjuster

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

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.