Claim register and evidence index

The JSON register and CSV matrix are generated from substantive public paragraphs and table rows across all sixteen papers and the evidence library. Each entry binds its exact public wording with a digest of that wording, public page, edition, separate research/reference/production records, engineering maturity and assurance. Digests identify public text, never private sources. Full assumptions and qualifications stay in each assertion and its linked paper.

Scope of evidence

A public exposition or conditional argument is recorded as such. Historical implementation inspection is source_inspected and does not imply execution of private tests. The corrected source-and-test-coverage assertion has no production evidence. Dated authenticated metadata and retained workload observations are separate operational records, limited to the properties actually observed. They are not new successor observations. See implementation evidence.

The synthetic evidence catalog supplies claim-specific tested reference records, actual negative cases and reproduction commands. A green build cannot promote those cases into production conformance or independent reproduction. Neither register has a global verified flag. The assurance boundaries remain part of every interpretation.

Historical correction

The immutable predecessor registry remains available in the old edition downloads. Its private-source correspondence metadata and production build identifiers are not fields of this successor register. The predecessor source-inspection record was labeled production observed; this successor explicitly corrects that classification. Earlier public exposure remains a cumulative review consideration.

Reproduce and challenge

Run python tools/claims.py --write, then python tools/claims.py and python tools/qa.py --artifacts from the public source. The first command regenerates only public derivatives; QA compares coverage with a separate Markdown parser traversal. Cite an exact public claim ID, edition and counterexample using the review guide. New evidence requires a new scoped record and review; release requires separate approval of the exact bundle and destination.