Fleet Feeds Fleet: The Coupled Readiness
Burner readiness and breeder readiness advance together, because each burner's fuel is bred by breeders that must be built first.
Two fleets, one clock
Burner deployment cannot outrun breeder deployment. Each burner runs on helium-3 bred by breeders, so a burner fleet requires a breeder fleet sized to feed it. The two readiness timelines are coupled, not independent.
How the coupling constrains dates
- A burner cannot start before breeder FOAK (~2030) makes fuel
- A commercial burner (~2036) needs breeder output at scale
- A burner fleet needs a breeder fleet, both maturing FOAK→NOAK→BOAK
- Lunar ³He enters only when burner demand exceeds the breeder fleet
Why this is the honest frame
Presenting the burner alone would hide its hardest dependency. The fuel gap (~400x per unit) is only closable through the breeder first and lunar recovery later. Coupled readiness is the truthful way to state the burner's timeline.
Coupling the two readiness timelines is not a complication we add; it is a fact we refuse to hide. A burner fleet cannot outrun the breeder fleet that fuels it, so the ~400x per-unit gap is only closable through breeders first and lunar recovery later. Presenting the burner's timeline any other way would omit its single hardest dependency and overstate how soon a fleet could exist.