Wyrd records what happened, who authorized it, and what the system refused to do.
Below is a point-in-time engineering snapshot per system: the evidence last observed, what it establishes, and what it does not. It is not a general public claim and not a substitute for a fresh release audit.
We do not add test counts together. Doing so would require duplicate tests removed, branches pinned, dates current, commands reproducible, skips disclosed, and generated checks separated from behavioural tests. Until all six hold for a combined figure, individual cards are the honest form.
And software test evidence proves engineering work. It does not automatically prove safety, field reliability, clinical performance, regulatory approval, customer value or production security.
Every system, each with its own receipt — once the receipts are real.
This register renders directly from a signed manifest so a published count can never drift from the recorded one. It is intentionally empty right now: see why below, rather than showing placeholder figures.
Fund the proof, not the promise.
The ladder we hold ourselves to, in order. Each rung is a thing that can be shown, not asserted.
Check it, then decide.
Technical diligence, reproduction commands and partner-level evidence are available to qualified institutions.