Every organization needs six layers in its city map. Click any layer to see its full set of attributes — the things an architect must define at that level before anyone starts building.
Every technical artifact — service name, URL, repository, Kubernetes namespace, monitoring dashboard, cost center — must encode its position in the hierarchy. If you look at any service and cannot immediately tell which domain, LOB, and product it belongs to, the city map is broken.
Here is our organization's hierarchy would look with proper domain mapping applied. Click to expand each level and see how the naming convention flows from top to bottom.
The city map is not a one-time exercise. It requires ongoing governance instruments — the equivalent of a city's zoning board, building codes, and address registry.
Before any engineer writes code, before any new service is created, these questions must be answered. This is the "building permit" — no construction without an address. Click items to check them off.