diff --git a/docs/design-decisions.md b/docs/design-decisions.md
index 52821c5..14dd75b 100644
--- a/docs/design-decisions.md
+++ b/docs/design-decisions.md
@@ -1619,7 +1619,11 @@
 utterance: "Adopt as proposed (Recommended)". Cadence = monthly review of `can-upgrade-to` +
 controller patch delta; non-empty review opens a maintenance window run via
 ops-update-procedure; security-driven charm revisions may pull a window forward; no
-on-discovery updates.
+on-discovery updates. Point 2 RULED 2026-07-21 (GA-R5): question as presented = "adopt the
+patch-only controller rule for routine windows?"; operator selection, exact utterance:
+"Adopt as proposed (Recommended)". Routine windows move the controller by PATCH level only
+within the pinned 3.6 track; minor/major jumps are each their own D-NNN with rehearsal,
+never a routine-window action.
 
 **Problem:** the cloud accumulates available updates on two layers with no standing
 policy for either: (a) the Juju controller/agents (patch releases on the 3.6 track;