ADRs are required before unsafe P0 implementation work.
ADRs are also the amendment mechanism for the Stream specification set, as
defined in docs/spec-policy.md: an accepted ADR is the
only way to change the normative content of a spec at Review or Final
status, and a spec cannot reach Final while it depends on a Proposed
ADR. After the genesis deployment, specs for Permanent surfaces change only
through errata or successor-line documents; an ADR that would alter deployed
Permanent semantics is invalid by construction.
Expected ADRs are tracked in ops/ROADMAP.md:
| ADR | Status | Issue |
|---|---|---|
0001-drop-authorization.md |
Accepted | #17 |
0002-auction-custody.md |
Accepted | #21 |
0003-payment-accounting.md |
Accepted | #24 |
0004-admin-governance.md |
Accepted | #33 |
0005-randomness.md |
Accepted | #14 |
0006-metadata-freeze.md |
Accepted | #45 |
0007-upgrade-redeployment.md |
Accepted | #53 |
0008-revenue-splits-and-royalty-resolver.md |
Accepted | Protocol design request |
0009-protocol-v1-open-question-resolutions.md |
Accepted | Protocol v1 open-question resolutions |
0010-world-class-spec-pass.md |
Accepted | Nine-lens review resolutions |
0011-world-class-pass-round-2.md |
Accepted | Nine-lens round-2 resolutions |
0012-world-class-pass-round-3.md |
Accepted | Nine-lens round-3 resolutions |
0013-world-class-pass-round-4.md |
Accepted | Nine-lens round-4 resolutions |
0014-world-class-pass-round-5.md |
Accepted | Nine-lens round-5 resolutions |
0015-collection-identity-and-facade-readiness.md |
Superseded in part | W1/W2 identity signal and evidence gate remain; W3-W5 launch facade path superseded by ADR 0016 |
0016-core-native-only-erc721.md |
Accepted | Core-native-only launch line; facade ownership machinery deferred to a successor design |
0017-raise-only-parameter-governance.md |
Accepted | Raise-only GGP/GTP launch model; probes, lowering, emergency class 6, and permissionless parameter mutation removed pre-genesis |
0018-batch-operation-root-and-token-identity.md |
Accepted | #688: one manager batch root, N token operation IDs, ledger-owned root replay, and the atomic Core replay-state cutover are implemented; typed settlement and repeated-sale replay remain ADR 0019 / #694 blockers |
0019-payment-intent-orchestration.md |
Proposed | #664 contract-20 payer boundary and narrow sale/revenue settlement callbacks |
0020-executor-only-finality-recovery.md |
Proposed | #667; executor-only append-only recovery with dedicated Core pointer and recovery-aware serving; owner evidence and serving integration remain acceptance blockers; current LTA/LCM remain authoritative |
0021-immutable-revenue-resolver-validation-adapter.md |
Accepted | #670; source implementation remains blocked pending the independently approved normative interface freeze |
0022-immutable-artist-registry-validation-adapter.md |
Proposed | #670; artist-registry implementation remains blocked pending explicit architecture acceptance and interface freeze |
Each ADR should include problem, current behavior, intended behavior, alternatives, security impact, release impact, test plan, rollout plan, non-goals, and accepted risks.