# C316 — Alternate cumulative antecedent and provenance review

24 September 2026. Separate source/method review of the bounded C316 question. Later proposed questions are not executed here.

## The forced h=i−2 comparison

C315 keeps the matched regular Noah endpoint n=q_i+8993, where q_i=−5290+i, and the coherent source Flood boundary f=n−600. Retaining the8395 constant forces a different cumulative Flood antecedent q_h with h=i−2. This is selection of another already admitted annual station in the cumulative LXX_OFF Flood field. It is not a two-year Gear movement of cumulative chronology. C271 expressly stores regular_Gear=null for the cumulative source.

The five held i values3…7 require h1…5, within the retained cumulative index field0…7. Admission must be checked as a cumulative source station and separately as a regular endpoint with the intended Gear and event start/close role. It must not be inferred merely from a computed integer. Both exact phases require the same displacement, with all original ancestry labels retained.

## Critical inherited-ancestry distinction

The actual C271 register uses cumulative LXX_OFF **Shem_i** for its regular SP Flood records, and cumulative LXX_OFF **Flood_i** for its SP Noah records. Both records describe the endpoint comparison as a derived T8993 comparison between admitted records; no new stored path is asserted. For the Flood records the local intermediate additionally records translation5888 and reflection_after_translation=true. These fields must be preserved rather than rewritten to describe the new8395 path.

Write a_i=−5890+i for the cumulative Shem node. The inherited Flood endpoint relation is f=a_i+8993. The newly tested antecedent satisfies q_(i−2)=a_i+598, so q_(i−2)+8395 equals a_i+8993. This demonstrates coordinate equality of two differently labelled source paths. It does not make Shem_i and Flood_(i−2) identical nodes. The original Flood record remains descended from cumulative Shem_i. A new comparison annotation may record the alternate path, but no source ancestry replacement is warranted.

C271's exact phase entries make this distinction checkable. Its matched regular Noah and Flood outputs are each at the same signed quarter-year offset as their respective cumulative source components. Its Flood output's local-coordinate stage can reverse orientation, but that is not grounds to erase the source_phase/reflected_phase associations recorded in the register.

## Relation to permitted regular Gear descent

File_18 §3.1.4 supplies the two-year spacing of successive regular SP Flood Gears and keeps start and close as separate event boundaries. The three admitted same-i8395 aliases from C315 can be moved down one regular Gear, keeping event role, to the coherent Flood boundaries. The two candidates above G3 cannot undergo a source-supported Gear descent because their starting nodes are not admitted. Merely computing their values minus2 does not establish a source Gear operation.

The h-selection path can therefore have a larger valid domain than the regular-Gear comparison path. A commuting coordinate equation does not equate the provenance or domains of those operations. Neither operation changes the8395 constant, adds an anchor, extends the Gear register, or propagates the SP person-companion action to Flood events.

## Conclusion and next question

Report three layers separately: original C271 Shem_i ancestry; alternate admitted Flood_h comparison; and regular Gear descent on admitted aliases only. Source-valid regular biographies and coordinate equality do not restore the rejected common cumulative-Flood-ancestor600 claim: the8395 route explicitly uses h different from i.

A strong next bounded question after C316 is the **same17K rectangle already suggested by the inherited source records**: cumulative Shem_i and Flood_i are600 apart, while their admitted SP Flood-boundary and Noah endpoints are600 apart under the same8993 translation. Test the five existing cases and exact phase associations, then state the relation to C287's stricter domain. Preserve cumulative node classes and the reversal between ordinary BC chronology and reflected endpoint order. Such a rectangle would be a typed comparison of selected records, not a universal chronology graph isomorphism or historical-design proof. That subsequent finite test is not executed by this review.