The dedicated knowledge base, vault, and developer-tooling stack for Chio — Backbay's capability-based agent runtime with signed receipts.
Status: planning. The carve-out from
arc/ops/knowledge-base/(PR #599) is scoped in PLAN.md. Phase 0 begins after ADR-0000 is accepted.
A three-layer stack:
kb-engine/— generic retrieval / graph / MCP framework (pgvector + Neo4j + Graphiti). Zero Chio knowledge.chio-pack/— Chio schema, the 10kb_*MCP tools, evals.vault/— git-versioned markdown that is the canonical store for episodes, ADRs, briefs, playbooks. Obsidian renders it; agents read it as files; Graphiti is derived from it.
Plus two ambitious bets unique to Chio:
- A PR-time
kb_impactgate that fails PRs touching guards / policies / protocol contracts without acknowledging downstream blast radius. - Self-evidencing retrieval — every
kb_search_*returns a signed receipt. The KB demos the protocol it documents.
Phase 1 has not started. The sketch below is the target post-Phase-1 surface; nothing runs from this repo yet.
chio-dev up # docker compose up + wait for health
chio-dev ingest # incremental index of source repos + vault
chio-dev query "capability revocation receipt"
chio-dev eval # retrieval + outcome evalsPLAN.md— full design, repo layout, phased deliveryAGENTS.md— guidance for AI agents working in this repoCLAUDE.md— Claude Code-specific notesdecisions/— ADRs (start at ADR-0000)chio-pack/eval/PHASE-0.md— outcome evals that gate everything in Phases 1–4
Carved out of arc PR #599 (codex/chio-kb-a-grade-dogfood). The current A-grade retrieval eval (22/22 fixtures, p@5 ≥ 0.99, MRR ≥ 0.97, p95 < 1.5s) is the regression floor — no feature ships if it breaks.
This repo lives inside the Backbay multi-repo workspace at /Users/connor/Medica/backbay/standalone/chio-developer-base/. The workspace root CLAUDE.md is authoritative for cross-repo dev workflow (Moon, Bun, UV, cluster ports).