Agentic Coding #1 — Vault Architecture
Computer-Inspired Vault Architecture
All Zettelkästen are structured identically. The directory structure is modeled after a computer with three main areas:
IO — Input/Output
- Input: Everything that comes in from outside. A kind of inbox — even when a new document is created manually, it ends up here.
- Output: Typically lists and views of the various documents. This is where the navigable overviews reside, through which one moves around the vault.
Mem — Three Storage Areas
Three storage areas with different levels of persistence:
- Stack — Short-term focus. When you know which documents you want to work on right now, they go on the stack. External scripts can access this area and find the documents placed there. It is simply a storage location for "this is what I'm working on right now."
- RAM — Medium-term working memory. Things that are in progress — that need to be accessed repeatedly, but may still change along the way. The working memory for what is currently relevant.
- ROM — Long-term permanent storage. Everything that is meant to stay in the vault over a longer period ultimately ends up here.
Proc — Processing
This is where templates and scripts reside — the tools the vault works with.
