carlos / platform Public

spec: host lifecycle claim rev 6.29, the two-box model gates relocation, not moves

Moves Phase 1 is one-box; relocating (L1, L9-L13) activates only after
region HA's two-box model and witnesses validate it. A source-terminated
pre-flip move in a one-box region holds safely at relocating/pinning
until a box is enrolled.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
claude agent, operated by paul@keymail.dev 5f0fa3b4c9d4a1eba4a1a9abf9ee1775506c00a0 parent 4ffe8a0
1 file changed, +13 −5
  • docs/superpowers/specs/2026-10-02-host-lifecycle-claim-design.md +13 −5

CI passed — run details

diff --git a/docs/superpowers/specs/2026-10-02-host-lifecycle-claim-design.md b/docs/superpowers/specs/2026-10-02-host-lifecycle-claim-design.md
index f342d3961..41de6c828 100644
--- a/docs/superpowers/specs/2026-10-02-host-lifecycle-claim-design.md
+++ b/docs/superpowers/specs/2026-10-02-host-lifecycle-claim-design.md
@@ -1,6 +1,6 @@
# The host lifecycle claim
-Design, 2026-10-06, **rev 6.28**. Joint rounds 6 and 7 judged the claim ready for primitive planning. Rev
+Design, 2026-10-06, **rev 6.29**. Joint rounds 6 and 7 judged the claim ready for primitive planning. Rev
6.5 added the R6-4 rule. Rev 6.6 added writer epochs (R7-1, amadan #225).
Rev 6.7 answered the moves session's notes on §6.4a. Rev 6.8 rewrote §6.4a
around writer sessions, for joint round 8. Rev 6.10 answers joint round 10
@@ -28,7 +28,8 @@ spec's rev 7.17 notes (a delete's parks are scoped; a create's first
admission declares nothing). Rev 6.26 answers joint round 17's R17-2 (a
delete may use the whole-host staging scope). Joint round 17 was CLEAN. Rev 6.27 records Paul's rulings on #236
(§1.1) and marks §5.9, §6.6, §7.3 and §10.1 ruled, as amended there.
-Rev 6.28 adopts region HA spec 1 rev 5.4's L1 to L20 (amadan #236) at their sections, pending joint round 18.
+Rev 6.28 adopts region HA spec 1 rev 5.4's L1 to L20 (amadan #236) at their sections. Rev 6.29 scopes the two-box model to region HA's plan as
+an activation gate for `relocating` (moves Phase 1 is one-box).
Rev 6.9 answered
joint round 9
(R9-1 to R9-4) and takes **Paul's ruling R6 (2026-10-04): a box never
@@ -171,9 +172,16 @@ where this section and the proposal text differ, this section wins.
Litestream fix or upgrade (#234) makes a certificate safe. Revisit then.
L1-L20 are adopted in rev 6.28 at the sections named in
-`docs/superpowers/specs/CODEX-ANALYSIS-REGION-HA-L1-L20.md`, pending joint
-round 18, which must include the two-box-per-region model, L18, and the
-analysis's extra witnesses (§11).
+`docs/superpowers/specs/CODEX-ANALYSIS-REGION-HA-L1-L20.md`. Joint round 18
+reviews them statically with moves 7.20; moves Phase 1 runs only in
+one-box regions and refuses a move into or out of a region with more than
+one eligible box. **Activation gate:** `relocating` and the rules it
+depends on (L1, L9 to L13) must not be enabled until region HA's own
+two-box-per-region model (L18) and the analysis's extra witnesses (§11)
+validate them, as part of region HA's plan. A source-terminated pre-flip
+move in a one-box region converts to `relocating` and holds at `pinning`
+(no writer, data pinned, obligations kept) until an eligible box is
+enrolled.
## 2. The object