amadan
Astra stage B round 9 brief (confirming rev 5.3)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1 file changed,
+24
−0
docs/superpowers/plans/CODEX-PLAN-REGION-HA-STAGE-B-BRIEF-9.md+24 −0
CI cancelled — superseded by a newer push — run details
CI log
=== gate === cd launchctx && go vet ./... && go test ./... -count=1 ok amadan.net/carlos/platform.git/launchctx 0.011s ? amadan.net/carlos/platform.git/launchctx/controlname [no test files] ? amadan.net/carlos/platform.git/launchctx/wireid [no test files] go vet ./... gofmt -l .: clean go test ./... -count=1 -timeout 30m amadan: job cancelled — a newer push superseded it
diff --git a/docs/superpowers/plans/CODEX-PLAN-REGION-HA-STAGE-B-BRIEF-9.md b/docs/superpowers/plans/CODEX-PLAN-REGION-HA-STAGE-B-BRIEF-9.md| new file mode 100644 |
| index 000000000..2ece84ea3 |
| --- /dev/null |
| +++ b/docs/superpowers/plans/CODEX-PLAN-REGION-HA-STAGE-B-BRIEF-9.md |
| @@ -0,0 +1,24 @@ |
| +# Astra round 9 brief: region HA stage B plan rev 5.3 (confirming) |
| + |
| +**Review:** `docs/superpowers/plans/2026-10-10-region-ha-1b-next-stage-b.md` rev 5.3 (a8744902). It answers your round 8 (`CODEX-PLAN-REGION-HA-STAGE-B-R8.md`). Only Task 10 changed. |
| + |
| +**Ruling 82.** The completion pass (discharge, hold release, owned-fence lift, mark) runs whenever claim mode is on, whatever `CARLOS_REGION_HA` is set to. With the flag off, or the relocation owners unbound, `NewRelocationRuntime` builds a completion-only runtime. That runtime reads only this box's own registry rows. It is covered by two tests: |
| +- A→B completes, the mark fails, and B restarts with region HA off: the pass still finishes and marks. |
| +- A box with no completion changes nothing. |
| + |
| +Checklist item 19 documents the operator loss path. |
| + |
| +**Two follow-on rulings:** |
| +- **83.** On every claim box, the agent now opens the claim assembly before the claim wiring, not just on region HA boxes. It is the same call the claim factory makes, made earlier. |
| +- **84.** In claim mode the documented loss path has no working route yet. Termination needs a failover start, which this plan's flag-off runtime does not build, and the console's declare-lost is refused while claim mode is on. This is recorded as a residual: |
| + - When B is alive, its pass now always runs. |
| + - When B is permanently dead and never terminated, and region HA is off, the host is already down, which is pre-HA behaviour. |
| + - In that case the barrier only blocks moves, deletes and purges, which would need loss resolution anyway. |
| + - The operator route for that case is the claim's loss resolution in claim mode, which the claim session owns. |
| + |
| +**Judge:** |
| +1. Is round 8's finding closed? |
| +2. Are rulings 83 and 84 acceptable? |
| +3. Is anything new introduced? |
| + |
| +Give findings as P1/P2/P3 with file:line, then a verdict: ready to build, or not. |