Tag: verification5
← All Articles“Not found” is not “does not exist”
An AI agent's 'not found' is not 'does not exist.' Five rules for proving absence with bounded reads, positive controls, and scoped negative claims.
The AI agent that deleted 474 of my files was right. I checked anyway.
An AI agent deleted 474 files and its report was accurate. Verifying an agent's summary, not just its work, is the discipline that catches the divergence.
Your coding agent should watch its own work run
Your coding agent should watch its own work run: browser automation like Playwright turns 'it should work' into 'I watched it work' with evidence attached.
"All tests pass" is a warning, not a clearance
Why a green test suite after a schema change should trigger suspicion, not confidence. A verification methodology that catches what tests structurally cannot —
Never verify a result with the tool that produced it
Orthogonal verification for AI-assisted development: check results through a mechanism independent of the one that produced them, and at every pipeline stage.