Tool outputs — index
Raw graph-intelligence tool exports for Strix (usestrix/strix), plus the curated,
readable views built on top of them. Generated 2026-08-14 against commit 8ca0c4a9
(main branch, shallow clone).
Readable interactive views (start here)
| View | What it shows | Open |
|---|---|---|
codeviz/strix-codeviz.html |
Module -> file -> function drill-down with plain-English notes per function, plus a module dependency graph. Built by tools/codeviz/codeviz.py (pure Python AST, no LLM). |
Open directly in a browser |
graphify/labeled-clusters.html |
All 197 Graphify communities, deterministically named (no LLM) from their dominant package + representative symbols. Built by tools/codeviz/gen_cluster_labels.py. |
Open directly in a browser |
graphify/strix-callflow.html |
Curated Mermaid call-flow diagrams + call tables, grouped into 17 sections, generated from the full Graphify knowledge graph. | Open directly in a browser |
graphify/GRAPH_TREE.html |
Collapsible-tree explorer over the same graph -- expand any file/symbol to see its edges. | Open directly in a browser |
../diagrams/04_module_dependencies.svg |
Package-to-package dependency graph, aggregated directly from CodeGraph's real imports/calls/instantiates/extends/references edges (weight >= 3). |
Open directly in a browser |
Raw exports (data, not for reading)
| Folder | Tool | Contents |
|---|---|---|
codegraph/ |
CodeGraph v1.5.0 -- tree-sitter + SQLite code intelligence | db/codegraph.db (SQLite -- nodes/edges/files tables), files.json (per-file language/node-count/size, 279 files), module_dependencies.json (aggregated package-to-package edge counts, derived from the DB -- see below), status.txt (plain summary). |
graphify/ |
Graphify v0.9.42 -- tree-sitter AST + Leiden clustering | graph.json (5,005 nodes, 12,933 edges, 197 communities -- raw, --code-only so no LLM/API key was used), graph.labeled.json + labeled-clusters.html (communities given deterministic, non-LLM human names via tools/codeviz/gen_cluster_labels.py -- grouped by dominant strix/<package> and representative symbols), GRAPH_REPORT.md (auto-generated text summary -- community list is unnamed "Community 0...196", confirming raw output alone is not meant to be read directly), manifest.json (per-file mtime/hash for incremental graphify update), analysis.json, graph.html (raw force-directed viz -- dense, superseded by the labeled/callflow/tree views for reading). |
codeviz/ |
Custom (tools/codeviz/codeviz.py, reused from a prior project's onboarding kit) |
strix-codeviz.html only -- this tool has no separate raw-data export; the HTML is the output. |
How the numbers were produced
- CodeGraph:
codegraph init .against the cloned repo -> 279 files, 8,287 nodes, 31,870 edges (Python 166 files, Go 48, TSX 47, TypeScript 15, YAML 2, JS 1 -- the Go/TSX/TS files are theinterface/tuiBubble Tea frontend andinterface/viewerReact SPA).module_dependencies.jsonwas built by a one-off script joiningedgestonodes.file_path, mapping each file to its top-levelstrix/<package>and aggregating cross-package edge counts by kind -- this is the same technique CodeGraph's own CLI doesn't expose directly, done here so the module-dependency diagram is grounded in real call/import data rather than authored from memory. - Graphify:
graphify extract . --code-only(deterministic tree-sitter AST extraction, no LLM backend configured or needed) -> 5,005 nodes / 12,933 edges / 197 communities, 93% of edges taggedEXTRACTED(explicit in source) vs. 7%INFERRED.graphify cluster-only --no-labelre-ran Leiden clustering; community naming was skipped (--no-label) since no LLM backend was available in this sandbox -- the community list inGRAPH_REPORT.mdis intentionally left as placeholders, per the "never ship raw output" rule (see the vault's Graph Intelligence Findings note for what is readable instead: the callflow HTML and the god-nodes list). - Graphify god-nodes (CodeGraph doesn't have this command; Graphify's own graph was used instead): the most-connected symbols across the whole code graph were
AgentCoordinator(152 edges),ReportState(84),run_strix_scan()(46),ReportUsageHooks(37),StrixProvider(36) -- i.e. the tool independently rediscovered the same orchestration core identified by manual source reading, which is a useful cross-check.
Regenerate
# CodeGraph
npm i -g @colbymchenry/codegraph
cd /path/to/strix && codegraph init .
codegraph status .
# Graphify (code-only, no API key required)
pip install graphifyy
cd /path/to/strix && graphify extract . --code-only --out /path/to/out
graphify cluster-only /path/to/out --no-label # add --backend=<name> to also name communities
graphify god-nodes --graph /path/to/out/graphify-out/graph.json --top 20
graphify export callflow-html --graph /path/to/out/graphify-out/graph.json
# codeviz (project-agnostic, dependency-free)
python3 tools/codeviz/codeviz.py --root /path/to/strix --name "Strix" \
--top-package strix --exclude tests --exclude .venv --exclude interface/tui \
--out tool-outputs/codeviz/strix-codeviz.html
Rules
- The readable view is always listed before its raw folder (see table above) -- nobody
should have to open
graph.jsonby hand to understand the codebase. - Raw exports are never deleted, even once superseded by a curated view -- they're the ground truth the curated views were built from, and the basis for re-verifying any claim in the docs.
- Every regenerate command above was actually run to produce this folder's contents -- none are aspirational.