Skip to content

Obsidian ownership — BluTown and /Volumes/AgentPlatform/knowledge

1. Inventory (two vaults)

Vault Path Role
A — Operational BluTown Git repo root (e.g. $ESTATE_ROOT/BluTown) bus/, library/, runtime/ pointers, Beads, operator docs
B — Platform knowledge /Volumes/AgentPlatform/knowledge NAS wiki mirrors, research, long-form reference (when mount is present)

Record both paths in operator onboarding. Do not symlink vault B into vault A (repo policy).

2. NAS mount

  • Expected mount: /Volumes/AgentPlatform.
  • Verify: ls /Volumes/AgentPlatform/knowledge before opening vault B in Obsidian.
  • If your org uses a different volume name, update NAS-Knowledge-Vault.md and .obsidian/BLUTOWN-OBSIDIAN.md once; avoid scattered copies.

3. Obsidian setup

  1. Open folder as vault → BluTown root.
  2. Open another vault → /Volumes/AgentPlatform/knowledge.
  3. Bookmarks: see .obsidian/bookmarks.json (BluTown vault) for quick links to NAS-Knowledge-Vault.md, AGENTS.md, handoff files.

Self-hosted sync (optional)

  • Obsidian Sync (paid) or community plugins (LiveSync + CouchDB, Remotely Save, etc.) apply per vault. If you sync BluTown via Git, avoid a second cloud sync that fights Git unless you know the conflict model.
  • Folder sync (Syncthing, Resilio) on the NAS knowledge tree is outside Obsidian; treat as filesystem sync.

4. Agent and IDE access

  • CLI / skills that read markdown must use absolute paths valid on the host (BluTown path and, when mounted, /Volumes/AgentPlatform/knowledge).
  • MCP or other integrations: configure in the owning repo; vault paths belong in operator config or env, not secrets in notes.

5. macOS permissions

  • Grant Full Disk Access if Obsidian or terminal tools cannot read under Documents or the NAS mount.
  • Fix ACLs only with operator-approved chmod / chmod -N procedures; do not strip protections on shared NAS roots without a runbook.

6. Backup

  • BluTown: Git + remote.
  • NAS knowledge: NAS snapshots / backup policy for AgentPlatform.

7. Validation checklist

  • [ ] Both vaults open when NAS is mounted.
  • [ ] NAS-Knowledge-Vault.md in BluTown describes the two-vault pattern.
  • [ ] No duplicate “combined” tree inside BluTown for NAS content.

See also: obsidian-sync.md, obsidian-cc-integration.md.