Strix — how the graphs were built

docs / tools / graph-intelligence

← all docs

Strix — how the graphs were built

Two independent, real code-intelligence tools were run directly against the cloned usestrix/strix repository (commit 8ca0c4a9) to ground the architecture diagrams and module-dependency claims in actual data instead of guesswork, plus one purpose-built drill-down generator. See ../../tool-outputs/README.md for the full index and exact commands.

Tool Type What it found
CodeGraph v1.5.0 Tree-sitter + SQLite code-intelligence CLI 279 files, 8,287 nodes, 31,870 edges indexed. Used to derive tool-outputs/codegraph/module_dependencies.json (real package-to-package edge counts) — the direct source for ../../diagrams/04_module_dependencies.svg.
Graphify v0.9.42 Tree-sitter AST extraction + Leiden community clustering 5,005 nodes, 12,933 edges, 197 communities (--code-only, fully local, no LLM). graphify god-nodes independently surfaced AgentCoordinator, ReportState, run_strix_scan(), ReportUsageHooks, StrixProvider as the most-connected symbols in the whole codebase — the same orchestration core identified by manual source reading, which cross-checks that reading.
codeviz.py (reused, project-agnostic) Pure-Python AST script, no dependencies beyond optional Graphviz Module → file → function drill-down with a plain-English one-liner per function (../../tool-outputs/codeviz/strix-codeviz.html).

What was skipped and why

Graphify's semantic extraction pass (naming communities via an LLM, extracting structure from the 106 non-code doc files) was not run — the sandbox this kit was built in has no LLM API key configured. --code-only mode was used instead, which is fully deterministic (tree-sitter AST only) and needs no credentials — this is explicitly the mode Graphify's own README recommends for CI/scripted use. The practical effect: GRAPH_REPORT.md's community list is left as unnamed placeholders ("Community 0…196") rather than human-readable names — per the ten-rule discipline this kit follows, that raw list is not presented as a deliverable; the curated strix-callflow.html and GRAPH_TREE.html views (and the god-nodes list above) are what a reader should actually open.

Setup instructions for tools not run locally

Two tools mentioned in the reference methodology this kit is based on were not available in this sandbox and were not run:

Either could be added later as a third cross-check without invalidating anything in this kit — CodeGraph and Graphify's outputs are on disk and regeneration commands are documented in ../../tool-outputs/README.md.

Related: STRIX — Graph Intelligence Findings, ../../tool-outputs/README.md.