**Spec:** `docs/superpowers/specs/2026-10-15-region-ha-two-box-regions-design.md`, rev 15, approved, including H27. Plan 2a is the core only. 2b (joining and enrolment), 2c (infrastructure and boot) and 2d (the §8 single-box fixes) are separate plans.
5
6
The plan's code was dry-run against main `70e57449`. Main has since moved; census values must be recomputed on the build base, and the plan includes tooling for that.
7
8
**Judge:**
9
1. **Spec coverage for 2a's scope:**
10
- box and group roles;
11
- the placement policy over identity-filtered candidates;
12
- H27's refusal;
13
- the health answer's conditions;
14
- the address source and private-address forwarding;
15
- the capacity metric;
16
- §25's enforcement tests.
17
Is anything in 2a's scope missing or wrong?
18
2. **H27 coverage.** H27 says every door that **chooses a box** refuses with 503 and alerts. Task 11 covers the instance create door. Do any other doors on main call the chooser? Name them.
19
3. **Correctness of the code in each task** against main: claim invariants, roster writes, concurrency.
20
4. **Census handling:** the record-write digests, and the Plan 14 overlay `plan14-root-reads-region-ha-2a.tsv`. Tasks 7 and 10 need platform-1e rulings. Is anything else unflagged?
21
5. **Tests.** Do they prove the claims, and would they fail without the change?
22
23
Give findings P1/P2/P3 with plan section or file:line and a failure scenario. End with a verdict: ready to build, or not.
amadan