C227 — Holding Creation while the macro Noah endpoint moves
23 September 2026 · Step 22 of 60, continuing C205.
If Creation remains native while only the macro-expanded Noah endpoint is used, the widths are 8125, 8447 and 8797, with interval-center gains 161 and 175.
| p | Right endpoints | Widths from held Creation | Centers |
|---|---|---|---|
| 3 | [Fraction(3706, 1), Fraction(4028, 1), Fraction(4378, 1)] | [Fraction(8125, 1), Fraction(8447, 1), Fraction(8797, 1)] | [Fraction(-713, 2), Fraction(-391, 2), Fraction(-41, 2)] |
| 5 | [Fraction(3708, 1), Fraction(4030, 1), Fraction(4380, 1)] | [Fraction(8125, 1), Fraction(8447, 1), Fraction(8797, 1)] | [Fraction(-709, 2), Fraction(-387, 2), Fraction(-37, 2)] |
These are C04’s held-Creation intervals. They do not form the 13-fold ratio ladder after 8125. The center gains are half of 322 and 350, the movement of the macro Noah endpoint. This isolates which side of the interval moves and prevents the two expansion constructions from being conflated.
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/.