The Operator Vault

The Promise

A six-folder Obsidian vault that survives eighteen months of running a real business — capture-first, AI-readable, ruthlessly minimal, and still the same six folders on day 547 as on day one.

The One-Sentence Setup

Most operators think Obsidian failed them because they "couldn't stick with the system" — the actual problem is they installed a knowledge-management hobby instead of a workbench, and the workbench has six folders, four file conventions, and two plugins.

The Core Insight

Most operators bounce off Obsidian within thirty days. The failure isn't discipline — it's the templates. PARA, Zettelkasten, Johnny.Decimal, the r/ObsidianMD plugin maze, the YouTube-aesthetic dashboards — these systems were designed for academics, students, and personal-knowledge-management hobbyists. None of them were designed for a multi-unit founder who needs to walk into a vendor call in nine minutes with the right context loaded. The Operator Vault inverts the question. We don't ask "how do I organize my second brain?" We ask "what's the smallest surface that lets AI load context, log decisions, and stay out of my way?" The answer is six folders. Anything more is procrastination dressed as productivity.

The Mechanism

1. Install Obsidian + Sync ($4/month)

What: The base app (free) plus official Obsidian Sync at $4/month billed annually. How: Download Obsidian. Create an account. Subscribe to Sync. Create one remote vault with an encryption password. Install Obsidian on iPhone and sign in. Do not store the vault inside iCloud Drive — iCloud silently overwrites notes on conflict and operators lose work that way every week. Miss this and: voice memos transcribed on iPhone never reach the vault, the system stays desktop-only, and the entire Capture surface dies.

2. Create the six folders, in this order

What: 00_Inbox/, 10_Projects/, 20_People/, 30_Decisions/, 40_Reference/, 90_Archive/. How: Use the leading numbers. They auto-sort in the sidebar and free the alphabet for actual note titles. Each folder does exactly one job — Inbox captures, Projects holds one folder per active project with a single Project — [Name].md as the source of truth, People holds one file per person, Decisions is an append-only log, Reference is rarely-touched playbooks and SOPs, Archive is where finished projects retire (never deleted, sometimes resurrected). Miss this and: the vault drifts into nested-folder cosplay and the operator can no longer answer "where does this go?" in under two seconds.

3. Install exactly two plugins — Templater and Dataview

What: Templater for repeatable note structures. Dataview for ad-hoc queries like "show every open Project note touched this week." How: Settings → Community plugins → install Templater, install Dataview. Stop. The community plugin store is a casino — every tab promises to be the one that "completes" the vault. None of them do. Resist installing a third plugin for ninety days. After ninety days, if a real friction has appeared, install one more. Obsidian Git is the only commonly-justified third for engineers; everyone else stays at two. Miss this and: the operator spends the next four weekends configuring plugins instead of running the business.

4. Write the first five notes

What: Reference/Identity.md, Inbox/Context.md, one Project note, one Person note, one Decision line. How: Identity is one paragraph — who you are, what you run, how you make decisions. Context is one paragraph — what's active right now, this quarter, this week. The Project note uses a four-section template: Goal, Status, Open Questions, Next Action. The Person note matches the format from The Memory Architecture so AI can load it before calls. The Decision is one line: 2026-05-30 · switched ops platform from X to Y · alternatives: A, B · why: lower per-unit cost at our volume. Miss this and: the vault is empty when AI tries to read it, and AI without context is just a chatbot.

5. Set the Sunday 30-minute ritual

What: A recurring calendar block, Sunday, 30 minutes, non-negotiable. How: Empty Inbox (file, delete, or convert to a Project/Decision). Update Context.md to reflect the coming week. Append any Decisions that happened ad-hoc. Move finished projects to 90_Archive/. That's it — thirty minutes, four moves, every Sunday. Miss this and: the vault becomes a graveyard inside ninety days, and the operator quietly stops opening it.

The Pitfalls

PARA / Zettelkasten / Johnny.Decimal cosplay. Borrowing systems designed for academics and PKM hobbyists. Fix: delete the nested taxonomy, collapse to the six folders, and resist the urge to "extend" the system for at least ninety days.

Plugin sprawl. Eleven community plugins, three of which conflict, none of which the operator uses daily. Fix: uninstall everything except Templater and Dataview. Set a calendar reminder ninety days out to reconsider a third — and only if a real friction surfaces between now and then.

The wrong daily-notes pattern. Forcing a daily note when there's no actual journaling practice. Fix: skip daily notes unless you genuinely write to one every day. Most operators don't; the Inbox and the Sunday ritual cover the same job with less ceremony.

Vault inside iCloud Drive. The most common silent data-loss bug in the entire Obsidian ecosystem — iCloud overwrites notes on conflict. Fix: move the vault out of iCloud immediately, use Obsidian Sync ($4/month) or Git, never both at once.

Treating the vault as the dashboard. Trying to make Obsidian the KPI surface, the CRM, and the project tracker. Fix: the vault is a writing surface, not a status board. KPIs live in Vercel, Supabase, or whatever business system actually owns the numbers. The vault references those systems; it doesn't replace them.

The Drill (this week)

Thirty minutes, one sitting. Install Obsidian. Subscribe to Sync. Create the six folders with the leading numbers. Install Templater and Dataview — only those two. Write Identity.md (one paragraph: who you are, what you run). Write Context.md (one paragraph: what's active this quarter and this week). Open one Project note for the most important thing in flight right now and fill the four sections — Goal, Status, Open Questions, Next Action. Open the calendar. Create a recurring Sunday block titled "Vault — 30 min." That's the whole drill. If it takes longer than thirty minutes, you're over-configuring.

The Tools

Tool	Role	Cost
Obsidian (desktop + iOS)	The vault app itself	Free
Obsidian Sync	Cross-device sync, end-to-end encrypted	$4/month annual
Templater	Repeatable note structures	Free community plugin
Dataview	Ad-hoc queries across the vault	Free community plugin
Obsidian Bases (core, 2026)	Database-style views of notes by property — use sparingly, only if the Sunday ritual surfaces a real need	Free, built in
iPhone Voice Memos → Shortcuts	Voice capture into 00_Inbox/	Free
Git (alternative to Sync)	Version control for engineers who prefer it	Free

Verala stays vendor-neutral on most tooling, but Obsidian Sync over iCloud is not a preference — it's a data-integrity call. Use Sync, or use Git. Never both, never iCloud.

Cross-references

The Operator Vault is the implementation layer of two upstream frameworks:

• The 4-Surface AI Stack — the vault is the canonical Remember surface. Without it, the other three surfaces have nowhere to write.
• The Memory Architecture — the file conventions inside 20_People/, 30_Decisions/, and Identity.md are how Claude actually loads long-term memory. The vault is the file system that architecture runs on.

Forward to:

• The Voice Memo → AI Loop — 00_Inbox/ is the landing zone for transcribed voice memos. The vault is one half of that pipeline; the loop is the wiring.

---

One framework. One drill. One week at a time.

The Operator Stack is the architecture. Verala is the practice that runs it on your own communication delivery — voice, pitch, pause, presence. One foundation per week, until it's automatic.

Take the free 5-Foundation Voice Audit → · Book a 30-min intro call →