File: File_47 Title: Patriarchal Pairing System — Six Birth-Pairs from Noah to Jacob Entity: PATRIARCHAL PAIRING SYSTEM Classification: Structural System / Machine Reference Status: Final; bounded September 13 2026 Shem role-state / cross-state-overlap clarification applied; marked Final by author direction June 10 2026; Passes 0–2 complete Publication-cleanup status: Public-clean Markdown source; archival amendment history routed to Repository_Change_Archive. Pressure-test status: Current; publication-clean verification complete after author-Final marking and Passes 0–2 completion; no argument-bearing content changed in trust-status equalization. Register Agreement status: Historical File_47 registration checked against State_Vocabulary_Register v1.17; September 13 Shem role-state / cross-state-overlap clarification registered at current State Vocabulary Register v1.55 §D.44 and Restart Capsule v11.54 §10.31; convergence / pointer update only; no arithmetic, anchors, modal states, node-classes, operators, sign conventions, slash-pairs, ranges, envelopes, Mirror protocols, Machine Guards, claim-status labels, theological claims, or dependency boundaries changed. Primary domain: Regular; Comparative; Cumulative; Theological Traditions: MT; SP; LXX Canonical source: Markdown Primary anchors: 3058/3056 BC; 2558/2556 BC; 2458/2456 BC; 2236 BC; 2166 BC; 2081 BC; 2066 BC; 2006 BC; 1929 BC; 1919 BC; 1915 BC; 1876 BC; 1859 BC; 1805 BC; 1782 BC; 1446 BC; 1406 BC; 2366 BC; 2736 BC Related files: File_00; File_02; File_04; File_07; File_16; File_18; File_51a; File_54; Restart Capsule v11.15; State Vocabulary Register v1.17; 490d Repository Style Guide v2.5; Project Procedures v3.2 Major operators: Key of 23; 25/23; 70/69; Column-walk (A-walk / B-walk); Compression (pair-skip); mod 10 decadal display; Shem ±2; SP inclusive +1 Noah/Shem toggle (local); +60 Terah; +215 Sojourn; restored 2nd Cainan +130 / 460 by dependency; same-side BC subtraction Major modal states: +215 position with ±2; MT S0 / S2 (Shem ±2 regular-localized); S2 co-shift reading; S2 502-bracket reading; SP S0 / S1 local inclusive toggle; T0 / T60 (+60 Terah); J0 / J215 (+215 Sojourn); ENC encoded-coordinate state; LXX restored 2nd Cainan insertion state; cumulative dependency state; pair node-class register P0–P6 Revision basis: 490d Repository Style Guide v2.5; Restart Capsule v11.15; State Vocabulary Register v1.17; Project Procedures v3.2; File_00 Final; File_16 Final; File_18 Final; File_51a Final; File_54 Final; author direction June 10 2026 retaining the S0/S2 mode-flag system; Repository_Change_Archive (non-controlling history) Current refresh note: Public-clean trust-status equalization aligns active control pointers to 490d Repository Style Guide v2.5, Restart Capsule v11.15, State_Vocabulary_Register v1.17, and Project Procedures v3.2. Register Agreement status is recorded in the header; no arithmetic, anchors, modal states, node-classes, operators, sign conventions, slash-pairs, ranges, envelopes, Mirror protocols, Machine Guards, claim-status labels, theological claims, or dependency boundaries are changed. Detailed pass logs, pressure-test records where applicable, pointer-refresh history, and replacement-workflow notes are preserved in Repository_Change_Archive.

File_47 — Patriarchal Pairing System: Six Birth-Pairs from Noah to Jacob

0. File-function

File_47 is the machine reference document for the patriarchal pairing system: the organization of the 12-node chain from Noah to Jacob into six birth-pairs, the two gap-column systems generated by that pairing, the Key-of-23 block decomposition of the gap columns, the Column-walk and Compression operators, and the cross-tradition verification of the pairing structure across MT, SP, and LXX.

This file does not replace the Key-of-23 and structural-variator definitions in File_00, the Shem ±2 and Flood-state controls in File_02, the 1876 BC convergence controls in File_16, the chronological data tables and cumulative architecture in File_18, or the cumulative controls in File_51a.

Modal-state rule: A shared date-label, number, or span does not create identity unless state, node-class, tradition, and operator agree.

0.1 Working state register

The following states are active in File_47. They are simultaneous, non-competing working states unless a local section explicitly narrows the working state.

0.2 File map

0.3 Mode-flag notation and repository operator mapping

File_47 uses a compact mode-flag system in table captions and walk logic. By author decision (June 10 2026), the flag system is retained as the local notation of this file. Each flag is bound to its repository operator or state below; the repository term carries the state, and the flag is its bound shorthand.

