amadan
spec: region HA spec 1 rev 5.4, Astra review brief (round 5)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1 file changed,
+57
−0
docs/superpowers/specs/CODEX-REVIEW-BRIEF-REGION-HA-REV5-5.md+57 −0
CI cancelled — superseded by a newer push — run details
diff --git a/docs/superpowers/specs/CODEX-REVIEW-BRIEF-REGION-HA-REV5-5.md b/docs/superpowers/specs/CODEX-REVIEW-BRIEF-REGION-HA-REV5-5.md| new file mode 100644 |
| index 000000000..6ee6f9093 |
| --- /dev/null |
| +++ b/docs/superpowers/specs/CODEX-REVIEW-BRIEF-REGION-HA-REV5-5.md |
| @@ -0,0 +1,57 @@ |
| +# Review brief: region HA spec 1 rev 5.4, round 5 |
| + |
| +You are an independent second reader. Review |
| +`docs/superpowers/specs/2026-10-04-region-ha-box-placement-design.md` at |
| +the commit named in the prompt, in the repository at the working |
| +directory (Go; carlos platform). |
| + |
| +## What changed and why |
| + |
| +Rev 5.4 answers your rev 5 round 4 findings |
| +(`CODEX-FINDINGS-REGION-HA-REV5-4.md`). §23 is the disposition table. |
| + |
| +- **B4-1:** under H19, volume recording never gates execution, |
| + admission, relocation or recovery. §8's multi-box gate no longer |
| + checks it. A box's start re-checks only the gate's runtime half |
| + (capability, floor, roster); the termination queues and the recorder |
| + are rollout checks. Recorder failure alerts and keeps a dead box's |
| + `park-local` chores open. §10 tests start, row minting and recovery |
| + with `control/box-volumes/` unwritable; §19 drops it from plan 1b's |
| + gate item. |
| +- **B4-2:** §5.8's source-loss table discharges chores only on |
| + qualifying volume records; §6's tofu note says |
| + `delete_on_termination` affects only discharge; §7's one-box row |
| + fences on the `terminated` read alone. |
| + |
| +## Fixed: do not re-argue |
| + |
| +Rulings H1 to H19 in §0 (H19 supersedes H15 and the volume half of |
| +H10), and the claim's own ruled text (R6 in particular: no warm reuse of |
| +a local database). Report only mechanisms that fail to honour them, are |
| +unsafe, or are missing. |
| + |
| +## Sources to check against |
| + |
| +- Claim spec: `git show origin/design-replica-ownership:docs/superpowers/specs/2026-10-02-host-lifecycle-claim-design.md` |
| + (§2, §4, §5.1, §5.9 PROPOSED, §6.4, §6.4a, §6.6 PROPOSED, §7, §8, §10.1 PROPOSED). |
| +- Claim code on main: internal/hostclaim, internal/hostguard, |
| + internal/stopevidence, internal/park, internal/genselect. |
| +- Moves spec: /home/paulca/amadan.net/carlos/platform-moves-design/docs/superpowers/specs/2026-10-02-move-any-app-design.md |
| + (latest committed rev on that worktree's branch). |
| +- Plan 1a's code on main, for §18 and §19's claims about it. |
| +## Focus |
| + |
| +1. **First, a disposition table** for B4-1 and B4-2: resolved, partly |
| + resolved (say what remains) or not resolved, each with the section |
| + that answers it. |
| +2. **Then only new findings.** Do not re-raise anything resolved in any |
| + earlier round (rounds 1 to 6 of rev 4.x, rev 5 rounds 1 to 4) unless |
| + this revision broke it; if it did, say which change broke it. Data |
| + retention of surviving disk copies is out of scope by H19. |
| + |
| +## Output |
| + |
| +The disposition table, then new findings ranked P1 (unsafe or blocks a |
| +plan), P2 (wrong or missing), P3 (clarity). Each: section, the problem, |
| +a concrete failing sequence, and a suggested fix. End with a verdict: |
| +ready for plan, or not ready. |