review(1b): acknowledge operator RL5+RL6 (plan §7) as new blocking items. RL5 (nix/ folder consolidation) verification folds into RL3 cold byte-identical rebuild; RL6 (machine-docs/ move) is coordinated near-end-of-1b — REVIEW*.md are my files, I keep writing at root until the lockstep watchdog cutover then git mv my own. DoD now RL1–RL6

REVIEW-1b.md

@@ -112,6 +112,22 @@ Remaining §3 checklist items. **No blocking findings.**
 IDEAS; app-secret redaction → RL3/D6 watch-item). I expect Builder's W1 to be light. I have NOT filed
 `[adversary]` BACKLOG items since nothing is blocking — will file if W1/RL3 surfaces a real defect.
 
-## Status: W0 PASS + §3 white-box pass complete (no blockers). Awaiting Builder W1 claim (review+fixes).
-RL3 (full cold D1–D10 re-verify) deferred to LAST per plan order. Cardinal rule: cleanup must not
-weaken/skip/regress any test — incl. the conditional-upgrade-skip watch-item from pass #1.
+## Operator added RL5 + RL6 (plan §7, 2026-05-27) — both BLOCKING for 1b DONE. Noted; verification plan:
+- **RL5** (Builder moves; Adversary verifies cold): `modules/`→`nix/modules/`, `hosts/`→`nix/hosts/`;
+  `flake.nix`/`flake.lock` STAY at root so build ref `#cc-ci` is unchanged; fix flake internal paths +
+  `.drone.yml`/scripts refs; update `docs/architecture.md`. **Verification folds into RL3:** a fresh
+  recursive clone must still rebuild **byte-identical to the running system** (toplevel store hash WILL
+  change — expected; what must hold is build==running + reproducible). I'll re-confirm cold at RL3.
+- **RL6** (coordinated near-END-of-1b): move `STATUS*/REVIEW*/JOURNAL*/BACKLOG*/DECISIONS.md` →
+  `machine-docs/`; **README.md stays at root** (operator decision — human readme, not protocol). Update
+  ALL refs (cc-ci-plan plans, AGENTS.md, .drone.yml, scripts). I verify refs updated + nothing broken.
+  ⚠ **CAVEAT affecting ME:** the watchdog (`launch.sh`) reads `STATUS-<id>.md`/`REVIEW-<id>.md` at repo
+  ROOT for handoffs/transitions — moving breaks it until launch.sh updated + watchdog restarted IN
+  LOCKSTEP (orchestrator handles that). So **I keep writing REVIEW-1b.md at root until the coordinated
+  cutover**, and at that moment I `git mv` my own REVIEW files (single-writer rule) in lockstep. Will NOT
+  move them unilaterally or while a phase transition is pending.
+
+## Status: W0 PASS + §3 white-box pass complete (no blockers). New blocking items RL5/RL6 noted.
+DoD for 1b is now **RL1–RL6** (was RL1–RL4). Awaiting Builder gates (W1 review+fixes; RL5 layout move;
+then RL3 cold re-verify LAST, now also covering the RL5 byte-identical rebuild). Cardinal rule holds:
+cleanup/refactor must not weaken/skip/regress any test — incl. the conditional-upgrade-skip watch-item.