ProofFlow MCP server

ProofFlow

English | 简体中文

Agent Work Ledger for AI coding.

Vibe coding is fast. Blind trust is not enough.

ProofFlow makes AI-generated work reviewable, traceable, and reversible by recording the full chain from work contract to proof packet: contract first, record the algorithm decision, declare the cost budget, snapshot the code state, bind claims to evidence, evaluate done criteria, then export an auditable packet.

Latest release: v0.1.8 - Agent Work Ledger for AI coding

▶ Watch the 72s demo: From AI agent claims to verifiable Proof Packets

Demo asset (deferred): The end-to-end dogfood Demo_Asset GIF and the

VSCode_Channel inline audit / Approve Gate screenshots for the v0.1.x

dogfood-and-channel-polish milestone are deferred to the next dogfood cycle

(no capturable VS Code window in this milestone). Tracked in

PLANS.md#vscode-channel-screenshots-deferred-from-v0-1-x-dogfood.

📦 Example Proof Packets: code review · issue triage · agent work ledger · ledger dogfood

Maintainer workflow: docs/maintainerevidenceworkflow.md

Agent Work Ledger guide: docs/agentworkledger.md

Ledger Risk Hints: docs/ledgerriskhints.md

5-minute MCP quickstart: docs/ledgerquickstartmcp.md

Ledger PR comment template: docs/examples/prcommentagentworkledger.md

AgentGuard semantic rules: docs/agentguardsemanticrules.md

Agent Work Ledger

ProofFlow is not only a PR review helper. It is a local-first ledger for AI coding work. A Ledger Case captures the workflow before, during, and after an agent changes code:

forbidden actions, required tests, done criteria, evidence requirements, algorithm requirements, and cost budget.

1. Work Contract - record the objective, repo path, allowed scope,

alternatives, invariants, and forbidden approaches before implementation.

1. Algorithm Decision - record the selected approach, rationale,

before expensive work begins.

1. Cost Budget - declare token, API, GPU, CPU, runtime, or iteration limits

diff hash so reviewers know exactly what code state was examined.

1. Snapshot - capture the git diff, changed files, HEAD SHA, base ref, and

or other artifacts as searchable evidence.

1. Evidence - store command output, test output, diffs, notes, screenshots,

trusted.

1. Claim - require every agent claim to bind to evidence before it is

cost budget, scope boundaries, missing evidence, unaccepted risks, and non-blocking Risk Hints for suspicious routes.

1. Evaluation - deterministically check required tests, algorithm decision,

timeline, snapshots, claims, evidence, evaluation, decisions, and remaining risks into markdown.

1. Proof Packet - export the contract, algorithm decision, cost budget,

Main chain: Work Contract -> Algorithm Decision -> Cost Budget -> Snapshot -> Evidence -> Claim -> Evaluation -> Proof Packet. This keeps the core product invariant sharp: no Case, no workflow; no Evidence, no trusted Claim; no done criteria evaluation, no quiet success.

Shortened. The full README is on GitHub.