What each tier can see
One set of documents, four audiences. Every block of content declares the lowest tier that may read it, so the same page grows as your access does rather than becoming a different page.
Anyone, signed in or not. The default, and never a denial.
- The full Level 0 map: six layers and every module in them
- What each module is for, in one sentence
- The roadmap, and the status of the architecture as a whole
Named partners and clients working against the platform.
- Everything public, plus what each module owns and explicitly does not
- Ratification status, version and owner of every specification
- The decision register by title and status
- Delivery criteria on the roadmap
Engineers building on or inside the runtime.
- Everything a partner sees, plus the Level 1 decomposition of every module
- The open questions decomposition surfaced and could not settle
- Component diagrams, interfaces, consumed contracts and owned state
- Failure modes, and how each is detected and answered
- The full text of every decision record
Architecture owners accountable for the register.
- Everything a developer sees, plus the source document behind every node
- Content health, and the ability to reload content without a deployment
- Preview of any lower tier, to check what it actually shows
How roles are granted
Roles are Microsoft Entra ID application roles, assigned to a user or a group against this application. Nothing on this site grants access, and no self-service path exists here by design: the register of who may read the architecture belongs in the directory, where it is audited, and not in a page anyone can reach.
An account with no assigned role is treated as public. Being known to the tenant is not a grant.
The two lenses
What a module is for, what it owns, and where its responsibility ends. Written to be read by someone who will never open the code.
How a module is built: its components, the interface it exposes, what it consumes, the state it holds and the ways it fails.