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

Coordinating Twin & Copilot

Orchestration reconciles L3 twin predictions and L5 copilot proposals into a single bounded action, resolving disagreement conservatively.

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.

Two intelligences, one machine

The digital twin (L3) predicts machine state and consequences; the copilot (L5) proposes actions to achieve goals. Both are learned, both can be wrong, and they can disagree. Layer 4 is the arbiter: it consumes twin predictions and copilot proposals as events and produces at most one bounded command per actuator per step, or none.

Reconciliation policy

python
def reconcile(proposal, twin_pred):
    if proposal.confidence < CONF_MIN:      return route_to_human(proposal)
    if twin_pred.uncertainty > UNC_MAX:     return HOLD   # act only on trusted state
    if disagree(proposal, twin_pred):       return conservative_of(proposal, twin_pred)
    return proposal.command                 # still must pass rules + envelope

Conservatism on disagreement

When the copilot's expected outcome conflicts with the twin's prediction beyond a tolerance, orchestration chooses the more conservative action or holds. For the breeder, that biases toward staying inside the current operating point rather than pursuing a proposed higher-performance point on contested predictions. For the burner, it biases toward maintaining established plug confinement over an aggressive efficiency move.

Confidence and uncertainty are inputs, not authority

The gate is downstream

Reconciliation only selects a candidate command; it does not authorize it. The selected candidate still traverses the full gating pipeline: schema, rules, envelope, approval. This ordering means even a perfectly reconciled, high-confidence proposal is rejected if it would leave the safe region. Both machines remain design-and-simulation studies, so this coordination is exercised against replayed and simulated scenarios today.

Content reviewed August 2026 · design-and-simulation stage