History

Post-Flood source packet and structural candidates

Download source fileOpen in research workspace

Post-Flood source packet and structural candidates

Frozen preparation only. File18 SHA256: 68301ab760bfbe2e874aedc5c8d943ced7a6219d34bc2859332a70713f9630d5. The full Strategy was read before selection. No numbered action or source edit is included.

Strategy fit and prior-work boundary

The Strategy asks how local row changes generate whole chronological families. C733–746 already reconstructs the complete bridge and difference fields, and C973 separates the SP cap contribution from Eber/Terah. Repeating those fields is validation, not discovery. This packet isolates the complete post-Flood source rows for a further question: how much of their joint structure can be represented by explicit shared constraints, and which values still have to be supplied?

Exact selected row packet

Each entry is begetting / calculated remainder / lifespan. Remainders are L−b; they are not independently claimed manuscript readings. MT and SP are native Cainan OFF. LXX retains native Cainan ON. All displayed Terah rows select the no-+60 minimum state.

RowMTSP officialLXX native
Shem100 / 500 / 600100 / 500 / 600100 / 500 / 600
Arphaxad35 / 403 / 438135 / 303 / 438135 / 330 / 465
2nd Cainanabsentabsent130 / 330 / 460
Shelah30 / 403 / 433130 / 303 / 433130 / 330 / 460
Eber34 / 430 / 464134 / 270 / 404134 / 370 / 504
Peleg30 / 209 / 239130 / 109 / 239130 / 209 / 339
Reu32 / 207 / 239132 / 107 / 239132 / 207 / 339
Serug30 / 200 / 230130 / 100 / 230130 / 200 / 330
Nahor29 / 119 / 14879 / 69 / 14879 / 129 / 208
Terah70 / 135 / 20570 / 75 / 14570 / 135 / 205

Literal source locators: MT §2.2 lines1244–1252; SP §3.2.1 lines1600–1608; LXX §4.2 lines1716–1725. Every row in the JSON retains the literal Markdown and its line number. LXX §1.6.1 lines1132–1136 separately displays Cainan and Shelah 130/460/330 and Eber 134/504/370.

Native versus OFF comparison

The LXX OFF comparison deletes the Cainan row. Within this bounded post-Flood domain it subtracts130 from Shem and Arphaxad regular birth/death coordinates and460 from their cumulative boundaries; the Shelah-forward suffix is fixed. Local begetting and lifespan rows for the surviving people remain unchanged. The complete LXX OFF regular birth path then equals SP’s selected path. This is an inherited consequence of the matched-Cainan path results, not an additional chronology fit. Native LXX must not receive another +130.

Conditional source dictionary to test

Hold the nine labelled MT b,L rows. Set u=100, t=60, a=27, and retain the following masks as explicit premises. This generates every shared post-Flood b,L value in SP and LXX OFF; the preparatory check passes across the complete two-tradition packet. The dictionary is fitted to known data and is not a holdout test.

MeasurementRow support and increment
SP and LXX begetting+u: Arphaxad, Shelah, Eber, Peleg, Reu, Serug; +u/2: Nahor; zero: Shem, Terah
SP lifespan−t: Eber and Terah; zero elsewhere
LXX lifespan+a: Arphaxad and Shelah; +u−t: Eber; +u: Peleg, Reu, Serug; +t: Nahor; zero: Shem, Terah

This distinguishes two kinds of century change. The earlier pre-Flood MT→LXX move preserved lifespan and transferred100 from remainder into begetting. The post-Flood Peleg/Reu/Serug move increases begetting and lifespan together, preserving remainders209/207/200. Arphaxad/Shelah also form complete equal-remainder blocks:403 in MT,303 in SP,330 in LXX. Native Cainan extends the LXX330 block with an exact copy of Shelah’s b,r,L vector. Eber, Nahor and Terah must retain their explicit roles; a uniform century rule does not cover the family.

The natural next investigation is conditional rank and reconstruction: with this row support frozen, which amplitudes can be recovered from regular paths, cumulative paths, or both? Which target life can be withheld and generated from a retained remainder relation? Do the shared amplitudes save description after their masks and exceptional cases are counted? These are source-information questions; no historical priority, global minimality or statistical rarity follows from the fitted arithmetic.

State and boundary guards

Use Arphaxad-bound Shem: MT2341→2241, SP2991→2891, LXX3121→3021. Each edge is100. The Noah-bound alternative changes the binding and must not silently enter the packet. The contextual Noah→selected-Shem edge is502 despite the Noah500 ledger; no upstream Gear is executed. SP’s −1 companion applies only to Noah/Shem and cannot move the Arphaxad-forward suffix.

SP Terah is officially 70+75=145, at2021→1876. Ideal205 is distinct. One cannot replace145 by205 while keeping both literal endpoints. The already-proved source triangle distinguishes a held-birth comparison, which gives death1816, from the +60/b130 comparison2081→1876 that retains Abraham1951. MT/LXX minimum selects70+135=205; their +60 state selects130+75=205. See File18 §§2.2,3.2.2,4.2 and C779–780.

LXX Peleg/Reu/Serug lifespans339/339/330 are the corrected controlling values;239/239/230 were copy errors. Cumulative outputs remain generated boundary coordinates with a held Abraham2435 terminal; they are not historical births. The source Flood marker conventions remain separate even where labels agree.

What is inherited and what remains open

Open work is an explicit relational generator and its identifiability limits across the complete post-Flood packet. The numerical rows, generic L=b+r, mode recurrence, Cainan weights, state triangle and prior endpoint totals are inherited. The cap rule has not been extended into an authorized post-Flood cap, and this packet proposes no such source claim.

The JSON records eight questions before preparatory derivation, exact source excerpts, all literal rows, OFF comparison rows, complete derived row differences, cumulative checkpoint validation, the proposed masks, and inherited-result citations. All validation checks pass.

Freeze rule: this packet is ready for root adoption. After notification, these two files will not be edited; any correction should be a separately named version.

Linked sources and evidence

Edition and provenance

postflood_source_packets.md

SHA-256 ef7d4476832c383fc195122db60dbe96116357ff0f5a310304a51eff4732c7bc

C480–C1634/Research_Cycles/C1132_C1431_Recovered/prep/postflood_source_packets.md