Agents write the code. Who signs off?
Proof turns what an agent did into a record you can review, question, and defend.
Autopilot flies the plane.
The pilot is still responsible for the flight.
Coding agents are autopilot for software. Proof keeps you in the seat.
A prompt can only give you so much
Does your chat look like this?
Good idea. Here is what you will want:
- 1.RSVP form
- 2.Guest list
- 3.A reminder email
- 4.A date and location field
- 5.A thank-you page
Want me to start on the form?
Yes, add a plus-one field to the form.
Good point. You could add a capacity check. Want me to?
Sure, add a song field and build a shared playlist.
Of course, here is the form again.
Could you remind me what you wanted for capacity?
Two sides of the same coin
Proof is active before the run and after it.
Before the run.
Your agent writes the code.
After the run.
Proof gates a merge on how much of the diff was actually read, not on how many people clicked approve.
Approval counts stopped meaning much once agents started writing most of the diff. A reviewer can clear 60 files in a minute and the pull request looks exactly as approved as one somebody read.
Set the bar as coverage, not headcount
Require a percentage of the review-required files to be read in depth. Two approvals on an unopened diff do not satisfy it.
The check runs on the pull request
A status appears on the PR and states where the review stands. Nobody has to remember to look somewhere else.
Unread files are counted, not hidden
A file approved without being opened is recorded as approved without being opened. The number is on the record and on the check.
A new commit does not inherit an old sign-off
A record sealed against an earlier commit stops satisfying the policy, so pushing after approval reopens the gate instead of slipping through it.
Roles are sealed at signing time
The signer’s role is written into the record when they sign. Promoting someone later cannot retroactively make an old sign-off count for more.
All of it is live today. What a record holds, and what it deliberately does not, is on the trust page.
Write to us.
Questions, bug reports, ideas: they all land in the same inbox, and we reply.