Verification Debt
Definition
The growing gap between how fast code can be generated and how fast it can be validated. Defined by Lars Janssen (March 2026). Unlike technical debt, which usually announces itself through mounting friction, verification debt breeds false confidence — the code works, the demos look good, but nobody has verified the implementation against requirements, edge cases, or design specifications. Survey finding: 96% of developers don't fully trust AI-generated code to be functionally correct, but only 48% say they always check it before committing. The remaining 52% are accumulating verification debt with every commit.
Builder Context
Verification debt is why your agent-built site has 'bugs that aren't bugs' — features that work but don't match the spec, designs that render but don't match the system, code that passes tests but violates architectural constraints. The fix: close the verification loop. For design: visual regression testing (Playwright VRT, Percy, Chromatic) catches drift automatically. For behavior: screenshot-driven QA loops (Frontend Review MCP) let agents self-verify. For architecture: lint rules (ESLint custom rules, Stylelint) gate CI/CD. The goal: make verification as fast as generation by automating everything that can be automated and budgeting time for the rest.