Layered, vendor-neutral design
System Architecture
The Mitochondria separates what a health signal means from how it arrives and how it is displayed. Each layer depends only on the layer below it, so devices, transports and interfaces can change without rewriting scientific meaning.
Why it matters for long-duration spaceflight
- Long-duration missions outlive individual devices and vendors; health meaning must survive hardware changes.
- Crews cannot rely on a cloud round trip, so the critical sensor-to-astronaut path must run locally.
- Reviewers need to trace any displayed value back through a stable, inspectable chain.
How The Mitochondria addresses it
- Routes and components present results but never own sensor normalization, thresholds or alert reasoning.
- The domain layer holds the reviewed metric registry, baselines, health intelligence and action guidance.
- Integrations (device SDK, wearables, laboratory, environment) translate external data into the canonical model.
- Infrastructure owns configuration, encrypted local storage, synchronization and the canonical-origin rule.
Architecture diagram
- 01Routes & screens
- 02Application workflows
- 03Domain (canonical meaning)
- 04Integrations & infrastructure
Technical explanation
Dependency direction
Code flows routes → components → application → domain → integrations/infrastructure. The domain stays independent of any concrete provider, persistence schema or transport.
Local critical path
Live observations reach the astronaut interface directly from local adapters. Cloud persistence sits behind a transport contract and is never required to display a reading.
Governed safety separation
Deterministic reviewed rules are kept apart from experimental analytics. Research-only relationships cannot produce operational actions.
Implementation status and limitations
- Implemented in repository
Layer boundaries, domain registry, adapters, local runtime and mission-scoped backend exist in the repository.
- Not clinically or flight validated
The system is a challenge prototype; it is not a certified medical device or flight-qualified software.
Known limitations
- The dependency direction is an enforced convention and review rule, not a compiler-enforced module boundary.
- No autonomous diagnosis, treatment or flight-rule decision is part of the architecture.
The Mitochondria is human decision support. It does not diagnose, prescribe treatment or replace qualified medical judgment.