Exploring the Graph

The graph is the map of a System and everything that makes it up — application code, infrastructure, CI/CD, containers, and governance — with the relationships between them. This guide covers how to move through it.

Layers and colors

Every node is colored by its layer, and the Layer filter chips in the toolbar carry the same color, so the toolbar doubles as the legend:

• App Code — green
• IaC — purple
• CI/CD — amber
• Container — cyan
• Governance — pink

System nodes are blue. Use the Show (Systems / Components) and Layer chips to hide what you don’t need; Drift only and Governed only narrow the view further.

Drilling in

The overview shows the whole project as constellations. Click a container node to drill into it — the scene swaps to that node plus one level of its children. Drilling reveals exactly one level per hop: deeper containers stay collapsed until you click into them, so a drilled scene stays a focused “city” rather than another sprawling map.

A breadcrumb shows the full path you’ve descended; Back / Forward walk your drill history, and Exit to overview returns to the top. The current scope lives in the URL (?drill=<id>), so any drilled view is shareable.

Relations

By default the graph shows containment. Use the Relations chips to overlay a single relationship kind at a time — references, provisions, deploys, tests, or governs — so you can read one kind of connection without the others crowding it out.

Tracing a path

To see how two nodes connect, open a node’s detail panel and choose Trace path from here, then open another node and choose Trace path to here. The shortest path between them is highlighted, with the relationship on each hop listed in a banner. The endpoints live in the URL (?path_from=, ?path_to=), so a traced path is shareable too.

Blast radius

Blast radius answers the Govern question: what could a change here affect? Open a node’s detail panel and choose Show blast radius (or View blast radius from a Component’s detail page). The node rings red and everything reachable from it — within two hops, across dependency and impact relations — rings amber, with a banner counting the affected nodes.

This mirrors the same definition the platform uses when it evaluates a change, so the console and the change gate always agree on what a change touches. The view is shareable via ?blast=<id>.

Sharing a view

Every navigation state is a URL parameter — ?focus=, ?drill=, ?path_from= / ?path_to=, and ?blast=. Copy the link (or use Copy link in the toolbar) to hand someone the exact view you’re looking at.