Reconciliation
Different numbers measure different things.
Eight test figures circulate across this estate. Rather than quietly deleting the ones that no longer apply, here is what each one counts, which artifact produces it, and which of them you can rerun today without contacting us.
The canonical public figure
403 executable conformance cases across 22 suites, 0 failures. That is the number to quote, because it is the one an independent party has reproduced cold and offline, and the only one whose per-suite figures sum to the published total exactly.
| Figure | What it counts | Artifact | Rerun today? | Status |
|---|---|---|---|---|
| 403 cases / 22 suites | Backend conformance battery | tests/conformance/*.test.mjs | Yes | CANONICAL |
| 11 simulations | Concurrency and failure-mode models | tests/sim/*.mjs | Yes | CANONICAL |
| 45 cases | Tenant Read API, a subset of the 403 | tests/conformance/tenant-read.test.mjs | Yes | SUBSET |
| 66 cases | Adapter conformance, a subset of the 403 | src/adapters + six-adapters suites | Yes | SUBSET |
| 228 tests / 32 suites | 2026-07-08 release ledger snapshot | RELEASE_TEST_LEDGER-2026-07-08.json | No | SUPERSEDED |
| 394 cases | 2026-07-20 preflight snapshot | READINESS_SCORECARD.md addendum | No | SUPERSEDED |
| 84 tests | Adapter-only subset, stale | READINESS_SCORECARD.md section 2 | No | SUPERSEDED |
| 28 checks | Release-gate checks run by the diligence harness | DILIGENCE.sh | No | NOT REPRODUCIBLE |
| 14,914 assertions / 146 suites | Full estate battery including site-claim and doctrine suites | founder-held release package | No | NOT REPRODUCIBLE |
On 14,914
The 14,914-assertion figure counts the full estate battery, including site-claim and doctrine suites that are not in the public bundle. It is not reproducible from anything shipped, so it is not presented as independently verifiable. It is scoped rather than withdrawn: the number is real and the corpus exists, but until the corpus is published, 403 is the figure that survives a stranger running it. That restoration is tracked against requirement R5 of The Verify Standard, which this estate currently fails.
Why this page exists
A vendor with one number and no explanation looks tidier than a vendor with eight and a reconciliation. The tidier vendor is the one you cannot check. Requirement R2 of The Verify Standard exists precisely to make this page mandatory, and we wrote the requirement knowing we would fail it first.
The Verify Standard · Machine-readable · Connector conformance detail