CC-025 — Second Brain + Agentic OS

Why this exists

The Van Clief incident (2026-07-02): two research files written to /tmp, machine rebooted, both lost. This was not a reminder problem — no rule could have prevented it. Only architecture prevents it. CC-025 builds three layers that make the failure structurally impossible.

Architecture (three layers, consensus between Claude + Grok plans)

  1. Session Path Resolver (path-resolver) — every agent output lands in a durable path (~/second-brain/sessions/) before the first byte is written. /tmp is never the work-output location again.
  2. LLM Wiki (Karpathy pattern) — interlinked markdown knowledge base at ~/second-brain/notes/. Entities, concepts, decisions, research — all interlinked via [[wikilinks]], compounding over time. See SCHEMA.md for conventions and tag taxonomy.
  3. Basic Memory MCP — open-source MCP server (basic-memory, project smk9-ecosystem) sitting on top of the wiki directory. Agents query and write to the wiki through MCP tools instead of loading 40k-token Drive docs just to answer a question. Registered in Hermes via hermes mcp add basic-memory.

Phase 3 addition — Alexandria intake

alexandria closes the loop: agents write Surface 1 (session output + confidence sidecar), a 15-minute cron classifies and promotes to Surface 2 (wiki / decisions_log / Qdrant / Firestore depending on artifact type and confidence). Nothing an agent produces is silently lost — low-confidence output is quarantined with a reason, not deleted.

The two-surface rule

Codified in AGENTS.md §OUTPUT CONTRACT: work is not done until it exists on two surfaces — local session dir (rsync’d to VPS every 15 min) and one of Drive/VPS/Git/Qdrant. Alexandria handles Surface 2 promotion automatically; agents only need to handle Surface 1 by using the path resolver.

Namespace map

smk9/ (Sound Mind K9 LLC) | encompass/ (Encompass Holdings LLC) | personal/ (Elliott personal) | tech/ (this build)

Status

Phases 1–3 built 2026-07-07 on eco-chi-001. Qdrant integration and Firestore client_data routing are stubbed in alexandria_intake.py but not yet wired to live endpoints — future work.

hermes | alexandria | indiana-holmes | path-resolver