The Digital-Twin Fleet Registry

A registry holds a live twin for every unit, tagged by machine type, generation, and configuration, forming the addressable model of the whole fleet.

Every unit has a twin; the registry holds them all

Each Kronos unit runs its own L3 KRONOS-CTRL twin. The fleet registry is the L7 index of all of them: a directory that maps each unit to its live twin, its machine type (breeder or burner), its housing (Aegis or MetroVolt for burners), its generation (FOAK/NOAK/BOAK), and its configuration (for the breeder, the active TBR lever; for the burner, the plug operating point). The registry is how fleet-level services address individual units.

What the registry enables

• Discovery: which units exist, of what type and generation
• Addressing: route a coordination or learning action to the right twins
• Compatibility: match spares, models, and updates to a unit's configuration
• Rollup: aggregate state, forecast, and inventory across the fleet

# registry entry per unit
{
  'unit': 'metrovolt-noak-03',
  'type': 'burner', 'housing': 'MetroVolt',
  'generation': 'NOAK',
  'config': {'plug_field_T': 26.49, 'throat_field_T': 17.0,
             'neutron_fraction': 0.0544},
  'twin_endpoint': 'internal://twin/metrovolt-noak-03',
  'status': 'design-stage',        # -> commissioned at build-out
}

The registry is the join point for the other fleet services. Multi-unit coordination iterates the registry to read state and issue intents; fleet learning uses the type/generation/config tags to decide where a model update is compatible; spare-parts lifecycle uses configuration to match a spare to a unit. Without the registry, fleet-scale services would have no consistent way to know what they are acting on.

Configuration is part of identity because it changes physics. A breeder at TBR lever 1.8 breeds and consumes differently from one at 1.1; a burner at its nominal 26.49 T plug behaves differently from one de-rated for maintenance. The registry carries the active configuration so fleet decisions use each unit's true operating point, not a nominal one.

The registry today lists design-stage units backed by their twins in simulation. As units are built from Q2 2027 and commissioned from FOAK ~2030, their status advances in the registry, and fleet services extend to them automatically because they are already addressable.