Skip to content

Architecture overview

Each wiki has three zones, plus a registry that lives outside every wiki and lists them all. The zones separate what you drop in from what the agent distills and from the operational state it keeps.

ZONE 1 · ENTRY POINTS Quick-notes quick-note Articles, PDFs article Transcripts voice-transcript LLM conversations claude-chat READ /ingest classify, dedup, distill WRITE ZONE 2 · STRUCTURED KNOWLEDGE Projects active work Documentation curated articles Resources references, lists People person pages Concepts companies, frameworks ZONE 3 · SERVICE, READ AND WRITTEN BY EVERY COMMAND manifest sha256 ledger log append-only hot.md last 20 touches sources per-source pages archives snapshots feedback behavioral rules LEGEND read write
Zone Contents Agent permission
Entry points Folders you drop sources into. Configured per wiki Read, add processed frontmatter, move per post_ingest rule
Structured knowledge Projects, documentation, resources, people, concepts (whichever you enable) Read and write
_service/ Manifest, log, hot list, source summaries, archives, feedback rules Read and write

Entry points are the boundary between things you saved and things the agent has read. Structured knowledge holds the distilled pages the agent writes and you edit. The _service/ folder holds operational state that the agent maintains and mostly stays out of your way.

The registry at ~/.claude/obsidian-wiki/wiki-registry.json lists every wiki and its absolute root path. The plugin reads it on every invocation to resolve which wiki a command targets. It is set at the first /setup-wiki run and records the shared vault_root where the docs at <vault_root>/_service/docs/ live. See Entry points and Structured knowledge for what each zone does.

For the whole system at once, the plugin folder, the registry, the shared docs, one wiki blown up to show its three zones and config files, and the command groups, see the panopticon view.

PLUGIN AND GLOBAL STATE · ONE PER USER obsidian-wiki plugin ~/.claude/plugins/obsidian-wiki/ commands · skills · templates · scripts · docs registry ~/.claude/obsidian-wiki/wiki-registry.json list of wikis · vault_root shared docs <vault_root>/_service/docs/ README + diagrams · refreshed by /upgrade Agent runs command files in Cowork or CLI READS ONE WIKI · REGISTER N OF THESE <wiki-root>/ three zones plus config + index at the root CLAUDE.md generic · identical for every wiki wiki-config.md YOUR config · entry points · structure · rules index.md auto-maintained page catalog ZONE 1 · ENTRY POINTS where you drop sources 99_Quick-notes/ 98_Other/ 4_Conversations/ (custom) POST-INGEST RULES move | keep | read_only SOURCE TYPES quick-note, article, claude-chat, voice-transcript, image, ... ZONE 2 · STRUCTURED KNOWLEDGE where agent writes pages 1_Projects/ 3_Documentation/ 2_Resources/ (custom) PAGE LIFECYCLE draft → reviewed → verified PROVENANCE PER CLAIM extracted | ^[inferred] | ^[ambiguous] ZONE 3 · _SERVICE operational state .manifest.json sha256 dedup log.md append-only hot.md last 20 touches sources/ per-source pages _archives/ snapshots entry-points/ moved sources feedback.md one-line rules custom-procedures/ multi-step hooks last two are user-authored; the rest agent-managed /INGEST TRACK COMMANDS · ALL TAKE A WIKI SLUG · ACT ON ANY WIKI VIA THE REGISTRY Daily loop /status /ingest /ingest-url · /ingest-claude /capture Maintenance /lint /cross-linker /archive · /restore /rebuild (rare) Use and refine /query [--visibility ...] /update /research /project (list|new|archive) Setup and teach /setup-wiki /upgrade · /update-docs /feedback /daily-note FOCAL POINT INGEST FLOW READS / TRACKS AGENT-MANAGED YOU EDIT

Two files at each wiki root drive everything: CLAUDE.md (generic boilerplate, identical across every wiki) and wiki-config.md (yours). Every command reads both on every invocation. See Commands for what each verb does.