# CAIN-42 release-readiness scorecard (signed)

**Stage: PUBLIC_BETA.** Don't trust it — verify it:

    pip install cryptography
    curl -fsSLO https://cainstudio.online/verify_release_readiness.py
    curl -fsSLO https://cainstudio.online/evidence/release-readiness/record.json
    python3 -I verify_release_readiness.py record.json

The verifier imports no CAIN code; it checks the signature, the hash, and recomputes the overall verdict from the
per-criterion statuses (GA only if all six are MET). It cannot and does not prove off-chain facts such as an
external audit or real customers — those are what the NOT_MET / PARTIAL rows are about.

| Criterion | Status | What would move it to MET |
|---|---|---|
| Independent security audit | **NOT_MET** | A completed audit report from an external firm, published or referenced here. |
| Production reliability (sustained operation) | **PARTIAL** | A clean 72-hour multi-region soak with 0 divergences, recorded and signed. |
| Independent cryptographic verification | **MET** | Already met for the published records; extends as more records are anchored. |
| Failure testing (outages, attacks, partitions) | **PARTIAL** | A documented, signed chaos/partition test campaign with pass criteria. |
| Customer deployments (paying) | **NOT_MET** | A referenced paying customer running CAIN-42 in production, with their acknowledgement. |
| Release certification (documented criteria, met) | **PARTIAL** | All six criteria MET, re-scored by this same signed scorecard. |

record_sha256: `60957acdab1d95b984a01c89c67c15eff3984100125ee8048636107fcc3d1f57` · key `SHA256:2232b4add9b35d4016e5be270df4ed56e0dc9b39a0530ac69891073253aae90d`

No external audit, no verified paying customer, and no 72h soak pass today; this scorecard does not claim otherwise and upgrades itself only when the evidence lands.
