Architecture decision records
This catalogue brings the archived ADRs and the current platform decisions into one sequence. The historical records retain their original status and rationale. Read them in the context of the platform they describe; the current architecture starts with 0034 — fresh service-first skeleton.
Numbering and provenance
- The 25 historical records come from the archived ADR directory
in the main snapshot
8046ea0f1. The originals were relocated byte-for-byte intodocs/content/adrunder ADR 0042;docs/provenance.jsonrecords their original blobs and destinations. - Historical filenames are preserved, including both records numbered 0000 and both numbered 0007. Cite their full filenames to distinguish them. These exact pairs are the only exceptions to the duplicate-number check.
- Links between ADRs resolve within this directory. Supporting documents link to their archived copies. The LFS quota record's heading is corrected from ADR-0003 to ADR-0001 to match its original filename.
- ADR-0025 refers to a network-segmentation ADR-0024 absent from the archive. Its reference is retained as text with that limitation recorded.
- Numbers 0026–0033 occur in open legacy proposals as checked on 13 October 2026,
including the security proposals under
internal_plans/adrin PR #559. They are reserved here; importing this history does not accept those proposals. - The five newer records are renumbered in their existing order:
0001 → 0034, 0002 → 0035, 0003 → 0036, 0006 → 0037 and 0007 → 0038.
Allocate future numbers after the highest on
mainand in open pull requests.
Current platform decisions
Historical records
Page source
Source snapshot · Revision f928834c8.