Reactor Criticality Margin

Tracks effective multiplication factor k_eff: subcritical → critical → supercritical-warning with automatic scram. The core reactivity-safety contract.

Category	Nuclear
Template ID	reactor-criticality-margin
Definition	reactor_criticality_margin v1.0
States	4 (initial: subcritical; terminal: scrammed)
Transitions	4
Operators composed	NP1, NP2, KO42
Audit clock	on · tick rate 1

What it's for

• Research-reactor ops
• SMR control rooms
• Criticality-safety in fuel handling

States

State	Role
subcritical	initial
critical	intermediate
supercritical_warn	intermediate
scrammed	terminal

Transitions

From	To	Operator	Fires when	Proof	Trigger / actions
subcritical	critical	NP1	input.k_eff >= 1.0 - input.deadband && input.k_eff <= 1.0 + input.deadband	required	—
critical	supercritical_warn	NP2	input.k_eff > 1.0 + input.deadband	required	—
critical	subcritical	NP1	input.k_eff < 1.0 - input.deadband	required	—
supercritical_warn	scrammed	KO42	input.scram == true	required	—

Operators it composes

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

• NP1
• NP2
• 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/reactor-criticality-margin

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

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.