File: SP Noah–Shem Gear Knot — Canonical Register
Title: Governing Coordinates, Counting Conventions, and Comparison Permissions
Status: Revised — author-authorized replacement; universal Flood Gear transport and SP-only Noah/Shem adjacent rail clarified
Date: 18 September 2026
Primary domain: Regular SP chronology; qualified Gear comparisons; SP cap interface
Primary architecture: SP; BJ as derivative corroboration in the project model
Canonical source: Markdown
Revision basis: Author's September 18 clarifications, including the Flood-Gear / Noah-Shem rail separation; Repository Style Guide v2.5
Companion: Report V — The SP Noah–Shem Gear Knot, same revision

SP Noah–Shem Gear Knot — Canonical Register

1. Governing interpretation and scope

The 490d Unified Chronology examines how chronological traditions reconcile inherited figures, calendars, and representative roles. The SP mechanism registered here coordinates the conventional 600-year span associated with Noah's cardinal age expression and the ordinal 599+ of his 600th year. Its purpose is to make those chronological conventions work together with the fixed anchors.

Genesis 7:6 and 7:11 supply the two number forms. Their organization into this SP field is the study's reconstruction. The conventional 480 used for 1 Kings 6:1, including File_05's 966+480=1446, illustrates the same need to state how an ordinal expression is used in a chronological calculation.

Two distinct mechanisms are registered and must not be blended:

• Flood Gear transport is cross-tradition. Ordinary Gear displacement −2 / 0 / +2 applies to the Flood start boundary in MT, LXX, and SP; each Gear's Flood year then extends one annual boundary from start to close.
• The adjacent Noah/Shem rail is SP-only. Within this localized SP field, the upper Noah/Shem station is primary and the lower companion is primary minus one. It does not transfer to MT or LXX, does not generate the Flood closing boundary, and does not turn the Flood into a two-rail object.

“Lower” means farther forward in time. The SP one-year adjacency does not create a fourth Gear or six independently attested source states. A numerical landing of a lower Noah/Shem calculation on a Flood-close coordinate does not erase the distinction between person-station companion and event closing boundary.

Counting rule: Attach the ordinal or completed-year convention to the interval and its named endpoints. A primary/companion column label does not prescribe one convention for every interval using that column.

2. Fixed coordinates, three observations, and universal Flood Gear transport

All dates below are BC unless marked AM. The equalized comparison plane has second Cainan OFF, full Egypt 430, and Terah +60 OFF.

The preferred SP Gear-2 genealogical comparison head is 4414. Its eight intervals to Lamech give:

The corrected structure is registered as three separate observations.

2.1 G2 midpoint relation — Arphaxad endpoint

3760 BC is Lamech's G2/Normal birth midpoint between G2 SP Creation / chain head 4414 BC and fixed Arphaxad 3106 BC. It is not a Flood midpoint.

2.2 G1 convergence — 3106 BC

In SP Gear 1, Lamech death, Flood start, and Arphaxad birth are distinct node classes sharing 3106 BC. No midpoint language belongs to this convergence.

2.3 Universal Flood Gear rails

At this layer LXX is date-for-date 780 years earlier than MT: 2460/2458/2456 + 780 = 3240/3238/3236. The corresponding Arphaxad stations are MT 2456, LXX 3236, and SP 3106; the MT/LXX +780 relation therefore continues through Arphaxad. Each start→close pair is the one-year Flood-event span for that Gear. It is not a Noah/Shem primary→companion relation.

Expanded annually, the SP line is 3110→3109→3108→3107→3106→3105 = 1+1+1+1+1; MT and LXX have the exact same pattern at 2460…2455 and 3240…3235 respectively. This annual display embeds the three one-year Flood spans inside the two 2-year Gear separations. In all three traditions Arphaxad shares the G1 Flood-start coordinate; the additional Lamech-death convergence at that coordinate is the SP-specific observation registered in §2.2.

