Platform
Architecture
Layers, services, and boundaries: how the public layer, shared services, and application runtimes fit together.
The public layer (this site) presents the platform. Shared services provide identity, roles, rights, consent, provenance, search, notifications, and agent orchestration. Application runtimes consume those services and never re-implement them.
What this covers
- Application shell and design system shared by all areas
- Shared services consumed through governed APIs
- Each application is a bounded context with its own routes
- Interactive runtimes arrive per application, behind the same shell
Help us shape this platform
We're looking for municipalities, museums, communities, and creators who want to put these ideas to work. If that sounds like you, we'd love to talk.