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 › L3 · Twin Modeling & AI
L3 · Twin Modeling & AI

The Certified Safe Operating Envelope

MPC never optimizes freely; it optimizes inside a certified envelope of states and actuator moves proven safe, which is the constraint set X_safe.

THE STACK · click to jumpL7Ecosystem & StrategyL6Experience & VisualizationL5Applications & CopilotsL4OrchestrationL3Twin Modeling & AIL2Data FabricL1Control PlaneL0Foundation▲tlmctl▼L3 · TWIN MODELING & AIThe KRONOS-CTRL digital twin and its predictive shadow.1KRONOS-CTRL Twinlive plant state2GNNscoupled subsystems3PINNsphysics-constrained4Anomaly Ensemblesdrift & fault detection5MPCreceding-horizon control6Predictive Shadowruns seconds aheadMACHINE TIEState estimate descends to L1 control; alerts rise to L4 / L5.KRONOS FUSION ENERGYAI-NATIVE S.M.A.R.T. GENERATORTWIN MODELING & AISHEET 05REV. 2026-08L3 · AI-NATIVE STACK
L3 · Twin Modeling & AI — its place in the stack (left, click any layer) and its internal components (right). Telemetry rises; control descends.

What the envelope is

The safe operating envelope is the region of state and actuator space in which the machine is known to operate safely. It is defined offline from physics limits and validated against simulation and (later) plant data: field and current limits, stability margins, thermal and strain limits, density limits, and the DEC operating range. MPC treats it as the hard constraint set X_safe; the optimizer may seek performance anywhere inside it but may never plan a trajectory that leaves it.

Envelope vs failsafe

The envelope and the L1 hardware failsafe are distinct and complementary. The envelope is a soft, model-based boundary MPC stays well inside; the failsafe is a hard, hardware-enforced trip that fires if physical thresholds are crossed regardless of any model. MPC's job is to make failsafe activation rare by keeping the machine comfortably within the envelope; the failsafe's job is to guarantee safety if MPC or its model is ever wrong.

The envelope has margins. Kronos does not let MPC ride the exact edge of a constraint, because model error and imputation uncertainty are real. When observability degrades (many imputed channels, low twin confidence), the effective envelope shrinks automatically, so the controller becomes more conservative exactly when it knows less. This uncertainty-aware tightening is a core safety property of the L3 design.

The envelope is machine-specific and phase-specific: a commissioning ramp uses a tighter envelope than a validated flat-top, and the envelope expands only as operation is proven, a deliberately conservative posture consistent with the design/simulation status of both machines before FOAK.

Content reviewed August 2026 · design-and-simulation stage