Frozen document. Dates and status refer to its original source. Private resources and unreviewed images are unavailable.
Atlas architecture and design
This collection describes the selected prototype architecture. Read it with the accepted ADRs and four published specifications: shared platform, six-product journeys, employer benefits, leave and return to work, and local certification and cloud promotion. A diagram box describes a responsibility; it does not imply that every product journey or cloud component is implemented.
| View | Question answered |
|---|
| System context and reference alignment | Which responsibilities from the supplied enterprise diagram apply to Atlas, and where do they sit? |
| Component design | Who owns identity, workflow, content, business state, and integration? |
| Fastify, TypeBox and private gRPC adapters | How are HTTP schemas, CMS rules and private service transports separated, and how will existing routes migrate? |
| React-to-SDUI BFF tRPC | How do typed experience procedures preserve CMS rules, sessions, owner checks and durable commands? |
| Server-driven task and form flow | How do Camunda state and a pinned Contentful release become an authorized screen? |
| Deployment view | What runs on the Mac for certification, and what moves to hosted UI plus VPS? |
| Decision index | Which ADRs are accepted, superseded, or still open? |
| Screen reference design | How do the supplied screen and domain references map to Atlas's approved journeys and UI? |
The domain glossary, record ownership, form contract, workflow contract, security contract, and acceptance strategy supply the behavioral detail. Where an older discovery page names MuleSoft or browser-held tokens, the later accepted ADRs in the decision index govern the prototype.