amadan
docs: rehearsal runbook P-0 names the post-Plan 12 branch, Plan 13's home rollout order and the claim's #250 activation items
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1 file changed,
+30
−6
docs/superpowers/plans/2026-10-06-moves-phase1-rehearsal.md+30 −6
diff --git a/docs/superpowers/plans/2026-10-06-moves-phase1-rehearsal.md b/docs/superpowers/plans/2026-10-06-moves-phase1-rehearsal.md| index 87806b515..cb583fd00 100644 |
| --- a/docs/superpowers/plans/2026-10-06-moves-phase1-rehearsal.md |
| +++ b/docs/superpowers/plans/2026-10-06-moves-phase1-rehearsal.md |
| @@ -204,14 +204,38 @@ deployment before its first run. |
| - [ ] **Moves Plan 5 Task 9b, Plan 4 Tasks 9 and 10 (the box half), and |
| Plan 5 Task 8 merged.** They wire moves onto claim Plan 12. Run 4 also |
| needs claim Plan 12's loss-bound admission. |
| -- [ ] **The moves cut guard merged** (branch `moves-cut-guard`, Paul's |
| +- [ ] **The moves cut guard merged.** It is on main (b04ff852, Paul's |
| ruling of 2026-10-11). The source refuses a cut unless the target |
| - reports its landing armed. It adds a `T13` check to the target's report |
| - and records why a cut did not start. It is not on main yet. |
| + reports its landing armed (the `T13` check), and records why a cut did |
| + not start. |
| +- [ ] **Moves' post-Plan 12 branch merged** (`moves-phase1-5f`). It brings |
| + the wake source, the recovery owners, the loss rules, the root held |
| + release (T7 stages, `configured` publishes, through root's control |
| + socket) and the C8 files-manifest provider. |
| - [ ] **For any run that touches the home region: the home-region parks fix |
| - part 1 merged** (#236). Part 1 covers moves out of home. Moves into home |
| - need part 2, and the door refuses them until then ("moves to the home |
| - region are not supported yet. the home publishes no staging lane"). |
| + part 1 merged** (#236, on main as 359e8ac2) **and claim Plan 13's home |
| + naming** (a0806e4c, follow-ups 2ad5412c). Part 1 covers moves out of |
| + home. Moves into home need part 2, and the door refuses them until then |
| + ("moves to the home region are not supported yet. the home publishes no |
| + staging lane"). A home box arms only when the claim grants it the |
| + `@home` alias, which needs the signed fleet home designation. Plan 13's |
| + rollout order is binding: every roster reader on a Plan 13 build first, |
| + then publish the designation, then turn the flag on. Older binaries |
| + cannot read a roster that carries `home_region`. |
| +- [ ] **The claim's activation checklist (#250) done for this deployment.** |
| + Among its items: |
| + - the one-time files-manifest backfill for every host older than the |
| + files publisher. Until it has run for a host, that host refuses to wake |
| + (`ErrNoEvidence`), by design; |
| + - claim Plan 15's admitted-generation record, so hosts with history past |
| + the eight-admission window can prove their file origins. Until then |
| + those hosts refuse; |
| + - claim Plan 14 (#280), so that root trusts no service-owned state; |
| + - `CARLOS_RELEASE_PUBKEY` readable by instance control |
| + (`/etc/carlos/host.env`), or every held release is refused; |
| + - with `CARLOS_MOVES_PHASE1` on, a usable `CARLOS_SECRETS_KEY` on every |
| + box. Without it the moves source refuses to open and the box serves |
| + nothing. Its log names the cause once per start. |
| - [ ] **All of the above released and rolled, consoles first, then every |
| box.** Check every box with `carlos system status --console <console>`: |
| each reads `current` on the new version. |