Graphify Insights
This page is auto-generated from a semantic knowledge graph of the Layerr codebase. The graph was built from 1,090 source files producing 796 functional communities with inferred relationships between concepts, code, and documentation.
God Nodes
Section titled “God Nodes”God nodes are the most connected concepts in the codebase, they touch the most other parts of the system. These are the architectural anchors.
| Node | Degree | Description |
|---|---|---|
| fileHashes | 467 | File integrity and caching system |
| startServer() | 183 | Server bootstrap and initialization |
| OrchestrationBar.tsx | 81 | Primary orchestration UI component |
| WorkspaceProfile | 80 | Workspace configuration and profiles |
| UsageLimitsPanel | 60 | Usage quota and limit management |
| CapabilityMatrixPage | 58 | Provider capability scoring matrix |
| StrategyBenchmarksPage | 56 | Strategy comparison and benchmarking |
| RuntimeHealth | 54 | Runtime health monitoring dashboard |
| MobileRuntimeDashboard | 54 | Mobile-optimized runtime status view |
| ProviderLearningPage | 51 | Adaptive provider learning and calibration |
Surprising Connections
Section titled “Surprising Connections”These are relationships the graph found that are not explicitly stated in code, inferred connections that bridge separate communities.
-
extractGatewayContext()→GatewayRequestContext(shares_data_with)- inferred connection - not explicitly stated in source
-
Layerr. Live Orchestration Interaction Layer→orchestrationOneLiner()(conceptually_related_to)- inferred connection - not explicitly stated in source
-
ExecutionOutcomeEvaluator→API Reference(conceptually_related_to)- inferred connection - not explicitly stated in source
-
ExecutionOutcomeEvaluator→Four Evaluation Dimensions(conceptually_related_to)- inferred connection - not explicitly stated in source
-
ExecutionOutcomeEvaluator→Grade Thresholds(conceptually_related_to)- inferred connection - not explicitly stated in source
Top Communities by Cohesion
Section titled “Top Communities by Cohesion”Communities with high cohesion have tightly focused, single-purpose code.
| Community | Symbols | Cohesion |
|---|---|---|
| Community 359 | 3 | 1.00 |
| Community 364 | 3 | 1.00 |
| Community 374 | 2 | 1.00 |
| Community 375 | 2 | 1.00 |
| Community 376 | 2 | 1.00 |
| Community 377 | 2 | 1.00 |
| Community 378 | 2 | 1.00 |
| Community 379 | 2 | 1.00 |
| Community 380 | 2 | 1.00 |
| Community 381 | 2 | 1.00 |
| Community 382 | 2 | 1.00 |
| Community 383 | 2 | 1.00 |
| Community 384 | 2 | 1.00 |
| Community 385 | 2 | 1.00 |
| Community 386 | 2 | 1.00 |
Cross-Community Flows
Section titled “Cross-Community Flows”The most complex execution flows span multiple communities. These represent the core orchestration paths.
| Flow | Steps | Type |
|---|---|---|
| ExecuteChat → Batch | 8 | cross-community |
| Resolve → ParseKeyMaterial | 7 | cross-community |
| ResolveProviderChain → GetSlugForUrl | 6 | intra-community |
| Resolve → ToB64url | 6 | cross-community |
| Resolve → Hmac | 6 | cross-community |
| StartServer → GetDb | 5 | cross-community |
| StartServer → _fireActivation | 5 | cross-community |
| PoolEntries → EmptySnapshot | 5 | cross-community |
These flows show how a single request (like a chat completion) touches Secrets (key parsing), Routing (URL resolution), Runtime (health checks), and Execution (batching) before completing.
Generated from graphify analysis of layerr-app. Last updated: May 2026.