diff --git a/servers/corviduo-dev/README.md b/servers/corviduo-dev/README.md
index e9f98a9..3d44546 100644
--- a/servers/corviduo-dev/README.md
+++ b/servers/corviduo-dev/README.md
@@ -44,10 +44,19 @@ Three `docker compose` projects under `/opt/`:
 
 | Project dir | Container name | Role |
 |---|---|---|
-| `/opt/worldtree/` | `worldtree-worldtree-api-1` (port 8080) | Demo deployment — auto-deployed by Worldtree's CI on every push to `main`. The "shared" Worldtree instance vor + asset-engine talk to. |
-| `/opt/worldtree-personal/` | `worldtree-personal-worldtree-api-1` (port 8081) | Personal deployment — manually managed, separate compose project, persistent state independent of demo. |
+| `/opt/worldtree/` | `worldtree-worldtree-api-1` (port 8080) | Demo deployment — the "shared" Worldtree instance vor + asset-engine talk to. |
+| `/opt/worldtree-personal/` | `worldtree-personal-worldtree-api-1` (port 8081) | Personal deployment — separate compose project, persistent state independent of demo. |
 | `/opt/worldtree-pinned/` | `worldtree-pinned-worldtree-api-1` (port 8082) | Pinned deployment — intentionally lags behind `demo` for regression/comparison purposes. |
 
+> **Deploys are CI/CD-only — NOT an infra-ops job.** All three
+> deployments (demo, pinned, personal) are deployed exclusively by the
+> Worldtree team's CI/CD pipeline. infra-ops does **not** deploy these
+> manually. A peer "deploy Worldtree vX.Y.Z to <deployment>" request
+> sent to infra-ops is **misrouted** — point them back to their
+> pipeline; do not run the docker-as-root pattern to do it. The
+> docker-as-root pattern below is for **emergency-ops only**
+> (provider-key restore), not routine deploys.
+
 Each project has:
 - `compose.yaml` (image, env wiring, healthcheck, port mapping)
 - `.env` (provider keys, ports, image tag — `deploy:deploy mode 600`)