Skip to Content
Architecture DecisionsIndex

Architecture Decision Records

An ADR captures a specific, owner-approved (or proposed) architecture or product decision — not a feature spec. Most day-to-day design decisions in this codebase are made inline in the relevant concept doc (see Concepts) and don’t get a separate ADR; a decision gets one when it needs an explicit owner, an approval gate, or a record of alternatives considered.

Register

IDTitleStatus
ADR-015Holder IDV Liveness PrivacyProposed — not approved

Known gap: ADR-014

Master Data Registry states catalog/learner schema ownership was “Approved for implementation (ADR-014) and built.” No ADR-014 document exists, in this tree or its V1 predecessor — the decision was evidently approved without ever being written down. This register does not fabricate a retroactive ADR-014; the citation is left in place in that doc as an honest record of the gap. If that decision is ever formally documented, it belongs here as ADR-014 and this note should be removed.

There is no ADR-001 through ADR-013 or ADR-016+ anywhere in the project’s history — ADR-015 is the first (and so far only) architecture decision actually captured as a standalone record.

Functional RequirementsADR-015: Holder IDV Privacy