Space Mission Validation

make space-mission-validation-check is the bounded Phase S6 gate for

mission-grade validation campaign evidence.

It does not run long-duration jobs or physical hardware jobs by default. It

validates source-owned campaign records, deterministic seeds, accepted hosted

evidence, negative tests, and fail-closed physical/HIL boundaries.

Campaign Families

The gate requires these campaign families:

• compiler and backend differential validation for the selected Flight Core

subset;

• protocol parser fuzzing for CCSDS, CFDP, and TM/TC inputs;
• deterministic fault injection;
• 72-hour hosted/twin soak telemetry;
• 24-hour physical-board soak when a physical target is claimed;
• HIL campaign definition covering debugger attach, reset, flash, telemetry,

watchdog, bus fault, storage fault, timing fault, and recovery;

• RTEMS, cFS, and OSAL interoperability readiness when a mission selects those

frameworks.

Deterministic Seeds

Fault injection rows in space/fault-injection-campaigns.tsv must use positive

numeric seeds. The fault report in

space/mission-validation/fault-injection-report.json must record each fault

kind with the same seed and recovered status.

The required fault classes are:

• dropped packet;
• delayed message;
• reset;
• clock drift;
• sensor bias;
• actuator saturation;
• memory corruption simulation;
• SEU-like transient fault.

Soak Evidence

space/mission-soak-campaigns.tsv records soak requirements.

The hosted/twin row must show a 72-hour hosted/twin soak with memory, timing,

fault, and health telemetry. The physical-board row must show a 24-hour

physical-board soak requirement and remain physical-gated until physical

hardware evidence is accepted.

HIL Boundary

space/hil-campaigns.tsv records required HIL steps. HIL rows remain

physical-gated unless make physical-hardware-evidence-check accepts real

target artifacts.

This lets the repository define the production HIL evidence shape without

claiming board execution from local source evidence alone.

Negative Tests

space/mission-negative-tests.tsv records negative tests and failure-mode

tests for protocol validation, strict replay time policy, certification support

claims, physical evidence intake, and HIL physical evidence boundaries.

Mission-Conditional Interop

space/mission-interop-readiness.tsv records RTEMS, cFS, and OSAL readiness

rows as mission-conditional. A mission that selects one of those frameworks

must supply target-specific integration evidence before claiming that surface.

Diagnostics

tools/space-mission-validation-check.py reports stable JSON diagnostics. See

docs/diagnostics.html for the diagnostic class list.