The action is written down
A command arrives, the rover plans a drive, a battery reading is taken. Each becomes a receipt: what happened, who or what did it, under which mission intent, and when.
It is hashed canonically
The receipt is reduced to canonical bytes and hashed with SHA-256, so the same record always produces the same fingerprint on any machine.
It is signed twice
Ed25519 and ML-DSA-65 sign the same bytes, and both legs are required. PQ leg: ML-DSA-65 (FIPS 204) via the R-Series engine; software key custody; not flight-qualified.
It joins the chain
Each receipt names the hash of the one before it. Removing, reordering or editing a record breaks every link after it, visibly.
Anyone can check it, offline
A verifier needs the receipts and the public keys, nothing else: no network, no account, no trust in COSRYX. That is what makes it evidence rather than a log.