Verification
AI code verification, decided by the change
Tests say whether they passed. Headron asks a second question: did anything test what just changed? If the proof a change owes is missing, the change does not land.
How it works
- Contract
- One file in the repo declares which checks prove each kind of change. Every agent working in the repo reads the same contract.
- Classify
- Headron reads the change and works out which class it falls in, so the proof owed comes from the change itself, not from a generic checklist.
- Verify
- The owed checks run, and Headron tracks which ones actually produced evidence. A check that never ran looks the same as a check that passed, so the distinction is the product.
- Receipt
- The verdict and its evidence are kept as a receipt. Anyone can see what was proved, what was refused, and why.
Start
Run it locally with the free CLI, connect any agent over MCP, or call the hosted Mind API. The core is open source under MIT.
Read the docs · Mind API reference · Create an account · Star on GitHub