Skip to content

Choose a Reading Path

Choose a route by the decision you need to make, not by repository folder order. Each route starts with a visual map, then links to long-form explanation, reconstructed contracts, and evidence.

Route selector

This diagram is editorial navigation, not a statement about runtime behavior, so the maps’ O/D/H evidence markers do not apply to its branches.

flowchart TD
    accTitle: Choose a Reading Path - Route selector
    accDescr: Diagram showing route selector in the Choose a Reading Path section.
    Start["What do you need from the atlas?"] --> Orient{"Understand the whole system?"}
    Orient -- Yes --> General["General orientation route"]
    Orient -- No --> Build{"Build or integrate?"}
    Build -- Extensions --> Ext["Extension-author route"]
    Build -- SDK/automation --> SDK["Automation route"]
    Build -- Reconstruct internals --> Impl["Implementation route"]
    Build -- No --> Operate{"Operate or secure it?"}
    Operate -- Administer --> Ops["Operator/admin route"]
    Operate -- Review security --> Sec["Security route"]
    Operate -- Audit evidence --> Audit["Evidence-auditor route"]

Reading-path matrix

Audience 10-minute route 30-minute route Deep route / source
Product or technical leader System map → threat summary Add scope and boundaries and the versioned snapshot E:claims for what is actually established
New implementation contributor Execution flow → evidence/code cross-reference Add the runtime architecture overview R:reconstruction-index, then source files in call order
Extension or plugin author Extension surfaces → settings/permissions Add plugins, hooks, and MCP R:plugins, R:hooks, R:MCP
Operator or administrator Settings/permissions → provider/network Add the persistence map and runtime modes R:settings, R:sandbox
Security or privacy reviewer Threat model → provider/network → persistence Add trust boundaries and the extension supply chain Trace every control through evidence/code cross-reference and E:claims
SDK or CI automation integrator Execution flow → provider/network Add the CLI reference and headless integrations H:root, R:startup, R:model-stream
Evidence or legal auditor Evidence/code cross-reference → methodology Add the claim catalog and version limits E:provenance, E:inventory, E:anchors, E:claims

Questions the atlas can answer quickly

Question Start here Source-of-truth follow-up
Why did a tool not run? Execution flow R:tool-pipeline, R:permissions
Can project settings override managed policy? Settings/permissions Claims security.managed-permission-rules and security.disable-bypass-mode in E:claims
Which extension can execute local code? Extension matrix R:hooks, R:plugins, R:MCP
What leaves the machine? Provider/network map R:providers-http, R:telemetry
What persists after a turn? Persistence map R:sessions, R:memory
Is a map edge fact or interpretation? Map legend Basis field in E:claims

Read the map legend, the 2.1.177 snapshot, and the limitations before treating a relationship as current product behavior.