Normative requirements
What conforming mission design must express.
Every standard record publish code, version, status, canonical URL, summary, requirements, related records, and research links.
Breaking changes increment the major version and retain the superseded public record.
Current, guidance, experimental, planned, and retired states remain visibly distinct.
Mission implementations attach validation evidence and telemetry before claiming conformance.
Publish machine-readable catalogs, schemas, examples, and discovery manifests beside human-readable pages.
Mission lifecycle fit
Where this record applies.
This list identifies the mission stages where the record is most likely to be implemented or reviewed. It does not prevent the requirement from influencing adjacent phases.
Search and implementation terms
Vocabulary carried by this record.
Supporting research
Deep links into the complete report archive.
The canonical record stays concise. These links preserve the longer argument, design context, limitations, and source lineage in the `/docs/` archive.
