BluTown Obsidian — vault map

Role: Operator UI only — approved_as_operator_surface, canonical_truth: false. Full ruling: AGENTS.md (obsidian_role, obsidian_policy). Obsidian must not become a third knowledge canon.

This directory (Git repo BluTown) is vault A: operational control plane — bus/, library/, curated catalogs; not NAS mirror.

Vault B — NAS platform knowledge (required companion)

Path: /Volumes/AgentPlatform/knowledge

• Same machine: open as a second Obsidian vault (Obsidian can keep multiple vaults in the vault switcher).
• Prerequisite: NAS share mounted so /Volumes/AgentPlatform exists (see workspace AGENTS.md / NAS config).
• Do not symlink knowledge into this repo (platform policy: no repo symlinks for content trees).

Operator quick steps

1. Mount AgentPlatform (SMB / Tailscale / your standard path) until ls /Volumes/AgentPlatform/knowledge succeeds.
2. Obsidian: Open another vault → Open folder as vault → select /Volumes/AgentPlatform/knowledge.
3. Pin both vaults; use Quick switcher to move between BluTown (ops) and Knowledge (wikis / reference).

What goes where

Location	Role
BluTown (this repo)	bus/, library/, runtime/, operational truth, Beads context
/Volumes/AgentPlatform/knowledge	GitLab Wiki clones, research, long-form platform docs (NAS master)

Integration surfaces

• ContextControl.ai — primary product memory surface; ContextControl.ai may remain for parity/testing.
• GitLab wiki — team-visible docs; often mirrored under knowledge on NAS.
• Agents — point skills/tools at the actual path for the machine (this vault vs NAS mount).

See also: obsidian-ownership-runbook.md, obsidian-sync.md, obsidian-cc-integration.md in this folder.