Graphify Views
Graphify is the structural and source-relationship map. Use it before answering codebase or repository-structure questions when graphify-out/graph.json exists.
Graphify complements the LLM wiki:
- Graphify shows extracted source relationships, hubs, communities, and code/document structure.
- The LLM wiki records durable operational knowledge, contracts, workflows, and decisions.
The current Graphify output is viewable inside the wiki. The enhanced standalone graph pages are generated as RAG / Tooling pages rather than default landing pages.
Raw vs wiki view
graphify-out/ remains the raw Graphify output. The wiki-hosted copy under docs/assets/graphify/ is post-processed for readability: communities get source-derived names, Markdown links between pages are added as links to edges, SRC-### citations are added as source-reference edges, MkDocs navigation hierarchy is added as nav contains edges, repository paths are added as filesystem contains edges, and explicit file mentions are added as references file edges.
Durable Outputs
Committed Graphify publication artifacts are:
GRAPH_REPORT.mddocs/assets/graphify/graph-3d.htmldocs/assets/graphify/graph.htmldocs/assets/graphify/graph.jsondocs/assets/graphify/summary.json
Do not publish or gate checks on manifest.json.
Available Views
| View | Best for |
|---|---|
| 2D Relationship Map | Precise structural inspection, node search, readable communities, and stable link checking. |
| 3D Spatial Map | Exploring dense clusters and cross-links spatially with rotate, zoom, and pan. |
| Graph JSON | Tooling, checks, and direct agent inspection. |
Use the 2D view for most maintenance work. Use the 3D view when you need to understand broad cluster separation or inspect dense interlinking.
Published browser graph communities are post-processed by scripts/publish-graphify-assets.mjs so the legend uses source-aware names such as Module Pages: TrakCare rather than generic numeric community labels. The 2D and 3D views both load the same enhanced graph.json, so community naming, Markdown links to edges, source-reference edges, navigation edges, filesystem edges, and file-reference edges carry across views.
Update
npm run kb:update
If Graphify is unavailable, run npm run kb:code-index and record the limitation in docs/log.md.
Checks
npm run check:graphify
The check regenerates Graphify in a temporary copy and compares normalized committed artifacts. The normal update path also removes graphify-out before rebuilding so stale incremental cache state does not change the graph. The Graphify report title, optional Git freshness block, and commit fields, plus the JSON commit field, are normalized because the temp copy path and final JJ commit differ from the live working tree.