echo/.references/goldbrain-obsidian/spinup.md

spinup.md

Purpose

This guide is the complete user (not agent) spin-up walkthrough for taking a fresh Obsidian vault from empty folder to live operational memory system for Claude Code, with a path toward future CoWork plugin integration through the Obsidian Local REST API.

High-Level Flow

• 1. Create the vault.
• 2. Add root operating docs.
• 3. Build the folder tree.
• 4. Add templates.
• 5. Create initial notes.
• 6. Validate Claude Code access.
• 7. Enable the Obsidian Local REST API.
• 8. Start the daily/session/review operating rhythm.

Verified status — 2026-06-02

Checked against the live vault at goldbrainapi.mpm.to after the scaffold copy.

• 1. Create the vault — Done. Vault is live and reachable via the REST API.
• 2. Add root operating docs — Done. CLAUDE.md, BOOTSTRAP.md, STRUCTURE.md, spinup.md, index.md, README.md, and .env.example all present.
• 3. Build the folder tree — Done. Full tree present and verified over the API. The empty subfolders that file-copy dropped (inbox/imports, inbox/processing-log, journal/weekly, journal/monthly, projects/incubating, projects/on-hold, projects/archived, areas/personal, resources/meetings, resources/source-material, decisions/by-date, decisions/by-project, reviews/monthly, reviews/quarterly, reviews/annual, archive/notes, archive/projects, archive/imports, _agent/memory/episodic, _agent/outputs/{briefs,drafts,summaries,synthesis}, _agent/skills/archived) were recreated with a placeholder README.md in each so they persist.
• 4. Add templates — Done. All eight templates present (_agent/templates/*, journal/templates/*, projects/project-template.md, decisions/decision-template.md).
• 5. Create initial notes — Done. Seed/anchor notes present (current-context.md, operator-preferences.md, active-setup.md, initial session log, daily note, people notes, etc.).
• 6. Validate Claude Code access — Not yet verified. Confirm Claude Code can read/write the vault folder directly on the host.
• 7. Enable the Obsidian Local REST API — Done. Verified end-to-end: API v4.1.2 responds through the reverse proxy with a valid TLS cert, the bearer key authenticates, and a write → read → list → delete round-trip succeeded.
• 8. Start the daily/session/review operating rhythm — Not yet. Begins once the operator starts using the vault day-to-day.