Whole-network reference

Network Topology

Use Network when you need the whole-map view of who exists, what shared layers connect them, and how the major pieces relate before you inspect one owner or one flow.

Validated · Oct 6, 2026Revalidated on October 6 against the live gateway topology: the September 30 pass re-probed every agent gateway and converged the map onto the native shared-instance split (lc-builders 18811: Samwise + Scout; lc-makers 18814: Dexter, Buzz, and Meg; lc-stewards 18805: Atticus + Grafton; Clawdy via the 18789 ssh forward to minip3), retiring the container-era 18796/18802/18809 spellings — alongside the nine-agent directory, the Bridge v1 command vocabulary, and the graph-first route shape. New this pass: the hero carries a mobile opening-scan panel — the same above-the-fold quick-jump pattern the other long routes already use — so phone readers can jump straight to the topology graph, the exit-route split, or the next-route picker without scrolling past the fold.

Take the fastest network jump

Open the whole map, see where routes split off, or pick the owning page for your next question — before you scroll.

Open the whole map See the route split Pick your next route

Open the whole map firstHere

Go straight to the topology graph when your question is about structure, adjacency, or shared platform shape.

Start here

Open topology graph

Once the graph shows you the right neighborhood, leave only when the remaining question is ownership, a handoff, or the rationale behind the system shape.

Leave only when the map changed the question

Keep the hero light, then use the owning route for detail

Capabilities

Leave for the owner map once the graph made the system area clear.

Open Capabilities →

Coordination

Leave when the map is clear but the first message or handoff path still is not.

Open Coordination →

Architecture

Leave when you understand the shape but still need the trust model or rationale.

Open Architecture →

Need the longer decision guide? The support rail below the graph keeps the same route split without turning the top of the page into another card deck.

Mobile first view

Choose a lens or a core node first

On a phone, Atlas should not make you rescue a miniature desktop map before you can learn anything. Pick the question-shaped lens or open one anchor node, then bring up the full topology when you are ready.

Quick lenses · change the graph

Core nodes · open an anchor

Graph controls

All lens

🗺️ All

Keep the map primary. Use these controls only to narrow, compare, or save the current topology view.

Map lens

React Flow

👆 Touch to pan · Pinch to zoom · Tap a node to explore

Graph guide

Use the graph first, then check only the signal you need

The topology graph stays primary. Drop into this guide when you need one control reminder or one signal definition—not a second tour of the page.

Inspect and reset

Select nodes or edges for details

Use a pointer to select, or focus a node or edge and press Enter or Space with a keyboard, to open its details as soon as the map shows the neighborhood you care about. Close NodeModal or EdgeInfoPanel when you are done; focus returns to the node or edge that opened it.

Hover to highlight connections

Use hover when you want the shortest visual answer to “what is this connected to?” before opening anything.

Drag to rearrange and scroll to zoom

Reposition the map when labels overlap, then zoom once the right layer is isolated.

Signal key

Edges

Solid = direct call

Dashed = telemetry

Animated = data flow

Node families

AI Agents

Clawdy, Currybot, Scout, Atticus, Meg, Grafton, Dexter, Buzz, Samwise

Knowledge Layer

QMD search

Services

Currybox, Observability, ClawConnect MCP, CurryChat

Infrastructure

Bridge, Kokoro Proxy, QMD Public Proxy, Observability

💡 Read only the edge type or node family blocking you, then go straight back to the map.

Support rail

Keep the graph first, then either narrow the question or leave for the owner

Once the topology graph has shown you the neighborhood, either reopen the map with a tighter lens or leave for the page that owns the missing answer.

Exit rule

Stay on the map vs leave for the owning page

Stay on Network

Keep the graph primary while the question is still about connections, neighborhoods, or overall system shape.

Leave for the owning page

Once the map worked, switch to the route that owns the missing answer: ownership, handoff, rationale, or runtime follow-through.

Fast rule: Leave only after the graph answered the topology question.

Stay on Network

Narrow the map before you abandon it

Use a helper lens only when the graph is still too broad. Atlas will reopen the map already filtered to the layer or overlay that matches the question.

Leave for the owning page

Leave once the map has done its job

Switch routes only after the topology is clear and the missing answer is about ownership, handoff, or rationale.

Leave for Capabilities when the boundary is ownership

Go there when the real question is who owns the work, what tools they have, or which agent should act first.

Ownership

Open Capabilities

Use this when the map is clear but the worker boundary is not.

Leave for Coordination when the boundary is the handoff

Go there when you know the area of the network but still need the right owner, first message, or delegation path.

Handoff

Open Coordination

Use this when the question is less “who exists?” and more “who goes first?”

Leave for Architecture when the boundary is rationale

Go there when the map is clear but you still need the trust model, rationale, or tradeoffs that produced it.

Rationale

Open Architecture

Use this when the whole-system shape makes sense but the “why” still does not.

Common second stops

Use the map, then pick the page that carries the detail

These are follow-on routes, not a second starter competing with the graph.

Need a concrete execution story?

Open Workflows when the graph made the actors clear but you still need to see the sequence play out end to end.

Sequence

Open Workflows

Need transport mechanics?

Open Bridge when your question is about call, watch, result, interject, cancel, list, and how a message actually travels between nodes on this map.

Transport

Open Bridge

Need the live companion?

Open Watchtower Guide when you need runtime truth or operational panels instead of Atlas's static explanation layer.

Runtime

Open Watchtower Guide

Question-led Atlas pages

Pick the deeper page by the answer you still need.

Once the graph narrowed the system area, use these question-led rows to jump straight to the explanation layer that owns the missing answer.

Need the delegation logic behind the edge?

Open Coordination Patterns when the map is clear but you still need the first owner, advisor, or handoff rule.

Handoff

Open Coordination Patterns

Need the transport protocol behind the connection?

Open Bridge Communication when the question is how sync, submit, and query actually move between nodes.

Transport

Open Bridge Communication

Need the sequence after the map identified the actors?

Open Example Workflows to watch a real end-to-end path instead of inferring the order from topology alone.

Sequence

Open Example Workflows

Need the judgment rule behind a stop or approval?

Open Governance when the topology is clear but the decision threshold or escalation logic still is not.

Decision

Open Governance

Need the owner boundary, tools, or action scope?

Open Agent Capabilities when you need the operating limits for a node, not the shape of its neighborhood.

Ownership

Open Agent Capabilities

Need the design grammar shaping Atlas surfaces?

Open Design System when the question is about tokens, shared components, or visual rules rather than network structure.

Design

Open Design System

Need the structural why behind the map?

Open Architecture Decisions when you need the trust model, tradeoffs, or rationale that produced the topology.

Rationale

Open Architecture Decisions