Decay-Heat Removal Watch

Post-shutdown decay heat vs cooling capacity: adequate → marginal → insufficient. The Fukushima-class failure mode, made continuously provable.

Category	Nuclear
Template ID	decay-heat-removal
Definition	decay_heat_removal v1.0
States	4 (initial: adequate; terminal: recovered)
Transitions	4
Operators composed	NP3, NP4, KO42
Audit clock	on · tick rate 1

What it's for

• Spent-fuel pool monitoring
• Post-shutdown cooling
• Emergency-cooling readiness

States

State	Role
adequate	initial
marginal	intermediate
insufficient	intermediate
recovered	terminal

Transitions

From	To	Operator	Fires when	Proof	Trigger / actions
adequate	marginal	NP3	input.cooling_margin_pct < input.marginal_pct	required	—
marginal	insufficient	NP4	input.cooling_margin_pct < input.critical_pct	required	—
marginal	adequate	NP3	input.cooling_margin_pct >= input.marginal_pct	required	—
insufficient	recovered	KO42	input.backup_cooling_online == true	required	—

Operators it composes

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

• NP3
• NP4
• 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/decay-heat-removal

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

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.