🥫 PANTRY · Dev-docs cockpit
One installable server for the whole stack.
PANTRY is the BREAD stack's installable developer-docs and AI cockpit: one app that composes the layers (BATCH, GRAIN, MILL, PROOF) into a single server you drop into any project. It is an app, not a fifth layer: the neutral, project-agnostic sibling of this portfolio. Two composition roots wiring the same stack is a stronger reuse proof than one. And it's AI-legible, not AI-powered: PANTRY runs no model itself, it just makes a project legible to one, through plain files and endpoints an agent can read without a UI.
Live · the board is home, AI-retrieval (/llms.txt, /knowledge.json), the /map mindmap, ⌘K search, the framework docs, reference, catalog, and standards, plus an install kitAn app, not a layer
PANTRY doesn't sit in the batch → grain → mill → proof chain. It mounts all four, the same job this portfolio does, just without the personal branding.
The board is home
Reshaped so an installed PANTRY's front door is its own live PROOF plan board, not a stack pitch. The stack's own pitch moved to its /about. The home page is what's actually happening, right now.
Legible to an agent, not just a person
An installed PANTRY serves /llms.txt and /knowledge.json so an AI gets a direct, structured read on the project; a whole-codebase mindmap at /map (data at /map.json) gives a person the same view visually.
Drop it in anywhere
Verified installed against a scratch external project: bunx it into a repo and it reads that project's own plans/ folder.
The board-forward reshape, the AI-legible-not-AI-powered framing, and what PANTRY mounts are written up in the PANTRY plan that ships beside the code.
Part of the BREAD stack, alongside BATCH, GRAIN, MILL, PROOF, and CRUMB.
🤖 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 →