Every correction this record has published against itself.
2 corrections, carried by 15 dated instruments. Each one below states what was wrong, where the error originated, what the correction changed, and what — if anything — still stands. Sealed documents are never edited: when a statement stops holding, a new sealed instrument says so and the original bytes stay untouched. Every root and hash on this page opens in /verify with the value prefilled, so nothing here has to be taken on trust.
Anything that looks wrong on this page, including this page: corrections@trustnav.health.
Withdrawal of the Network Integrity findings
issued 2026-08-04nothing standsAll 189 published Network Integrity findings were withdrawn after a control comparison showed the method did not distinguish the flagged population: 72.2% of flagged providers matched an active Colorado licence, against 68.2% across the 146,310-provider comparison population.
Ours. The licence-binding method could not support the class of finding TrustNav published, and the control that established that was one we ran on ourselves.
Withdrawn in full. 189 of 189 findings retracted; no corrected edition exists and none is coming. The comparison does not establish that the underlying listings were accurate — it establishes that the withdrawn method did not support the finding class.
The instruments — originals, corrections, supersessions, custody
| role | instrument | dated | scope | root / sha256 |
|---|---|---|---|---|
| original edition | Edition One | 2026-07-28 | 189 findings — 182 licence-gap + 7 no-corroboration · 0 standing · never publicly served | root cfc90a7936aa1699… |
| original edition | Withdrawn intermediate | 2026-07-28 | 1,562 findings · 0 standing · never publicly served | root 03d3010c2d644611… |
| original edition | Edition Two — the pinned, publicly served edition | 2026-07-28 | 189 findings — 182 licence-gap + 7 no-corroboration · 0 standing · publicly servedcustody: subject-level artifact moved to operator custody archive (withdrawn-editions-custody, preserved byte-identical; CUSTODY-MANIFEST.md records each sha256) on 2026-08-05; sealed bytes preserved (sha256 7defcfd2342c6f7db95cfa9c33162fc4245079c174056e4a444f0d32df4bdec6) | root 733b056b6952cf42… |
| original edition | Edition Three — never pinned, never public | 2026-07-31 | 183 findings — 182 licence-gap + 1 NPPES-inactive · 0 standing · never publicly servedcustody: subject-level artifact moved to operator custody archive (withdrawn-editions-custody, preserved byte-identical; CUSTODY-MANIFEST.md records each sha256) on 2026-08-05; sealed bytes preserved (sha256 11fbb5a0d979762e4c1b479d4bc754a56044536b4814526d5f40d9ed22ecccf0) | root e2471e43a7e6060b… |
| original edition | Edition Four — never pinned, never public | 2026-07-31 | 183 findings — 182 licence-gap + 1 NPPES-inactive · 0 standing · never publicly servedcustody: subject-level artifact moved to operator custody archive (withdrawn-editions-custody, preserved byte-identical; CUSTODY-MANIFEST.md records each sha256) on 2026-08-05; sealed bytes preserved (sha256 d899907bb2f989719fbe38a4cfebbde4208191af807b2f23edc7dfceb9d18366) | root f7c5d16b7d6785ba… |
| withdrawal | Notice of withdrawal | 2026-08-04 | withdraws all 189 findings, in every edition in which they appeared | sha256 238f46985f05c148… |
| supersession | Supersession record | 2026-08-05 | supersedes the notice's section 1 serving statement only — five subject-level packet files moved to operator custody under the Gate 6 controls | sha256 863393e41ae308e4… |
| custody amendment | Subject-level artifact custody move | 2026-08-05 | the withdrawn editions' subject-level packet files are no longer served publicly — moved byte-identical (sha256 verified before and after) to operator custody archive (withdrawn-editions-custody, preserved byte-identical; CUSTODY-MANIFEST.md records each sha256). Their old URLs answer a governed 410 naming edition and reason; every root still resolves at /verify as withdrawn. | no separate identifier |
| supersession | Addendum | 2026-08-06 | supersedes the notice's section 4, first bullet only — the UHC Insurance Company / Surest availability bullet, as corrected by the record below | sha256 408ba59a9af6ca9c… |
Correction of the UHC Insurance Company / Surest availability claim
issued 2026-08-06narrowed — part standsEarlier editions said no public copy of these entities' Colorado rates existed anywhere. That was false when it was published.
Ours. A federal-catalog search filtered on the `_CO_` filename token and stopped at its first negative; removing that token resolves twelve of thirteen basenames to live counterparts. The HTTP 403 refusals are real and dated, but they are scoped to the storage account — an invented blob name in the same container returns the same refusal — so they say nothing about the thirteen named files.
The finding is NARROWED, not withdrawn: what survives is a registry-currency observation about the Division's own published sheet. The correction record is itself on its fourth issue — three earlier issues were superseded after audits of the correction found defects of their own, and the record lists them in its §7.
The instruments — originals, corrections, supersessions, custody
| role | instrument | dated | scope | root / sha256 |
|---|---|---|---|---|
| original edition | The claim as published | 2026-07-28 | the availability claim as it appeared in the sealed rate packets and on the live public pages — that no accessible public copy of these entities' Colorado rate files existed | no separate identifier |
| correction | Correction record — first issue (superseded) | 2026-08-06 | superseded the same day: a same-day audit found six defects of its own, listed in the current record's §7 | sha256 prefix 96a58b23… (prefix only on record) |
| correction | Correction record — second issue (superseded) | 2026-08-06 | superseded: a second audit found the claim had also reached two hash-published proof bundles the first issue did not cover | sha256 prefix b85a34fc… (prefix only on record) |
| correction | Correction record — third issue (superseded) | 2026-08-06 | superseded: a third audit refuted completeness again and named the structural cause — three passes superseded by enumeration, with no catch-all rule | sha256 prefix 87ac4689… (prefix only on record) |
| correction | Correction record — current issue | 2026-08-06 | supersedes BY RULE rather than by enumeration: every instance list in it is declared non-exhaustive. Carries the method error named first, the negative control, the Division's sheet re-read, the per-file retrieval table, and the explicit non-conclusion list. | sha256 2d0307caf39bc74f… |
| supersession | Withdrawal-notice addendum | 2026-08-06 | carries this correction into the withdrawal notice's section 4, first bullet only | sha256 408ba59a9af6ca9c… |