# C222 — The expanded rectangle preserves lengths but loses source support

23 September 2026 · Step 17 of 60, continuing C205.

Expanding the whole four-point rectangle produces segment lengths 650, 1300/23 and 650. Only the first two images retain the original source ladder’s MT/SP Noah endpoints; the SP Flood and SP Noah images become nonannual.

| Chain | Expanded centers | Successive widths |
|---|---|---|
| 3 | [Fraction(3056, 1), Fraction(3706, 1), Fraction(86538, 23), Fraction(101488, 23)] | [Fraction(650, 1), Fraction(1300, 23), Fraction(650, 1)] |
| 5 | [Fraction(3058, 1), Fraction(3708, 1), Fraction(86584, 23), Fraction(101534, 23)] | [Fraction(650, 1), Fraction(1300, 23), Fraction(650, 1)] |

Equal opposite sides survive because the map is affine. Full source support does not. Thus the existence of the sourced original rectangle supplies no authorization to iterate the entire named configuration as a historical action. This closes the remaining rectangle-based route for extending C01 beyond its admitted endpoint stages.

## Evidence and scope

K=529 and r=25/23. BC base B means (B+1)t/Bn BC; reflected AD base A means AD At/(A+1)n. Their civil span is B+A in both seasonal components, with no year zero. Signed paired centers are −B and +A; the center model uses components ±1/4 and restores this separation after dilation. An interval center is geometry, not an event or a proposed universal Mirror axis.

Regular Gears are restricted to Noah/Shem/Flood. Creation and Conquest retain fixed source-field members; no fourth Gear is admitted. Generated coordinates, source-field membership and stored graph incidence are distinct. File_18/File_09 and the frozen C127 graph are unchanged. Earlier N01/N03 qualifications, the missing Shem join, closed primers and unestablished original Reports 11–25 remain unchanged. This packet selectively uses prior evidence; it does not rerun completed campaigns. Assertions and alternative placements are not independent historical witness counts.

**4 step-specific checks and 19 frozen-input checks passed.** Exact inputs, results and predecessor hashes are in the accompanying JSON records; calculation code is in the evidence archive. Source dependencies are identified in the body and frozen in `sources/`.