File over app. Master edition.

After the long detour through Obsidian, MCP servers, RAG pipelines, and agent frameworks, the master position turns out to be HTML. But the HTML on the right edge of the bell curve is not the same as the HTML on the left.

I was all in on file-over-app when I read Steph Ango's post in 2023. I messaged friends and family about Obsidian. I built a vault. I installed plugins. I customized templates. I tried Tana, Roam, Anytype. I made my own folder taxonomies. I bought Readwise. I rebuilt my workflow three times.

And then I became the meme.

The meme

The PKM Bell Curve has three positions. The beginner uses Apple Notes because it's accessible. The intermediate designs complex systems to get as many benefits as possible. The master uses Apple Notes because they realized it was all they needed.

I was the intermediate. I am, on bad days, still the intermediate.

The hidden flaw

The meme has a subtle problem. Apple Notes isn't actually the master position. It's the position the meme imagines mastery looks like, because Apple Notes is the canonical "simple" notes app most people have seen.

Apple Notes is platform-locked. Lossy on export. No provenance. No structured data. Can't be opened by anything that isn't Apple. If you tried to open an Apple Note in 2035, on a Windows laptop, or in an AI assistant, or on a phone you don't own, you'd get nothing.

The master position can't be a thing whose simplicity is bought by platform lock-in. The genuine master pick is HTML.

The LLM-era bell curve

Redrawn for the AI-assisted era:

The beginner copy-pastes from ChatGPT into a folder. Loses the source. Forgets which model. Can't find anything six weeks later. But it works.

The intermediate runs MCP servers, agent frameworks, RAG pipelines, vector DBs. Cursor plus Claude Code plus Codex plus four prompt libraries plus an Obsidian vault to capture everything plus three different conversation-export plugins, half of them broken.

The master has a workflow shaped like the beginner's. ChatGPT to Capsule to folder. The LLM does the work. The Capsule holds the output.

The punchline

The cleverness of the bell curve is that the master and the beginner end up at the same shape. The difference is what they know about it. The beginner doesn't know they're losing the source. The master knows, and engineered the substrate so they don't.

A Capsule is HTML informed by the long detour. It is what you reach for after you've tried the complex stack and remembered that the substrate has to be a single, self-contained, archive-able file you can hand someone in 2035 without explaining what software they need first.

HTML at both ends of the bell curve. But the HTML on the right edge is HTML with a manifest, an integrity hash, a structured data block, declared capabilities, and a runtime that does the things the intermediate needed plugins for. The master position is not "use less." It's "use the right substrate, in a way that survives."

If you're in the middle right now, I see you. The discipline that gets you to the right edge is not throwing the tools away. It's building the substrate that doesn't need them.