7eb8d756d1
Read all 62 source files (Dev: 37, Homelab: 22, Venture: 3, Reference: 0). Entity pages created (17): - Wiki/Reference: lovebug, jenny, sunnie, n8n, ob1, tailscale, authentik, traefik, cloudflare, obsidian, gitea, plant-based-southerner, claude-code, dispatch, docker - Wiki/Homelab: proxmox - Wiki/Dev: pbs-hub, herbydev Synthesis pages created (2): - Wiki/Homelab/homelab-ingress-stack — four-layer ingress model (Cloudflare + Traefik + Authentik + Tailscale); operational lessons from 10+ source files - Wiki/Dev/ai-memory-architecture — three memory layers (wiki + OB1 + Dispatch context); ingest paths; harness-vs-model design decision All 11 index pages rebuilt (Sources/Dev, Venture, Homelab, Reference, Sources root; Wiki/Dev, Venture, Homelab, Reference, Wiki root; vault root index.md). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2.6 KiB
| type | path | tags | created | updated | ||||
|---|---|---|---|---|---|---|---|---|
| entity | Wiki/Reference |
|
2026-05-08 | 2026-05-08 |
OB1
What it is
OB1 is Travis's personal AI memory and retrieval system — a Supabase + pgvector stack that stores embeddings of project notes, session logs, and vault content to enable semantic recall across AI conversations. Named as a reference to the "Old Ben" Kenobi archetype of a wise, reliable memory keeper. OB1 sits alongside the wiki-vault in the broader second-brain architecture: the vault provides structured human-readable knowledge, OB1 provides fast semantic search for AI context injection.
Current state
In active deployment across Phases 0–6. Key architectural decisions (from the addendum):
- Tailscale-only access — Phase 4 deferred public endpoint; OB1 only reachable over Tailscale mesh
- Parallel write pipeline — n8n writes new vault notes to both wiki-vault and OB1 simultaneously
- Phase 7 (planned) — Dispatch pre-compact hook wires Lovebug's context windows into OB1 for automatic memory ingestion before context is dropped
The AI memory architecture research session explored harness-vs-model layering, Poolside and Pi.dev approaches, and the split between episodic (session notes) and semantic (wiki entity) memory modes.
Where it lives
- Supabase instance — hosted in homelab (Proxmox), contains pgvector extension
- Ingest pipeline — n8n on PBS Docker stack
- Query interface — planned: homelab MCP server exposes OB1 recall as a tool
- Access — Tailscale-only (no public endpoint)
Related projects
- Sources/Homelab/ob1-main-deployment — full deployment plan (Phases 0–6)
- Sources/Homelab/ob1-deployment — addendum (Tailscale, parallel write, Phase 7)
- Sources/Dev/ai-memory-architecture-research — architecture research session
- Sources/Dev/second-brain — wiki-vault + OB1 second-brain pattern
- Sources/Homelab/homelab-mcp-server — MCP server will expose OB1 recall
- Wiki/Reference/n8n — ingest pipeline
- Wiki/Reference/tailscale — access layer
- Wiki/Dev/ai-memory-architecture — synthesis page
History
- 2026 — Architecture research session: pgvector, harness vs model layers, Poolside/Pi.dev reviewed
- 2026 — Full deployment plan written (Phases 0–6, Supabase + pgvector)
- 2026 — Addendum locked: Tailscale-only, parallel n8n write, Phase 7 Dispatch hook
- Planned — MCP server integration to expose OB1 recall as homelab tool