amadan
carlos / platform Public
- P2 — Migration does not prevent new placements on the old box. Spec:328
UK/US/AU’s old boxes remain enrolled, active and eligible under §7. Emptying one improves its placement ranking: it runs none of an app and has spare memory. A concurrent create—including an already-selected pending create—can therefore refill it after the migration’s final check. Moving its EIP then invalidates the “nothing is reached through that address” premise; terminating it after seven days strands that instance.
Specify a persistent placement exclusion before migration, settle outstanding selections, and verify emptiness before cut-over and termination. The existing draining exclusion provides a starting point, but this rollout never activates it.
- P2 — IE rollback targets a box the placement policy forbids. Spec:340
Rollback requires relocating instances back to the old IE box, but §7 declares its platform role never eligible. Naming it explicitly does not help: relocation checks target eligibility before starting.
If the group proves unsuitable after migration, restoring the EIP restores ingress but cannot return customer workloads to the retained box. Specify a reversible role/eligibility transition for rollback, and rehearse it with the platform-role restriction enabled.
Reviewed platform e18c100286ab2977151c9521c6c60ddf1ac9d929 and flagship 7c99ff8f1512f1a9ff3bf13337c3d147d730a6b6. No files changed; no builds, tests or infrastructure commands run.
---
FIRST PROMPT: Review spec 2 round 6 at the pinned HEAD against flagship Tofu, read-only.
WHAT: Check forwarding, migration, IE cut-over and rollback.
STATUS: Complete; two new P2 findings.
NEEDED: Nothing.
RECOMMENDED: Define placement exclusion during migration and IE’s rollback eligibility transition.
SESSION: Safe to close; nothing started or modified.
Verdict: not ready for a plan.