Proof-of-Fix Verification Receipts: Making AI-Generated Pull Requests Auditable in CI/CD
Reviewers should never have to guess whether an AI agent actually ran the test suite or checked downstream callers before opening a pull request.
The AI Pull Request Review Bottleneck
As teams adopt AI coding agents, pull request volume rises faster than senior engineer review bandwidth. When an agent opens a PR with a vague summary like 'Fixed the bug', reviewers still have to check out the branch, verify tests, inspect caller impact, and audit for subtle regressions.
What a Deterministic Verification Receipt Proves
Kronumos attaches a structured Proof-of-Fix Verification Receipt (available as terminal output, `--json` for CI pipelines, and Markdown tables for GitHub PRs via `--pr`) containing verifiable evidence from the actual run:
- Test Gate: exact before/after status on the real repository test runner.
- Static AST Audit: Tree-sitter hazard count before and after on modified files.
- Blast Impact: maximum risk level, affected exported symbols, and downstream caller count.
- Knowledge Crystal & Sub-Cortex Savings: whether a prior fix was reused and exact tokens/USD pruned.
- Deterministic Receipt Digest (`rcpt_...`) for audit trails.
“The fastest way to make AI-generated pull requests reviewable is to ship machine-verified proof of tests, AST safety, and blast impact alongside every diff.”
Frequently Asked Questions
Can CI pipelines consume Verification Receipts in JSON?
Yes. Pass `--json -q` to output structured machine-readable receipts directly in GitHub Actions or GitLab CI.
Audit your repository in milliseconds with zero LLM calls
Run native Rust Tree-sitter AST checks on Linux, macOS, and Windows PowerShell, or test in the browser.