What we claim, and what we do not.
Every number on this site is an internal result, and each one names its population. Some earlier records did not deserve the trust they asked for, so we withdrew them. Both facts belong on the same page.
Three populations, never added together.
410 integrated tests belong to the COSRYX V2 mission recorder and gate G1. 692 product tests belong to the twelve products and the Hybrid Moat. 677 RC3 security-gate checks belong to the internal security freeze. They test different things, and adding them would produce a number that means nothing.
All three are internal: run by DCS on DCS-controlled infrastructure. Internal results are not an external audit, not certification and not flight qualification.
Simulated results are labelled "Simulated", every time.
Internal results, with their names on.
System Study 001 · 100/100
Lunar scenario checks across the product line.
Simulated
Conformance 46 / 0
46 conformance checks passed, 0 failed, under Mars delay.
Simulated
Radiation-integrity simulation 18 / 18
A simulation of bit upsets, not a radiation test.
Simulated
An internal security freeze, complete.
RC3 is the third release candidate of the COSRYX mission-evidence stack, frozen on 6 August 2026 after 677 of 677 internal security-gate checks passed.
Freezing means the code under review stops moving, so an external auditor examines exactly what we tested. The external audit has been initiated and is not completed.
We do not publish release archives, audit packs or evidence bundles on this site.
How 692 is made.
| Group | Product tests | Status |
|---|---|---|
| Foundation: PQ-Agility, DSRP, AI Sovereignty Oracle | 249 · 0 CVEs | Tested Simulation-validated |
| S1–S7: LENS, WATCH, WEATHER, MCC, EDGE, NEXUS, SWARM TRUST | 258 | Built Simulation-validated |
| N13 SPACETRACE, S8 SSA ACCOUNTABILITY, S9 MFG PROVENANCE | 96 | Built Ground-demonstrated |
| Hybrid Moat: HYBRID-01, 02, 03 | 89 | Built Definition-of-done sign-off pending |
| Total | 692 | Internal |
Per-product counts are on the products page.
Earlier soak records are withdrawn.
Why all six, not one. The defect was shared. In each run, real measurements passed through verdict logic that could not reach a failing outcome: a gate reading a field nothing writes, a timer that expired before the run began, a check that did not exist. Withdrawing one document while leaving the others standing would publish a set that disagreed with itself, so the whole set was withdrawn together and will be re-issued together.
No corrected figure, deliberately. Publishing corrected numbers one document at a time is how a set comes to contradict itself. Corrected figures will be released only as a coordinated set, once the runs have been re-gated against controls that can report a failure.
What was not wrong. The reconciliation found no fabrication at the source: the individual figures came from machine-generated closing records. An earlier generation of the documents had held the numbers back with explicit pending markers.
The finding, in one line: the measurements were largely sound; the judgements placed on top of them were not. That distinction is why the original documents are preserved unchanged as the historical record, rather than deleted.
Six documents, six findings.
Summarised from the 30 August notice. We describe the defect in each, and no result.
Receipt coverage was never checked
The record issued fewer receipts than it ran cycles, and none of the verdict checks read receipt coverage, so the gap could not affect the verdict however large it grew.
Withdrawn
A verifier that always said yes
The run was configured with a receipt verifier that returned true unconditionally. The cycles ran; nothing about them was verified.
Withdrawn
A timer that fired at once
The configured duration exceeded the largest delay the timer accepts. On overflow it fired within milliseconds and the run marked itself passed.
Withdrawn
Cycle completeness was invisible
The run completed materially fewer cycles than configured, but no verdict function read completeness. An uptime threshold was declared and read by nothing.
Withdrawn
"No error" over a recorded error
The run fell short of its schedule, and a no-error check passed while the record's own last-error field was not empty.
Withdrawn
Sums of withdrawn numbers
It repeated the withdrawn results and added aggregate figures that appear in no closing record. This is the one place where the numbers were not read from a record.
Withdrawn
What this evidence proves, and what it does not.
Proves
- The code exists and passes its own internal tests, by the counts above
- COSRYX V2 is code-complete (G0 and G1)
- The internal security freeze RC3 is complete
- Named scenarios behaved as specified in simulation
Does not prove
- Flight qualification or flight readiness
- Radiation testing (it is next)
- External audit or certification of any kind
- Customer deployment or agency acceptance
- Anything from the withdrawn soak records
Printed in full.
No status moves without evidence.
A status on this site changes only when three things exist: updated evidence, a green test suite, and sign-off by the named owner. A status never moves up because a page needs a better headline.
When a claim turns out to be wrong, it comes down, the reason is published, and the correction is dated. The soak withdrawal above is the standing example.
The full status vocabulary and its definitions are on the governance page.
About the evidence.
Can I see the withdrawn documents?
The originals are preserved unchanged as the historical record. They are not presented as current evidence, and we do not repeat their figures here.
When will corrected soak records be published?
When the runs have been re-gated against controls that can report a failure, and the set can be re-issued together. We will announce it in the newsroom.
Does the withdrawal affect the 410, 692 or 677 counts?
No. Those are separate test populations with their own verdict logic. The withdrawal concerns the soak records only.
Who is doing the external audit?
The process has been initiated. We do not name firms before an engagement is confirmed, and the audit is not completed.