Machine Guard [FILE_47 MODE-FLAG MAPPING]: The flags S0/S2, S0/S1, T0/T60, and J0/J215 are File_47-local shorthand bound to the repository operators in the table above. The symbol S0 is overloaded across traditions: MT S0 belongs to the Shem ±2 regular-localized state and SP S0 belongs to the local SP inclusive toggle. Always read a flag together with its tradition scope. Do not export the bare flags into other files without this mapping table or a Register convention entry.

Machine Guard [FILE_47 POSITION STATE]: All File_47 MT tables operate in the +215 position with ±2: Noah 3058/3056 BC; Shem 2558/2556 BC; Flood 2458/2456 BC (see File_16 §4.3.3). The MT Minimum-Regular tables of File_02 (Noah 2843/2841 BC) occupy a different matrix position. The two positions do not contradict; they are distinct position states of the same chain.

Author clarification — Shem role-state distinction (September 2026): 2558 BC is Shem's Gear-2 triad/biological birth reference. 2556 BC is the elected/covenant-line Gear-1 station by which Shem may occupy the elder/firstborn structural role; it is not another biological birth. Accordingly, the S2 cross-state construction intentionally combines Column A 2558→2456=102 with Column B bracket 3058→2556=502, giving 322+732=1054 against literal 3058→2006=1052. The extra 2 is exactly the 2558→2556 state overlap and is not added historical time. The co-shift 322/730 reading remains a separate valid sub-state; neither corrects the other.

Dependency note (author clarification, June 10 2026; Register Agreement Sweep refresh): The SP toggle refers, in the author's terms, to the SP's inclusive reckoning of Noah in his "600th year" (the ordinal parsing of Gen 7:11 / 8:13 described in §1.4). File_47's SP S1 is the pairing-file expression of that mechanism: a +1 at the Noah/Shem pivot. The current Register records File_47 SP S1 as a local label that shares mechanism-description territory with the SP Normal / Toggle ON family but is not merged with it. Formal identification still requires a dedicated cross-file check.

Publication-cleanup note: This public-clean source preserves the Final status and the Passes 0–2 completion status in the header. Detailed arithmetic-verification records, author-ruling ledgers, pass logs, and finalization records are archived rather than repeated in the public body. Active Machine Guards, state registers, dependency notes, and claim-status controls remain in the public source.

1. Scope Locks and Mode Conventions

1.1 Anchor Invariance Rule

Once a downstream anchor is fixed (e.g., Exodus 1446 BC), post-pivot dates remain fixed. Toggles (S0/S2, T0/T60, J0/J215) shift only earlier placements in the chain segment where they apply.

1.2 Mode Flags

See §0.3 for the binding of each flag to its repository operator.

1.3 Conventions Used in the Tables Below

• MT tables: S0 or S2 / T0 / J215
• SP tables: S0 or S1 / T0 / J215
• Post-Terah anchors (Abraham, Isaac, Jacob) remain fixed across all modes

1.4 Mixed Semantics Principle

The biblical text employs three age-counting methodologies:

1. Literal/Ordinal: explicit month/day timestamps (e.g., "in the 601st year, 1st month, 1st day")
2. Cardinal: completed years suitable for direct addition/subtraction
3. Rounded/Threshold: ages rounded to 5s or 10s as headline markers

Key example (Noah/Shem tension):

• Gen 5:32: "Noah was 500 years old" (threshold/headline for triad)
• Gen 11:10: "Shem was 100… two years after the Flood" (forces Shem born when Noah ~502)
• Gen 7:11 vs Gen 8:13: "600 years old" vs "in the 601st year" (ordinal vs cardinal ambiguity)

Resolution: MT/LXX permit mixed semantics (completed-years for age; ordinal for year-labels). SP applies strict ordinal parsing, using Gen 8:13 to retroactively force ordinal interpretation at Gen 7:11. This creates the S0/S2 fork.

Modal-state note: The mixed-semantics fork is the same state-producing ambiguity registered repository-wide as the Shem ±2 anomaly (File_02 §6). It is a state-producing ambiguity, not a scribal error to be removed.

Terah analogy pointer (bounded): the later author-approved Terah +60 / 0 / −33 sibling-slot field is structurally analogous in that Abram, like Shem, is the elected middle son who may occupy qualified sibling positions without acquiring multiple biological births. File_60 and File_00 control that Terah extension; File_47 does not rederive it or propagate −33 into Noah/Shem.

2. The Six Birth-Pairs Structure

2.1 Definition

The patriarchal chain from Noah to Jacob comprises 12 nodes organized as 6 birth-pairs. Noah functions as a pre-pair anchor (P0), supplying the closing gap that completes the symmetry.

Node-class note: The pair identifiers P0–P6 are pair node-classes. P0 is an anchor node-class, not a pair. Within each pair, the earlier-born member is pair1 and the later-born member is pair2.

