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

Graph Report - controlpanel_user (2026-10-04)

Corpus Check

• 56 files · ~46,173 words
• Verdict: corpus is large enough that graph structure adds value.
• Unclassified: 38 file(s) not represented in the graph (top: .ttf 16, .eot 6, .woff 6)

Summary

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

Graph Freshness

• Built from commit: bef5da62
• 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)

• khanegiSettingCatalog.ts
• formatValueForSave
• resolveSwitchChecked
• normalizeSettingRow
• superAdminSettingKeys.ts
• isSettingVisible

God Nodes (most connected - your core abstractions)

1. formatValueForSave() - 7 edges
2. resolveSwitchChecked() - 5 edges
3. switchValueFromChecked() - 5 edges
4. normalizeSettingRow() - 5 edges
5. normalizeMainWalletProductsValue() - 4 edges
6. isSupportMessengerType() - 4 edges
7. parseSupportMessengers() - 4 edges
8. resolveSettingFieldType() - 4 edges
9. resolveSettingDescription() - 4 edges
10. parseSupportMessengersDraft() - 3 edges

Surprising Connections (you probably didn't know these)

• formatValueForSave() --calls--> resolveSwitchChecked() [EXTRACTED] src/config/khanegiSettingCatalog.ts → src/config/khanegiSettingCatalog.ts Bridges community 2 → community 1

Import Cycles

• None detected.

Communities (6 total, 2 thin omitted)

Community 0 - "khanegiSettingCatalog.ts"

Cohesion: 0.06 Nodes (26): ref_config, ACTIVATE_DEACTIVATE_SWITCH_KEYS, conditionalOrderEnabledSetting, HIDDEN_LEGACY_SETTING_KEYS, KEY_HELP_FALLBACK, KEY_LABEL_FALLBACK, KEY_TYPE_FALLBACK, MAIN_WALLET_PRODUCTS_DEFAULT (+18 more)

Community 1 - "formatValueForSave"

Cohesion: 0.28 Nodes (9): formatMainWalletProductIds(), formatSupportMessengers(), formatValueForSave(), isSupportMessengerType(), normalizeMainWalletProductsValue(), normalizeTimeValue(), parseMainWalletProductIds(), parseSupportMessengers() (+1 more)

Community 2 - "resolveSwitchChecked"

Cohesion: 0.29 Nodes (7): isActivateDeactivateSwitch(), isReferralRequired(), isSwitchOn(), referralRequiredToString(), resolveSwitchChecked(), switchToString(), switchValueFromChecked()

Community 3 - "normalizeSettingRow"

Cohesion: 0.47 Nodes (6): helpText(), normalizeSettingRow(), resolveSettingCanEdit(), resolveSettingDescription(), resolveSettingFieldType(), resolveSettingTitle()

Knowledge Gaps

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

Suggested Questions

Questions this graph is uniquely positioned to answer:

• Why does formatValueForSave() connect formatValueForSave to khanegiSettingCatalog.ts, resolveSwitchChecked? High betweenness centrality (0.004) - this node is a cross-community bridge.
• Why does resolveSwitchChecked() connect resolveSwitchChecked to khanegiSettingCatalog.ts, formatValueForSave? High betweenness centrality (0.001) - this node is a cross-community bridge.
• Why does switchValueFromChecked() connect resolveSwitchChecked to khanegiSettingCatalog.ts, formatValueForSave? High betweenness centrality (0.001) - this node is a cross-community bridge.
• What connects conditionalOrderEnabledSetting, priceChannelAccessSetting, priceProviderSetting to the rest of the system? 27 weakly-connected nodes found - possible documentation gaps or missing edges.
• Should khanegiSettingCatalog.ts be split into smaller, more focused modules? Cohesion score 0.05714285714285714 - nodes in this community are weakly interconnected.