Water Contamination Gate

WATER_QUALITY composite: potable → advisory → unsafe, holding distribution until contaminant indices return below limits. Provable public-health record.

Category	Environmental
Template ID	water-contamination-gate
Definition	water_contamination_gate v1.0
States	4 (initial: potable; terminal: cleared)
Transitions	4
Operators composed	WATER_QUALITY, BIODIVERSITY_INDEX, KO42
Audit clock	on · tick rate 1

What it's for

• Municipal water supply
• Industrial discharge compliance
• Disaster-response water safety

States

State	Role
potable	initial
advisory	intermediate
unsafe	intermediate
cleared	terminal

Transitions

From	To	Operator	Fires when	Proof	Trigger / actions
potable	advisory	WATER_QUALITY	input.contaminant_index > input.advisory_limit	required	—
advisory	unsafe	WATER_QUALITY	input.contaminant_index > input.unsafe_limit	required	—
advisory	potable	WATER_QUALITY	input.contaminant_index <= input.advisory_limit	required	—
unsafe	cleared	KO42	input.retest_passed == true	required	—

Operators it composes

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

• WATER_QUALITY
• BIODIVERSITY_INDEX
• 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/water-contamination-gate

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

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.