This file is the single source of truth for ADR numbers. Before you start
a new ADR, claim the next free number by adding its row here first, then
create NNNN-slug.md. Numbers are permanent once claimed — an ADR that is
later rejected or superseded keeps its number and records that outcome in its
own Status line; the number is never reused.
Why a register: ADR numbers were being picked independently and two drafts
collided on 0009. Claiming the number here before writing the file makes the
next free number unambiguous even when more than one change is in flight at
once.
Next free number: 0020.
| # | Title | Status |
|---|---|---|
| 0001 | The seed library is the schema authority; a check's subject is a tag XOR a system | accepted |
| 0002 | Capture-side fields land before crews start logging | accepted |
| 0003 | Core/premium boundary: premium is a sidecar on the public REST API | accepted |
| 0004 | Test-equipment traceability lives in core; punch items link to their evidence | accepted |
| 0005 | Warranty & closeout tracking: record the clock, not the deadline | accepted |
| 0006 | Service connections: the third check subject, by nullable relation | accepted |
| 0007 | LOTO visibility: an append-only lock ledger, and the staleness asymmetry | accepted |
| 0008 | VFD rotation & parameter check: a specialized capture UI on the ordinary ledger | accepted |
| 0009 | Per-tag phase applicability (tags.phases_na) |
accepted |
| 0010 | Signatures & the turnover package: a signed, frozen snapshot over the append-only ledger | accepted |
| 0011 | Auth lockdown: a small public allowlist, everything else signed in | Accepted |
| 0012 | Open→resolve records: duration/reliability tests and bac-t samples as a linked pair of append-only checks | accepted |
| 0014 | Segment acceptance records: pipeline segments as the fourth subject kind | superseded — moved to MainLine (2026-07-18) |
| 0013 | Training as a signable milestone check, not only a closeout deliverable | proposed |
| 0015 | Stored-equipment preservation log (recurring, tag-subject) | accepted |
| 0016 | Instrument calibration uses a purpose-built as-found/as-left ledger | accepted |
| 0017 | Vendor field service reports: immutable visits with attached proof | accepted |
| 0018 | Multi-vendor startup: staged checkout, explicit resolution, and vendor evidence as the GC's master ledger | accepted |
| 0019 | Shutdown runbook execution: a planned outage as an append-only step-event ledger | accepted |
ADR 0010 has a companion, 0010-review-notes.md — a
design review, not its own numbered decision.
ADR 0018 has a companion, 0018-review-notes.md — a
source verification, not its own numbered decision. ADR 0018 was written
from a summary of the field observations; the notes record what reading the
source package directly confirmed, corrected, and newly raised.