Exhaustive Claim
A statement of the form "the last one" or "nothing else does this" — load-bearing, and only as good as the search behind it.
An exhaustive claim asserts completeness: the last remaining caller, the only consumer, nothing else imports this, no other file matches. Readers act on such claims — they delete the now-unused module, skip the extra check, close the issue — so a wrong one causes damage far from where it was written.
Nothing mechanical catches it. Type checking, linting, tests, and coverage all pass over prose without reading it. A false exhaustive claim in a pull-request description or a code comment ships clean and outlives its author's memory of writing it.
The discipline is that an exhaustive claim needs its own verification step, not a by-product of a search run for another purpose. Practically: count, do not eyeball. Scope the search to exactly the region the claim covers. If the count is not worth running, drop the superlative and describe only what you did change — "removed the caller in X" is always safe and usually just as useful.
The commonest cause of a false exhaustive claim is Truncation Bias: a search whose output was cut short, so every counterexample sat below the fold.
See also8
Hand-picked in the note itself — the neighbours worth reading next.
Truncation Bias
Reading a truncated result as if it were the whole result, so every counterexample is invisible.
Method15 connections
Falsifiability
A claim is only worth something if you know what observation would refute it.
Method16 connections
Plausible Mechanism
A causal explanation that was inferred rather than tested, and reads as more rigorous for being specific.
Method19 connections
Ground Truth
The measurement that arbitrates, as opposed to the artifact that merely reports.
Method30 connections
Code Review
A second person reading a change before it lands, and the practices that make it worth the time.
Version Control & Delivery15 connections
Hallucination
Fluent, confident output that is not grounded in anything real.
Agents & Language Models12 connections
Vacuous Truth
A statement that holds only because its subject set is empty — a green result that measured nothing.
Method25 connections
Linguistic Relativity
The hypothesis that language shapes thought, and the evidence that has narrowed it considerably.
Meaning & Society11 connections
Related2
Nearby in the graph rather than deliberately chosen. Looser, sometimes surprising.
Linked from11
Notes elsewhere in the wiki that reach for this one.
- Adversarial ReviewAgents & Language Models
Reviewing work with an explicit mandate to refute it, from a perspective that did not produce it.
- Code ReviewVersion Control & Delivery
A second person reading a change before it lands, and the practices that make it worth the time.
- FalsifiabilityMethod
A claim is only worth something if you know what observation would refute it.
- Fan-Out and Fan-InAgents & Language Models
Splitting work across parallel workers and recombining their results.
- GlobSystems & Tooling
Wildcard pattern matching over filenames, similar enough to regular expressions to mislead.
- Ground TruthMethod
The measurement that arbitrates, as opposed to the artifact that merely reports.
- HallucinationAgents & Language Models
Fluent, confident output that is not grounded in anything real.
- Linguistic RelativityMeaning & Society
The hypothesis that language shapes thought, and the evidence that has narrowed it considerably.
- Plausible MechanismMethod
A causal explanation that was inferred rather than tested, and reads as more rigorous for being specific.
- Truncation BiasMethod
Reading a truncated result as if it were the whole result, so every counterexample is invisible.
- Vacuous TruthMethod
A statement that holds only because its subject set is empty — a green result that measured nothing.