Mars water: 98% recovery, storage, quality and make-up
This dossier treats survival as a measurable, maintainable architecture. It distinguishes performance demonstrated on the ISS, known human constraints, physical relationships and choices that remain prospective for a Mars base.
DEMONSTRATED / MEASUREDENGINEERINGSCENARIO
1. Read boundaries before percentages
This dossier treats survival as a measurable, maintainable architecture. It distinguishes performance demonstrated on the ISS, known human constraints, physical relationships and choices that remain prospective for a Mars base.
A recovery rate, filtration rate or endurance figure means little unless inputs, outputs, duration and system configuration are stated. NASA’s 98% milestone concerns overall water recovery in a demonstrated ECLSS configuration; it is not an overall habitat recycling rate.
Teaching functional architecture.
2. Water recovery: correctly understanding NASA’s 98% milestone
Question : What exactly does “98% recovery” mean, and what happens to the remaining 2%?
NASA announced in 2023 that the ISS ECLSS demonstrated the approximately 98% overall water-recovery goal with the Brine Processor Assembly. The number describes a system boundary and configuration; it does not mean “98% of everything is recycled,” nor that the remaining losses have the same origin in every architecture. For Mars, a recovery rate must be translated into make-up mass, storage, maintenance, water quality and degraded-mode capability.
Useful relation :R = m_récupérée / m_entrée × 100 ; m_perdue = m_entrée × (1 − R) R equals recovered mass divided by mass entering the chosen boundary times one hundred; loss equals input times one minus recovery expressed as a fraction.
The relation is then connected to sensors, thresholds, stocks, spares, power and intervention time. A survival function is an operational capability, not merely nominal performance.
3. Humidity, condensation and microbial control: keeping a habitat dry without over-drying it
Question : Why does water in cabin air become a thermal, health and materials problem?
Breathing, perspiration, hygiene, crops and processes add water vapor. If a surface falls below the dew point, water condenses; in a cold recess it can promote corrosion or microbial growth. Humidity control must therefore be tied to air circulation, heat exchangers, water recovery and inspection of surfaces and filters.
Useful relation :HR = p_v / p_sat(T) × 100 relative humidity RH equals water-vapor partial pressure p sub v divided by saturation vapor pressure at temperature T, times one hundred.
The relation is then connected to sensors, thresholds, stocks, spares, power and intervention time. A survival function is an operational capability, not merely nominal performance.
4. Survival budgets and endurance
Each scenario must translate system state into hours or days of survival, minimum consumption, make-up mass, backup power, heat rejection, pressurized volume and crew workload.
The rule is to preserve an evidence chain: requirement → measurement → threshold → action → backup resource → criterion for returning to a safe state.
5. Repairability and spares
A remote base must diagnose, disassemble, clean, replace, bypass and requalify critical elements. Maintenance is a mission function consuming time, space, tools and consumables.
The rule is to preserve an evidence chain: requirement → measurement → threshold → action → backup resource → criterion for returning to a safe state.
6. Human factors
A poorly designed alarm, procedure or refuge can turn a recoverable hardware failure into a crisis. Interfaces must remain readable under stress, roles rehearsed and priority decisions explicit.
The rule is to preserve an evidence chain: requirement → measurement → threshold → action → backup resource → criterion for returning to a safe state.
7. Multiple failures
Analysis does not stop at one failure. Common causes and credible combinations are sought: power loss during a leak, dust during maintenance, fire in a compartment with an unavailable sensor, or a solar event during EVA.
The rule is to preserve an evidence chain: requirement → measurement → threshold → action → backup resource → criterion for returning to a safe state.
Reference architecture and boundaries
The dossier “Mars water: 98% recovery, storage, quality and make-up” should be read as a functional architecture, not a frozen blueprint. Start by drawing boundaries: main habitat, refuge, airlock, storage, local production, discharges, outside environment and interfaces with rover or lander. For each boundary, record mass, energy, heat and information flows. This prevents double counting: the same recovered water cannot be counted both as new inventory and local production. It also exposes hidden dependencies, such as a water pump that depends on cooling or a vital sensor sharing power with a non-vital load.
Size for the mission, not for one nominal day
Requirements must be evaluated over different horizons: seconds for depressurization, minutes for fire, hours for ventilation loss, days for water-recovery failure, months for wear and years for logistics. Separate average use from peak demand, nominal operation from survival. Buffers buy time but add mass; redundancy improves availability but requires maintenance and spares. Sizing is therefore a constrained optimization where the primary value is not instantaneous efficiency but staying inside a habitable envelope through credible deviations.
Measurement plan and system health
A durable base must know it is drifting before it reaches failure. Critical quantities are therefore tracked as trends: pressure, gas concentrations, humidity, temperatures, flow rates, water quality, filter pressure drop, battery state, consumables, radiation dose and crew health. Fixed alarms are complemented by consistency checks. Slow degradation can be more dangerous than a clean failure because it consumes margin gradually. Machine and crew logs are correlated so a symptom can be linked to maintenance, a consumable batch or a configuration change.
Maintenance as a survival resource
Maintenance procedures must be tested with real access, tools and protective equipment. Time to diagnose, isolate, repair and return to service is measured. Some tasks require bypassing a loop or temporarily consolidating the crew into a smaller volume; that transition must be designed. Spares are selected by criticality, failure likelihood, mass and potential for local fabrication or repair. A pile of spare parts without knowledge, documentation and test equipment is false redundancy. Modular, instrumented architecture can reduce the amount of backup hardware required.
Consumables and Mars logistics
Loop closure never removes logistics completely. Even with very high water recovery there are losses, filters, membranes, reagents, medical supplies, food and wear parts. Each daily loss is converted into mass for the interval between logistics opportunities and then given margin. Consumables can also be safety resources: water, food or gas may contribute to refuge or shielding. Good architecture seeks multiple uses without creating a dangerous dependency where spending a resource on one function deprives another vital function.
Emergency decision tree
An emergency should be manageable through a simple chain: detect, confirm, protect crew, stabilize, isolate, conserve resources, diagnose, repair, then requalify. In the first minutes, priorities are not global efficiency but pressure, breathable atmosphere, fire, temperature and medical capability. Once stable, functions can be restored progressively. Procedures include likely errors: wrong valve, bad sensor, interrupted communications or unavailable crewmember. Training is used to discover these traps before Mars.
From ISS to Mars: what truly changes
ISS has logistics, near-continuous ground support and a return path to Earth on a scale unavailable on Mars. Mars therefore needs more autonomy, storage, local diagnosis and repair. Dust and surface operations add contamination; EVA becomes routine logistics; communications delay prevents real-time medical or technical control from Earth. ISS heritage should be treated as evidence for components and behavior, not automatic proof of a Mars base. Ground and analog tests must reproduce duration, maintenance and failures, not only nominal performance.
Open questions retained in the Bible
A real reference preserves unknowns. What degree of loop closure truly maximizes reliability once maintenance is counted? What habitat atmosphere best trades physiology, fire safety and EVA preparation? How much shielding is optimal when water and consumables can be moved? What fraction of food should come from crops without making survival depend on one harvest? What medical autonomy is realistic for the crew size? These questions do not weaken the dossier; they identify exactly where research, testing and mission decisions still have to advance.
Worked mission-budget example — teaching only
Assume a subsystem has 600 usable units in stock and consumes 20 units per day in nominal mode. Raw endurance is 600 ÷ 20 = 30 days. If survival mode reduces use to 12 units per day, the same reserve represents 50 days. This calculation defines no real architecture; it illustrates how a mode change converts stock into time. Next remove unusable volume, reserves inaccessible after the failure and safety margin. The result is operational endurance, always accompanied by its assumptions.
Compare architectures without hiding tradeoffs
Option A may maximize loop closure but require more pumps, membranes and maintenance. Option B may lose more consumables but be easier to repair. Option C may physically separate two half-capacity trains to limit common causes. Compare them with the same criteria: launched mass, energy, heat, volume, noise, crew work, spares, time to maintenance, contamination tolerance and behavior after storage. The highest nominal efficiency is therefore not automatically the best mission solution.
Test campaign before departure
Qualification should progress from component to complete loop and then to crew scenario. First characterize performance and physical limits. Add endurance, cycling, relevant dust or contamination, temperature variation, power failures and failed sensors. Then couple multiple subsystems to observe interactions. Finally, crews execute maintenance and emergencies with real documentation. The expected result is not merely “the hardware works,” but “the crew can detect, understand, isolate, repair and return to a safe state within the available time.”
Crew organization and decision authority
A Mars base must state who decides during an alarm: onboard automation, watch officer, commander, physician or subsystem specialist. Authority can vary by emergency. Short procedures protect the first minutes; detailed procedures take over afterward. Two-person verification is reserved for actions where an error could worsen the crisis, because requiring two people for every action would unnecessarily slow operations. Simulations calibrate this human-control level and identify where automation must act immediately.
Logistics, spares and local fabrication
Spares should be analyzed by function, not only commercial part number. A motor, valve, sensor or electronic board may share subcomponents across systems when interfaces are standardized. Some parts may be fabricated locally, but a printed part is not automatically qualified for pressure, oxygen or medical service. Repair documentation therefore distinguishes certified critical parts, repairable items, consumables, raw materials and parts that can be locally produced after inspection. Standardization then becomes a resilience multiplier.
Combined-failure matrix
Build a matrix crossing power, cooling, atmosphere, water, communications, fire, pressure, EVA, medicine and crew. For each pair, ask whether a common cause exists and whether the refuge remains viable. Power loss can stop pumps and ventilation; a leak can consume reserves while forcing an EVA repair; contamination can remove one loop while its backup is under maintenance. Impossible or extremely unlikely combinations are documented as such, while credible combinations feed drills and stock sizing.
Criteria for closing the dossier
A chapter is mature only when assumptions, data and unknowns are separated. Demonstrated performance has a source and configuration; teaching scenarios are explicitly labelled; architecture decisions state rationale and budget impacts; risks have detection and recovery methods; unresolved points remain visible. This discipline allows the Mars Bible to evolve without turning an old assumption into “truth” simply because it has been copied many times.