2.2 Pair Assignments

Terminology note: Salah/Shelah is a name-variant display: Salah is the MT-table spelling and Shelah is the SP-table spelling in this file. It is not a modal slash-pair and is not a date range.

2.3 Decadal Pairing Lock

Within each pair, birth years share the same terminal digit (mod 10 clustering). This holds in MT and SP. In LXX (with 2nd Cainan inserted), a triple cluster forms in the P1/P2 region.

Display-state note: mod 10 clustering is a decadal display/diagnostic on birth-year coordinates. It is not an arithmetic operator and does not generate dates.

3. Gap Column Definitions

3.1 Two Gap Systems

Column A: within-pair gaps.

• Definition: (pair1 birth) − (pair2 birth)
• Example: Shem_birth − Arphaxad_birth = within-pair gap for P1

Column B: between-pair gaps.

• Definition: (pair_i pair2 birth) − (pair_{i+1} pair1 birth)
• With Noah: the final between-pair gap is Noah_birth → Shem_birth (P0→P1 closure)

Sign-convention note: All gaps in both columns are same-side BC subtractions of birth coordinates, earlier minus later, yielding positive spans.

3.2 Symmetry Property

Including Noah provides 6 gaps in each column, maintaining structural symmetry:

• Column A: 6 within-pair gaps
• Column B: 6 between-pair gaps (including Noah→Shem)

Node-class note: The Noah→Shem term (500; 501 under SP S1; 502 under the S2 502-bracket reading) is the P0 bracket term of Column B. It is a between-pair gap by definition even though it spans an anchor-to-pair1 interval.

4. Key of 23 Framework

Dependency note: The Key of 23 is defined in File_00. This section applies the Key of 23 to the pairing structure; it does not redefine it.

4.1 The Governing Constant

The number 23 functions as the architectural constant governing:

• internal structure within each tradition;
• gaps between traditions;
• conversion mechanisms (25/23 ratio for solar↔priestly calendar);
• block sums within gap columns.

4.2 MT Column B Block Decomposition (S0)

The between-pair gaps (excluding the Noah→Shem bracket) decompose into 23-multiples:

Observation: the coefficients 3, 7, 10 are themselves structurally significant (3 + 7 = 10; creation week numerics).

Claim-status note: The block sums and factorizations are arithmetic facts. The significance of the coefficients 3, 7, 10 is structural inference with symbolic association.

4.3 SP Key-23 Locks

The S0→S1 toggle (single +1 at Noah→Shem) flips Column B from calendar-lock (3 × 360) to Key-23 lock (47 × 23).

4.4 The 230/460 Module

230 years (10 × 23) functions as a fundamental building block:

4.5 Key of 23 Conversion Ratio

The 25/23 ratio converts between solar and priestly calendar frameworks.

Formula: priestly_years × (25/23) = solar_years

Examples:

690 × 25/23 = 750
460 × 25/23 = 500
230 × 25/23 = 250

Arithmetic note: All three conversions are exact integer results.

This conversion preserves pattern integrity across calendar systems.

4.6 The 552-Year Span (S2 Lock)

The span from Shem (S2) to Jacob = 2558 − 2006 = 552 years.

Because 552 = 23 × 24, it resolves exactly under both conversion ratios:

Arithmetic note: 2558 − 2006 = 552; 552 = 23 × 24; 552 × 25/23 = 600 and 552 × 70/69 = 560 are exact.

Claim-status note: The dual exact conversion is an arithmetic fact. The implication that the S2 toggle is not arbitrary — that it produces a "bridge span" simultaneously yielding Shem-language (600) and Jacob-language (8 × 70) — is structural inference.

5. MT Tables

5.1 MT Table — Mode: S0 / T0 / J215

Active state: MT; Shem ±2 lower member (S0); +60 Terah OFF (T0); +215 Sojourn position (J215).

MT S0 gap totals:

Column A (within-pair): 100 + 30 + 30 + 30 + 70 + 60 = 320
Column B (between-pair): 500 + 35 + 34 + 32 + 29 + 100 = 730 (= 365 + 365)

Column A block structure:

First half: 100 + 30 + 30 = 160
Second half: 30 + 70 + 60 = 160
Total: 320 (= 160 + 160)

Column B block structure:

35 + 34 = 69 (= 3 × 23)
32 + 29 + 100 = 161 (= 7 × 23)
69 + 161 = 230 (= 10 × 23)

Arithmetic note: Every row of the §5.1 table verifies: birth − death = lifespan for all 13 nodes; both gap columns extract from the birth coordinates as listed; all totals, halves, and block factorizations check.

5.2 MT Table — Mode: S2 / T0 / J215

Active state: MT; Shem ±2 upper member (S2), co-shift reading; +60 Terah OFF (T0); +215 Sojourn position (J215).

