awesome-claims-auditlisted

# Public Claims Audit A claim is any public sentence a reader could disprove: a permission list, a number, a quoted UI label, a copy-pasteable command, a guarantee. The code that decides it lives somewhere else — a constant, a manifest, a catalog, a route table, a locale file — and nothing links the two. A rename on one side leaves a false statement on the other, and every test stays green. The claims that rot are not the vague ones. They are the specific, checkable ones a reader was *invited* to verify. Two phases, separate on purpose: report everything first, fix second. A fix applied mid-audit changes the surface you are still reading. Reference files (load the one you need, don't inline both): - [`references/claim-source-map.md`](references/claim-source-map.md) — the map from each class of claim to the one file that settles it: how to build it, the template, and the resolution traps that cost the most time. - [`references/checker-recipes.md`](references/checker-recipes.md) — the four mechanical check kinds, the config schema the scripts read, and the mutation discipline that proves a check can fail. Scripts (Node ≥18, no dependencies): - [`scripts/check-claims.mjs`](scripts/check-claims.mjs) — runs the mechanical checks from a config you write for the product. - [`scripts/prove-checks.mjs`](scripts/prove-checks.mjs) — breaks one claim at a time and asserts the owning check names it. - [`scripts/map-coverage.mjs`](scripts/map-coverage.mjs) — cross-checks the claim-sou