Irrigation Pressure Guard

NM24 (PE=mgh, water-column head): nominal → low_pressure when line head drops below the minimum, → fault when the pressure drop crosses the leak/burst threshold. Keeps drip/sprinkler lines honest from cheap sensors.

Category	Agriculture & IoT
Template ID	irrigation-pressure-guard
Definition	irrigation_pressure_guard v1.0
States	4 (initial: nominal; terminal: serviced)
Transitions	4
Operators composed	NM24, KO42
Audit clock	on · tick rate 1

What it's for

• Drip-line leak detection
• Pump-failure alerting
• Frost-protection sprinkler readiness

States

State	Role
nominal	initial
low_pressure	intermediate
fault	intermediate
serviced	terminal

Transitions

From	To	Operator	Fires when	Proof	Trigger / actions
nominal	low_pressure	NM24	input.head_pressure_kpa < input.min_pressure_kpa	required	—
low_pressure	nominal	NM24	input.head_pressure_kpa >= input.min_pressure_kpa	required	—
low_pressure	fault	NM24	input.pressure_drop_kpa > input.fault_drop_kpa	required	—
fault	serviced	KO42	input.serviced == true	no	—

Operators it composes

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

• NM24
• 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/irrigation-pressure-guard

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

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.