The preferred birth sequence and its cap counts appear in §8. The old 4415/3761 state and the attempted 4415 Adam → 4414 Creation repair are superseded in this execution. Files 07, 11, and 18 still require separately typed Creation-week, Adam-Day, and genealogical nodes; their general distinctions are preserved.

For the selected capped Lamech biography, coherent Gear transport moves Lamech's endpoint with the Flood start. The G2 event sequence is 3109 Ark preparation → 3108 Flood start → 3107 Flood close → 3106 Arphaxad. The SP Ark interval 3109→3108 remains a likely, conjectural reconstruction from the BJ parallel. The coordinate 3109 also serves as the SP G3 Flood close, but that is a distinct node class from the conjectural G2 Ark-preparation boundary. Flood start and Flood close remain distinct event classes, and the close is never a Noah/Shem companion state.

3. Lamech's inclusive row and the three admitted counting paths

Selected Lamech row: 3760→3108, 653 inclusive. Ordinary label subtraction gives 652; counting both endpoint years gives 653.

Thus the full-600 and ordinal-600th-year readings reach the same 3108 Flood anchor from their qualified Noah stations. The one-year distinction is counted once along each path. A 53rd-year begetting uses 52 completed boundary units, not the earlier 54.

The full 600 from lower Noah 3707, or full 100 from lower Shem 3207, instead reaches 3107:

This is a distinct closing/equivalent-count endpoint. It is the G2 Flood closing boundary of 3108→3107; reaching it through a lower Noah/Shem completed-year calculation does not make it a companion state of the Flood. It does not move Lamech's selected death from 3108. The annual coordinate display does not establish an exact birthday or fractional-year phase; 599+ means a portion within year 600.

The Shem-to-Flood comparison also retains its binding. The ordinary Arphaxad-bound relation is 3206→3106=100; upper G2 Shem 3208→3106 is 102. These are distinct qualified comparisons.

4. Governing Noah/Shem two-rail tables

Noah birth

Shem birth

Noah death

Shem death

Matched upper or lower endpoints preserve Noah 950, Shem 600, and Noah→Shem 500. The mixed lower-Noah / upper-Shem comparison gives 499.

The correctly paired post-Flood spans are 3108−2758=350 and 3107−2757=350. Here 3108 is G2 Flood start and 3107 is G2 Flood close; only 2758/2757 is the SP Noah upper/lower death pair. The arithmetic pairing does not make the Flood a companion rail. The cross-pair 3108−2757=351 cannot be labelled an unqualified 350. The harmonic closure remains 4414−2758=1656.

5. Birth order, representative roles, and cross-Gear permissions

The author's confirmed SP upper son-order reconstruction is:

Shem occupies the middleborn position chronologically and can occupy firstborn or lastborn positions by status and substitution in the study's interpretation. Named persons, birth-order positions, and representative Gear stations remain distinct.

BJ's sequence in Jubilees 4:33 is Shem / Ham / Japheth. Jubilees 7:10 calls Ham the “younger son” in Charles's translation. The project reads this as a comparable distinction between chronology and narrative or representative standing; the BJ author's precise theological rationale remains undetermined.

Noah/Shem permission includes their birth/death and mutual endpoint comparisons. It is comparison permission, not automatic source-state identity or a universal execution generator. Other patriarchs require separate authorization for departures from coherent-Gear biography.

6. The 552/598/1150 comparisons

The primary 552 uses Lamech and upper Shem in the same Gear:

Using lower Shem instead gives 553 and is a different qualified comparison.

The operators are distinct. The cross-Gear step belongs to Shem and does not change his owned 600 lifespan or create a mixed-Gear Lamech biography.

Noah's qualified 598 examples are G2 primary 3708 → G3 Flood start 3110, and G2 companion 3707 → G3 Flood close 3109. Equal interval lengths do not identify their endpoint classes: 3708/3707 is the SP Noah primary/companion pair, whereas 3110/3109 is a G3 Flood start/close event pair.

7. BJ comparisons: event translation and birth-position translation

Repository policy treats SP as the underlying architecture and BJ as a derivative/corroborating witness. Arithmetic alone does not establish a historical direction of literary dependence.

