Gastronaut GASTRONAUT
Initializing Mission Systems
1,042 growth cycles
///
28 Scopus papers
///
+1.86 SD Nrf2 activation
///
$487B TAM by 2040
///
600d Mars-ready
← Environmental Control and Life Support
ECL-2 Gastronaut and ORCA Capability

Atmosphere Control as a Cultivation Capability

Nominal crop performance is the starting case. Mission relevance emerges when a cultivation module can detect a departure, protect its interfaces, recover control, and preserve enough evidence to...

Nominal crop performance is the starting case. Mission relevance emerges when a cultivation module can detect a departure, protect its interfaces, recover control, and preserve enough evidence to explain what occurred. Crop area and yield remain important, but the complete operational sequence establishes the result on which others may responsibly rely.

NASA needs observable fault behavior and testable module-habitat boundaries. Investors face a related question: does each development milestone reduce a named integration risk? Sensing, control authority, safe-state behavior, and recovery evidence make that reduction visible before claims about scale or autonomy. They also place technical progress within a record that can endure from one test campaign to the next.

The operational test

Acceptance requirements can be organized around sensing, environmental control, fault detection, safe state, recovery time, crew intervention, and data provenance. By characterizing its own environment, an enclosure preserves interpretability and supports the matched tests needed to identify what drove a biological outcome. This is both an engineering discipline and a duty of care toward the habitat with which the enclosure must share air, power, heat, water, and crew attention.

Gastronaut is developing ORCA as a 2.0 m diameter standalone modular cultivation enclosure. The operating concepts remain prospective. ORCA is approximately TRL 3 to 4 at the ground stage, with zero flight cycles and zero lunar cycles. Ground tests are required before those concepts can extend to flight or lunar use.

Four paths that control must cover

The Advanced Plant Habitat provides an environmental-control reference. Its architecture combines plant-environment control with active ethylene scrubbing (Monje et al. 2020). The lesson concerns the system boundary: atmosphere management and trace-gas control belong within the cultivation function.

Earlier potato flight work shows why local telemetry matters. Brown and colleagues reported 22 plus or minus 2 degrees Celsius, relative humidity of 81 plus or minus 7 percent, and light at 150 micromoles per square metre per second. Carbon dioxide exceeded 4,000 parts per million in darkness and was about 400 parts per million during the light period. Leaf senescence appeared after day 12 (Brown et al. 1997). These measurements place the crop observation within an environmental history. Assigning one condition as the cause would require a matched causal test.

The CEBAS program revealed a fault that crossed biological interfaces. Plant self-shadowing contributed to degradation, and the resulting microbial oxygen demand endangered animals in the coupled system (Blum 2004). This finding traces a propagation path from biomass condition through microbial response to atmosphere risk. A module would need to detect and contain that path; the record does not characterize biological integration as inherently unsafe.

Wetted surfaces provide another path. In a ground test, Obenhuber, Huff, and Rodgers found iodine at 1 to 2 milligrams per litre ineffective against the tested biofilm. Complete disinfection in that test required an initial concentration of 16 milligrams per litre (Obenhuber, Huff, and Rodgers 1991). This is a test-specific result, not a universal dosing rule. It shows that a control specification needs a named challenge, stated conditions, a response criterion, and a verified operating range.

International Space Station operational records offer a fourth lesson. They describe hardware degradation, modification, maintenance, and replacement of trace-contaminant beds. Those records support configuration and maintenance history as required data. They do not provide a general failure rate or predict the behavior of every cultivation module.

Make the fault observable

The operating chain begins at the scale experienced by the organism. Habitat atmosphere cannot stand in for leaf-level airflow, canopy carbon dioxide, or root-zone oxygenation. Local observation must be joined to sufficient actuator and control authority to hold defined bands under expected loads. Calibration state, set points, commands, maintenance, alarms, and environmental history then preserve the evidence. If control is lost, safe response and recovery become measurable events rather than undocumented interruptions.

That chain connects a crop result to its environment and a fault to a declared criterion. It also reveals detection time, recovery time, and crew intervention. With those links intact, nominal performance and sensor readings can contribute to a mission decision.

