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.
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.
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
- Every side-effecting step has an explicit precondition and abort criterion
- Preconditions are evaluated against live twin state at generation and at run time
- Abort criteria reference the certified safe operating envelope
- Steps that cannot satisfy a precondition are flagged, not silently skipped
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.