Architecture is a living map of how your software fits together — services, components, the dependencies between them, and the data that flows across them. It turns a pile of repositories into a picture you can reason about.
What you'll see
- Service and component maps showing how parts of your estate connect.
- Layers — how components stack, and where boundaries are crossed.
- Coupling and dependencies between services, so you can spot the parts that are hard to change in isolation.
- Architectural health scoring that summarizes the structural risk in the design itself.
How to use it
Use the map to understand blast radius before you change something. If one service is highly coupled to many others, an upgrade there carries more risk — plan it accordingly. High coupling and deep layering are signals, not verdicts: they tell you where to look, not what to conclude.
Where the map comes from
The architecture map is built from scan evidence — imports, calls, and configuration Vibgrate observed in your code. Relationships it inferred rather than read directly are marked as such, so you can tell a confirmed dependency from a likely one.