Proof · a record of what your software promises
Proof writes down the promises in your code. Your engineers sign them. A gate checks every commit against them.We find each point where your code breaks a promise. We give you the test that fails.
public on buger/jsonparser123 promises signed7 breaks fixed upstream1 miss published
A commit changes refund.go. The map shows the promises of that file.
Public receipt
buger/jsonparser is a Go JSON parser with 5,600 stars and ten years of use. All data below is public. You can run each check again.
promises signed by the maintainer
breaks fixed upstream. Each break has a test that failed on main
miss published, MISS-001
KI-3: Set() could remove a sibling value on an array-index path under an object parent. The promise says: replace one value, and change nothing else. The test that failed on main is in the register. The test stays there.
The finding
A finding is a test that fails on your main branch. The broken promise is attached. You run the test and see it fail. You apply the fix and see it pass.
Fig. 01 · One finding, from start to end. The test stays in your suite. This class of break cannot return without a gate failure.
What you keep
Four artifacts. They stay in your repository, under your licence.
We recover every promise of your component from the code. Your engineers sign each one.
Each break has a test that fails on your current main. A person validates each break before you see it.
Select a function or a promise. The map shows what else changes. Your engineers, your CI, and your agents use the same map.
The gate reads the map on each change. A broken promise stops the merge.
If we stop work tomorrow, your map, your gate, and your register continue to operate.
The map
You can see the effects of a change before you merge it.
Fig. 02 · The blast radius of one promise that is not written down. Example. The promise is only in a document. No check can fail on it. The failure occurs at your customers.
Accountability
Machines check everything, every time. People decide what a machine must not decide alone. This limit is written in the configuration. You can move it.
Agents
Run every check, on every commit. The quantity is more than a person can read.
A person
One person validates each finding before it reaches you. People sign the promises, the bar, and our misses.
Your engineers
Sign the promises. Each item an agent writes has a draft mark. An agent cannot approve its own requirement.
Fig. 03 · CI is green in the two pictures. The second picture is possible only after 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 speed did not increase ten times. I approve releases that I cannot examine myself.”
What Proof gives you: a map and a gate that you keep. The gate held the release to its promises before you sign it.
“I open the register and search for bad work.”
What Proof gives you: a live map, a published miss, and tests that fail on main. Run the tests again. Then tell your CTO.
“One bug in routing, auth, or billing touches every customer at the same time.”
What Proof gives you: the shared path as signed promises. A break on that path is a test that fails.
“My agents write most of the code now. I need a record that they must obey.”
What Proof gives you: a written record of the promises in the code. Agents can read the record. Agents cannot approve the record.
Start
Select the component that worries you most. We onboard it with your engineers. Then the map and the gate are yours.
Private early access: we onboard a small number of teams each month. Leonid onboards each team himself. Private code stays private. We countersign your NDA before we read a line of your code.
Do you prefer a call? 20 minutes with Leonid →
Leonid Bugaev · founder
signs the bar and the published misses