Platform Architecture
Top-level platform shape, authority boundaries, and how the documentation platform maps onto the codebase.
Authority boundaries
- Topolo Auth is authoritative for identity, organization access, service registration, service permissions, and API key catalogs.
- TopoloOne is the operator-facing control surface for those shared capabilities.
- Application services remain authoritative for their own data models and APIs.
Shared platform surfaces
- service registry
- user and organization resolution
- API keys
- resource-bound API access
- deployment and operational conventions
Documentation model
This docs site is built from:
- public content for developers
- internal content for operators and agents
- a system registry collection for canonical identifiers
- generated API summaries from source-controlled OpenAPI specs where available
Priority systems
The first migration wave covers Topolo Auth, TopoloOne, Socialize, TopoloCRM, and shared platform concepts. Additional applications can be added without changing the content contract.