diff --git a/docs/design-decisions.md b/docs/design-decisions.md
index 14dd75b..f7f48d9 100644
--- a/docs/design-decisions.md
+++ b/docs/design-decisions.md
@@ -1623,7 +1623,10 @@
 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.
+never a routine-window action. Point 3 RULED 2026-07-21 (GA-R5): question as presented =
+"adopt the standing update order (controller -> agents -> charms; keystone first,
+nova-compute last; never interleave)?"; operator selection, exact utterance: "Adopt as
+proposed (Recommended)". The ops-update-procedure grouping is now policy, not habit.
 
 **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;