Redundancy Across a Fleet

Multiple breeder units provide redundancy: no single outage halts isotope supply, and aggregate production rate rises as units are added.

Why one machine is not resilience

A single production source, however capable, is a single point of failure. If it goes down, supply stops — and for decaying isotopes, inventory falls during the outage. Resilience requires more than one independent source, so that the loss of any one leaves the others still producing.

Redundancy plus rate

A fleet delivers two benefits at once. It raises the aggregate production rate, and it adds redundancy: with several units, one outage removes only part of the supply rather than all of it. For self-renewing isotope demand, this combination is what turns a demonstration into a dependable supply.

• Independent units: an outage removes part, not all, of supply.
• Aggregate rate scales with the number of units.
• Redundancy matters most for decaying isotopes.
• Follow-on units are intended to build faster.

Program staging

Redundancy for a decaying supply

Redundancy matters most precisely for the isotopes that decay. When a single source goes down, tritium inventory falls during the outage and helium-3 supply is pinched at the same time, so the loss compounds. A fleet of independent units means an outage removes only part of the supply rather than all of it, keeping make-up flowing while the affected unit recovers. This is why resilience is a property of the staged program rather than of any single machine, and why aggregate rate and outage tolerance are treated as goals that grow together as units are added.

This redundancy is a property of the staged FOAK-NOAK-BOAK program, not of a single machine. It is a forward-looking design attribute: FOAK must first prove the pathway (~2030) before follow-on units add the redundancy and rate that a resilient supply requires.