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`).