diff --git a/docs/retirement-cutover-slice-plan.md b/docs/retirement-cutover-slice-plan.md
index 3e99460..9b775f9 100644
--- a/docs/retirement-cutover-slice-plan.md
+++ b/docs/retirement-cutover-slice-plan.md
@@ -180,10 +180,26 @@ dual-running now — the adapter is proven but switched off, and there is no
 `~/.repo-manager/dual-run.yaml`.
 
 **So the concrete next executable step is operational, not code:** create the
-dual-run config and enable `RM_WRITEBACK` + `RM_RECONCILE` for a pilot repo,
-then watch the mutation meter for divergence. That is A2a moving from `off` to
-`dual`. It needs an operator decision because it changes how live task writes
-flow; it is reversible by clearing the flags.
+dual-run config and enable `RM_WRITEBACK` + `RM_RECONCILE`, then watch the
+mutation meter for divergence. That is A2a moving from `off` to `dual`.
+
+**The pilot repo is already established — `repo-manager`**, per RMGR-WP-0003 and
+the shipped `repo-manager/config/dual-run.pilot.example.yaml`. No new decision
+is needed about which repo; the procedure is documented in
+`repo-manager/docs/dual-run.md`:
+
+```bash
+mkdir -p ~/.repo-manager
+cp ~/repo-manager/config/dual-run.pilot.example.yaml ~/.repo-manager/dual-run.yaml
+# then restart the State Hub API — settings are cached per process
+```
+
+Rollback is `rm ~/.repo-manager/dual-run.yaml` plus a restart, or setting
+`writeback`/`reconcile` false.
+
+**Requires an operator**, for one reason only: it changes how live task writes
+flow and needs a State Hub API restart to take effect. Piloting on
+`repo-manager` keeps the blast radius to a single repo.
 
 ### A3 · Registers — 49 items
 `sbom-inventory` (10) · `repo-goals` (9) · `upstream-contributions` (9) ·