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. Read it before tracing the first claim to its source. - [`references/checker-recipes.md`](references/checker-recipes.md) — the six mechanical check kinds, two recipes worth copying, the mutation discipline that proves a check can fail, and how a copy fix out of a shared file gets committed. Read it when you are about to write or repair a mechanical check, not while collecting claims. - Other runtimes — the runner is Node because that is what most public-facing repos already have. The four check kinds are ~40 lines in Python, Ruby, or Go; what matters is the disci