api/graphify-out/2026-10-13/GRAPH_REPORT.md

Graph Report - controlpanel_server (2026-10-04)

Corpus Check

• 157 files · ~66,840 words
• Verdict: corpus is large enough that graph structure adds value.
• Unclassified: 9 file(s) not represented in the graph (top: (none) 3, .example 2, .toml 2)

Summary

• 3 nodes · 2 edges · 1 communities (0 shown, 1 thin omitted)
• Extraction: 100% EXTRACTED · 0% INFERRED · 0% AMBIGUOUS
• Token cost: 0 input · 0 output

Graph Freshness

• Built from commit: 0c29222e
• Run git rev-parse HEAD and compare to check if the graph is stale.
• Run graphify update . after code changes (no API cost).

Community Hubs (Navigation)

• deploy-setting-catalog-keys.ts

God Nodes (most connected - your core abstractions)

1. DEPLOY_SETTING_CATALOG_KEYS - 1 edges
2. DEPLOY_SETTING_EDITABLE_KEYS - 1 edges

Surprising Connections (you probably didn't know these)

• None detected - all connections are within the same source files.

Import Cycles

• None detected.

Communities (1 total, 1 thin omitted)

Knowledge Gaps

• 2 isolated node(s): DEPLOY_SETTING_CATALOG_KEYS, DEPLOY_SETTING_EDITABLE_KEYS These have ≤1 connection - possible missing edges or undocumented components. (Counts symbols only; 2 node(s) total have ≤1 connection when file, concept and rationale nodes are included.)
• 1 thin communities (<3 nodes) omitted from report — run graphify query to explore isolated nodes.

Suggested Questions

Questions this graph is uniquely positioned to answer:

• What connects DEPLOY_SETTING_CATALOG_KEYS, DEPLOY_SETTING_EDITABLE_KEYS to the rest of the system? 2 weakly-connected nodes found - possible documentation gaps or missing edges.