7.1 Frame and event correspondence

BJ uses 3856 BC = Year 1; conversion is BC = 3856 − (AM − 1). The Creation-to-Conquest span is 3856−1406=2450.

The retained event correspondence is:

Jubilees 5:21–32 distinguishes the Ark/Flood years. Files 20 and 18 retain the corresponding comparison stations. The SP Ark interval is conjectural, and the one-year comparison concerns annual stations rather than an exact construction duration to the day.

7.2 Birth-position correspondence

This maps birth-order positions, not the same named person across traditions. BJ's spacing is 2+3; the SP ordinary upper son-order spacing is 2+2. The primary / primary / companion selection 3210 / 3208 / 3205 preserves BJ's 2+3.

The birth translation is 345+215=560; the event translation is 559. Comparing all three SP primary positions with BJ instead gives native-frame differences 345 / 345 / 346. Applying event +559 to the BJ births gives 3209 / 3207 / 3204, which does not supply the selected three-position correspondence.

7.3 Harmonic comparisons

The final 350 is structurally favorable to Noah's correctly paired post-Flood spans in §4. Scalar 460 does not automatically invoke Cainan or an insertion operator.

8. Nine-row cap and coherent-Gear transport

Retain the inherited capacity numbers with the corrected births and fixed Flood-year anchor by stating their count explicitly:

These are capacities, not nine asserted lifespans. Noah is outside this cap domain. The inclusive counting +1 does not confer a Noah/Shem companion birth rail on the nine rows. The equivalent subtraction to 3107 does not assign their physical deaths to that closing boundary; Lamech remains 3760→3108, 653 inclusive.

For δ_G = −2, 0, +2, transport birth and Flood-year anchor together:

The capacities are Gear invariant. Equivalently, the closing comparison boundary is 3107+δ_G. The Lamech check is 3758−3106+1 = 3760−3108+1 = 3762−3110+1 = 653.

With the input lifespan count qualified, write Q_G(L_i)=min(L_i,d_i^incl). Gear carries an already-capped record as:

It preserves the current capped lifespan, without restoring lost information. On this domain:

Classification: guarded/source-qualified commutation. The 3107+δ_G close boundary comes from the one-year Flood event span after the Gear-transported Flood start; it is not produced by the SP Noah/Shem companion operator. This makes no broader selector-domain or state-count claim.

9. Supersession and use

Machine Guard [SP NOAH/SHEM ORDINAL–COMPLETED RECONCILIATION + FLOOD GEAR SEPARATION]: Separate: G2 midpoint 4414→3760→3106 = 654+654 to fixed Arphaxad; SP G1 triple coordinate 3106 for Lamech death / Flood start / Arphaxad birth; and universal Flood Gear transport. Flood starts are MT 2460/2458/2456, LXX 3240/3238/3236, SP 3110/3108/3106; closes are respectively 2459/2457/2455, 3239/3237/3235, 3109/3107/3105. LXX = MT +780 at this layer. Flood start→close is an event-duration pair, never the SP Noah/Shem companion rail. SP G2: Lamech 3760; Flood start 3108; Noah birth 3708/3707; Shem birth 3208/3207; Noah death 2758/2757; Shem death 2608/2607. Apply the SP −1 distinction once per admitted Noah/Shem local path only. Keep BJ event +559 distinct from positional-birth +560. Preserve the nine-row inclusive cap and coherent-Gear transport without lifespan restoration.

The author's September 18 clarification sequence controls this revision. Report V supplies the fuller explanation and source qualifications. File_11 retains the Three-Gear controls; File_18 explicitly registers LXX Flood Gears 3240/3238/3236; File_00 retains the MT Flood-Gear rail 2460/2458/2456; Files 20 and 53 support the BJ comparison; File_05 supplies the conventional 480-year example.

Both revised reports use the same governing coordinates, arithmetic, and permissions. Earlier dependent reports or checkpoints require requalification before reuse where they rely on superseded statements. This replacement does not claim that those other artifacts have already been amended.