Skip to content

Obsidian cc integration.runbook

Scope

This runbook ties together:

  1. BluTown (Git vault) — $ESTATE_ROOT/BluTown or your clone path — operational bus and operator library.
  2. /Volumes/AgentPlatform/knowledge — NAS-resident wiki / research / long-form reference — second Obsidian vault.

Do not symlink the NAS tree into BluTown. Use Open another vault in Obsidian.

Prerequisites

  • NAS mounted at /Volumes/AgentPlatform (see workspace NAS / Tailscale runbooks).
  • ls /Volumes/AgentPlatform/knowledge succeeds before relying on vault B.
  • Obsidian desktop installed.

Open both vaults

  1. BluTown: Open folder as vault → BluTown repo root (contains bus/, AGENTS.md, .obsidian/).
  2. Knowledge: Open another vault → /Volumes/AgentPlatform/knowledge.

Use Quick switcher / vault list to move between ops (BluTown) and reference (knowledge).

ContextControl and wikis

  • ContextControl.ai is the primary product memory / context surface per platform portfolio policy.
  • ContextControl.ai may remain for testing or parity; do not treat it as the sole authority for new integrations.
  • GitLab Wiki (team docs) is often mirrored or PROJECTS/_DRUPAL under NAS knowledge; treat that tree as read-mostly reference unless your runbook says otherwise.

Knowledge source wiring (high level)

When attaching Obsidian or markdown mirrors to the platform:

  • Register paths via the owning product’s config (e.g. context hub / knowledge providers), not ad hoc copies under BluTown.
  • Prefer read-only export from vault B into CI or indexers; writes go through governed APIs or operator-approved jobs.
  • Secrets: never in vault JSON; use op:// and approved env (.agents/context/BLU-AUTHENTICATION.md).

Verification

  • [ ] Both vaults open without errors.
  • [ ] BluTown NAS-Knowledge-Vault.md matches your actual mount path if your org uses a different volume label (update the note, not scattered copies).
  • [ ] Agents and CLIs that need wiki content point at mounted /Volumes/AgentPlatform/knowledge (or your documented equivalent), not a broken relative path.

Maintenance

  • If mount path changes, update NAS-Knowledge-Vault.md, .obsidian/BLUTOWN-OBSIDIAN.md, and BluTown/AGENTS.md (Obsidian section) in the same change set.