Principles
Make every change verifiable
An agent's change is ready only when an automated check can show that it does what it claims.
When agents write most of the code, the volume of change outgrows what reviewers can read line by line. So each change comes with its own evidence: passing tests, completed checks and a record of what was verified.
Rationale
A reviewer who must trust an agent’s description of its work becomes a bottleneck or a rubber stamp. Automated checks replace trust with evidence. They behave the same way on each change at any volume, and the record they leave lets a person audit the work later.
How it works
The loop below shows where verification sits. The agent proposes a change, the checks test it and a person reviews the evidence before release.
Trade-offs
Writing checks takes time, and some qualities resist automation. Accessibility, tone and visual design still need a person’s eye. Verification narrows what people review, so they can spend their attention where machines cannot help.