Governance · Status as of 21 October 2026

No status inflates without evidence.

Governance at COSRYX covers who may decide, which words may describe the work, and who may be named alongside it. Each of those has a written rule, and the rules are on this page.

Document statusStructured draft
External auditAudit not completed
Last prototype update6 August 2026
Launch prototype: this page is a structured draft and requires legal, security and organisational review before production use.
01 Governance scope

Eight areas, one rule book.

Governance should cover corporate authority, research approval, programme status, security, responsible AI, data use, partner claims and public communications.

The same rules apply on all three COSRYX sites: cosryx.com, cosryx.space and cosryx.ai.

02 Decision ownership

Every decision has a named owner.

PROGRAMME

Organisational owner

A named organisational owner for each programme.

TECHNICAL

Technical owner

A named technical owner for each prototype or pilot.

DATA AND SECURITY

Data and security owner

A named data and security owner for partner information.

HUMAN APPROVAL

High-impact decisions

Authorised human approval for high-impact decisions. An AI system can recommend; it cannot approve.

03 Status governance

Nine words. Nothing else.

Every product, feature and milestone on a COSRYX site carries one or more of these labels, and only these. Each has a definition and an approval criterion.

Built

The code exists, is under version control and passes its own test suite.

Simulation-validated

Behaviour has been checked against simulated mission conditions and scenarios, not real hardware or orbit.

Ground-demonstrated

Shown working end to end on the ground, on ordinary computers, with real inputs and verifiable outputs.

Tested

A named test population has passed in full; the count and its population are always stated together.

Hardware-blocked

The next step needs hardware or a facility that is not yet available to us.

Audit not completed

An external review is required and has not been completed. Internal results are never described as audited.

Planning

Scoped and written down, but not started; usually subject to funding, licensing or an earlier gate.

In development

Work has started but is not yet in the published test totals.

Future direction

An intention we describe openly. No schedule, no commitment.

SIMULATED FEEDS

Simulated

Any feed, console or telemetry view driven by a simulation is labelled "Simulated", every time it appears.

A WORD WE DO NOT USE

Never "LIVE"

No COSRYX site describes a feed, service or system as live. Nothing we publish runs in orbit.

04 Changing a status

Three conditions, all required.

Status labels are verified against evidence files before publication. Changing a product's status requires:

  1. An updated evidence file that supports the new label.
  2. A green test suite for the population the label refers to.
  3. Named owner sign-off from the accountable owner for that programme.

No status inflates without evidence. Every count is published with its population: product tests, integrated tests and RC3 security-gate checks are separate numbers and are never added together.

05 A correction we keep visible

When a record is wrong, we withdraw it.

Withdrawn

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. No figure from those records appears on this site. Read the evidence page →

This is how the status rule works in practice: a verdict that cannot fail is not evidence, so the records it produced were taken down rather than relabelled.

06 Partnership and logo policy

No name without written approval.

No institution, agency, company or individual should be presented as a partner, adviser or customer without written approval and accurate scope.

Supplier and launch-provider names are not published. No logo or insignia of any agency is used on COSRYX sites.

07 Required lines

Three sentences that travel with every claim.

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.

Last prototype update: 6 August 2026. Status as of 21 October 2026.

08 Check us

Every label on this site should survive a question.

If a status looks stronger than its evidence, tell us. We will correct it in public.