MT S2 gap totals (co-shift reading):

Column A (within-pair): 102 + 30 + 30 + 30 + 70 + 60 = 322
Column B (between-pair): 500 + 35 + 34 + 32 + 29 + 100 = 730

Modal-state note (S2 dual reading): The S2 state carries two computational sub-states, both retained.

Neither sub-state corrects the other. The within-pair gap P1 is 102 in both sub-states (vs 100 in S0).

Alternative S2 computation (502-bracket reading):

Column B: 502 + 35 + 34 + 32 + 29 + 100 = 732

Arithmetic note: Both sub-state totals check: the co-shift reading gives 730 and the 502-bracket reading gives 732 = 4 × 183. The S2 table rows verify (3058 − 950 = 2108; 2558 − 600 = 1958; P1 within-pair gap 2558 − 2456 = 102).

6. SP Tables

6.1 SP Table — Mode: S0 / T0 / J215

Active state: SP; local inclusive toggle OFF (S0); +60 Terah OFF (T0); +215 Sojourn position (J215).

SP S0 gap totals:

Column A (within-pair): 100 + 130 + 130 + 130 + 70 + 60 = 620
Column B (between-pair): 500 + 135 + 134 + 132 + 79 + 100 = 1080 (= 3 × 360)

6.2 SP Table — Mode: S1 / T0 / J215

Active state: SP; local inclusive toggle ON (S1); +60 Terah OFF (T0); +215 Sojourn position (J215).

SP S1 gap totals:

Column A (within-pair): 101 + 130 + 130 + 130 + 70 + 60 = 621 (= 27 × 23)
Column B (between-pair): 501 + 135 + 134 + 132 + 79 + 100 = 1081 (= 47 × 23)

Arithmetic note: Both SP tables verify row by row (birth − death = lifespan; mod 10 columns; gap extractions; totals 620/1080 and 621/1081; 621 = 27 × 23; 1081 = 47 × 23).

Key observation: the S0→S1 toggle changes only the Noah→Shem term (500→501), flipping the Column B total from 3 × 360 to 47 × 23.

7. Death Date Decadal Analysis

7.1 Death Dates mod 10 (MT)

7.2 The "8-Column" Pattern

Deaths ending in 8 (sorted by time): 2118, 2088, 2018, 1988, 1958 (S2).

Intra-column gaps:

2118 → 2088 = 30
2088 → 2018 = 70
2018 → 1988 = 30
1988 → 1958 = 30 (S2 only)

Pattern: a 30/70/30/30 ladder using the same canonical gap vocabulary as the birth-pair structure.

7.3 Additional Death-Date Locks

7.4 Serug as 7th-Node Outlier

Serug occupies the 7th position in the 12-node chain (counting from Shem = 1).

Typological note: The 7th-position reading parallels Enoch as "the 7th from Adam" (Jude 14). The position count is a structural fact; the Enoch parallel is typological association.

Structural function: Serug's death (2065 BC) does not fit the dominant mod-10 = 8 ladder. Instead, it serves as a diagonal lock to Joseph's death:

2065 → 1805 = 260 = 130 + 130 = 2 × (10 × 13)

This "skip" behavior mirrors Serug's 230-year lifespan (= 10 × 23), the same value as the between-pair gap remainder (§4.2).

8. Abraham-Centered Locks

8.1 Birth Dates to Abrahamic Events

8.2 Extended Locks (Reu + Abraham Lifespan)

