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

Reflex and Supervisory Tier Separation

Intelligence proposes on a slow horizon; reflex disposes on a fast one. Keeping these tiers physically separate is what lets the safety case ignore the AI entirely.

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.

Two clocks, two mandates

Kronos runs two control mandates on two different clocks. The supervisory tier (L3 model-predictive control, twin-informed optimization) plans setpoint trajectories on a 50–100 ms horizon. The reflex tier (L1) enforces safety on a microsecond-to-millisecond horizon. The reflex tier never waits on the supervisory tier and never trusts it beyond a clamped setpoint.

What crosses the boundary

DirectionPayloadTrust level
L3 to L1clamped setpoint + validityadvisory, re-checked
L1 to L3validated state + gate statusauthoritative
L1 internalfailsafe triggerauthoritative, immediate

Setpoints from above are treated as suggestions until L1 re-validates them against the live envelope. If the supervisory link goes silent, stale, or produces an out-of-envelope value, L1 falls back to a safe holding law without any supervisory input at all. This is the property that lets the failsafe be certified independently — see the ML-independent failsafe.

python
def accept_setpoint(sp, live_envelope, age_ms, max_age_ms=150):
    if age_ms > max_age_ms:
        return holding_law()             # stale supervisory link
    if not live_envelope.contains(sp):
        return live_envelope.clamp(sp)   # trust, but verify + clamp
    return sp

The boundary is also a security boundary. Because the reflex tier accepts only clamped setpoints and never executable logic from above, a compromised supervisory node cannot induce an unsafe action — the worst it can do is propose values that L1 clamps or rejects, or fall silent, which triggers the holding law. Keeping the fast path free of any interpreter, script, or model weight means the certified safety behavior does not change when the software above it is updated, attacked, or replaced.

The separation is not only logical but physical: distinct compute (FPGA vs GPU/CPU), distinct networks, distinct power and clock domains. A fault that takes out the intelligence tier cannot propagate into the reflex tier, and the reflex tier can hold the machine safe with the intelligence tier entirely dark. Compare defense-in-depth layering.

Content reviewed August 2026 · design-and-simulation stage