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 › MLOps & Learning
MLOps & Learning

Offline Batch RL from Logged Pulses

Control policies are learned from the logged L0 pulse archive using conservative offline RL, never by exploring on the live machine, where exploration is a fault.

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.

No exploration on hardware

Classical reinforcement learning explores by trying actions and observing outcomes. On a fusion machine, an exploratory action is a candidate disruption or a coil overstress. Kronos therefore uses offline RL exclusively: policies are learned from the fixed dataset of logged breeder and burner pulses, plus twin-generated rollouts, with no live exploration whatsoever.

Offline RL has a characteristic hazard: the policy can favor actions that are rare or absent in the data, where value estimates are unfounded optimism. Kronos uses conservative algorithms (such as CQL and implicit-Q-learning style objectives) that penalize out-of-distribution actions, keeping the learned policy near the support of the logged behavior. The policy is pulled toward what has actually been observed to be safe.

Offline-RL safeguards

python
# Conservative Q-learning objective (schematic)
# minimize TD error + push down Q on OOD actions,
# pull up Q on actions actually seen in the dataset
L = td_error(Q, batch) \
  + alpha * (logsumexp(Q(s, all_actions))         # OOD penalty
             - Q(s, batch.action).mean())         # in-data bonus
# policy stays within logged support -> safe to evaluate

Offline RL is where preference-shaped rewards from control-policy RLHF are actually optimized into a policy. Everything learned here is evaluated first on the twin, then walked through the same validation and canary chain as any controller. The dataset it learns from carries the full data lineage, so the provenance of a learned policy reaches back to specific pulses.

Content reviewed August 2026 · design-and-simulation stage