Landscape
One architecture, eight ways of looking at it.
No single diagram explains a system. Each landscape below answers a different question — what the domain is, how the software is structured, what runs and how a use case flows through it, what is stored, what crosses the boundaries, what is exposed, what the business actually does, and where the models sit — and each is generated from a model under version control rather than drawn by hand.
Landscapes
DDD
Bounded contexts, aggregates and the language each context speaks — the domain map the other views are organised around.
Open the DDD landscape (leaves this site)C4
Context, container and component diagrams generated from a single model, so the four zoom levels cannot contradict each other.
Open the C4 landscape (leaves this site)Events
The messages that cross context boundaries — who publishes what, who listens, and which schema version is in flight.
Open the Events landscape (leaves this site)API
Every registered contract with its scorecard and revision history. This landscape is api-hub — the catalogue, scoring and registry already run there.
Open the API landscape (leaves this site)- Planned
Components
Every deployed component, and for each one the inner flow of a main use case as it actually ran — recorded from a real execution rather than drawn from memory.
See what is coming - Planned
Databases
The datastores behind the systems — relational schemas and the document, key-value and graph stores alongside them — browsable directly, instead of reconstructed from migrations.
See what is coming - Planned
Processes
The business processes the systems serve, and the step-by-step path a case takes across the components that implement it.
See what is coming - Planned
AI
Where models, agents and their tools sit in the architecture — what they may call, what data they touch, and who is accountable.
See what is coming