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

Guardrails: Safe-Operating-Envelope Checks

The certified operating envelope is the arbiter of every proposed action; membership is recomputed over the full state, never clipped or assumed.

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.

The envelope is the safety contract

The safe operating envelope is the certified region of state space in which the machine may operate. It is defined by physics and engineering limits — current, field, pressure, density, temperature margins, stability boundaries — and it is the arbiter of every proposed action. A proposed action is admissible only if applying it keeps the predicted state inside the envelope.

Membership, not clipping

Envelope enforcement checks membership; it does not silently clip an out-of-bounds proposal into the region. Clipping hides intent and can produce a physically inconsistent setpoint. Instead, a proposal that would leave the envelope is denied with the specific violated constraint returned to the copilot, which must replan. This keeps the reasoning honest and the operator informed.

text
envelope_contains(state, proposal):
  s' = predict(state, proposal)          # twin/reduced model
  for c in constraints:                   # breeder or burner set
     if not c.satisfied(s'):
        return (False, c.name, c.margin(s'))
  return (True, None, min_margin(s'))

Machine-specific constraint sets

Representative envelope constraints
Breeder Ip<= 9.66 MA design point, ramp-rate limitedcurrent / disruptionBreeder stabilityq95 >= q_min, betaN and li in bandMHDBreeder field<= 16.84 T peak, magnet temp marginmagnetBurner plug<= 26.49 T plug, 17 T throatmagnetBurner potentialambipolar phi >= phi_minconfinement

The envelope is recomputed by L4 from the full current state for every proposal, using the twin or a certified reduced model — L4 never trusts a copilot's claim that its proposal is in-envelope. Constraints carry margins, so L4 can distinguish a comfortable action from one that skirts a boundary, and can require human confirmation for low-margin actions even when they are technically admissible.

Envelope checks are the semantic complement to the structural schema validation: schemas stop malformed and grossly out-of-range calls cheaply; envelope checks stop contextually unsafe ones with full-state physics. Both sit inside L4 authorization ahead of L1 and the hardware interlocks. See the L3 safe-operating-envelope definition.

Content reviewed August 2026 · design-and-simulation stage