diff --git a/04-ISSUES/189-a-rebuild-from-the-same-commit-is-not-a-move/00-report.md b/04-ISSUES/189-a-rebuild-from-the-same-commit-is-not-a-move/00-report.md
index f2537ce..868a3d9 100644
--- a/04-ISSUES/189-a-rebuild-from-the-same-commit-is-not-a-move/00-report.md
+++ b/04-ISSUES/189-a-rebuild-from-the-same-commit-is-not-a-move/00-report.md
@@ -33,3 +33,11 @@ the artifact.
 *How this would be checked:* a controller test registering a build of an unchanged commit with a
 new artifact digest for a module whose policy rolls out: the machines are sent; `status` shows no
 machine behind afterwards.
+
+## Built in part, 2026-10-01
+
+mesh-controller 203 and 204: a plan sends the machines of every module in a built tier whose policy
+rolls out, once, moved commit or not, and waits for the ones a later tier is built by. After a merge
+nothing is left for a hand to push, except what a *record* policy leaves by design. What remains for
+a decision is the catalogue's own word: *moved* should follow the artifact, so a module rebuilt
+outside any plan — by `build` by hand — rolls out the same way.