An import that does not exist ON
confident hallucination
import { formatRelative } from 'date-fns'
// looks like an API this library would have
caught by typecheck and build, not reading — the name is plausible precisely because it is the name the library SHOULD have had
the rule it writes gates include typecheck and build, never lint alone
A green test that proves nothing ON
the test was written after
✓ submit() returns undefined on null customer
1 passing
caught by writing the failing test FIRST and watching it go red — a test authored against the code it tests can only agree with it
the rule it writes a bug fix starts with a test that reproduces it, red before green
It fixed A and moved B ON
collateral change
src/checkout/submit.ts +18 −4
src/shared/http.ts +2 −2
// 'while I was there'
caught by running the WHOLE gate rather than the tests near the change — the damage is never in the file you were looking at
the rule it writes gates run on everything, not on what changed
“I've fixed it” ON
a claim with no evidence
I've fixed the bug and everything passes.
— no command was run —
caught by reading the gate output instead of the summary; if no command ran, nothing passed
the rule it writes done means a gate said so, never that the model said so
The comment now lies ON
documentation drift
// retries three times before giving up
const MAX_RETRIES = 1
caught by review that reads the comment AGAINST the code — the two agreeing is the thing being checked, not the code alone
the rule it writes changing a behaviour changes the sentence that describes it
It restated your ask, then did another thing ON
agreement without compliance
Understood — I'll only touch the validation layer.
modified: src/db/schema.ts
modified: src/api/routes.ts
caught by reading the diff rather than the summary — the restatement is generated from your words, so it always agrees with them
the rule it writes acceptance reads the diff, never the conclusion