Astra brief: region HA spec 2, round 6
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1 file changed,
+16
−0
docs/superpowers/specs/CODEX-REVIEW-BRIEF-REGION-HA-SPEC2-6.md+16 −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/specs/CODEX-REVIEW-BRIEF-REGION-HA-SPEC2-6.md b/docs/superpowers/specs/CODEX-REVIEW-BRIEF-REGION-HA-SPEC2-6.md| new file mode 100644 |
| index 000000000..15bb13ae1 |
| --- /dev/null |
| +++ b/docs/superpowers/specs/CODEX-REVIEW-BRIEF-REGION-HA-SPEC2-6.md |
| @@ -0,0 +1,16 @@ |
| +# Astra: region HA spec 2, round 6 |
| + |
| +Rev 6 simplifies forwarding (§6, §9, §18). Rounds 3 to 5 each found a new edge in rev 3's two-hop protocol, so rev 6 removes it: |
| +- Today's one-hop forwarding, credential and mesh-key rotation are unchanged. |
| +- Within a region, a box dials the home box's private IP. Between regions, it dials the home box's own public IP. Group boxes have auto-assigned public IPs. |
| +- A box publishes only an address IMDS reports as its own. |
| +- Every instance is relocated off the old box **before** the region's EIP moves to the NLB. |
| + |
| +**Judge:** |
| +1. Are A5-1, A5-2 and rounds 3 to 4's forwarding findings genuinely moot? |
| +2. Does rev 6 reopen anything closed in rounds 1 to 2? In particular A1-12 (published address becoming the NLB's), A2-7, A2-9, and rollback. |
| +3. **The migrate-before-cut-over order (§9).** While the old box still holds the region's EIP and the instances live on group boxes, is every request path one hop? Consider requests via the region's EIP, cross-region forwards, platform routes, certificate challenges, and the NLB's zone B address. |
| +4. **IE platform routes at the cut-over (§9 step 3).** |
| +5. Anything new. Report only new items. |
| + |
| +Give findings P1/P2/P3 with file:line and a failure scenario. End with a verdict: ready for a plan, or not. |