The reviewed environmental-control set is bounded. It assessed 249 records and classified 150 as analysable from 5,111 unique records. Full text was retrieved for 13 of 56 targets across human-flight, non-human-flight, and crewed-analog tiers, with no human-flight full text in that subset. The evidence can shape requirements and fault hypotheses. A pooled reliability value or a complete exploration cultivation architecture would require further evidence.

On the evidence now available, confidence is moderate that local telemetry, configuration history, and fault provenance are necessary for an interpretable cultivation test. Confidence is low for any estimate of ORCA reliability or recovery performance. A prespecified ground fault campaign with repeated exposures would raise it; unresolved sensor-actuator ambiguity would lower it. This calibration keeps the next test in service of the next decision.

An ORCA fault record

Prospective ORCA measurements would cover:

  • local carbon dioxide and ethylene concentrations;
  • humidity, temperature, oxygen, and airflow at defined chamber locations;
  • root-zone moisture, temperature, oxygenation, and flow suited to the cultivation method;
  • sensor calibration state, uncertainty, health status, and time synchronization;
  • timestamped set points, measurements, commands, alarms, maintenance actions, and configuration changes.

Control and fault-response evidence would cover:

  • control bands and excursion limits for each mission-relevant variable;
  • alerts that distinguish sensor failure, actuator failure, environmental drift, and biological load change where the evidence permits;
  • a safe shutdown state protecting crew, habitat, and retained biological material;
  • restart and recovery procedures with measured recovery time;
  • crew-intervention assumptions and data-capture requirements;
  • interface limits for atmosphere exchange, heat, moisture, power, contaminants, and waste streams.

These are design objectives, not demonstrated ORCA capabilities. Gastronaut’s internal record covers 1,042 ground growth cycles over 18 to 24 months. That history can inform fault selection and operating ranges. Flight, lunar, variable-gravity, reliability, biological-efficacy, and edited-line performance retain separate evidence status.

For NASA review, Gastronaut can provide a linked data dictionary, crop-readiness assessment, resource-accounting template, ground-validation plan, and ORCA operating-history structure. NASA has not validated these company materials. They can serve as working inputs for interface definition and consistent evidence capture, allowing each campaign to contribute to a continuous technical record.

Challenge the module before the mission does

Gastronaut proposes an interface workshop followed by a ground fault-injection demonstration. The workshop would select a reference chamber, locate the module-habitat boundaries, assign control responsibilities, and define acceptance thresholds. The demonstration would introduce a limited fault set, such as airflow loss, carbon-dioxide excursion, sensor drift, root-zone oxygen loss, or degradation of contaminant control.

The resulting package would record detection, control response, safe-state behavior, recovery, crew action, biological material lost or retained, and provenance completeness. NASA would receive an auditable basis for technical judgment. Investors would receive a milestone showing whether a named integration risk had fallen.

The operational question remains direct: can ORCA’s environmental architecture be challenged, observed, and recovered before it advances to a more demanding evaluation? A ground demonstration places that question where it can be resolved, while the system is still accessible and before a crew and mission are asked to depend upon the answer.

References

Blum, Volker. 2004. Advances in Space Research. https://doi.org/10.1016/S0273-1177(03)80015-7.

Brown, Christopher S., et al. “Potato Tuber Formation in the Spaceflight Environment.” 1997. https://doi.org/10.4271/961393.

Gastronaut. Environmental Control and Life Support: Evidence Synthesis. Evidence version frozen 21 Aug. 2026. Research synthesis.

Monje, Oscar, et al. 2020. Frontiers in Plant Science. https://doi.org/10.3389/fpls.2020.00673.

Obenhuber, Donald C., H. E. Huff, and E. B. Rodgers. 1991. https://doi.org/10.4271/911378.

Evidence boundary

This report separates established findings, Gastronaut's research synthesis, company assertions, and recommendations. Cited works remain attributed to their authors and publishers. ORCA is a ground-stage system at approximately TRL 3 to 4, with a documented ground operating record, no flight operating history, and no lunar operating history. Statements about ORCA capability are design objectives or proposed work unless a cited source establishes otherwise. Biological efficacy, flight qualification, NASA validation, and procurement remain future determinations.

Supports
  • Question 2: information, crew time, equipment, operations

Gastronaut welcomes a bounded technical exchange on the questions this report raises.

needtheinfo@gastronaut.earth