Groundwater Drawdown Guard

Aquifer drawdown (Theis): sustainable → over-extraction → critical as the water table falls past recharge-balanced limits. Protects aquifers from collapse.

Category	Geophysics
Template ID	groundwater-drawdown-guard
Definition	groundwater_drawdown_guard v1.0
States	4 (initial: sustainable; terminal: restored)
Transitions	4
Operators composed	GP3, GP4, KO42
Audit clock	on · tick rate 1

What it's for

• Agricultural water management
• Municipal well fields
• Subsidence prevention

States

State	Role
sustainable	initial
over_extraction	intermediate
critical	intermediate
restored	terminal

Transitions

From	To	Operator	Fires when	Proof	Trigger / actions
sustainable	over_extraction	GP3	input.drawdown_rate_m_yr > input.recharge_rate_m_yr	required	—
over_extraction	critical	GP4	input.water_table_m < input.critical_depth_m	required	—
over_extraction	sustainable	GP3	input.drawdown_rate_m_yr <= input.recharge_rate_m_yr	required	—
critical	restored	KO42	input.extraction_reduced == true	required	—

Operators it composes

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

• GP3
• GP4
• 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/groundwater-drawdown-guard

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