The health loop continues without Earth
Offline-First Architecture
Communication delays to Mars can reach many minutes each way, with blackouts. The platform is designed so capture, display, interpretation and protocol guidance keep working locally and synchronize later.
Why it matters for long-duration spaceflight
- Real-time ground support is not possible on deep-space missions.
- Losing data during an outage would break personal baselines.
- Duplicate or conflicting records after reconnection must be resolved predictably.
How The Mitochondria addresses it
- AES-GCM encrypted events in IndexedDB with a non-extractable device-local key.
- Append-only mission-health events; conflicting reuse of an identity fails closed.
- A versioned protocol cache with SHA-256 integrity metadata.
- A store-and-forward queue with idempotency keys and deterministic conflict resolution.
Architecture diagram
- 01Local capture
- 02Encrypted local store
- 03Store-and-forward queue
- 04Authorized ground sync
Technical explanation
Service worker scope
The service worker caches the public application shell and assets only. It never caches health API responses.
Conflict resolution
Conflicts resolve by payload identity, source version, event time and source priority; ambiguous ties require manual review.
Implementation status and limitations
- Implemented in repository
Encrypted local store, protocol cache, sync queue and the Offline Mission Mode status page are implemented.
- Partially implemented
Offline OCR readiness is not claimed until real-device airplane-mode testing is completed.
- Not clinically or flight validated
Browser storage is not flight-qualified storage.
Known limitations
- Browser storage can be cleared by the user or operating system.
- Measured latency is environment-specific engineering evidence.
The Mitochondria is human decision support. It does not diagnose, prescribe treatment or replace qualified medical judgment.