One Obsidian vault. A clear folder hierarchy. Areas hold your ongoing work, projects serve areas, and archives keep what is finished. This is the backbone of a personal operating system that both you and AI agents can understand and maintain together.
I built this as a starting structure for a personal knowledge vault that both I and AI agents can read: one AGENTS.md for instructions, plain folders for notes, and nothing clever in between.
Open the folder as a vault in Obsidian and start your agent session. Agents will read AGENTS.md and follow the system you define.
The 300-line ceiling on memory files forces you to archive what is no longer current, and that discipline alone makes agents far more useful.
About this template
A file-based personal OS.
This is a generic template adapted from a personal life-system vault used daily, with all personal detail removed. The system provides three verified scripts: check.py, vault-link.py and paths-check.py.
Provenance. Everything here is plain Markdown that you, your team and your AI agents can read and update together. The folder structure follows the PARA method (Projects, Areas, Resources, Archives) adapted for AI collaboration.
What I learned
Building this taught me that the structure matters more than the tools. A good naming convention is worth a thousand tags. The 300-line ceiling on memory files forces you to archive what is no longer current, and that discipline alone makes agents far more useful. The append-only log turned out to be the one source of truth I could always trust.
Key principles
Areas are ongoing responsibilities that never truly finish
Projects serve areas and have a done state
Memory stays under 300 lines by archiving old truths
Log is append-only and never edited
MIT licence. Built for humans and agents. Deployed at rin.contact
Start building your vault.
Clone the template, run the setup scripts, and open it in Obsidian. Your agents will read AGENTS.md and follow the system you define.