Idea
Count independent ways to keep working
Two systems can look safer than one while sharing the same point of failure. A pair of computers connected to one failed power supply cannot cover for each other. Useful redundancy therefore asks a more demanding question than how many components are installed: which functions remain available after a specific fault?
Apollo 13 made that question concrete. The lunar module carried resources for a different phase of the mission. After the service module accident, it could provide a refuge. Yet spare supplies did not automatically fit the new job. The crew and ground teams had to connect available capacity to urgent needs.
A spare is useful only if it survives and fits.
Test the backup against the failure you actually need it to cover.
Where it breaks down
Extra systems add weight, cost, and complexity. They can introduce new failure paths, and independence is always relative to a particular threat. Redundancy helps preserve a function; it cannot guarantee that the original mission remains achievable.
How it connects
Independent resources matter only when they can serve the missing function.
This idea appeared in The spare that can actually help, the Involves connection for September 15, 2026, which asked: When does having more than one system make you safer?
Check yourself
Why is counting spare parts insufficient?
The parts must survive the fault and provide the required function. Exactly. Availability and compatibility determine whether extra capacity is usable.
What the sources establish
Compatibility and surviving capacity determine whether a backup can supply the needed function.
Sources
Apollo 13 Lunar Module Mail Box (NASA), Description of the improvised carbon dioxide removal arrangement
Apollo 13 Review Board Report, Appendices B–E (NASA), Lunar Module Lifeboat: interchange of oxygen, water, power, and canisters