Proof · a record of what your software promises
Proof writes down what your code promises, in words your engineers sign, and holds every commit to them.We find where your code breaks its promises, and hand you the failing test.
public on buger/jsonparser123 promises signed7 breaks fixed upstream1 miss published
A commit touches refund.go. The map shows the promises it carries.
Public receipt
buger/jsonparser: a Go JSON parser, 5,600 stars, ten years old. Everything below is public and re-runnable.
promises signed by the maintainer
breaks fixed upstream, each with a test that failed on main
miss published, MISS-001
KI-3: Set() on an array-index path under an object parent could drop a sibling value. The promise said it replaces one value and touches nothing else. The test that failed on main is in the register, and it stays.
The finding
A finding is a test that fails on your main, with the promise it breaks attached. You run it, watch it fail, fix, watch it pass.
Fig. 01 · One finding, start to finish. The test stays in your suite, so this class of break cannot come back without the gate saying so.
What you keep
Four things, in your repo, under your licence.
Every promise your component makes, recovered from the code and signed by your engineers.
Each with a test that fails on current main, validated by a person before you see it.
Touch a function or a promise and see what else moves. Your engineers, your CI and your agents ask the same map.
The map is asked on every change. A broken promise blocks the merge.
If we stepped away tomorrow, nothing you rely on stops.
The map
Change is safe when you can see what a change touches before you merge it.
Fig. 02 · The blast radius of one unwritten promise. Example. The promise lives in prose, so no check can fail on it, and the failure surfaces where your customers are.
Accountability
Machines check everything, every time. People decide what a machine must not decide alone. That line is written down, and you can move it.
Agents
Do the crunching: every check, every commit, at a volume no person could reach.
A person
Validates every finding before it reaches you, and signs the promises, the bar, and our misses.
Your engineers
Sign the promises. Anything an agent drafts is marked as a draft, and an agent cannot approve its own requirement.
Fig. 03 · CI is green in both pictures. The second one only exists once the promises are written down.
The whole method →Our misses are published. MISS-001, signed by Leonid Bugaev.
Who it is for
“We ship ten times faster now. Review did not get ten times faster. I sign off on releases I cannot personally vouch for.”
What Proof gives you: a map and a gate you keep. You sign a release that was already held to its promises.
“I open the register looking for slop.”
What Proof gives you: a live map, a published miss, tests that fail on main. Re-run them, then tell your CTO.
“One bug in routing, auth or billing hits every customer at once.”
What Proof gives you: the shared path as signed promises. A break is a failing test on that path.
“My agents write most of the code now. I need something they cannot drift from.”
What Proof gives you: a written record of what the code promises. Agents can read it and cannot approve it on their own.
Start
Pick the one you would least like to be asked about. We onboard it with your engineers, then the map and the gate are yours.
How onboarding works →Prefer a call? 20 minutes with Leonid →
Leonid Bugaev · founder
signs the bar and the published misses