Graphify eliminates the need for the Ruby/SQLite tag index (Step 2 on
the critical path). It provides entity extraction and relationship
inference over vault docs via a local SLM, and deterministic code
graphs for projects via AST — both at significantly lower complexity.
This commit records the architecture decision and evaluation that
justifies the pivot.
Vault graphs still require author-maintained summaries (human router
hint), but tagging discipline is now optional. Project code graphs are
free (no LLM cost). Stale-node drift requires periodic `--force`
rebuilds; strategy documented for SessionStart hooks.
The three-layer memory system remains unchanged: episodic (memsearch),
knowledge (Graphify + vault), integration (custom glue). See
06-graphify-evaluation.md for the open questions and limitations.
This documents the complete architecture for a personal, cross-project
memory system for Claude Code: three-layer (episodic/knowledge/deferred-
semantic) design using Milvus Lite for fast local storage with lazy
remote sync. Includes video synthesis, architecture decisions with
rejected alternatives (MemPalace, Mem0, Postgres, LightRAG), concrete
build plan with scripts and hooks, and initial handoff for implementation.
jared