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 › L5 · Applications & Copilots
L5 · Applications & Copilots

Copilot Confidence and Uncertainty

Copilots report calibrated uncertainty drawn from twin UQ, retrieval quality, and self-consistency — so operators know how much to trust each answer.

THE STACK · click to jumpL7Ecosystem & StrategyL6Experience & VisualizationL5Applications & CopilotsL4OrchestrationL3Twin Modeling & AIL2Data FabricL1Control PlaneL0Foundation▲tlmctl▼L5 · APPLICATIONS & COPILOTSAgentic copilots that reason over the machine.1Plasma Copilotscenario design2Engineering Copilotsubsystem analysis3Operations Copilotrunbooks & procedures4Agentic Toolsbounded action-taking5Knowledge BaseRAG over the fabric6Guardrailssafety-boundedMACHINE TIEReads the twin and fabric; proposes actions that route through L4.KRONOS FUSION ENERGYAI-NATIVE S.M.A.R.T. GENERATORAPPLICATIONS & COPILOTSSHEET 07REV. 2026-08L5 · AI-NATIVE STACK
L5 · Applications & Copilots — its place in the stack (left, click any layer) and its internal components (right). Telemetry rises; control descends.

Uncertainty is part of the answer

A copilot answer without uncertainty is incomplete. Kronos copilots attach a calibrated confidence to every substantive claim and proposal, aggregated from three sources: the twin's own uncertainty quantification on any predicted quantity, the quality and agreement of the retrieved evidence, and the self-consistency of the copilot's reasoning across independent samples.

Sources of uncertainty

text
confidence(claim):
  u_twin  = twin.uq(claim.predicted_quantity)     # if physical
  u_ret   = retrieval_quality(claim.sources)      # score + agreement
  u_self  = self_consistency(claim, n_samples)    # trace agreement
  c = combine(u_twin, u_ret, u_self)
  return recalibrate(c)     # via reliability curve from golden set

Calibration, not vibes

Stated confidence is only useful if it is calibrated — if answers the copilot calls 90% confident are right about 90% of the time. Calibration is measured against the golden set: predicted confidence is binned against realized correctness to build a reliability curve, and a miscalibrated copilot's confidences are recalibrated or the release is blocked. The evaluation harness reports calibration error alongside correctness.

Confidence drives behavior, not just display. Low-confidence proposals are flagged for extra scrutiny in human oversight, and below a threshold the copilot refuses or escalates rather than answering. This links uncertainty directly to safety: the copilot is most cautious exactly where it knows least.

Physical uncertainty is inherited honestly from the twin rather than manufactured. Because both machines are pre-FOAK, the twin's own uncertainty is often wide, and the copilots reflect that width rather than projecting false precision — consistent with making no net-gain claim before the machine demonstrates it. See twin confidence scoring and uncertainty quantification.

Content reviewed August 2026 · design-and-simulation stage