2327 → 2166 = 161 (7 × 23)
161 + 175 (Abraham's lifespan) = 336 = priestly year (days)

8.3 Peleg to Covenant of Pieces

Peleg birth 2357 → Covenant 2081 BC = 276 = 12 × 23

8.4 Serug-Nahor Pair to Joseph

The 460 decomposes as 230 + 230, and 460 is the age of Adam at Jared's birth.

Arithmetic note: Adam's age at Jared's birth checks: 130 + 105 + 90 + 70 + 65 = 460. Both table spans check: 2295 − 1805 = 490; 2265 − 1805 = 460.

Reception-history note: The identification of Jared's generation with the Watcher descent is Enochic tradition (1 Enoch 6). The Watcher signature is a reception-history association, not an operator.

9. LXX Note: Second Cainan Insertion

Dependency note: The restored 2nd Cainan operators (+130 begetting; 460 lifespan) are controlled by File_07 and File_18. This section applies them to the pairing structure.

9.1 Insertion Parameters

• 2nd Cainan inserted between Arphaxad and Shelah
• Begetting age: +130 years
• Effect: creates a triple cluster in the P1/P2 region

9.2 LXX-Adjusted Structure (SP-Based Births + Cainan)

9.3 Adjusted Gap Totals

Column A with Cainan:

• The original Arphaxad→Shelah gap (135) splits into:
  • Arphaxad→Cainan: 130
  • Cainan→Shelah: 130
• Effectively doubles one 130 into 260
• New Column A total: 100 + 130 + 260 + 130 + 70 + 60 = 750

Verification:

Total span Noah→Jacob: 3836 − 2006 = 1830
Check: 750 (Column A) + 1080 (Column B, S0) = 1830 ✓

9.4 Pattern Preservation

Reinserting 2nd Cainan does not destroy the pairing structure; it produces a robust extension where the structure accommodates an extra node while preserving the decadal/pair schema.

9.5 The 460 + 460 Chain to Exodus

Using the B-walk with Cainan inserted:

From Jacob 2006 BC: +100 +29 +32 +34 +(35+130) = 2366 BC (encoded Cainan coordinate)
2nd Cainan lifespan (LXX): 460 years
2366 − 460 = 1906 BC (≈ Benjamin's birth; Jacob ≈ 100)
1906 − 460 = 1446 BC (Exodus)

Key-23 verification:

460 = 20 × 23
460 + 460 = 920 = 40 × 23
2366 − 1446 = 920 ✓

This demonstrates the 460-module functioning as a structural cadence terminating precisely at the Exodus anchor.

Node-class note: 2366 BC is an ENC encoded coordinate generated by the B-walk (§10), not a literal Cainan birth row. 1906 BC is an ENC intermediate coordinate of the 460-chain.

Claim-status note: The chain arithmetic (2366 − 460 = 1906; 1906 − 460 = 1446; 2366 − 1446 = 920 = 40 × 23) is exact. The association "≈ Benjamin's birth; Jacob ≈ 100" is an approximate biographical correspondence and is structural inference, not a derived anchor.

10. Column-Walk Redating Operator

10.1 Definition

Column-walk = summing only one gap-column from a fixed start year, bypassing the other column's gaps.

Operator notation:

Y₀ = start year (typically Jacob birth = 2006 BC)
A-walk: Y_A(k) = Y₀ + Σᵢ₌₁ᵏ Aᵢ (sum of within-pair gaps)
B-walk: Y_B(k) = Y₀ + Σᵢ₌₁ᵏ Bᵢ (sum of between-pair gaps)

Operator note (P0 bracket closure): Each walk runs the six gaps of its column in reverse chain order from Jacob and then closes with the P0 bracket term (+500 in MT/SP S0; +501 in SP S1). The closing step is the P0 bracket, a Column B term by definition (§3.2); its appearance as the final step of the A-walk is part of the operator definition, not column mixing.

Node-class note (ENC coordinates): A coordinate generated by a walk that does not coincide with a literal node is an ENC encoded coordinate (notation ENC_*). ENC coordinates are encoded/compressed coordinates, not literal anchors. They never replace, overwrite, or re-derive literal birth/death rows.

10.2 MT B-Walk Example (from Jacob 2006 BC)

Cross-tradition note (author identification, June 10 2026): 2736 BC is the LXX Gear 1 Noah death; the remaining dates in this table are shared across MT, SP, and LXX. The B-walk from Jacob therefore lands on the MT Noah death (2106 BC) at step 1 and terminates on the LXX Noah death (2736 BC) at step 6. The implied LXX Gear 1 Noah birth is 2736 + 950 = 3686 BC.

Revision note: By author decision (June 10 2026), the former MT A-walk, SP A-walk, SP B-walk, and Exodus-anchoring subsections were removed: their claimed ENC Noah/Shem terminal coordinates (2326; 2826; 2526; 2626; 3126; 3086) match no Gear 1 Noah or Shem date in MT, SP, or LXX, and the section had conflated restored-2nd-Cainan coordinates with Noah/Shem coordinates (the author identifies the former 2526 BC value as the SP −215 2nd Cainan birth, not a Flood coordinate). The Column-walk operator definition (§10.1) and the verified B-walk table above are retained.

10.3 Closure Property

The column-walk operator maps the timeline into itself (up to ±1 or ±2 tolerance matching S0/S2 pivots), not generating generically new coordinates. See §14.1 invariant 3 for the verified statistical statement on the retained B-walk.

Claim-status note: The landings themselves are arithmetic facts. The conclusion that the system is designed for self-consistency is structural inference.

Modal-state note: The ±1 / ±2 tolerance is the same flex carried by the Shem ±2 and SP +1 toggle states. It is a state tolerance, not measurement error.

11. Compression Operator (Pair-Skip Encoding)

11.1 Concept

Compression = discarding one gap-column entirely and treating the retained series as a "condensed" coordinate generator.

The pairing process functions as an information-condensation operator: skipping inter-pair spans preserves structured totals and repeatedly lands on already-meaningful nodes.

11.2 Structural Bracketing

The six pairs are bracketed by outer terms.

Pre-Flood hinge:

• 500 (Noah→Shem)
• 100 (Shem→Arphaxad)

Post-Flood hinge toward patriarchs:

• 100 (Abraham→Isaac)
• 60 (Isaac→Jacob)

Central bulk (Flood→Abraham):

Column A central: 30 + 30 + 30 + 70 = 160
Column B central: 35 + 34 + 32 + 29 = 130
Combined: 160 + 130 = 290 (= 2456 → 2166 BC)

11.3 Reu as Crossroads

Reu's literal birth (2327 BC) serves as the mathematical center of both column walks.

From Jacob via Column A:

2006 + 60 + 70 + 30 = 2166 BC (Serug/Reu paired zone)

From Jacob via Column B:

2006 + 100 + 29 + 32 = 2167 BC

Reu's position relative to crossroads:

2327 → 2166 = 161
2327 → 2167 = 160

This mirrors the 160/161 block structure in Column A.

Arithmetic note: All crossroads sums check: 2006 + 160 = 2166; 2006 + 161 = 2167; 2327 − 2166 = 161; 2327 − 2167 = 160.

Theological note: Reu (רְעוּ) means "friend"; Abraham is called "Friend of God" (Isaiah 41:8). Reu occupies the mathematical friendship/crossroads position.

12. Cumulative Chronology Lock

Dependency note: Cumulative chronology is dependency-controlled by the File_18 cumulative architecture and the File_51a cumulative controls. The values in this section are applications of that architecture to the pairing structure; they are not locally re-proved.

12.1 Lifespan Sum (MT Shem → Jacob)

Summing the 12 lifespans (MT):

Arithmetic note: The 12 lifespans sum to 3498 as displayed.

12.2 The S2 Cumulative Lock

Adding the S2 adjustment (+2):

3498 + 2 = 3500 = 7 × 500 = ½ × 7000

Terminus calculation:

If the cumulative chain terminates at 1936 BC
Then: 1936 − 1446 = 490 = 7 × 70 (Danielic covenant unit)

Author identification (June 10 2026): The 1936 BC terminus is the cumulative-route Levi coordinate (route through Aaron, born 1529 BC; cumulative Levi band 1936–1933 BC; lifespan 137). The full cumulative derivation is controlled by the File_18 cumulative architecture and File_51a.

Implication: the same +2 that closes the regular birth-span lock (552 → 600/560) also closes the cumulative lock (3498 → 3500 → 490 to Exodus).

Claim-status note: The sums are arithmetic facts conditional on the 1936 BC terminus. The "double-lock" reading — that the convergence supports S2 as intentional — is structural inference.

Cross-file note: The 1936/1933 BC pair carried in the cumulative architecture is the same cumulative Levi band identified above (author confirmation, June 10 2026).

12.3 Extended Cumulative (with Aaron)

Adding Aaron's 3 years extends the chain:

Cumulative Shem: 5436 → 4836 BC (600-year lifespan)
Span to Jacob birth (regular): 5436 − 2006 = 3430 = 7 × 490
Span to Conquest: 4836 − 1406 = 3430 = 7 × 490

This creates a paired 3430 lock framing Shem's cumulative 600-year lifespan against both Jacob's birth and the Conquest.

Dependency note: The cumulative Shem coordinates 5436 BC and 4836 BC belong to the cumulative register. 4836 BC is also a registered cumulative anchor elsewhere in the repository (File_18); shared year-labels do not create identity unless state, node-class, tradition, and operator agree.

13. Cross-Tradition Verification

13.1 Principle

MT is the primary demonstration. SP and LXX serve as cross-tradition polarization checks: systematically shifted variants that preserve the same pattern-language under controlled toggles.

13.2 The 2300/1150 Cross-Tradition Lock

SP composite (extending beyond the 6 pairs):

Noah→Shem "500-marker" + Shem lifespan (600) + Shem→Jacob (600) + Jacob→Conquest (600)
Total: 500 + 600 + 600 + 600 = 2300 = 23 × 100

MT single span:

Shem elected-lineage station (2556) → Conquest (1406) = 1150 = ½ × 2300

Arithmetic note: 500 + 600 + 600 + 600 = 2300 = 23 × 100; 2556 − 1406 = 1150 = ½ × 2300 = 50 × 23.

Canonical note: The connection to Daniel 8:14's "2300 evenings and mornings" motif is a canonical association. The exact halving relation between the MT interval and the SP composite is the arithmetic fact; cross-tradition coherence is structural inference.

13.3 The SP Triple-600 Corridor

Using SP Shem = 3206 BC (S0, T0):

Total: 3206 → 1406 = 1800 = 3 × 600.

Shem's 600-year lifespan functions as the unit measure, creating a triple-600 corridor from Shem's birth to the Conquest.

13.4 Summary of Pattern Preservation

Modal-state note: The MT S2 row uses the S2 502-bracket reading (Column B = 732). The §5.2 table uses the S2 co-shift reading (Column B = 730). Both sub-states are registered in §5.2; neither corrects the other.

13.5 Key-23 Patterns Across Traditions

13.6 The 690 ↔ 750 Conversion

Example (SP):

Noah death (S0): 2756 BC
2756 → 2066 (Isaac) = 690 years
2756 → 2006 (Jacob) = 750 years
Relation: 690 × 25/23 = 750 ✓

This demonstrates the Key of 23 conversion preserving spans across anchor choices.

13.7 Toggle Behavior

The only structural change under S0↔S2 (MT) or S0↔S1 (SP) is the Noah→Shem term:

MT: 500 → 502
SP: 500 → 501

Everything else remains invariant, isolating the toggle as a single-bit flip.

Modal-state note: The MT line describes the S2 502-bracket reading. Under the S2 co-shift reading the bracket remains 500 (see §5.2 dual-reading register).

14. Invariant Checklist (Machine Verification)

Machine Guard [FILE_47 PAIRING INVARIANTS]: The following assertions must hold under correctly-implemented mode toggles.

14.1 Structural Invariants

1. Decadal clustering: within each pair, birth_mod10(pair1) = birth_mod10(pair2)
2. Column A symmetry (MT S0): first 3 within-gaps sum = last 3 within-gaps sum = 160
3. Closure property (statistical, under the stated test): with the MT birth and death coordinates as the node universe and ±2 tolerance, 3 of the 6 retained B-walk steps land on or within ±2 of a literal coordinate (2106; 2167; 2236). A uniform baseline over the walked span 2007–2736 BC gives a per-step landing expectation of 84/730 ≈ 0.115; binomial P(X ≥ 3) ≈ 0.023. Counting the author-identified cross-tradition landing at 2736 BC (LXX Gear 1 Noah death) gives 4/6, with binomial P(X ≥ 4) ≈ 0.0025 under the correspondingly enlarged node universe. The landing rate is statistically notable under the stated test. This statistical result does not by itself prove authorial intent.
4. Central crossroads: both column walks from Jacob converge at 2166/2167 BC (±1 tolerance) — the Column A partial sum 2006 + 60 + 70 + 30 = 2166 and the Column B partial sum 2006 + 100 + 29 + 32 = 2167 (§11.3)

Revision note: Invariant 3 formerly asserted landings "at ≥50% of steps" across both walks; the threshold form was inaccurate, and the A-walk example table was removed by author decision (June 10 2026). The invariant is restated in the verified statistical form above, recomputed for the retained B-walk.

14.2 Calendar Lock Invariants

1. Column B calendar lock (SP S0): total = 1080 = 3 × 360
2. MT Column B solar lock (S0): total = 730 = 365 + 365
3. LXX span check: Noah_LXX → Jacob = 1830 = Column_A + Column_B (S0)

14.3 Key-23 Invariants

1. Column B Key-23 lock (SP S1): total = 1081 = 47 × 23
2. Column A Key-23 lock (SP S1): total = 621 = 27 × 23
3. MT inner B-block: 35 + 34 + 32 + 29 + 100 = 230 = 10 × 23
4. MT sub-blocks: 35 + 34 = 69 = 3 × 23; 32 + 29 + 100 = 161 = 7 × 23
5. Cainan 460-chain: 2366 − 1446 = 920 = 40 × 23
6. Conversion ratio: 690 × 25/23 = 750 (within rounding tolerance)

15. Dependencies and Anchors

15.1 Fixed Anchors (Invariant Across Modes)

15.2 Mode-Dependent Anchors

• Noah birth/death: shifts under S0/S2 (MT) or S0/S1 (SP)
• Shem birth/death: shifts with Noah
• Flood: derived from Arphaxad birth (2 years post-Flood)

15.3 Joseph Anchors

Current Register handling: These Joseph anchors are retained as File_47 derivation routes, not as new repository-scope anchors. Joseph 1915 BC / 1805 BC remains controlled by File_03 by Register routing; File_47 preserves only the local derivations.

Derivation route 1 (Jacob's age):

Jacob age 91 at Joseph's birth (77 + 7 + 7 years of service)
Joseph birth: 2006 − 91 = 1915 BC
Joseph lifespan: 110 years
Joseph death: 1915 − 110 = 1805 BC

Derivation route 2 (Pharaoh timeline):

Joseph age 30 at elevation (Gen 41:46)
Plus 7 years plenty + 2 years famine = age 39 at Egypt entry (1876 BC)
Remaining: 110 − 39 = 71 years
Joseph death: 1876 − 71 = 1805 BC ✓

Arithmetic note: Both routes check: 2006 − 91 = 1915; 1915 − 110 = 1805; and 30 + 7 + 2 = 39; 110 − 39 = 71; 1876 − 71 = 1805.

Claim-status note: The dual-route convergence on 1805 BC is an arithmetic fact; "redundant convergence validates both routes" is structural inference of overdetermination.

15.4 Levi Anchors and the 77+70+77 Pattern

Levi dates:

Birth: 1919 BC (constrained by 7-year marriage window + pregnancy/purification minimums)
Lifespan: 137 years
Death: 1919 − 137 = 1782 BC

The 77+70+77 Jacob-Levi corridor:

Pattern: 77 + 70 + 77 = 224 = 32 × 7.

Arithmetic note: The corridor checks: 2006 − 77 = 1929; 1929 − 1859 = 70; 1859 − 1782 = 77; 1929 − 1782 = 147 = 3 × 7 × 7.

• Symmetric bracket around Jacob's life-cycle
• 147 years from Jacob's flight to Levi's death

15.5 Levi Birth Constraint (Pregnancy/Purification Logic)

In 7 years (1922–1915 BC), Leah bears 6 sons. Biological minimum:

• ~280-day gestation + 40-day purification (Lev 12) = ~320 days minimum per son
• For the 3rd son (Levi): minimum ~640 days from first birth
• Spring/autumn corridor snapping narrows the feasible band to 1919 BC

16. Notation Glossary

17. Key-23 Quick Reference

18. Methodological Framework

18.1 Numbers as Shared ANE Grammar

Small-prime factor-structure + astronomical constraints yields a shared ANE numeric grammar. Calendrical reconciliation (sun–moon; months–seasons) naturally generates repeated small-factor structures (2, 3, 5, 7, 12, 60).

18.2 Israel's Semantic Sovereignty

Israel's literature adopts the common numeric grammar but asserts semantic sovereignty—YHWH as the source and arbiter of the sacred numeric order manifested in calendrical and genealogical schemata.

18.3 Scribal Esotericism Hypothesis

Hypothesis: scribal guilds preserved advanced factor-based arithmetic and calendrical-astronomical schematization; explicit theory is sparse due to genre limits and restricted transmission.

Testability: rests on detectable invariants:

• repeated small-prime factor motifs;
• modular residues (especially mod 10, mod 23);
• multi-anchor locks across independent constraints;
• cross-text robustness exceeding coincidence under controlled nulls.

18.4 Evidence Criteria

Structural invariants (strongest): the same rule survives textual variation (e.g., 12 nodes → 6 pairs; consistent decadal grouping; consistent gap-block behavior across MT/SP/LXX).

Numerical coincidences (weaker): single-tradition numeric hits without cross-validation.

Null hypothesis rejected: not "random numbers" but "independent scribal traditions with no shared numeric grammar." Cross-tradition preservation of identical pairing logic is evidence against independence.

19. Summary: What the 12-Generation Exercise Establishes

Claim-status note: In the summary below, items 1, 2, and the numeric content of items 4–7 are arithmetic facts verified in this file. The design, intentionality, signal-carrier, and non-coincidence readings (items 3, 5, 6) and the overdetermination reading (item 7) are structural inference supported by those facts.

1. Births are pair-structured (6 pairs reflecting the "12 sons/pairing" theme) with consistent decadal and symmetric behavior.
2. Between-pair gaps encode Key-23 blocks (69 = 3 × 23; 161 = 7 × 23; total 230 = 10 × 23).
3. S2/S1 toggles function as multi-layer locks (regular span, cumulative totals, conversion harmonics), not arbitrary adjustments.
4. Deaths mirror births via decadal clustering and controlled switch behavior (T60 rotates pre-Terah structure without breaking post-Terah anchors).
5. Serug as 7th node repeatedly behaves as "signal carrier," aligning to auxiliary anchors (Joseph corridor), echoing the "7th from Adam" (Enoch) motif.
6. Cross-tradition locks (2300/1150; triple-600 corridor; 1656 distribution across LXX/MT/SP) demonstrate shared numeric architecture, not coincidence.
7. Text speaks for itself: multiple independent, text-driven derivation routes converge on the same anchors (e.g., Joseph 1805 BC via two methods), indicating overdetermination rather than arbitrary curve-fitting.

Revision and archive note

This public-clean Markdown source removes only archival amendment history, pass logs, pressure-test repetition, pointer-refresh records, and obsolete replacement-workflow notes.

Detailed revision history is preserved in the Repository_Change_Archive.

No arithmetic, anchors, modal states, node-classes, sign conventions, operators, slash-pairs, ranges, envelopes, Mirror protocols, Machine Guards, claim-status labels, theological claims, or dependency boundaries are changed.