Decisions and roadmap
Decision records
Every architecture decision record, rendered directly from docs/adr.
The pages in this section are compiled straight from the Markdown in
docs/adr/. The ADR files are the single
source of truth: they carry no docs-specific frontmatter, and their title, status, and date are
read from each record's own heading and bullet list. Links between records resolve to docs pages,
and links to other repository files point at the file on staging.
When records conflict, the newest accepted ADR wins. For example, ADR 0003 (Convex Auth v2) supersedes ADR 0002 (Clerk identity boundary).
0001: Reversible content backend
Status: superseded by ADR 0003 · Date: 2026-07-18
0002: Clerk identity and Exo authorization boundary
Status: superseded by 0003-convex-auth-v2-identity-plane.md · Date: 2026-08-26
0003: Convex Auth v2 as the shared identity plane
Status: accepted · Date: 2026-09-23
0003: Convex-first EXO control plane
Status: accepted · Date: 2026-09-14
0004: Exo ID — Exo is the central identity provider; apps are relying parties
Status: accepted · Date: 2026-09-25
0005: exo-verify — code verification as a platform service
Status: accepted (owner-approved 2026-09-27) · Date: 2026-09-27
0006: exo-analyze — Exo-owned product analytics
Status: accepted (owner-approved 2026-09-27) · Date: 2026-09-27
0007: exo-mobilize — Expo mobile release toolkit
Status: accepted (owner-approved 2026-09-27) · Date: 2026-09-27
Not yet on staging
ADRs 0005–0007 were accepted on main on 2026-09-27 and will appear here automatically once
they reach staging. Until then, read them on main:
0005 exo-verify ·
0006 exo-analyze ·
0007 exo-deploy (was exo-mobilize).
Summaries are on the platform services pages.
Writing a new ADR
- Add
docs/adr/NNNN-short-slug.mdwith a# ADR NNNN: Titleheading and- Status:and- Date:bullets, following the existing records. - Open it through the normal canary →
stagingpath. The docs pick it up at build time with no further change.
Source: content/docs/adr/index.mdx