Explore the structure
Follow the connections.
Find what depends on your code. See what your code depends on.
Select a node to trace its connections, or find a module in the explorer.
Keep exploring
From the map to your terminal.
The pillars4 arms · crowns & evidence
The arms the walk proposes. Each crown is the unit that orchestrates its arm.
requests · the pillars 5 layers · 5 nodes · 10 edges · 0 unconnected · [LR]
┌────────────────────┐┌───────────────────────┐ ┌────────────────┐┌─────────────────────────────┐ ┌───────────────────┐
│ SESSIONS (49→ ·→2) ├┤ └╪◀│ EDGE (11→ ·→8) ├┤ └╪┌┌▶│ MODELS (55→ ·→22) │
└────────────────────┘├───────────────────────┐│ └────────────────┘│ ┌────────────────────────┐ │││ └───────────────────┘
│ ││ └╪┌▶│ EXCEPTIONS (12→ ·→130) ├─╪┘│
│ ┌────────────────────┐└╪────────────────────╪┘ └────────────────────────┘ │ │
├▶│ ADAPTERS (38→ ·→3) ├─┤ │ │ │
│ └────────────────────┘ ├───────────────────┌╪─────────────────────────────┘ │
│ │ │ │
└───────────────────────┐└───────────────────┘┌───────────────────────────────┘
│ │
└─────────────────────┘
| Arm | Crown | Units | Evidence |
|---|---|---|---|
| MODELS | requests.models | 2 | crown — fan-out at least half the leader's (50) |
| SESSIONS | requests.sessions | 1 | crown — fan-out at least half the leader's (50) |
| ADAPTERS | requests.adapters | 1 | crown — fan-out at least half the leader's (50) |
| EXCEPTIONS | requests.exceptions | 8 | the floor's crown — the greatest fan-in (41) no arm owns (ADAPTERS 13, MODELS 12, SESSIONS 5) |
Compiled arms live at /site/.work/psf/requests/.graphy/GRAPH.md. Open one arm; blast its crown.
The package ring0 connected packages
Minted beside requests: none.
Not carried: OpenSSL, _typeshed, certifi, chardet, charset_normalizer, cryptography, idna, simplejson, typing_extensions, urllib3.
Add your modelMCP configuration
Paste this into the repo's .mcp.json (Claude Code) or your client's MCP settings. The client can start anywhere in the repo. Any model; the walk is graphy's.
{
"mcpServers": {
"graphy": {
"command": "/usr/local/bin/graphy",
"args": [
"mcp",
"--repo",
"."
]
}
}
}Ask the codebaseThree starting points
/usr/local/bin/graphy blast requests.models --tenant /site/.work/psf/requests/.graphy/tenant.json --tenant-id requestsif requests.models changes, what breaks/usr/local/bin/graphy descend requests.exceptions --tenant /site/.work/psf/requests/.graphy/tenant.json --tenant-id requests --depth 3what requests.exceptions reaches, across packages/usr/local/bin/graphy draw --tenant /site/.work/psf/requests/.graphy/tenant.json --tenant-id requests --symbol requests.models --radius 2 --lrthe neighbourhood, drawn
Make your own atlasOne command · no model
pip install graphyos cd <repo> && graphy eat . && graphy showcase .
https://github.com/psf/requests.git
Every edge comes from code structure, a wormhole between packages, or a label resolved through the code's own scope. The module map shows cross-group connections with at least 2 dependencies; 35 below that floor.