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: Runbook Generation

Assembling an approved scenario into an ordered, precondition-checked runbook where each side-effecting step routes through L4 and human confirmation.

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.

From approved scenario to executable runbook

A runbook is the ordered, checkable sequence that takes an approved scenario from a cold machine to a completed shot and back. The Operations Copilot generates it by retrieving the approved template for the scenario class, binding it to the current twin state, and inserting the scenario-specific setpoints from the Plasma Copilot's approved design.

Structure of a generated step

Each step carries an action, a precondition checked against live twin state, an expected observable with tolerance, an abort criterion, and an authorization tag. Read/monitor steps run freely; any step that commands hardware is tagged for L4 authorization and human confirmation.

text
step:
  action:        'ramp Ip to 9.66 MA at dIp/dt <= limit'  (breeder)
  precondition:  vacuum ok, coils armed, envelope entered
  expected:      Ip(t) tracks reference within tolerance
  abort_if:      q95 < q_min OR vertical growth > gamma_max
  authorization: L4 + human            # side-effecting

Preconditions and aborts are first-class

The copilot will not emit a runbook that steps outside the envelope; such a runbook is refused with an explanation rather than clipped. Generated runbooks are proposals for human review; approval, and each side-effecting step at run time, requires operator confirmation through human oversight and L4 authorization. For the burner (Aegis / MetroVolt) the same generator produces plug-conditioning and DEC-startup runbooks bound to the tandem-mirror operating point. Every runbook is retained for audit.

Content reviewed August 2026 · design-and-simulation stage