COSRYX V2 · Mission Recorder · Status as of 21 October 2026

The mission black box, distributed.

COSRYX V2 keeps the last verified state, decision history, command lineage and failure evidence of a spacecraft, rover or satellite, even when its link is down. Code-complete and simulation-validated; not yet flown.

Gates G0 + G1Complete
Integrated tests410 / 410 · C0–C9 GO
Manifest entries5,447 / 5,447
G2–G7Pending
01 What it is

When a mission goes quiet, the record should not.

An aircraft flight recorder exists because the most important evidence is produced in the moments nobody is watching. Spacecraft and rovers face the same problem at a larger distance: long silences, delayed links and, sometimes, no recovery at all.

COSRYX V2 is a verifiable mission recorder. Every command received, every decision taken on board and every health reading becomes a sealed, chained receipt. Copies live on the vehicle, at the relay and on the ground, so no single loss erases the record.

Because each record is signed and chained, an investigator, insurer or partner agency can check the record themselves instead of relying on the operator's summary.

02 What it records

Four kinds of record, one chain.

CMD

Commands

Every command received, who signed it, and whether it was accepted, refused or deferred. The full lineage from ground to execution.

DECISION

Autonomous decisions

What the vehicle chose on its own, the signed intent that allowed it, and the inputs it saw at the time.

HEALTH

Health

Subsystem state for power, thermal, communications, mobility, compute and instruments. See Mission Health.

FAULT

Faults and recovery

What failed, what was quarantined, and what the vehicle did next. The record of a bad day is the most valuable one.

03 The gate ladder

Eight gates. Two closed, six open.

Gates, not dates. G0 and G1 are within DCS's control and are complete. G2 to G7 need outside parties, hardware or missions, and are pending.

G0Scope, IP and evidence freezeComplete
G1V2 codebase completeComplete
G2External security and cryptographic auditAudit not completed
G3Radiation and target-hardware testingPlanning · next
G4Hardware-in-the-loop telemetryPlanning
G5LEO shadow on a hosted payloadPlanning
G6Lunar bounded autonomyFuture direction
G7Mars and mission-critical acceptanceFuture direction
Gate ladder01 / 08
G0 · COMPLETE

Scope, IP and evidence freeze

What V2 is, what it owns and what counts as evidence were fixed before the build was judged, so the goalposts could not move afterwards.

G1 · COMPLETE

V2 codebase complete

All ten code gates C0–C9 returned GO. 410 of 410 integrated tests pass, and 5,447 of 5,447 manifest entries reproduce exactly. The final release candidate is frozen.

G2 · PENDING

External security and cryptographic audit

An independent firm reviews the code and the cryptography. The process has been initiated; the audit is not completed.

G3 · NEXT

Radiation and target hardware

The recorder runs on representative hardware under radiation, to see how it detects and contains bit upsets for real. This is the next step on the roadmap. It has not been done.

G4 · PENDING

Hardware-in-the-loop

Live telemetry from real flight-like hardware drives the recorder on the bench, with faults injected on purpose.

G5 · PENDING

LEO shadow

The recorder runs alongside a real mission in low Earth orbit, recording in parallel without being in control of anything.

G6 · PENDING

Lunar bounded autonomy

Bounded autonomous decisions recorded and verified in a lunar setting.

G7 · PENDING

Mars and mission-critical acceptance

Acceptance by a mission owner for mission-critical use. The final gate, and the furthest away.

04 What G0 and G1 mean, exactly

Internal gates, closed with evidence.

C0–C9all ten code gates returned GOG1
410/410integrated tests passing for COSRYX V2G1
5,447of 5,447 manifest entries reproduced exactlyG0 + G1
677RC3 internal security-gate checks, 677 of 677 passingFreeze complete

These are internal, DCS-controlled results. They are not an external audit, and they say nothing about flight qualification. The 410 integrated tests are a separate population from the 692 product tests and the 677 RC3 checks.

05 Founder feature · Store, seal, forward

Link lost for months. Nothing lost.

If contact with a rover is lost for three or four months, it keeps recording everything with sealed, chained receipts on board. When contact returns, the backlog goes to the nearest orbiter it has a relay agreement with, and on to Earth.

Store · seal · forward01 / 04
01 · NORMAL CONTACT

Records flow as they are made

While the link is up, receipts reach Earth in the normal course of passes and relays.

02 · LINK LOST

Keep recording, keep sealing

Contact drops: a dust storm, a fault, solar conjunction. The rover does not stop. Every command, decision and health reading is still sealed and chained on board, day after day.

03 · CONTACT RETURNS

Forward to the orbiter

When a relay comes into view, the rover forwards the whole backlog to the nearest Mars orbiter it has a relay agreement with. DSRP carries custody across the hop.

04 · VERIFY ON EARTH

The chain shows nothing is missing

The orbiter sends the backlog to Earth. Because every receipt names the one before it, a gap or an edit would be obvious. Nothing is lost, and nothing can be quietly altered.

Mission Recorder V2 · BuiltDSRP · Simulation-validatedCOSRYX-EDGE · Built
06 Why distributed

No single place where the record can die.

A recorder on the vehicle alone is lost with the vehicle. A record on the ground alone misses everything that happened out of contact. COSRYX V2 keeps the chain in three places: on board, at the relay and on the ground.

Each copy is checkable on its own. When they meet again, the chain tells you whether they agree.

07 Who reads it

Evidence for people who were not in the room.

INVESTIGATORS

Failure review

Reconstruct the last verified state and the decisions leading to a failure, from a record the operator could not have edited afterwards.

INSURERS

Claims and liability

Check what was commanded, when, and whether the vehicle acted within its signed bounds.

PARTNERS

Shared missions

When two organisations share a mission, each can verify the other's actions without a shared database.

08 Limits

What V2 does not claim.

Claimed

  • Code-complete; G0 and G1 complete
  • Simulation-validated and ground-demonstrated as a verifiable mission recorder
  • Ready for an external audit, target-hardware testing and partner telemetry integration

Not claimed

  • Flight qualification or any operational space deployment
  • Radiation testing (G3 is next)
  • Hardware key custody for the PQ leg (key custody in this stage is software; hardware custody certification is pending)
  • Agency acceptance or an external audit
Internal security freeze (RC3) complete · External audit not completed · No flight qualification claimed.
The post-quantum (PQ) leg uses ML-DSA-65 (FIPS 204) via the R-Series engine. Key custody in this stage is software; hardware custody certification is pending. Not flight-qualified. Not independently audited.
09 Questions

About the recorder.

Is this a hardware box?

Not today. COSRYX V2 is software that runs on the vehicle's own computer, on relays and on the ground. Radiation and target-hardware testing (G3) will show how it behaves on representative flight hardware.

How much storage does a long outage need?

It depends on the mission's record rate. Receipts are small, and the chain does not require keeping raw payloads, only their hashes. Sizing is part of mission integration.

What happens if the vehicle is never recovered?

Everything forwarded before the loss is already verifiable on the ground, with the chain showing exactly where the record ends.

Has the recorder flown?

No. No launch contract is signed. The roadmap puts our own CubeSat after radiation testing, subject to funding and licensing.

10 Next

Know why it failed, and before it fails.

The health heartbeat feeds the recorder every 5 to 10 minutes.

Mission healthRoadmap