ACI-053: A Document Is a Set of Claims

Thesis

Nothing a project builds checks whether a sentence is true: a compiler never reads a doc comment, and a reference check proves only that a named thing exists. Audit documents against the as-built code with one disposition per finding, and where the code fails a claim, leave the claim standing and file the defect. Drive the claims of any page that tells readers what to run against the shipped build, as you would acceptance rows.

Story

On 20 August 2026, three agents working on Laksa, an Elixir web platform, found seven documents in one day that stated the opposite of what was true. None was a code defect, and no instrument the project had would have raised any of them. Every check it had read code: "The docs-reference census checks that a named thing EXISTS. Nothing checks that a claim is TRUE" (Laksa@f941ff7b1, 2026-08-20). The day before, one module's documentation had shown readers how to call a module nobody built. "A missing module reads as a gap and invites a lookup; a documented one reads as a fact and ends the enquiry" (Laksa@40e027781, 2026-08-19). The project recorded the exposure and declined to propose a guard, since a prose-against-code guard is not buildable in general.