🥫 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 BATCH, GRAIN, MILL, and PROOF into one server you drop into any project. Its review cockpit can host CRUMB tours from its own folder or read the tours already mounted by a project it proxies. 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 · installation verifiedWhat PANTRY gives a project
An app, not a layer
PANTRY sits outside the batch → grain → mill → proof chain. It composes those four core layers, like this portfolio without the personal branding. Its review cockpit can host CRUMB tours or read tours from the project it proxies.
The work board opens first
The installed app opens on the host project's plan board and working-with-AI surfaces. Its docs and the stack overview stay one step away, while the home page shows the work in that repo.
The project has two useful views
The server exposes /llms.txt and /knowledge.json for an AI agent. People can follow the codebase mind map at /map, and tools can read the same graph from /map.json.
The install kit reads the host repo
The kit adds the project instructions, standards, and initial plan structure. I tested it in a separate project, where it read that project's own plans folder.
From install to first use
PANTRY is installed inside the project you want to work on. These are the documented commands I used to scaffold its plan board, check the starter plan, and start the local cockpit.
bun add -d @tjakoen/pantry@github:tjakoen/pantry#mainbunx pantry init --kitbunx proof checkbunx pantry serveOpen the printed local URL. The board reads the host project's plans folder; PANTRY does not copy or replace the plan files.The design
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.
Where it sits in the stack
Part of the BREAD stack, alongside BATCH, GRAIN, MILL, PROOF, and CRUMB.
AI helps me write and review. I direct the work, test the result, and answer for what ships. How I work with AI →