Interactive system-in-the-browser
Mission operations console
Flight-software state
BOOTHealth inputs
Adjust values, then advance a tickTelemetry timeline
Mode and fault state by tickEnd-to-end digital thread
From ground command to verified telemetry
The browser model follows the same documented boundaries: packet integrity, freshness and replay guard, authorization policy, semantic command processing, recovery supervision, FDIR, operational modes, telemetry, and event evidence.
- 8 stable operating modes
- 10 modeled fault dispositions
- 11 typed command outcomes
- 3 failed recovery exits before SAFE fallback
Provenance-bound results
Verification evidence
These are software-engineering results for the documented source, CI, and Raspberry Pi configurations. They do not establish certification, flight qualification, hard-real-time guarantees, production security, or defect absence.