Skip to content
Technology How it works Breeder — Hyperion Burner — Aegis Burner — MetroVolt AI-Native Architecture Magnets Fuel cycle Safety Roadmap
Solutions AI & Data Centers Defense & Government Grid & Baseload Neutron Detection Quantum
Learn Technical Library
Proof Publications Whitepapers Technical Library Open Science & Reproducibility The Honest Gates
Company About / Mission Leadership Environment Health & Safety Investors Careers Press Contact
3D Model
AI Architecture › L5 · Applications & Copilots
L5 · Applications & Copilots

Operations Copilot: Procedure Generation

Generating startup, shutdown, recovery, and maintenance procedures from approved templates, twin state, and retrieved standing orders.

THE STACK · click to jumpL7Ecosystem & StrategyL6Experience & VisualizationL5Applications & CopilotsL4OrchestrationL3Twin Modeling & AIL2Data FabricL1Control PlaneL0Foundation▲tlmctl▼L5 · APPLICATIONS & COPILOTSAgentic copilots that reason over the machine.1Plasma Copilotscenario design2Engineering Copilotsubsystem analysis3Operations Copilotrunbooks & procedures4Agentic Toolsbounded action-taking5Knowledge BaseRAG over the fabric6Guardrailssafety-boundedMACHINE TIEReads the twin and fabric; proposes actions that route through L4.KRONOS FUSION ENERGYAI-NATIVE S.M.A.R.T. GENERATORAPPLICATIONS & COPILOTSSHEET 07REV. 2026-08L5 · AI-NATIVE STACK
L5 · Applications & Copilots — its place in the stack (left, click any layer) and its internal components (right). Telemetry rises; control descends.

Procedures beyond the shot

Where a runbook covers a single scenario, procedures cover the standing operations of the machine: cool-down and warm-up of the superconducting magnets, vacuum conditioning, plasma-facing-component bake-out, fault recovery, and maintenance interventions. The Operations Copilot generates these from approved procedure templates bound to the current condition of the machine as reported by the twin and the Engineering Copilot.

Recovery procedures

Recovery procedures are the most safety-relevant class. After a disruption on the breeder or a potential collapse on the burner, the copilot generates the ordered recovery: verify hardware state, confirm quench-detection and dump-system integrity, re-establish vacuum and cryogenics, and re-enter the operating envelope from a known-safe state. The generated procedure defers to hardware interlocks and never proposes bypassing an interlock.

text
generate_procedure(kind, machine):
  tmpl  = rag.retrieve(kind, machine)   # approved template
  cond  = engineering_copilot.state(machine)
  steps = fill(tmpl, cond)
  assert no step bypasses an interlock       # hard rule
  mark side-effecting steps -> L4 + human
  return procedure(steps, cite=[tmpl, cond])

Machine-specific procedure families

Generated procedures are drafts for the responsible engineer to review and approve; they are never self-authored into standing orders. A procedure that would create or modify a persistent operating rule is explicitly out of the copilot's authority and is surfaced for human decision. All procedures are validated for consistency against the current approved procedure set before proposal, and are exercised against the twin during commissioning. See commissioning support and the evaluation harness.

Content reviewed August 2026 · design-and-simulation stage