DEV Community

Cover image for The vault is the memory, not the tool
Jens Reynders
Jens Reynders

Posted on

The vault is the memory, not the tool

An AI assistant is only as useful as what it can remember, and chat history doesn't count. Close the window and it's gone. The actual fix isn't a smarter prompt, it's giving the assistant a place to keep things: a folder of plain markdown files I own, structured on purpose, that any model can read.

I know a lot has been written about Obsidian already, this is not about that. I use it on top of the vault, not because Obsidian is special (it's a solid markdown editor with backlinks), but because the vault underneath is just files on disk, organized the way my actual job needs it to be organized.

Structure built for being a Tech Lead, not for the AI

I organize the vault loosely on PARA: projects, areas, resources, archive. The folders doing the real work exist for the files, not for the AI: meetings/ and people/ sit at the top level because leading a team needs them, and every meeting note links back to the people in it, so each person's file builds itself out of backlinks with no separate log to maintain.

50-writing/ gets the same treatment: it could have lived under areas as one more ongoing responsibility, but it runs on its own pipeline, seeds to drafts to published, and burying that a level deep would have hidden it. It earned a root folder. 00-inbox/ is the other exception, the one folder with no rule about what belongs there. A quick-capture skill drops a thought in with one line, no folder decision required in the moment, and I triage it into the right place later.

What the AI does is help me uphold that structure. When I open a 1:1 prep, it already has the last five meetings and the running context on that person, because the structure surfaces it without being asked. And when I'm not sure where something belongs, it tells me, keeping a new note from drifting into the wrong folder just because that was faster in the moment.

One file, _claude/conventions.md, documents the layout and naming rules. Every project's instructions tell the assistant to read it first. That single habit is what makes the assistant behave the same way across sessions and even across different projects: I run separate Cowork projects for Tech Lead, PDP, and Writing, each scoped to its own slice of the vault, and switching projects is switching hats.

Why not wherever the knowledge already lives

The obvious move is to plug the assistant into wherever the team already keeps things: Notion, Confluence, whatever. I tried that instinct and dropped it.

Markdown wasn't a new habit for me. I used to keep notes in Bear, plain markdown there too. Moving to a vault was the same habit with a folder on disk instead of an app's database behind it.

That's the real angle: owning something, in a format basic enough that nothing can lock it up. Notion doesn't store a page as text, it stores it as a tree of proprietary "blocks" you can only get to through Notion's app or API. Confluence does something similar. Markdown has no such lock-in, so the assistant just reads the file, no translation layer in between. Tools don't last, files do. Notion could change its API tomorrow, Claude could stop existing next year. A folder of .md files survives all of it.

It also travels. Obsidian's git plugin commits and pushes the vault on its own, so backup and version history come free, no extra service to pay for or trust. I write on a second machine sometimes, and it's a git pull away: same files, same conventions.md, same context the assistant reads first, on either machine.

Building this took a few hours: folder structure, the conventions file, one project's instructions. It paid for itself the first time the assistant nailed a task because it had read the right file instead of guessing. The side effect is a personal knowledge base that's better structured than any note system I've had before, because the assistant enforces the structure instead of letting me get lazy about it. It doesn't need Obsidian, or Cowork, or any specific tool. It needs a folder, a rulebook file, and the discipline to make the assistant read the rulebook before it does anything else.

Top comments (0)