🧭Atlas
Leave the overview as soon as one route sounds right: jump straight to the district directory, pick a reader journey, or open the whole-map route.
Sections
Now viewing District directory
When you know the area, enter the district right away
Choose the worker or owner area first, then drop into the street that answers the question without guessing.
Primary assistant district for planning, coordination, and execution oversight.
Team assistant district focused on review quality and team FAQs.
Autonomous explorer district for cycles, delivery, and platform documentation.
Decision and governance district for proposal review, policy enforcement, and alignment oversight.
Design engineer and visual authority for the Saffron Network, design systems, UI reviews, and aesthetic standards.
Seed and initiative lifecycle manager, promotes Seeds to Work Items when gate criteria are met and tracks initiative health.
Labs leader for Lambda Curry Labs. Guides experiment design, enforces kill criteria, and makes the honest continue/pause/sunset call on product ideas.
Labs distribution and market-signal agent. Finds audiences, designs approved distribution experiments, sharpens messaging, and turns learnings into playbooks.
Single-owner delivery agent on the Linear system of record: Samwise shapes intake, keeps the shared thread visible, and executes bounded tasks with parent-identity skills; the retired Lantern and Spade charters remain as history.
Choose the shared layer first, then take the street-level route that matches the specific technical question.
Inter-agent transport, communication modes, and request flows.
QMD/Recall indexing, retrieval paths, and API behavior.
Telemetry, monitoring, diagnostics, and operational health.
Compute/network substrate and platform economics.
Use the pathfinder for depth guidance, or reader journeys for the fuller why behind each route.
Still deciding how deep to start?
Start at the depth that matches your question, then stop as soon as you have the next click.
Use Sky when you want the broad shape first, then decide which area deserves a deeper read.
Choose this depth when you want sky-level guidance before you open anything denser.
Need the wider map? Atlas still keeps the top-level route contracts and lane boundaries close by, but they now sit after the fastest district entry path instead of blocking it.
Open the full route mapPick the journey that sounds most like your real question
These five journeys turn the route chooser into real entry-to-goal paths. If one sounds like you, take the first click and ignore the rest for now.
Use this fuller map when the fast district shortcut above is not enough context.
Open Getting Started first if you want Atlas to guide your first five minutes. Once the basic shape makes sense, Capabilities becomes the right second click.
Need the wider lane map?Use one route lane, not the whole route grammar
Treat this as backup help when the district shortcut and active journey still feel too narrow.
Show 4 lane shortcutsHide lane shortcuts
Use one route lane, not the whole route grammar
Treat this as backup help when the district shortcut and active journey still feel too narrow.
Atlas in plain languageNeed Atlas vocabulary?
Expand this only when a route still feels unclear. The active journey and lane shortcut above should stay the first move.
Show 5 termsHide terms
Need Atlas vocabulary?
Expand this only when a route still feels unclear. The active journey and lane shortcut above should stay the first move.
- 🤖 Agent
- A named worker that can take action, use tools, and own a kind of execution boundary.
- 🏗️ Charter
- A named body of work with a mission, owner, and reason to exist over time.
- 🪟 Surface
- A thing you can open, inspect, or use directly, like a product UI, dashboard, or tool endpoint.
- ⚙️ System
- Shared infrastructure or platform behavior that multiple agents and surfaces rely on together.
- 🧭 Guide
- An explanation layer that helps a reader choose a path, interpret a system, or recover from a problem.
Not the same as a charter, which is the body of work the agent owns or serves.
Open CapabilitiesNot the same as an agent, which is the worker, or a surface, which is the thing you can open.
Open ProjectsNot the same as a charter, which owns the surface, or a guide, which explains how to navigate it.
Open NetworkNot the same as a surface, which you open directly, or a guide, which explains the system for readers.
Open ArchitectureNot the same as a system or surface. A guide helps you navigate; it does not own the thing itself.
Open Getting Started⚡ What changed on the fast-moving pages
Check recent updates first. These pages move when the network or live support surfaces change.
The agent gateway map converged onto the live shared-instance topology: Scout rides lc-builders 18811 with Samwise, Meg rides lc-makers 18814 with Dexter and Buzz, Grafton rides lc-stewards 18805 with Atticus, and Clawdy’s 18789 row teaches the minip3 ssh forward — the container-era 18796/18802/18809 spellings are retired. Samwise's network-map card now teaches the single-owner delivery model: the registry retired the Lantern intake and Spade execution charters, so intake and execution read as parent-identity skills with Linear staying the system of record.
Open first when Open Network first when the question is about the overall shape of the system, which agents or services are involved, or how major pieces connect before you inspect one owner or one workflow.
Symptom and recovery sections on Troubleshooting are now focusable jump targets: activating a spine link moves keyboard focus to the failure-pattern content with a visible ring instead of leaving it on the nav rail (SFD-404).
Open first when Open Troubleshooting first when something already feels wrong and you need the shortest path from a symptom to the most likely check or fix.
The access section retires the Meg preview mirror: Watchtower on main-mini:5175 is the one live surface after the 2026-09-30 gateway consolidation.
Open first when Open Watchtower Guide first when the live dashboard changed, a panel meaning feels unclear, or you need runtime truth instead of static explanation.
The agent roster's Clawdy row now teaches the verified GPT-6 model — self-reported from Clawdy's own gateway config over Bridge — and the agent-port map converged onto the verified shared-instance topology — lc-builders 18811 (Samwise, Scout), lc-makers 18814 (Dexter, Buzz, Meg), lc-stewards 18805 (Atticus, Grafton), Clawdy via the 18789 ssh forward (gateway on minip3) — retiring the container-era 18796/18802/18809 spellings and Meg's preview mirrors (18803, 5181). The gateway map and architecture timeline now teach Dexter and Buzz registry-direct surfaces — Dexter on Slack, Notion, and CurryChat; Buzz on Bridge and CurryChat, the pair's shared direct surface — retiring the lumped (Slack, Notion, CurryChat, Bridge) union. The Samwise agent row and the Linear Agent Gateway row now teach the single-owner delivery model, and the July 10 audit-refresh capture's Lantern-first sentences are named as point-in-time history after the July 24 charter retirement. Spine links still move keyboard focus to the destination panel — including the audit-refresh section — with a visible ring (SFD-404).
Open first when Open Infrastructure first when the question is about ports, mirrors, host placement, public entry paths, or which support service actually sits behind a reader-facing surface.
🕐 Recently updated
Clawdy's taught model converged from the GPT-5.4-era capture to GPT-6 across the home card, the Capabilities chip, the FAQ answers, and the Infrastructure roster — verified by reading Clawdy's own gateway config over Bridge (its default entry reports the luna GPT-6 variant; taught per the network's simplified family naming).
The agent roster's Clawdy row now teaches the verified GPT-6 model (Bridge-verified from Clawdy's own gateway config), keeping the compose edit-point story (live-verified 2026-07-10), the orchestrator queue, and the five-route funnel shape as still-current.
Watchtower Guide’s access section retires Meg’s 5181 preview mirror — Watchtower on main-mini:5175 is the one live surface — while the route census keeps every FreshnessProof consumer represented in the coverage contract.
The agent-port map converged onto the verified shared-instance topology — lc-builders 18811 (Samwise, Scout), lc-makers 18814 (Dexter, Buzz, Meg), lc-stewards 18805 (Atticus, Grafton), Clawdy’s gateway on minip3 via the 18789 ssh forward — retiring the container-era 18796/18802/18809 spellings and Meg’s preview mirrors.
Expand this only when you need the longer arc behind today's map. The newest changes above should answer the common first-reader question faster.