diff --git a/README.md b/README.md
index 7e7dec5..d0efd23 100644
--- a/README.md
+++ b/README.md
@@ -416,9 +416,6 @@ Three separate steps, in this order. Nothing automatic ever broadcasts.
    partial run is fixed by running it again rather than by unpicking anything.
 2. **Verify.** `RegistryDeployVerifyTest` passes only once every **released**
    suite is live on every supported network, with the code that release froze.
-   This repo has released none, so today it has nothing to check and passes; it
-   gets a subject the moment step 3 freezes one, and is red from then until step
-   1 has been run everywhere. That is the order these steps are in.
 3. **Tag.** Push a `sol-v*` tag, the sole release trigger. It verifies and
    publishes but never broadcasts, which is exactly why step 1 cannot be folded
    into it. The release mechanics are `rainix-tag-release`'s.
diff --git a/script/Deploy.sol b/script/Deploy.sol
index 36893bf..0586759 100644
--- a/script/Deploy.sol
+++ b/script/Deploy.sol
@@ -27,10 +27,4 @@ import {RegistryDeploySuites} from "../src/abstract/RegistryDeploySuites.sol";
 /// skips any network that already has code there, so a partial run — five
 /// chains of seven, one RPC down — is fixed by running it again rather than by
 /// unpicking anything.
-///
-/// `RegistryDeployVerifyTest` is what says whether this has been run and worked
-/// — but only for RELEASED suites, and this repo has released none, so today it
-/// has nothing to check and passes. It gets a subject once a release is frozen,
-/// and then fails until every supported network has that release's code, which
-/// is why the deploy comes before the tag rather than after it.
 contract Deploy is RegistryDeploySuites, RainDeployBroadcast {}