Fusion Confinement Monitor

Triple-product confinement vs ignition criterion: subignition → confined → disruption-risk. The control surface for tokamak / stellarator shots.

Category	Plasma Physics
Template ID	fusion-confinement-monitor
Definition	fusion_confinement_monitor v1.0
States	4 (initial: subignition; terminal: safed)
Transitions	4
Operators composed	XIION_1, XIION_2, KO42
Audit clock	on · tick rate 1

What it's for

• Tokamak shot control
• Stellarator experiments
• Inertial-confinement diagnostics

States

State	Role
subignition	initial
confined	intermediate
disruption_risk	intermediate
safed	terminal

Transitions

From	To	Operator	Fires when	Proof	Trigger / actions
subignition	confined	XIION_1	input.triple_product >= input.lawson_criterion	required	—
confined	disruption_risk	XIION_2	input.mhd_instability > input.disruption_threshold	required	—
confined	subignition	XIION_1	input.triple_product < input.lawson_criterion	required	—
disruption_risk	safed	KO42	input.plasma_terminated == true	required	—

Operators it composes

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

• XIION_1
• XIION_2
• 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/fusion-confinement-monitor

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

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.