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

The L1 Deterministic Reflex Loop

L1 is the hard real-time reflex tier: a fixed-latency sense-decide-actuate loop whose worst-case timing is proven, not measured after the fact.

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.

What the reflex loop is

The Kronos control stack separates intelligence from reflex. Learning-based control lives in L3 on a 50–100 ms predictive shadow; the reflex loop lives in L1 and runs on edge FPGAs with a fixed, provable cycle. Its job is to hold the breeder (Hyperion) and burner (Aegis / MetroVolt) inside a hardware-defined operating envelope regardless of what any model does or fails to do.

A reflex loop is a strict pipeline: acquire the validated state vector, evaluate bounded control laws and envelope checks, arbitrate the resulting commands, and gate them onto actuators. Every stage has a budgeted, bounded execution time. The pipeline is data-flow, not event-driven, so there is no queue whose depth can grow without bound.

Loop invariants

python
# The reflex cycle, conceptually: fixed work per tick, hard deadline
def reflex_tick(state, T_loop_s):
    x  = read_validated_state()      # bounded: fixed channel count
    u  = bounded_control_law(x)      # affine / lookup, no iteration
    u  = envelope_clamp(u, x)        # range + rate-of-change limits
    if not within_envelope(x):
        return drive_failsafe()      # single-cycle escape
    return gate_actuators(u)

# deadline == period: the loop must finish inside its own tick
assert wcet(reflex_tick) < T_loop_s

A useful mental model is that L1 is a governor, not a driver. It does not try to make the plasma perform; it makes sure the plasma cannot do anything the hardware cannot survive. Performance is the supervisory tier's problem and can be as clever as it likes, because it can only ever move setpoints inside a box L1 refuses to let it leave. That division is what keeps the reflex tier small, auditable, and stable across firmware and model changes above it.

The remainder of this category decomposes each element of that tick: the sub-10µs latency budget, the synchronized actuation gates, and the ML-independent failsafe that makes the whole design certifiable independent of the AI layers above it.

Content reviewed August 2026 · design-and-simulation stage