Lab · Simulation

Simulated, and labelled that way.

Before anything flies, COSRYX checks its behaviour in simulated missions: an Earth–Moon relay, Mars autonomy under delay, bit flips in on-board models, and a matrix of broken links. Every feed on this page is labelled Simulated, because simulation is not flight.

SIM-LUNAR-01100/100
Mars MCC + EDGE46/0
Radiation-integrity sim18/18
DSRP scenarios100/100
01 Ground rule

A green simulation means the logic held. It does not mean it has flown.

Simulation is the right first step for systems that will run where no one can reach them. It lets us break links, delay messages by minutes, flip bits and inject faults thousands of times, cheaply and repeatably.

It also has a hard ceiling. A simulated radiation event is a model of one; a simulated relay pass is not a real antenna. That is why every result here carries its label, and why radiation testing (G3) is the next step on the roadmap.

What we claim: the scenarios below ran, and the software behaved as specified in each.

What we do not claim: flight qualification, radiation qualification, operational service in orbit, or any external audit. None of those has happened.

02 The four runs

What is simulated, and what was checked.

Simulation lab · simulated01 / 04
01 · SIM-LUNAR-01 · SYSTEM STUDY 001

Earth–Moon relay with real gaps.

A lander, a relay in lunar orbit and an Earth station, each with contact windows. Messages wait for a window, sealed and queued by priority, then forward. The study checks that nothing is dropped, reordered or altered across the gaps.

  • 100/100 simulation scenarios.
  • Built on DSRP's store-and-forward relay.
02 · MARS · MCC + EDGE

Autonomy inside signed bounds.

Earth sends a signed intent once: the plan and the actions allowed. The rover acts alone within those bounds and receipts each decision. The run checks that out-of-bounds actions are refused, stale plans rejected and every decision chained.

  • 46 conformance assertions met, 0 failed.
03 · RADIATION-INTEGRITY SIMULATION

Flipped bits never earn a clean receipt.

Bit flips are injected into model state in software. The check is that a corrupted result is caught by a hash mismatch, quarantined, and scrubbed from the signed image before any clean receipt is issued.

  • 18/18 scenarios, including adversarial ones.
  • A simulation, not a radiation test.
04 · DSRP SCENARIO MATRIX

Delay, loss, reorder, partition, replay.

The Deep Space Relay Protocol is driven through a matrix of broken-link conditions. In each, the receipt chain must arrive complete and in order, or the gap must be flagged.

  • 100/100 scenarios · 78 tests.
03 Results, with their populations

Four numbers. Four different things.

RunPopulationResultLabel
SIM-LUNAR-01 (System Study 001)Simulation scenarios100/100Simulation-validated
Mars MCC + EDGEConformance assertions46 met / 0 failedSimulation-validated
Radiation-integrity simulationSimulated fault scenarios18/18Simulation-validated
DSRPSimulation scenarios · product tests100/100 · 78 testsSimulation-validated

These are separate from the 692 product tests, the 410 integrated tests and the 677 RC3 security-gate checks. None of the populations is added to another.

04 Simulation versus flight

What a simulation can and cannot show.

SIMULATION SHOWS

The logic is right.

  • Receipts chain and verify under delay and loss.
  • Policies refuse what they should refuse.
  • Faults are caught before a clean receipt exists.
  • Results are repeatable, byte for byte.
ONLY FLIGHT AND HARDWARE SHOW

It survives the real place.

  • Behaviour under real radiation on target chips.
  • Timing on flight-class processors and memory.
  • Real antennas, real passes, real power limits.
  • Years of operation, not hours of runs.
05 How a run is built

Deterministic, seeded, replayable.

Each scenario is a script: a mission timeline, a link model with its contact windows and delays, and a set of injected faults. Runs are seeded, so the same scenario reproduces the same bytes; COSRYX-NEXUS adds byte-identical replay for custody chains.

Because runs are seeded, a reviewer can re-run a scenario and compare the result, rather than taking a log on trust.

06 Light-time in the model

Delays are physics, not parameters we tune away.

≈1.3 sEarth–Moon, one way
3–22 minEarth–Mars, one way
6–44 minEarth–Mars, round trip
WeeksSolar conjunction silence, Mars
07 What comes after simulation

The next proofs need hardware.

StepWhyState
Radiation testing (G3)Replace the radiation-integrity simulation with tests on real partsPlanning · next
Hardware-in-the-loop (G4)Run on flight-class processors with real telemetryPlanning
Our own 6U CubeSatA test bench in orbit: power-cycle the payload, check it re-acquires signal, run controlled fault drillsPlanning · no launch contract signed
LEO shadow, lunar, Mars (G5–G7)Shadow real missions, then bounded pilotsPlanning
08 The required lines

Stated in full.

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.

No launch contract is signed.

Earlier internal soak records were withdrawn on 30 August 2026 because the verdict logic could not report a failure; corrected records will be re-issued as a set. See the evidence page on cosryx.com.

Status as of 21 October 2026.

09 Questions

On simulation.

Why say "Simulated" on every feed?

Because a moving chart looks like a real system. We would rather a reader never wonder. Nothing on this site shows data from a spacecraft.

Is the 18/18 radiation result a radiation test?

No. It is a software simulation of bit flips and the system's response to them. Radiation testing is the next gate (G3) and has not been done.

Can partners run the scenarios?

That is the intent once the external audit is under way. Write to research@cosryx.com or use the enquiry form.

10 Read the studies

The notes behind the runs.

Research Notes 001–004 and System Study 001, with the themes we are working on next.