Every working AI stack needs a place where the human end lives — a layer that is editable by hand, readable by tool, and not held hostage by any single piece of software. For the studio, that layer is Obsidian sitting on top of a folder of markdown files.
Obsidian is, at the lowest level, just markdown. The files sit in a folder you own. There is no database, no proprietary export, no SaaS to escape from. You can run a script across them, point an MCP server at them, hand the same folder to a different note app next year, and nothing breaks. That is the whole pitch.
What Obsidian adds on top is shape — backlinks, a graph, a search that respects the way notes actually cross-reference each other. None of it interferes with the underlying files. The AI tools the studio uses — Claude Code, custom MCP servers, scheduled scripts — read the same markdown the human is reading. There is no separate “context” the agent has to be told about. The agent just reads the folder.
Two consequences fall out of this. Notes and AI context become the same set of files, and stay current by definition. And the cost of changing AI tools collapses, because the data layer does not move when the tool changes.
Filed May 2026 · Folkestone