THE FLAGSHIP SYSTEM
Your whole company. One vault. Alive.
A complete operating structure for a one-person business — folders, templates, file-creation rules, and a closed schema that keeps it all true over time — installed into your own Obsidian in an afternoon.
30-day no-questions refund · instant download · yours forever
capture → file → map → an AI reading the vault
Six months of design, so you don't spend them.
BEFORE
You run the business from memory. Decisions live in chat histories, money lives in a spreadsheet you dread, processes exist only as habits. Every new tool starts from zero.
AFTER
Every part of the business has a place, every place is linked, and the maps show you the whole machine at a glance. When you ask an AI for help, it reads your actual business — structure, decisions, numbers — instead of guessing.
I built this because I had to. I have an ADHD brain running a one-person company: if the business lived in my head, the business was in trouble.
And if you've abandoned a stack of planners and half-built vaults and quietly concluded you're the problem — I know that shame cycle from the inside. You're not the problem. Systems that demand a maintainer are.
About six months of design later, nothing here depends on me remembering it — or on you remembering it. Then people kept asking for the structure, so it's packaged, sanitized, and installable so you don't spend the six months.
Separation by metadata, not walls.
Most tools sell you the wall: one workspace for the business, another for your life. There's a TV show about where that logic ends — Severance — and it's told as horror for a reason. An employee can be severed; the person who runs everything can't. Every decision you make crosses the line: the book highlight that becomes a campaign, the family trip that moves the sprint.
In practice, the wall costs you three specific things: no search across, no links across, and a where-does-this-go decision taxing every single capture.
So Indexed Brain separates with metadata instead. One vault. Capture first — templates pre-fill the properties, so it takes seconds — and classify later, reversibly, when you actually know what a thing is. The same metadata is your privacy boundary with AI: point it at one folder or at everything; scoped, deliberate, yours.
Honest filter: some people genuinely focus better behind hard walls — separate vaults as separate modes. If that's you, this architecture will fight you, and you shouldn't buy it.
The honest problem with this category.
The productivity world has a critique it refuses to engage: serious thinkers have argued, with evidence, that the clearest output of most note-taking systems is more note-taking. Beautiful graphs that produce nothing. Systems that become the hobby.
They're right — and Indexed Brain is built as an answer, not a denial. This isn't a note-taking philosophy. It's an operating structure judged by exactly one output: the running company on top of it. Maps that surface your next bottleneck. Files an AI can act on. A structure that produces work — or it's furniture.
The critics have a second line too: we don't have a capture problem, we have a processing problem — captured notes that are never used again are hoarding with extra steps. Also right. That's what the maps are for: they're the processing layer, where captured material gets connected, seen, and turned into the next decision. Nothing here exists to store more. It exists to surface what you already know, when it matters.
How it stays true.
What actually happens inside Obsidian
The whole system is plain .md files and folders with YAML properties, plus .canvas maps. Nothing proprietary, no accounts on our side, no lock-in — open the vault in any editor and it's still entirely yours.
Why it can't quietly rot
Every file type has creation rules. Tags and properties come from a closed registry — a fixed vocabulary, not a suggestion. New files inherit their shape from templates. Systems degrade when they rely on discipline; this one relies on schema.
Why strict rules mean less work, not more
Pre-built systems usually die of one thing: "it became work to keep up with it." So the rules here are decisions already made — you never re-decide where a file goes, what to tag it, or how to name it. Templates pre-fill the metadata, so capture takes seconds; classification happens later, or not by you at all. If logging a thing is more work than remembering it, a system dies — so logging isn't allowed to be work.
Why AI can enforce it
Because the schema is closed and machine-readable, an AI can police it — validate frontmatter, refuse invented tags, file strays where they belong. PARA, LYT, and every other organizing philosophy hands you principles, and principles can't be enforced. A schema can. That's the honest version of "it doesn't degrade": rules are conventions until something checks them — here, something checks them, and the janitorial work isn't yours.
If Obsidian disappeared tomorrow
You'd still have a folder of plain, readable markdown — organized, searchable, portable to any editor. The structure doesn't depend on plugins to survive; the few modules that use them for dashboards name them plainly.
What's inside.
The spine
The full folder architecture (everything except the finance module, which is its own product), the tag and property registry, note templates, journal structure, and the MOC home menu. The skeleton everything hangs on.
The file-creation rules
The part no template store ships: exactly how new files enter the system, so it's as clean in month six as on day one.
The setup guide and walkthrough
Ships as .md, which means it's AI-readable: paste it into your assistant and let it walk you through your own install. Fresh-vault path, no prior Obsidian expertise assumed beyond willingness.
Operating Maps — the layer on top.
Living .canvas maps wired to your actual operating files: business model, offers, pricing, tool stack, operations. Click a node, the real file opens; update the file, the map is current.
Sold as an add-on to the structure — never standalone — because a map with nothing underneath is a poster.
The free Light preview exists to show the difference on purpose: the static version is what everyone else sells.
to a real file
How it installs.
Get Obsidian. It's free and runs locally on your machine.
Download Indexed Brain and drop it into a fresh vault.
Follow the walkthrough — replace placeholder content with your business, one area at a time.
No accounts on our side, no lock-in: it's your vault from minute one.
Three ways to end up with a system.
| Criterion | Build it yourself | Buy a static template | Get Indexed Brain |
|---|---|---|---|
| Time | Months of design, trial, and error | An afternoon of filling boxes | An afternoon of setup |
| What you get | Your own conventions — enforced by no one | A pretty structure that starts rotting on day one | Structure + rules + registry + living maps |
| AI-readability | Maybe, if you designed for it | Accidental at best | By design |
| Six months later | Depends entirely on your discipline | Abandoned (you've seen this movie) | Same schema, still clean |
| Price | Free — your time isn't | $79–$199 typical | $[X] |
Whether this is actually for you.
For you if
- You run — or are building — a one-person business.
- You're willing to work in Obsidian and plain files.
- You'd rather own your system than rent another dashboard.
Not for you if
- You want a hosted app that does it for you.
- You won't touch plain files.
- You focus better behind hard walls between work and life.
- You're looking for a note-taking method rather than an operating structure.
If none of the "for you" lines describe you, close this page with a clear conscience — the free guides at ricardona.dev will serve you better than a purchase you'd refund.
The system in the demo is the system that runs a real business — the same vault, around six months of design iterations, in daily use, documented in public at ricardona.dev. What you download is what I run.
One purchase. Yours forever.
One-time purchase. Instant download. Yours forever, modify freely. The structure sells alone; the bundles live on the Pricing page.
30-day no-questions refund — if it doesn't fit how you work, say so and it's refunded.
A human answers your email.
The four people ask first.
Do I need Obsidian?
Yes. Indexed Brain is a structure of plain files designed to be opened in Obsidian, which is free and runs locally. If you won't install it, this isn't the right purchase — that's a real filter, not a soft one.
What exactly do I download?
A folder. The full architecture, the tag and property registry, note templates, journal structure, the MOC home menu, the file-creation rules, and the setup guide — all as plain .md files you drop into a fresh vault.
What does an AI actually get to see?
Exactly what you point it at. Because separation is by metadata rather than walls, you can scope an assistant to one project, the whole business, or the finances only. The structure also works with zero AI — AI-readability is a property, not a dependency.
Refunds?
30 days, no questions. If it doesn't fit how you work, say so and it's refunded.
Six months of system design. One afternoon of setup.
30-day no-questions refund · instant download · a human answers