The estate
Six hubs, one system to describe.
Each hub owns one perspective and publishes it as a portal, and some of them carry tools you work in rather than pages you read. Nothing here is a copy of anything else: a hub is the single place its own subject is written down, which is what makes it safe for the others to link to it instead of restating it. This page is only the way in.
doc-hub
The product perspective. What each product does, for whom, where it is going — and three boards for the conversations that produce that answer in the first place.
Doc portal
The product catalogue, the two landscapes that cross products, and the form that puts a new product in the registry.
Open doc-portal (leaves this site)Story mapping
A user’s journey across the top, the work that serves it underneath, and a release cut as a line through the middle rather than a list of tickets.
Open doc-sm (leaves this site)Example mapping
One story, its rules, an example for each rule, and the questions nobody in the room could answer — the half-hour that decides whether a story is ready.
Open doc-em (leaves this site)Event storming
A domain on a wall in orange, at any of the three levels the practice is run at: the events, then the commands and policies that cause them, then the components inside one boundary.
Open doc-es (leaves this site)
ba-hub
The business-analysis perspective. Where a domain is cut into bounded contexts and the relationships between them are made explicit — the seams an event storm finds, drawn as a map instead of left in the room.
arch-hub
The architecture perspective. How the system is put together and what travels between its parts, both generated from a model rather than drawn — which is why they are still true a quarter after a diagram would have stopped being.
Architecture portal
The architecture perspective on a product: the decisions taken, what they cost, and which of them are still true.
Open arch-portal (leaves this site)C4 model
Context, container, component and deployment views of the whole system, generated from one LikeC4 model — so the four zoom levels cannot contradict each other.
Open arch-c4 (leaves this site)Event catalogue
Every message that crosses a product boundary: who publishes it, who consumes it, which schema version is in flight, and what breaks if it changes.
Open arch-eventcatalog (leaves this site)
api-hub
The contract perspective. What one product promises another, versioned and scored.
dev-hub
The practice perspective. How the work is done here, written down once so that the tools in the other hubs can point at it rather than explain themselves.
qa-hub
The quality perspective. What was tested, what it found, and which requirement each answer belongs to.