Explorer roadmap
The explorer ships static and gets livelier. Each phase below is only started once the one before it is genuinely finished, because a search box over incomplete content and a status light wired to nothing are both worse than not having them.
-
Phase 1 — The static map
Everything the architecture already says, readable by the four audiences it is written for, with nothing invented and nothing leaked.
- Level 0 map with drill-down to Level 2Six layers, thirty-one modules, and the components inside them. Pan, zoom, breadcrumbs and shareable URLs.
- Business and technical lensesOne content set, tagged per section, so the same page reads for a client and for an engineer.
- Entra ID sign-in and four application rolesPublic, partner, developer and admin. Anonymous visitors get the public reading rather than a login wall.
- Decision register with role-gated bodiesPartners see the index and status; developers read the reasoning.
-
Phase 2 — Search and traceability
Make the architecture answerable, not just browsable. Most real questions start from a word, not from a layer.
- Full-text search across modules, components and decisionsResults respect the viewer's tier, so a search never confirms the existence of something the viewer may not read.
- Command paletteJump to any node or decision record by name from anywhere, without leaving the keyboard.
- Backward traceability from a decision to what it governsOpen a record and see every module whose boundary it sets, and every contract consumed under it.
-
Phase 3 — Live status
Put the running system next to the design, so the map stops being only a description of intent.
- Per-module health from Azure MonitorA module card carries the state of the thing it names, not a colour someone set by hand.
- Implementation status against design statusApproved, built, deployed and validated are four different states, and the map should say which one a module is in.