The Graphiti Graph Gets a Face — and a Way to Build It for Free
We built a viz for the knowledge graph, lost it to a cleaned temp folder, and rebuilt it properly. Plus: local extraction, debugged.
62 commits · +430,044 lines
We built a viz for the knowledge graph, lost it to a cleaned temp folder, and rebuilt it properly. Plus: local extraction, debugged.
Every context-v document across ~40 repos swept for frontmatter conformity, then re-indexed into Chroma and pushed to the cloud.
The tree grew for two and a half months while the corpus stood still. Tonight the discovery walk ran again: 16 new context-v sources opted in, 3 relocated repos reconciled, 1,001 files re-collated, the Chroma collections re-embedded, and the splash rebuilt so every new repo shows on the corpus page.
A new spec inverts the kit's build order: instead of the Chroma-first memory system the June specs planned, the MVP is a plugin — the context-vigilance skill, a scaffolder, and a five-command surface (/cv:init, /cv:new, /cv:kickoff, /cv:prep, /cv:implement) installable in one step. Chroma becomes an upgrade adopters grow into via /cv:init chroma.
Saturday the splash started speaking llms.txt to LLMs. Tonight it learned to speak sitemap.xml to search engines, robots.txt to crawlers, and a 1024×1024 JPG to share-preview bots. The three audiences each get a machine-readable handhold pointed at the same corpus.
Context Vigilance's splash now phones home to OpenPanel like its siblings — production-only, clientId-from-env, no secrets in the browser. The interesting part wasn't this wiring; it was figuring out why the other three splashes had been silently 401-ing for a day.
The splash now serves the llms.txt standard at /llms.txt (a 132 KB link index, grouped by source repo) and /llms-full.txt (the full 5.7 MB corpus concatenated as raw markdown). LLM crawlers and agentic tools that follow the convention can ingest 460 hand-authored context-v documents in one fetch.
Context Vigilance gets its public face: a dark-default engineer's-clipboard splash that walks readers through Hook → Practice → Proof → Invitation, opens with a Google-style 'what context do you need?' prompt over the 587-doc corpus, and ships to GitHub Pages on every push.