Architecture decision records

An ADR records a decision that changes the architecture for everyone: what we decided, why, and what it costs. Decisions about one initiative live in that initiative's kickoff in Emargen; decision records for product and planning use Emargen's Decision record template. If a decision here changes, write a new ADR and mark the old one superseded.

ADR	Decision	Status
ADR-001	A Laravel API and a React portal	accepted, 2019
ADR-002	PostgreSQL for identity-service	accepted, 2019
ADR-003	Containers on ECS	accepted, 2020
ADR-004	Events leave identity-service through an outbox	accepted, 2021
ADR-005	notifier as its own service	accepted, 2021
ADR-006	One region per client, set at onboarding	accepted, 2022
ADR-007	Feature flags per client	accepted, 2022
ADR-008	Single sign-on switched per depot	accepted, 2023
ADR-009	Session length of eight hours	accepted, 2023
ADR-010	Roles from Entra ID groups at every sign-in	accepted, 2024
ADR-011	Audit log in identity-service's database	accepted, 2024
ADR-012	A US region for Ridgeway Freight	accepted, 2025
ADR-013	Phone codes by SMS through Textbridge	accepted, 2026
ADR-014	Sign-in rate limits at the edge and per account	accepted, 2026

The older ones without a page were written in the repositories' docs/adr folders before this space existed.

Writing one

Copy the shape of ADR-014: Context, Decision, Consequences, Status. Keep it to a page. Link the Jira issue or the Emargen initiative it came from. Ask Rafael to review.