Cross-Machine and Fleet View
A single surface to supervise more than one machine at once — breeder and burner side by side, and multiple units of a kind — without diluting per-machine depth.
Supervising more than one machine
Kronos operates one architecture across two machine types, and units of each kind follow (breeder first-of-a-kind, then next-of-a-kind and beyond). Operators and engineers will need to watch several at once. The fleet view presents a compact health row per machine — the essential KPIs, the worst active alert, and confidence — so a supervisor sees the state of everything at a glance and drills into any one machine for full depth.
Comparable, not identical
The breeder and burner have different physics, so the fleet row shows each machine's own most-decision-relevant indicators (breeder: shape fidelity, disruption risk, Q_sci vs 3.076; burner: plug-density balance, potential-well depth, DEC stability) under a common health summary. Same-type units are directly comparable, which is how a supervisor spots that one breeder unit is drifting relative to its siblings — an early, cheap signal.
- Per machine: health summary, top KPI set, worst active alert, confidence
- Breeder rows: shape/disruption/performance indicators
- Burner rows: plug/potential/DEC indicators
- Cross-unit comparison to surface a single drifting unit early
- One click to the full single-machine control view
Attention routing across the fleet
With several machines in view, attention discipline matters even more. The fleet view ranks machines by triage score so the one that most needs attention rises to the top, and it never lets a fleet overview replace per-machine authority: control of any machine still happens in that machine's control room, with its own crew and its own L1 failsafe. The fleet surface is supervisory awareness, not remote control.
The fleet view is the multi-machine expression of the dashboards and shares the ranking logic of the triage stream. It is honest about status the same way single-machine surfaces are — units still in design and simulation are labeled as such, and no cross-fleet net-gain claim is made before the breeder FOAK (~2030).