Space Protocol Conformance

make space-protocol-conformance-check is the bounded Phase S3 gate for

space protocol evidence. It validates the source-owned CCSDS, CFDP, TM/TC,

FDIR, time-kind, XTCE, and crypto review rows without running heavy release or

hardware gates.

This is local protocol conformance evidence for the checked 0x0 package

surfaces. It is not mission certification and it is not a claim that a

specific spacecraft protocol profile has been approved by an external

authority.

Evidence Files

• space/protocol-conformance.tsv records accepted and rejected CCSDS, CFDP,

and TM/TC cases with fixture paths, validation symbols, and evidence.

• space/tmtc-schemas.tsv records telemetry and telecommand schemas,

sequence-counter policy, time kind, checksum policy, authorization hook, and

XTCE names.

• space/fdir-primitives.tsv records deterministic FDIR primitives for

watchdog, heartbeat, timeout, mode guard, safe mode, retry budget, degraded

mode, and persistent fault log behavior.

• space/time-kinds.tsv distinguishes monotonic, mission elapsed, UTC, GPS,

and simulation time.

• space/protocol-fuzz-campaigns.tsv records bounded fuzz evidence for

external CCSDS, CFDP, and TM/TC parser inputs.

• space/xtce-exports.tsv records XTCE-compatible XML export rows generated

from the same TM/TC schema table used by code and tests.

• space/crypto-surface-review.tsv records crypto surfaces as wrappers around

reviewed providers. 0x0 does not invent mission cryptographic algorithms in

this evidence lane.

Requirements

• REQ-S3-001: telecommand handlers validate input before state mutation.
• REQ-S3-002: protocol parsers for external input have fuzz evidence.
• REQ-S3-003: FDIR actions are deterministic and traceable.
• REQ-S3-004: mission code distinguishes monotonic, mission elapsed, UTC,

GPS, and simulation time.

• REQ-S3-005: XTCE export is produced from the same schemas used by code and

tests.

Failure Behavior

The checker emits stable JSON diagnostics:

SPACE_PROTOCOL_MISSING   required table, document, fixture, or evidence file is missing
SPACE_PROTOCOL_SCHEMA    a protocol TSV has the wrong header
SPACE_PROTOCOL_CASE      protocol conformance rows are missing or incomplete
SPACE_PROTOCOL_STATUS    a conformance row is not accepted
SPACE_PROTOCOL_FIXTURE   JSON fixtures are malformed or status/protocol mismatched
SPACE_PROTOCOL_EVIDENCE  a referenced source symbol or evidence file is missing
SPACE_PROTOCOL_TMTC      TM/TC schema rows are invalid
SPACE_PROTOCOL_FDIR      FDIR primitive rows are invalid
SPACE_PROTOCOL_TIME      time-kind rows are invalid
SPACE_PROTOCOL_FUZZ      fuzz campaign rows are invalid or record crashes
SPACE_PROTOCOL_XTCE      XTCE exports are missing or do not match schemas
SPACE_PROTOCOL_CRYPTO    crypto surface review rows are invalid
SPACE_PROTOCOL_REQ       S3 requirement trace rows are missing or invalid
SPACE_PROTOCOL_DOC       public documentation is missing required S3 terms

Operational Boundary

S3 closes local conformance evidence for the current package surfaces. A

mission still has to provide mission-specific protocol tailoring, key custody,

operational authorization policy, and external assurance review for its own

deployment.