System Map Dashboard

Pullminder’s System Map renders your repository as an interactive dependency graph. Modules, datastores, queues, and services appear as nodes connected by import, call, and data-access edges. When Collective Memory is enabled for the same repository, incident counts are overlaid as a heat layer so you can see where trouble clusters in your architecture.

For a conceptual overview of how System Map works, see the System Map guide.

Enabling System Map

System Map is off by default. Enable it per repository from the Settings page:

1. Open Settings from the sidebar.
2. Find the repository in the list.
3. Toggle the System Map switch on.

When you disable System Map for a repository, its stored graph data and cached renders are purged immediately. Re-enabling it starts fresh. The graph rebuilds on the next push to the default branch.

Viewing the graph

Once enabled, click View map next to the repository in Settings, or navigate directly to /map/{repoId}.

The graph view shows:

• Nodes positioned by a force-directed layout. Each node is colored by type: modules in blue, datastores in green, queues in orange, external services in gray, and other services in purple.
• Edges drawn as directional arrows connecting nodes by relationship: imports (solid), calls (dashed), reads/writes (dotted), depends-on (solid with diamond).
• Incident heat overlay on nodes where Collective Memory has recorded trouble. Darker nodes indicate more incidents. Nodes with no incident history appear neutral.

Node panel

Click any node to open a side panel showing:

• File path and node type
• Incident count from Collective Memory
• Finding categories broken down by type (e.g. SQL injection, secret leak, test gap)
• Connected nodes listed by edge type

Filters

Use the filter bar at the top of the graph to narrow the view:

• Node type toggles show or hide modules, datastores, queues, external services, and services.
• Incident threshold filters to only nodes meeting a minimum incident count.
• Search highlights nodes whose label or file path matches a query.

Limits

• Maximum 5,000 nodes and 20,000 edges per graph. Builds exceeding these limits are truncated.
• The graph reflects the state at the last push to the default branch. It is not updated continuously.
• Single repository only. Cross-repo edges are not detected in Phase 1.
• The heat overlay requires Collective Memory to be enabled for the same repository.