The command is formed and receipted on the ground.
Mission-operations software forms a telecommand. The receipt is minted where the command is formed: who authorised it (two-person authorisation), under which key and key epoch, and exactly which bytes were sent.
- Signing keys for the mission stay on the ground.
- The receipt wraps the mission stack; it replaces nothing in it.
The existing link security carries the frames.
Fielded command links protect each frame with symmetric authentication under the CCSDS Space Data Link Security protocol. ORBIT leaves that alone and binds the receipt to the link's sequence count.
- No stateful signer on board.
- On board: hash commitments and a sealed, chained recorder.
The acknowledgement closes the loop.
The spacecraft's acknowledgement telemetry comes down and is bound to the same receipt, so the record shows what was sent and what the asset reported back.
Anyone with the spec can check it later.
A verifier rebuilt from the published specification and test vectors checks the hybrid signatures, the sequence binding, the acknowledgement and the key epoch, with DCS servers switched off.