Superconductor Tc Guard

Critical-temperature / critical-current margin: superconducting → approaching-quench → normal as a magnet nears its quench boundary. Protects MRI, fusion, and accelerator magnets.

Category	Condensed Matter
Template ID	superconductor-tc-guard
Definition	superconductor_tc_guard v1.0
States	4 (initial: superconducting; terminal: recovered)
Transitions	4
Operators composed	CDO1, CDO3, KO42
Audit clock	on · tick rate 1

What it's for

• MRI magnet protection
• Fusion / accelerator magnets
• Maglev / power cables

States

State	Role
superconducting	initial
approaching_quench	intermediate
normal	intermediate
recovered	terminal

Transitions

From	To	Operator	Fires when	Proof	Trigger / actions
superconducting	approaching_quench	CDO1	input.temp_k > input.tc_k * input.margin || input.current_a > input.ic_a * input.margin	required	—
approaching_quench	normal	CDO3	input.temp_k > input.tc_k || input.current_a > input.ic_a	required	—
approaching_quench	superconducting	CDO1	input.temp_k <= input.tc_k * input.margin && input.current_a <= input.ic_a * input.margin	required	—
normal	recovered	KO42	input.recooled == true	required	—

Operators it composes

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

• CDO1
• CDO3
• 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/superconductor-tc-guard

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