Why Breeder and Burner Straddle Defense
Kronos serves defense from two directions at once: the breeder as a strategic-isotope platform and the burner as a resilient on-site generator.
Two machines, two contributions
The defense value of Kronos does not come from one machine. The breeder (Hyperion) is a strategic-materials platform: it produces tritium, helium-3, and 14 MeV neutrons domestically, addressing the isotope half of energy security. The burner (Aegis / MetroVolt) is a resilient on-site generator concept, addressing the power half. Together they straddle both.
The two are linked by helium-3: the breeder produces it (design point ~1.97 kg/yr), and the burner consumes it. But the linkage is honest about scale: breeder-bred helium-3 supplies detection and technology markets, while burner-fleet fuel demand (~400x domestic supply) points to lunar helium-3. One machine's product is the other's fuel, at very different scales.
Different readiness, different gates
The breeder is nearer term: construction targeted Q2 2027, first tritium around 2030, with the tritium breeding ratio treated as a lever (1.1 / 1.5 / 1.8). The burner is further out, gated by plug-coil overstress (3-3.9x), an un-post-dictable regime (166-830x), the helium-3 fuel gap (~400x), and availability (0.86-0.995 vs 0.99982). Both are design-and-simulation studies; their defense contributions arrive on different timelines.
- Breeder = strategic-isotope platform (materials half)
- Burner = resilient on-site generator (power half)
- Linked by helium-3, at very different scales
- Breeder is nearer term; burner is further out and more gated
Because the two machines mature on different timelines, their defense contributions should be planned separately rather than as a single package. The breeder's isotope value is the nearer-term contribution, tied to its build starting Q2 2027 and first tritium around 2030. The burner's resilient-power value is the longer-horizon contribution, gated on physics and on lunar-scale helium-3. Treating them as one deliverable would obscure both timelines.
Design-and-simulation stage across both machines.