docs(adr): ratify ADR-0003, 0006, 0007, 0008, and 0009

[mbeacom]

What and why

Five foundational ADRs — 0003, 0006, 0007, 0008, 0009 — move from proposed to accepted. This is hygiene catch-up: the work these records authorize shipped long ago (the Spec Kit extension, adapter isolation, affects resolution, MADR migration), but the records themselves were never ratified.

This closed a governance inversion, not a formality. Nine accepted records already relied on ADR-0007 and six on ADR-0009 — and two of them narrow clauses of a record that was never ratified: ADR-0013 amends both, ADR-0012 refines ADR-0009. Accepted decisions were resting on a proposed foundation.

Pending	Depended on by accepted ADRs
0007	9 — 0004, 0010, 0012, 0013, 0014, 0017, 0018, 0019, 0020
0009	6 — 0012, 0013, 0014, 0015, 0020, 0022
0006	2 — 0010, 0011
0003	1 — 0019

Verified, not assumed

Each record was checked against the tree rather than trusting its own checkboxes — which turned out to matter, since the boxes were stale in both directions:

• 0007 — both assertions are live and are required status checks on main (clean-clone-builds, plus scripts/check-deps.ts, observed failing per ADR-0016).
• 0009 — four of five deliverables exist: core/src/affects/, the purity test, test/conformance/, and adr explain. The catalog-port item is left unchecked — the port type exists, but no adapter implementation ships (catalog-backstage is placement only and generates nothing).
• 0006 — Apache-2.0 on all five packages, schema/LICENSE (CC0), and $id already on the namespace-independent adrkit.dev. The repo is public, so this one-way door is irreversible in fact.
• 0008 — adr migrate --from madr, import-incomplete, and the fingerprint + four-bucket classifier all ship.
• 0003 — @adrkit/spec-kit 0.1.2 and the standalone CLI both ship; ADR-0019 already resolved the spike no-go.

Ratification is recorded as review.decidedAt and review.approvals — the first use of either field in this corpus — so the audit trail carries when and by whom instead of leaving status to imply it.

Left honestly unchecked

Action items that are genuinely open were not ticked:

• ADR-0006 feat: Seed project and initial ADRs #2 — DCO bot. Sign-off is practiced (every commit carries the trailer) and documented (CONTRIBUTING.md, PR template), but no ruleset check enforces it. Tracked in Enforce DCO sign-off as a required check (ADR-0006 action item 2) #130.
• ADR-0006 Phase 0: spec-kit constitution + schema and core #5 — external participation obligations, not verifiable from the tree.
• ADR-0008 chore: Initialize spec-kit in project #4 — re-import PR, unbuilt because non-MADR re-import is unbuilt.
• ADR-0003 feat: Add Bun config & instructions for using Bun as primary toolchain #3 — positioning one-pager.
• ADR-0009 chore: Initialize spec-kit in project #4 — catalog port; the port type exists but no adapter implementation ships. Still governed by ADR-0013 and ADR-0020.

Why several records in one PR

This follows existing practice: #74 ratified ADR-0016 and ADR-0017 together; #110 ratified ADR-0022 and ADR-0023 and retired ADR-0021. The CONTRIBUTING rule requiring a superseding record "with the argument, not just the status flip" is scoped to changes that contradict an accepted record — ratifying a proposed record contradicts nothing and completes its intended lifecycle. (Contrast e45335a, where changing ADR-0021's substance correctly produced ADR-0022 rather than an edit.) All five share one rationale, so they belong together.

ADR-0005 deliberately stays proposed

Only Pass 0 of its four passes exists — by design, since spec 005 scoped itself to Pass 0. But the record carries a SOC2 CC8.1 control plus a standing commitment to publish escalation precision and recall each release, including the false-negative rate. Ratifying it would assert a compliance obligation the project cannot yet compute. Its reviewBy of 2027-01-18 leaves room to ship Passes 1–3 first.

ARB queue depth drops 6 → 1, which the queue-depth badge reads from $.totalItems (regenerated at site build; nothing committed goes stale).

Checklist

• Commits are DCO signed off (git commit -s). No CLA is required.
• If this changes a recorded decision in docs/adr/, an ADR is added or
  supersedes the affected record — with the argument, not just a status flip.
  (N/A — no accepted record is contradicted; see "Why several records in one PR".)
• If the schema changed, I edited the Zod source — N/A, no schema change.
• If packages/ci/src or @adrkit/core changed, I regenerated
  packages/ci/dist — N/A, docs-only change.
• New or changed behavior is covered by tests — N/A, no behavior change;
  the corpus is covered by existing lint/check/conformance gates.
• bun run typecheck && bun run build && bun test && bun run lint pass from a
  clean clone with no credentials configured
  (ADR-0007).

Also green locally: adr lint (25 records, 0 errors/0 warnings), adr check on the changed files (0 changed-record errors), check:deps, check:changelog, check:doc-pins, check:freeze-hashes, and 1997 tests.

Review feedback addressed (fe4363a)

All three review comments were correct.

1. ADR-0009 item 4 unticked. I had ticked it on the reasoning that the port type plus a committed adapter package was the deliverable. The package disagrees: it exports only PACKAGE_NAME and states "No generator has run. No envelope exists." The item now says exactly what exists and points at ADR-0013/ADR-0020.
2. Changelog corrected from "all five deliverables" to "four of five", dropping catalog-backstage as a claimed reference implementation.
3. MANIFEST.md refreshed — and it was worse than reported. Beyond listing the five as proposed, it stopped at ADR-0019 and claimed "19 records, 13 accepted" against an actual 25. Now carries 0020–0025, the real counts (23 accepted, 1 proposed, 1 superseded), and a catalog note consistent with the unticked item.

Also closed the two follow-ups this decision satisfies: ADR-0012 item 4 (open the ratification decision for 0007/0009) and ADR-0013 item 1 (fold the amendments in on accept — both records already carry them inline). ADR-0012 items 2 and 3 stay open; they gate the persisted envelope and the generator, which no ratified clause asserts.

None of this disturbs the ratification: ADR-0009's decision is the pinned resolution semantics, which are implemented, pure, and conformance-tested.

[Copilot]

Pull request overview

Ratifies five foundational ADRs and records their implementation status and approval metadata.

Changes:

• Moves ADRs 0003, 0006–0009 from proposed to accepted.
• Updates completed action items.
• Documents the ratifications in the changelog.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
CHANGELOG.md	Records the ratifications and queue impact.
docs/adr/0003-ship-as-spec-kit-extension.md	Accepts ADR-0003.
docs/adr/0006-license-apache-2-and-single-monorepo.md	Accepts ADR-0006 and updates actions.
docs/adr/0007-adapter-isolation-and-public-surface-build.md	Accepts ADR-0007 and updates actions.
docs/adr/0008-import-and-migration-semantics.md	Accepts ADR-0008 and updates actions.
docs/adr/0009-affects-resolution-and-catalog-binding.md	Accepts ADR-0009 and updates actions.

---

💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.