You interrupt your own flow to check /context, racing to save your work before compaction eats it. That vigilance is a tax — and you can automate it away.
Generating technical documentation from a codebase is easy now. Trusting it isn't. Evidence-linked claims and human sign-off are the missing steps.
Compaction keeps a coding agent running by quietly deleting the why, so you become its memory. What gets lost, why it compounds, and the local-first fix.
A spec extracted from code reads what is there, not what was decided — so placeholders and fallbacks get promoted to intent. Sign-off is the missing step.
Execution memory has tooling. Decision memory is emerging. The behavior layer — what your product promises to do — is the one almost nobody has built yet.
Paste a prompt into Claude or ChatGPT, describe your product module briefly, and get a .pbc.md behavior spec you can view, edit, and commit to your repo.
CLAUDE.md and AGENTS.md tell agents how to work in your repo. They don't tell agents what your product promises. That's a different artifact — the PBC layer.
A step-by-step guide to writing a .pbc.md file for your product's most critical module. Start with plain Markdown; add structured blocks agents can read.
Shipping fast with AI agents feels productive. But the costliest mistake isn't bad code — it's building confidently when nobody wrote down what was decided.
PRDs capture intent. Tests verify assertions. Between them, there's no artifact tracking what the product promises — grounded in code, confirmed by humans.
AI agents have AGENTS.md, memory banks, harnesses, and monitors. They still lack the product context layer — what the product promises and what must hold.
Your agent ships code that passes review and still breaks a product promise. It is not a capability gap — it is the product context no rules file gives it.
Your repo has workflow instructions, session context, and feature specs. None of them answer what the product promises to do. That's the PBC layer.
A .pbc.md file opens in VS Code, renders on GitHub, reads like any Markdown doc. Drop it into pbc.stewie.sh and the same file becomes navigable UI.
