← Atlas Journey · Docs

Frozen document. Dates and status refer to its original source. Private resources and unreviewed images are unavailable.

Architecture decision index

The ADR files record accepted choices and their amendments. This index does not turn the supplied reference diagram or open questions into new decisions.

ADRCurrent standing for the prototype
0001 — Scope and simulationAccepted: selected journeys across six products, synthetic records and simulated money movement.
0002 — Shared login and business contextAccepted: context-specific permissions under one identity.
0003 — Record ownershipAccepted: Contentful, Camunda and business owners have separate authority.
0004 — Bilingual pinned formsAccepted: Contentful-driven en-US/es-US forms and immutable case releases.
0005 — Durable commandsAccepted: idempotency, outbox and owner-controlled effects.
0006 — Browser-held Keycloak tokensSuperseded by 0009 for the prototype's browser session model.
0007 — CloudHub MuleSoftSuperseded by 0008 for phase one; MuleSoft is deferred.
0008 — TypeScript BFFAccepted for Fastify BFF and adapters. Its earlier dedicated-VM placement is superseded by 0010.
0009 — Keycloak-backed BFF sessionsAccepted for confidential OIDC client and opaque browser session.
0010 — Local certification then cloudAccepted for Mac certification, hosted static UI, single VPS and Contentful SaaS.
0011 — TypeBox boundary contractsAccepted September 30 for Fastify schemas and inferred types. CMS form rules retain their ownership; adoption is pending.
0012 — Private gRPC adaptersAccepted September 30 for suitable internal integrations. Private gRPC migration is pending. ADR 0013 amends its earlier browser REST clause.
0013 — React-to-SDUI BFF tRPCAccepted September 30 for tRPC over same-origin HTTPS. Retains TypeBox, pinned CMS rules, sessions, CSRF and private gRPC; migration requires evidence.

Open design choices are recorded as questions in the reference alignment and as gated work in the issue map. In particular, broker/dependent portal actions, a DMN or separate policy engine, and a named cloud provider are not accepted additions. Future decisions should receive a new ADR rather than silently changing these files.