graphlisted

# Knowledge Graph (graphify) Build a map of how this AIOS actually fits together — which code files and which wiki notes depend on, reference, and cluster with each other — so you can see the structure instead of guessing it. Powered by **graphify** (a knowledge-graph builder), scoped hard to what's safe to graph. ## When to run - The user asks to see how the repo / second brain hangs together ("map the codebase", "graph the repo"). - After meaningful structural change — new skills, tools, SOPs, or a `/wiki` loop that added entries — to refresh the picture. - As a thinking aid before a refactor, an audit, or a `/weekly` review: *what's load-bearing, what's orphaned, what's surprisingly connected.* - Before exploring with `/graph-query` (this builds/refreshes the graph it queries). ## The output (always this shape) graphify writes everything to **`graphify-out/`** (git-ignored — a derived artifact, never committed): ``` ## Knowledge graph — <date> **Built from** — code (local AST) + committed wiki/. Excluded: raw/, .tmp/, .env, secrets. **Artifacts** — graphify-out/graph.html (interactive) · graph.json · GRAPH_REPORT.md **God Nodes** — the most-connected hubs (what everything leans on): 1. <node> — <why it's central, in a phrase> 2. … 3. … **Surprising Connections** — edges you wouldn't expect (cross-domain links worth a look): - <A> ↔ <B> — <what the link is> **Suggested Questions** — what the graph invites you to ask next: - <question> → run `/graph-query "<question>"` `