Space Mission Operations
make space-mission-ops-check is the bounded Phase S7 gate for mission
ecosystem operations evidence.
It validates source-owned operations policy rows, offline release bundle
evidence, dependency controls, compatibility windows, advisory workflow, and
operator training links.
Policy Set
space/mission-ops-policies.tsv records the required mission operations
policies:
- LTS branch policy;
- security update policy;
- deprecation policy;
- migration policy;
- signing key custody policy;
- offline release bundle policy;
- dependency policy;
- vulnerability disclosure policy.
Each policy points to a versioned document under docs/mission-ops/.
Offline Release Bundle
space/offline-release-bundles.tsv records the sample mission offline release
bundle. The row requires:
- compiler input;
- documentation;
- package cache;
- SBOM;
- provenance;
- evidence schemas;
- operator runbooks;
- frozen lockfile;
- no-network build report.
space/mission-ops/offline-build-report.json records that the sample bundle is
offline and has network access disabled.
Dependency Policy
space/mission-dependency-policy.tsv requires vendored dependencies, frozen
lockfiles, banned build scripts, no network during flight builds, reviewed code
generation, and a source-owned package cache for Flight Core, Flight Extended,
and Ground/Twin profiles.
Compatibility Windows
space/mission-compatibility-windows.tsv records LTS windows and compatibility
gates for the Flight Core profile, package registry, and runtime capability
boundary. Breaking changes must pass the named gates before a frozen profile is
updated.
Advisory Workflow
space/mission-advisory-workflow.tsv records the vulnerability disclosure,
severity, key rotation, revocation, recovery, regression evidence, and
publication workflow for mission users.
Training
space/mission-training-onboarding.tsv links operator, release manager,
security officer, and hardware custodian roles to current runbooks and evidence
review docs.
Diagnostics
tools/space-mission-ops-check.py reports stable JSON diagnostics. See
docs/diagnostics.html for the diagnostic class list.