Policy
Last reviewed: 2026-09-19
Deceit distinguishes suspicion from discrimination. Naming a pattern is not the same as proving a claim false. Every instrument here ships with the conditions under which it misfires.
No tool, ledger entry, pattern, or chapter leaves the desk without a specific, checkable statement of what a false positive looks like for that instrument. Not a disclaimer. A test.
An instrument that only proves your enemies wrong is being used incorrectly. If every result flatters what you already believe, you are running a suspicion engine, not a recognition engine.
howMisused (the weaponized reading) and falsePositive (the signature of a misfire). Both render.A usable false-positive statement is concrete and local to the instrument. It names a condition under which the pattern or verdict could appear while the claim underneath is true, fair, or innocent.
"This pattern can be misread as..." is better than "context matters." The first can be checked. The second cannot.
If a pattern call, verdict, or tool result looks like a false positive, the route is the same as any other correction. See the corrections policy.
Every challenge is reviewed. A confirmed false positive is corrected, logged, and used to sharpen the instrument that produced it.