How it actually works
Four stages, one closed loop. Then you can try it yourself.
The thinking stays yours
Frame the problem on a canvas
Concepts, not one long prompt.
Hand off a scoped brief
Your agent builds it. Proof picks it back up.
Review through three lenses
Concepts, architecture, and files, tracked as you open them.
Signing off a file you never opened is allowed, and the record notes it as exactly that.
Prove it with a sealed record
What you read, approved, or sent back.
Same four stages. You're driving this time.
An interactive walkthrough of the full Proof loop loads here: Ideation before the run, the agent's run, and Review after it. It shows how you frame a problem into concepts, hand the chosen approach to your agent, then review what changed as a map of concepts with a defensible record of every decision and who approved it.
Where Proof fits next to the review tools
They check the diff. Proof checks whether the right person understood it and decided.A diff is the line-by-line list of what changed in the code.
active only at the end · you judge off the record.
active at both ends · a person is on the line.
Free to start. No card needed.