Architecture & Engineering Standards¶
The durable, cross-service architecture documents — how services talk to each other, how authorization composes, how events flow, and the platform-wide conventions every new service is expected to follow.
| Doc | Covers |
|---|---|
| Microservice Architecture | The master architecture reference — communication patterns, service discovery, resilience, observability, shared libraries. Start here. |
| Trinity Authorization Pattern | The three-layer authorization model: RBAC (auth-service) + Licensing (subscriptions-service) + Resources (domain services). |
| Event Architecture | NATS JetStream event catalog, the outbox pattern, envelope formats. |
| SSO Integration Guide | The OIDC/PKCE login flow, JWT claim shape, JIT provisioning. |
| Login Flow Contract | Frontend-specific API signatures/route contracts for the login flow, per service. |
| Subscription Gating Guide | The mutations-only subscription enforcement pattern — full implementation guide (code samples). |
| Cross-Service Data Ownership | The canonical data-ownership matrix — which service owns which entity, and the integration pattern for reading it from elsewhere. |
| Go Backend — Ent + Atlas Migrations | The Ent codegen + Atlas versioned-migration convention every Go service follows. |
| DevOps-K8s Ingress & CORS | The canonical CORS origin allowlist and NGINX ingress annotation conventions per service. |