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 › Real-Time Control & Safety
Real-Time Control & Safety

Defining the Fail-Safe State

A trip is only as good as the state it trips to; each machine has an explicitly defined, benign resting state that every failsafe path drives toward.

STRATEGY / SLOW ▲ ▼ MICROSECOND REAL-TIMEL7Ecosystem & Strategytelemetry ▲ control ▼open ▸L6Experience & Visualizationtelemetry ▲ control ▼open ▸L5Applications & Copilotstelemetry ▲ control ▼open ▸L4Orchestrationtelemetry ▲ control ▼open ▸L3Twin Modeling & AItelemetry ▲ control ▼open ▸L2Data Fabrictelemetry ▲ control ▼open ▸L1Control Planetelemetry ▲ control ▼open ▸L0Foundationtelemetry ▲ control ▼open ▸PHYSICAL S.M.A.R.T. GENERATOR PLANTBREEDER · HYPERION1R0 1.2 m · A 2.5 · 16.84 T · δ −0.30BURNER · TANDEM MIRROR2317 T throat · 26.49 T plug · fₙ 5.44% · DEC1 center stack + plasma · 2 high-field plug · 3 expander → direct converterCOLOR GRAMMAR strategy AI-workflow infra/data models reactor/DECLINE SEMANTICStelemetry (µs)controlKRONOS FUSION ENERGYAI-NATIVE S.M.A.R.T. GENERATORMASTER BLUEPRINTSHEET 01REV. 2026-08L0-L7 · 2 MACHINES
The AI-Native S.M.A.R.T. Generator Master Blueprint — eight layers (L0→L7), one control stack, wired to both machines. Telemetry rises in microseconds; control descends the same path.

Safe is a place, not an absence

Cutting power is not automatically safe. A safe state is a specific, defined configuration where stored energy is being removed in a controlled way and no protected limit is being approached. Kronos defines the safe state per machine and per subsystem, and every failsafe path is designed to reach that defined state, not merely to stop.

Breeder safe state

Burner safe state

python
def safe_state_reached(machine_state, limits):
    # all monitored quantities inside their benign holding band
    return all(limits[k].lo <= machine_state[k] <= limits[k].hi
               for k in limits) and machine_state['stored_energy_falling']

Defining the safe state per subsystem also disciplines recovery. Because the resting configuration is explicit, the path back to operation is a checked sequence from a known state rather than an improvisation from wherever the trip left things. Operators and the supervisory tier both reason against the same defined state, which removes a whole class of restart hazards where a machine is brought up from an ambiguous, partially-tripped configuration whose stored energy and interlock status are not fully known.

For fast-growing faults, reaching the ideal safe state may be impossible in the available time; then the failsafe drives to the least-unsafe reachable state and hands off to mitigation. That trade — ideal versus reachable — is decided in advance per fault, not improvised. See the failure response decision table and this page's companion on magnet energy extraction.

Content reviewed August 2026 · design-and-simulation stage