Architecture Review Path designed
Use this path to explain the platform architecture, shared-service model, domain ownership, API/event boundaries, and deployment direction.
Reader Questions
- What is the platform shared services model?
- Which parts are product-owned versus platform-owned?
- How do API, schema, event, route, and frontend ownership align?
- What is the extraction sequence?
- Which architecture decisions remain open?
Architecture Review Route
| If the reviewer needs to understand... | Open this first | Then go here |
|---|---|---|
| the high-level runtime shape | Architecture | System Overview |
| the shared-platform and product split | Platform Foundation | Shared Services |
| domain, route, and API ownership | Domain Ownership | API Domain Authoring |
| deeper implementation packets | Architecture Review Pack | Detailed Design Index |
Start With
Publication Notes
External architecture pages should explain boundaries and decisions without exposing private environment topology, sensitive operations runbooks, or agent-only execution traces.
Review Rule
These pages should be detailed enough for ARB and partner architecture review, but still summary-first. Canonical internal design packets remain authoritative for implementation and internal release control.