---
type: "synthesis"
primary_sources: ["s11", "s18", "s21", "s22"]
tags: ["memory", "open-brain", "mcp", "byoc", "context"]
id: "arc-byoc-memory-architecture"
sources: ["cross-day"]
---
# The BYOC Memory Stack

Four videos build a single architectural argument across days: **professionals must own and host their own AI context**, on open protocols, outside any single vendor's walled garden. This is the longest-developed technical thread in the series.

## The Four-Day Build

### S11 — The Architectural Debate (Wiki vs. Database)

[[concept-ai-wiki]] (Karpathy's proposal) is contrasted with [[concept-openbrain-architecture]] (Nate's proposal). The Wiki performs [[concept-write-time-synthesis]] and excels at solo deep research; it breaks at scale via [[concept-error-baking]], [[concept-race-conditions-ai]], [[concept-silent-contradictions]], [[concept-wiki-staleness]]. The Database performs [[concept-query-time-synthesis]], preserves provenance, scales multi-agent. The resolution is the [[concept-hybrid-memory-architecture]] — DB as truth, disposable wiki as presentation. The reframe: AI moves from [[concept-oracle-vs-maintainer|Oracle to Maintainer]].

### S18 — The Career Stakes (Four Layers + 5th Capital)

[[framework-four-layers-context]] is the cleanest taxonomy in the series:
1. [[concept-domain-encoding]] — what the AI knows about your industry
2. [[concept-workflow-calibration]] — how it structures work for you
3. [[concept-behavioral-relationship]] — implicit interaction preferences
4. [[concept-artifact-layer]] — outputs linked to prompts

The phenomenology: [[concept-honing-effect]] + [[concept-implicit-context]] = [[concept-tool-switching-penalty]]. The economic stakes: AI Working Intelligence becomes [[concept-professional-capital|the 5th category of professional capital]]. The escape: [[concept-mcp]] as bidirectional read/write standard.

### S21 — The Visual Layer (Two Doors)

[[concept-shared-surface]] = single DB table accessed by [[concept-agent-door]] (programmatic, MCP) and [[concept-human-door]] (visual, [[entity-vercel-d21]]). [[claim-no-sync-layer]] is the architectural credo. [[concept-cross-category-reasoning]] is the killer demo. [[concept-ai-flywheel]] is the strategic case: every model upgrade upgrades your stack for free.

### S22 — The Concrete Stack

[[entity-postgresql]] + [[entity-pgvector]] + [[entity-supabase-d22]] + [[concept-model-context-protocol]] + [[entity-slack-d22]]. [[claim-architecture-over-models]] is the load-bearing claim: memory architecture matters more than model selection. The [[contrarian-notion-is-dead|Notion is dead]] move and the [[contrarian-corporate-memory-is-hostile|corporate memory is hostile]] move are sharpened versions of the [[concept-memory-silo-problem]].

## Why The Same Architecture Across Four Days

The series is tracing one design pattern from *philosophy* (S11) to *career stakes* (S18) to *implementation* (S21) to *toolchain* (S22). A practitioner who reads only one of these gets a fraction of the argument. The full BYOC playbook is:

1. Hybrid storage: structured DB as truth, generated narratives as disposable
2. Open protocols (MCP) so any model plugs in
3. Visual interfaces over text chat (escape [[concept-infinite-scroll-problem]])
4. Live capture pipelines (Slack → webhook → DB)
5. Long-term: this is *career capital*, not productivity tweak

## Connection to Other Arcs

- The lock-in critique connects to [[arc-walled-garden-vs-open]].
- The Maintainer reframe connects to [[arc-agentic-loop-evolution]] (long-running agents need persistent memory).
- [[concept-context-rot]] (S04) is the failure mode this stack prevents.
- [[concept-shadow-agents]] (S24) is the *organizational* version of the same fragmentation problem.