📋 PROOF · AI plan board
Files are the source. The board just shows it.
PROOF is the stack's AI plan board: a standardized way to write an AI's development plans as markdown files, and a board that renders what those files already say. Files are the source of truth; the board is a projection of them, never the other way round. Delete PROOF and the plans stay readable markdown.
Live · the core parser, the board, the check/init tooling, and the live SSE board are shippedPlans are files
Each plan is a markdown file with a small frontmatter (status, track, depends, owner). The AI edits them with its native tools, no new workflow.
The board never edits
The machine index is derived by the parser, never hand-maintained. A hand-edited index beside the markdown would be dual bookkeeping, so PROOF refuses to let that happen.
A small schema, on purpose
Six fields, no more. A heavy schema makes the AI do bookkeeping instead of work, which would undercut the whole point.
Mostly for the human
The honest split: most of the value is a person watching the AI's intent, not the AI going faster. The AI never reads the board itself, only the files.
Shipped: the core parser, the kanban-style board, the check/init command-line tooling, and the board itself streams live over SSE (this page's own /plans board updates as the files change, no refresh needed). The canonical design, the schema, and what's next are written up in the PROOF plan that ships beside the code.
Part of the BREAD stack, alongside BATCH, GRAIN, MILL, CRUMB, and PANTRY.
🤖 Built with Claude. I don't prompt and pray, I prompt and prove. Every commit here is co-authored with an AI, on purpose. How I actually work with AI, receipts and all →