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

Phase-Locked Actuation Commit

When several actuators must move as one, Kronos uses a two-phase commit locked to a shared clock so the group either acts coherently or not at all.

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.

Coherent multi-actuator action

Some actions require several actuators to change together: a synchronized poloidal-field coil step for shape control, or a coordinated gas-and-pellet fueling event. If they act at slightly different times the transient can be worse than the steady state they aimed for. Kronos commits such groups with a phase-locked, two-phase protocol referenced to the distributed clock.

Prepare, then fire

python
def phase_locked_commit(actuators, fire_edge_ns, prepare_deadline_ns, now_ns):
    armed = [a for a in actuators if a.arm()]        # phase 1: prepare
    if len(armed) != len(actuators) or now_ns > prepare_deadline_ns:
        for a in armed: a.disarm()                   # atomic abort
        return 'aborted'
    for a in armed:
        a.schedule_fire(fire_edge_ns)                # phase 2: same edge
    return 'committed'

The protocol is all-or-nothing: a partial fire is never allowed, because a half-executed coordinated action is exactly the failure mode it exists to prevent. If the group aborts, each actuator holds its prior safe setpoint, which is always a defined, benign state.

The prepare-then-fire structure also gives the supervisory tier a clean failure signal: if a group repeatedly aborts because one actuator will not arm, that actuator is flagged for maintenance rather than silently degrading the coordinated action. Because the abort is atomic and the fallback is each actuator's prior safe setpoint, a chronically unready actuator reduces capability but never creates a hazardous partial action, which is exactly the property a coordinated fueling or coil step needs.

This is distinct from the general orchestration two-phase commit in L4; here the commit is bounded to a single clock window and carries a hard deadline, so it lives in the reflex tier. It builds directly on the synchronized actuation gates and the clock distribution described in the L1 control plane.

Content reviewed August 2026 · design-and-simulation stage