Add Obsidian as a tracked tool directory¶
- Date: 2026-03-09
- Status: Accepted
- Tags:
structuretooling
Context¶
The repo tracks AI development tools (Claude Code, Cursor, Windsurf, Gemini). Obsidian is the vault system powering LifeOS — a personal operating system managed almost entirely through AI tooling. Claude Code interacts with the vault on every session: reading notes, creating daily notes, processing the inbox, writing session logs, and surfacing task context.
Without a dedicated directory, Obsidian integration decisions and patterns
were undocumented and spread across claude/ config files, with no clear
home for vault-specific conventions or the MCP setup that bridges Obsidian
and Claude Code.
Decision¶
Add obsidian/ as a first-class tool directory, parallel to claude/,
cursor/, etc. It will contain:
decisions/— Obsidian-specific ADRs with their own numbering sequencemcp/— MCP server config for the Local REST API pluginplugins/— Plugin configurations and notespatterns/— Documented AI-assisted vault workflows
The adr-check CI workflow is updated to require an ADR when obsidian/
is modified, consistent with all other tool directories.
Alternatives Considered¶
| Option | Why Rejected |
|---|---|
Document Obsidian inside claude/ |
Obsidian is a first-class tool with its own plugins, config, and decisions that don't belong under Claude |
| Skip tracking Obsidian entirely | The MCP integration and vault conventions are non-trivial; losing this context would mean re-deriving it repeatedly |
| Flat files at repo root | Doesn't fit the established tool-per-directory structure |
Consequences¶
Positive:
- Obsidian integration is self-documenting and version-controlled
- Vault conventions and MCP config decisions survive session resets
- ADR requirement enforces discipline when the integration evolves
obsidian/decisions/gives Obsidian its own decision lineage, separate from repo-level ADRs
Negative / Trade-offs:
- Obsidian config is not source-controlled in the same way as code tools — this repo is a reference, not the live config
- Requires keeping
obsidian/in sync when plugins or vault structure changes
Ongoing obligations:
- Update
obsidian/when MCP config, plugin setup, or vault structure changes significantly - Log an Obsidian ADR for decisions specific to vault conventions or plugin choices
ADRs are immutable. If this decision changes, create a new ADR with status "Superseded by" pointing here, and update this record's status.