Your architecture map is a visual summary of how your code is structured (services, modules, and the dependencies between them), generated automatically from the source.
How to read it
- Boxes represent services, modules, or notable files.
- Lines represent a real call, import, or dependency between them.
- Click any box to drill into the underlying files it was derived from.
What it's useful for
Architecture maps shine during onboarding, incident response, and migration planning. If you're explaining your system to a new hire or a stakeholder, the map often beats a whiteboard, and it stays current automatically.