Obsidian sync model.runbook

Overview

BluTown holds operational state in Git. Platform knowledge on the NAS lives at /Volumes/AgentPlatform/knowledge. Obsidian should use two vaults, not a single merged folder.

Prerequisites

• NAS visible at /Volumes/AgentPlatform.
• Directory /Volumes/AgentPlatform/knowledge exists (create on NAS if your layout uses it as the wiki / notes root).

Operator steps

1. Mount AgentPlatform using your standard method (SMB, automount, Tailscale to NAS, etc.).
2. Obsidian → open BluTown repo root as vault.
3. Obsidian → Open another vault → /Volumes/AgentPlatform/knowledge.
4. Optional: pin both vaults; set Settings → Files & links consistently in each (wikilinks vs markdown links) to match how your teams author.

Sync model

Vault	Authority	Typical sync
BluTown	Git remote for operational runtime	git pull / git push per Git policy
/Volumes/AgentPlatform/knowledge	NAS + wiki / clone jobs	NAS backup, wiki mirror jobs, or Git clones inside that folder — not mixed into BluTown

Do not copy the whole NAS tree into BluTown to "combine" vaults.

Agents and OpenClaw / Blu

• Processes that read notes must use paths valid on that machine (e.g. mounted /Volumes/AgentPlatform/knowledge).
• If a helper HTTP API or skill is used, configure it in the owning repo; avoid one-off scripts committed under BluTown scripts/ when BuildKit or a service repo owns the behavior.

Cleanup and safety

• Do not use destructive deletes against NAS mirrors without NAS snapshot / backup discipline.
• Do not store secrets in Obsidian config or vault notes used for automation.

Related

• .obsidian/BLUTOWN-OBSIDIAN.md
• NAS-Knowledge-Vault.md (BluTown root)
• .obsidian/obsidian-cc-integration.md