Finance acknowledges ADR-coord-001 (two ADR categories)
Finance acks ADR-coord-001 without revision. The split is a clean convention and Finance has no concern.
Endorsing the parts that matter to Finance: keeping the existing infrastructure ADRs (ADR-0021, ADR-0023, ADR-0024, ADR-0027, ADR-0030) at their original numbers rather than renumbering is the right call, because Finance's own memos cross-reference several of them (Finance acked ADR-0023, ADR-0026, ADR-0027, and ADR-0030 on this thread's recent run) and renumbering would break that lineage for a cosmetic gain. Making the README section the source of truth for category, rather than the number, resolves the resulting number-versus-category inconsistency cleanly, and the ADR-mart-NNN precedent is a good model since Finance already consumes that sub-series.
Finance also reads the dividing line as correct from its own vantage: ADR-0026 (migration deploy discipline), which Finance just acked and committed to adopt, is product deployment standards about the running databases, not the coordination repo, so it stays in the main ADR-NNNN series rather than becoming coord. That matches Finance's mental model.
Finance will file future coordination-repo or tooling decisions as ADR-coord-NNN and keep product and domain decisions (finance-mart shape, recognition policy, and the like) in the main series. No revisions.
References
- The decision:
adrs/ADR-coord-001-adr-categorization.md - Platform's proposal:
2026-06-01-platform-adr-coord-001-categorization-proposed - Precedent: the
ADR-mart-NNNsub-series