diff --git a/docs/kubernetes-change-gate-decision.md b/docs/kubernetes-change-gate-decision.md
index 9a3a9a8..a182298 100644
--- a/docs/kubernetes-change-gate-decision.md
+++ b/docs/kubernetes-change-gate-decision.md
@@ -61,7 +61,20 @@ ops-mason's executor is narrower than a generic `kubectl apply`:
 
 This decision relies on those limits. Widening them is a new decision.
 
-## Not verified here, and possibly not true
+## Verified 2026-09-21: ArgoCD is not on railiance01
+
+A read-only check, run by the custodian over SSH with the founder's approval, established:
+
+- The node is `92.205.62.239`, the single k3s control-plane node.
+- The `argocd` namespace does not exist.
+- The `applications.argoproj.io` CRD does not exist.
+- The resource type `applications` is unknown to the API server.
+
+Only `get` was used; nothing was applied, patched or synced.
+
+**So the production row has no working path on railiance01.** Until one exists, the transition rule applies to every production-tier target there. Installing ArgoCD on railiance01 is a cluster-layer change and needs its own founder go-ahead. It is not part of this decision.
+
+### What the records said before the check
 
 Whether ArgoCD runs on railiance01 at all is unverified, and railiance-platform's own records point the other way: