| 1 | # Review brief: region HA spec 1 rev 5.4, round 5 |
| 2 | |
| 3 | You are an independent second reader. Review |
| 4 | `docs/superpowers/specs/2026-10-04-region-ha-box-placement-design.md` at |
| 5 | the commit named in the prompt, in the repository at the working |
| 6 | directory (Go; carlos platform). |
| 7 | |
| 8 | ## What changed and why |
| 9 | |
| 10 | Rev 5.4 answers your rev 5 round 4 findings |
| 11 | (`CODEX-FINDINGS-REGION-HA-REV5-4.md`). §23 is the disposition table. |
| 12 | |
| 13 | - **B4-1:** under H19, volume recording never gates execution, |
| 14 | admission, relocation or recovery. §8's multi-box gate no longer |
| 15 | checks it. A box's start re-checks only the gate's runtime half |
| 16 | (capability, floor, roster); the termination queues and the recorder |
| 17 | are rollout checks. Recorder failure alerts and keeps a dead box's |
| 18 | `park-local` chores open. §10 tests start, row minting and recovery |
| 19 | with `control/box-volumes/` unwritable; §19 drops it from plan 1b's |
| 20 | gate item. |
| 21 | - **B4-2:** §5.8's source-loss table discharges chores only on |
| 22 | qualifying volume records; §6's tofu note says |
| 23 | `delete_on_termination` affects only discharge; §7's one-box row |
| 24 | fences on the `terminated` read alone. |
| 25 | |
| 26 | ## Fixed: do not re-argue |
| 27 | |
| 28 | Rulings H1 to H19 in §0 (H19 supersedes H15 and the volume half of |
| 29 | H10), and the claim's own ruled text (R6 in particular: no warm reuse of |
| 30 | a local database). Report only mechanisms that fail to honour them, are |
| 31 | unsafe, or are missing. |
| 32 | |
| 33 | ## Sources to check against |
| 34 | |
| 35 | - Claim spec: `git show origin/design-replica-ownership:docs/superpowers/specs/2026-10-02-host-lifecycle-claim-design.md` |
| 36 | (§2, §4, §5.1, §5.9 PROPOSED, §6.4, §6.4a, §6.6 PROPOSED, §7, §8, §10.1 PROPOSED). |
| 37 | - Claim code on main: internal/hostclaim, internal/hostguard, |
| 38 | internal/stopevidence, internal/park, internal/genselect. |
| 39 | - Moves spec: /home/paulca/amadan.net/carlos/platform-moves-design/docs/superpowers/specs/2026-10-02-move-any-app-design.md |
| 40 | (latest committed rev on that worktree's branch). |
| 41 | - Plan 1a's code on main, for §18 and §19's claims about it. |
| 42 | ## Focus |
| 43 | |
| 44 | 1. **First, a disposition table** for B4-1 and B4-2: resolved, partly |
| 45 | resolved (say what remains) or not resolved, each with the section |
| 46 | that answers it. |
| 47 | 2. **Then only new findings.** Do not re-raise anything resolved in any |
| 48 | earlier round (rounds 1 to 6 of rev 4.x, rev 5 rounds 1 to 4) unless |
| 49 | this revision broke it; if it did, say which change broke it. Data |
| 50 | retention of surviving disk copies is out of scope by H19. |
| 51 | |
| 52 | ## Output |
| 53 | |
| 54 | The disposition table, then new findings ranked P1 (unsafe or blocks a |
| 55 | plan), P2 (wrong or missing), P3 (clarity). Each: section, the problem, |
| 56 | a concrete failing sequence, and a suggested fix. End with a verdict: |
| 57 | ready for plan, or not ready. |
| 58 | |
amadan