From d7e96156993f85f07f544404d781503e7723295f Mon Sep 17 00:00:00 2001 From: Lily Shen <115414357+lilyshen0722@users.noreply.github.com> Date: Wed, 2 Sep 2026 16:50:32 -0700 Subject: [PATCH] docs(adr-027): name ADR-025's Draft status where ADR-027 inherits from it ADR-027 cites four ADR-025 decisions (D6, D9, D10) as if settled. ADR-025 is `Status: Draft / Proposed` and its own text reads D1-D7 as proposals; D8-D16 arrived via the 2026-09-02 fold carrying the same status. A reader arriving at ADR-027 through those citations inherits an unratified premise with nothing in the document signalling it. The scope-boundary block already names ADR-025 as the sibling, so the qualifier lands in place beside the existing cross-link rather than as a new section. Closes the second half of #1424; the citation half was repaired by the fold (#1295, `702bc638`) and is verified on main. Co-Authored-By: Claude Opus 5 --- docs/adr/ADR-027-pm-tool-projection-contract.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/docs/adr/ADR-027-pm-tool-projection-contract.md b/docs/adr/ADR-027-pm-tool-projection-contract.md index 3259e4287d..60bb2e6e06 100644 --- a/docs/adr/ADR-027-pm-tool-projection-contract.md +++ b/docs/adr/ADR-027-pm-tool-projection-contract.md @@ -18,7 +18,14 @@ architecture. status, assignees, provenance) project two-way between a Commonly pod and an external PM surface. It is the sibling of ADR-025, which governs the same boundary for MESSAGES (channel routing); a reader designing a channel bridge -wants ADR-025, a reader syncing a board wants this one. It does not govern +wants ADR-025, a reader syncing a board wants this one. **ADR-025 is itself +`Draft / Proposed`** — its own status line reads D1–D7 as the substrate +audit's proposals, and D8–D16 arrived through Sam's 2026-09-02 fold +carrying that same status. So the ADR-025 decisions this document inherits +(D6 for credentials behind a secret reference, D9 for transport-is-kernel, +D10 for the relayMap routing table) are premises, not settled rulings: +ratifying this ADR does not ratify them, and if D9 or D10 move, D2 and the +attribution rule move with them. It does not govern the attention gate (ADR-017/018), and it uses — not changes — the Installable taxonomy (ADR-001) and the task board (`/api/v1/tasks`).