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 › L4 · Orchestration
L4 · Orchestration

Saga & Compensation

Long machine procedures cannot hold a single lock; sagas break them into steps each paired with a compensating action that undoes it safely.

THE STACK · click to jumpL7Ecosystem & StrategyL6Experience & VisualizationL5Applications & CopilotsL4OrchestrationL3Twin Modeling & AIL2Data FabricL1Control PlaneL0Foundation▲tlmctl▼L4 · ORCHESTRATIONEvents, workflows, rules, and human routing.1Event Streamingthe backbone2Workflow Enginecampaign procedures3Rules & Safety Boundshard limits4Human-in-the-Loopapproval routing5Schedulerexperiment campaigns6Audit Busfull decision lineageMACHINE TIECoordinates L3 outputs with L5 copilots and human operators.KRONOS FUSION ENERGYAI-NATIVE S.M.A.R.T. GENERATORORCHESTRATIONSHEET 06REV. 2026-08L4 · AI-NATIVE STACK
L4 · Orchestration — its place in the stack (left, click any layer) and its internal components (right). Telemetry rises; control descends.

No global transaction on a tokamak

A breeder shot touches vacuum, magnets, fuelling, and heating across seconds; a burner startup spans minutes. You cannot wrap that in one database transaction. The saga pattern instead sequences local, individually-committed steps and pairs each with a compensation that returns the machine toward safety if a later step fails.

Forward and compensating steps

python
saga = [
  step(pumpdown,     compensate=vent_to_holding),
  step(field_ramp,   compensate=field_deenergize),
  step(fuelling,     compensate=stop_gas_and_pump),
  step(heating,      compensate=heating_off),
]
# on failure at step k: run compensations k-1..0 in REVERSE order
# each compensation is idempotent and itself safety-bounded

Compensation is not naive rollback

A compensation is a forward action chosen for safety, not a literal undo. You cannot un-inject neutrons or un-heat a plasma; the compensating action for heating is a controlled ramp-down, and for field it is a rate-limited de-energize that respects magnet slew limits. Every compensation is itself checked against the safety envelope and is idempotent so a retried rollback does not overshoot.

Ordering and partial failure

Burner long procedures

The burner (Aegis / MetroVolt) targets steady state, so its sagas are long-lived: a plug-field establishment saga may run for minutes with compensations that gracefully bleed the 26.49 T plug field back down if throat confinement at 17 T is not achieved. The saga state is persisted continuously so a supervisor restart resumes mid-procedure; see checkpointing.

Sagas coordinate with the two-phase action commit for the small number of steps that must be all-or-nothing across two coupled actuators.

Content reviewed August 2026 · design-and-simulation stage