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 › Security & Zero-Trust
Security & Zero-Trust

Threat Model: Attacking the Plasma-Control Loop

An attacker who reaches the fast control loop would try to drive the plasma off its operating point; layered identity, attestation, and an independent safety path deny that.

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.

The most consequential target

The L1 fast loop keeps the breeder plasma on its operating point - shape and vertical position at 9.66 MA with negative triangularity delta -0.30 - and manages the burner's mirror/plug regime. An attacker who could issue or alter commands here could attempt to induce a disruption, a vertical displacement event, or an off-normal excursion. This is the scenario the whole architecture is built to defeat.

Attack paths and denials

Timing as a defense and a constraint

The loop is deterministic and sub-millisecond; injected commands that violate timing or rate envelopes are anomalous and rejected. But the same timing budget forbids heavy per-cycle cryptography on the innermost loop, so integrity is enforced at configuration and identity time (attested firmware, authenticated bitstream) rather than by signing every cycle. This is an honest trade: the fast path trusts an attested, isolated FPGA rather than re-verifying each command.

python
# Command acceptance combines identity, rate envelope, and mode
def accept_cmd(cmd):
    if not verify_issuer(cmd):          return REJECT   # attested identity
    if not within_rate_envelope(cmd):    return REJECT   # physics-plausible
    if cmd.op not in mode_allowed(state): return REJECT  # legal in this mode
    return ACCEPT

Design status: these denials are validated against the digital twin and hardware-in-the-loop rigs, including simulated injection attacks. No live reactor plasma exists yet; the loop runs against simulated plasma models pending FOAK from Q2 2027.

Content reviewed August 2026 · design-and-simulation stage