diff --git a/docs/CURRENT-STATE.md b/docs/CURRENT-STATE.md
index 466f51f..813823b 100644
--- a/docs/CURRENT-STATE.md
+++ b/docs/CURRENT-STATE.md
@@ -1488,6 +1488,24 @@
   path (ruling 2), which is the D-135 items 2-3 gap.** Progression across the session, all
   measured: 22 error -> 17 (backports) -> 4 (prefer-ipv6) -> 7 units in the single snap class
   (the count rose because more units reached the snap stage, not because more broke).
+  **NODE NAMING -- CANARY TESTED 2026-07-31, and the answer is that a MAAS rename alone is
+  COSMETIC-ONLY.** Operator asked for the `juju status` `Inst id` values (`mint-roughy`,
+  `pure-condor`, `able-puma` ...) to become role-based. **CORRECTION TO AN EARLIER CLAIM IN
+  THIS SESSION: that column shows the MAAS HOSTNAME, not the system_id** -- the first reading
+  came from the JSON `instance-id` field (`677cta`) and was wrong; the DISPLAYED value is the
+  hostname and it IS renameable. Canary: `civil-bug` resolved BY PINNED BOOT MAC
+  (`52:54:00:2b:ed:ab`) to the ruled `vr1-dc0-storage-04`, then renamed. **MEASURED RESULT:
+  MAAS ACCEPTED the rename on a `Deployed` machine (`fqdn: vr1-dc0-storage-04.maas`), but
+  `juju status` still shows `civil-bug` AND the running OS still answers `civil-bug`
+  (`hostname` and `hostnamectl --static`).** So MAAS's record moves and nothing else does --
+  juju captured the name at provisioning and the OS hostname is applied by cloud-init at
+  DEPLOY time. **CONSEQUENCE: renaming the other eight would buy nothing where the operator is
+  looking and would leave a three-way divergence (MAAS ruled name / juju stale name / OS stale
+  name).** Nothing functional rides on any of it -- the bundle places by TAG and every gate
+  resolves by PINNED BOOT MAC. **THE CLEAN POINT IS ENLISTMENT: this folds into the DC1
+  standup as a definition-of-done item (set the ruled hostname BEFORE commissioning, so MAAS,
+  the OS and the ruled name agree from the start), and reaches DC0 at its next node
+  redeploy.**
   **memcached SCALED to 3 in `overlays/dc-ha-scaleup.yaml`** (operator-directed 2026-07-31);
   its exclusion comment is RE-POINTED rather than left stale. **`ceph-rbd-mirror` is PINNED,
   NOT SETTLED** -- gap register **item 22** carries four options and the recommendation