Available now · Two-way — Founder OS reads the vault and writes back to it
Obsidian integration
Read your vault as a state source and mirror the reconciled company state back into it as ordinary Markdown.
Data flow
What Founder OS reads and writes
Stated in both directions, because an integration that only reads and one that also writes are very different commitments.
Reads from Obsidian
- Markdown notes, including frontmatter and wiki-links
- Goals, projects, tasks and decisions expressed as ordinary prose
- Meeting notes and daily notes, with their dates
- Backlinks, used as evidence when the reconciler merges entities
Writes back to Obsidian
- A mirrored view of company state as plain Markdown files
- Project and goal pages that stay current as state changes
- Links back into the notes each fact was derived from
Setup
Connecting Obsidian
Roughly ten minutes, most of which is deciding what to connect rather than doing it.
- 01
Sign up and open Apps in the dashboard.
- 02
Add Obsidian as a state source and point it at your vault directory.
- 03
Run the first observe pass — the engine reads existing notes and builds your initial company state.
- 04
Review what it extracted; the write gate has already rejected anything it was not confident about.
- 05
Turn on mirroring, and the reconciled state is written back into the vault as Markdown you can read without Founder OS.
In detail
How the Obsidian adapter actually works
Obsidian is the state source Founder OS shipped first, and it is the cleanest illustration of the adapter model: your vault is not imported, migrated, or locked in. It is read where it already lives. Founder OS parses the notes you write anyway — daily notes, meeting notes, project pages — and lifts the goals, projects, tasks, decisions and people out of them as first-class entities in the Company State Engine.
The interesting half is the return trip. Once state is reconciled across every source you have connected, the renderer writes it back into the vault as ordinary Markdown. Nothing proprietary, nothing that needs Founder OS running to read. If you cancel tomorrow, the vault is still a vault — the mirrored pages just stop updating.
Because everything is plain text, the hygiene layer matters more here than anywhere else. The same project written as "Q3 launch", "launch" and "the launch" across three months of notes is one entity after reconciliation, not three. The write gate rejects updates it cannot support from what the notes actually say, and decay surfaces the project you stopped writing about six weeks ago instead of leaving it looking active forever.
The mechanics behind every adapter are the same — see the feature breakdown for the state engine, the reconciler and the approval gate, or an illustrative scenario for what this looks like across a working week.
Other integrations
Point Founder OS at your Obsidian
The free plan covers one state source. Connect it, run the first observe pass, and look at what the engine extracted before deciding anything.
Free tier, no credit card. We reply to every message within 24 hours on business days.