File: File_18 Title: Chronological Data Tables Status: Inherited Final baseline retained; bounded September 18 2026 author-authorized SP Flood / Noah–Shem correction and cross-tradition Flood-Gear clarification applied; bounded September 13 2026 source-table / phase clarification applied (LXX Peleg/Reu/Serug copy-error correction; Aaron-before-Moses phase wording); September 8 2026 Lamech settlement clarified by author direction: attested LXX lifespan 753, restored begetting 182, calculated remainder 571; the combined 182/753 biography is component-wise reconstructed. LXX 777 remains an MT-derived appendix overlay. The September 8 Lamech wording clarification changed no numerical table; the September 13 LXX triplet correction changes only the three author-confirmed §4.2 copy-error cells and their death labels. Focused verification only; no new full-file pressure test or separate re-Finalization. Pressure-test status: Prior full and focused certifications remain historical to their source editions. The September 8 Lamech and September 18 SP/Flood amendments receive focused arithmetic, source-diff, guard, protected-region, and dependency verification only; no new full pressure test is claimed. Focused correction verification status: Complete July 24 2026 — included in the File_63 Finalization package-level 176/176 verification PASS; no new full pressure test claimed Reciprocal-routing verification status: Prior File_61/File_62 and File_69 routes remain retained. The August 20 2026 coordinated File_09/File_69 package adds one derived restored-Cainan/Apparent-Adam companion row and one reciprocal guard; focused package verification is complete; no pre-existing raw table row or Primary anchor is changed. Register Agreement status: Lamech source hierarchy remains at State Vocabulary Register v1.54 §D.43 / current v1.55 inherited §D.43 and Restart Capsule v11.53 §10.30; September 13 corrections are registered at State Vocabulary Register v1.55 §D.44 and Restart Capsule v11.54 §10.31; the v1.53 / v11.52 numerical settlement is unchanged. Earlier Lamech-specific D.18/D.42 instructions remain superseded in scope. The September 18 SP/Flood correction is author-authorized in this file and the revised Report V / companion register; corresponding central Register and Restart Capsule updates remain pending. Unrelated inherited controls, nested Gears, Sothic amendments, and Primary anchors remain unchanged. Publication-cleanup status: Public-clean Final Markdown; bounded reciprocal replacement included in the coordinated Final File_09/File_69 source/control package. Repository Change Archive, Publication Manifest, indexes, landing pages, deployment, and external archival recapture remain separate subsequent work. Source-history status: Essential companion to all inquiries; Version 5.0 Entity: RAW CHRONOLOGICAL DATA Classification: Foundational Tables / Lookup Reference UUID: DATA_TABLES_CORE Primary domain: Regular; Cumulative; Comparative; SKL; Calendar; Theological Traditions: MT; SP; LXX; BJ / Jubilees; SKL; Berossus by dependency Canonical source: Markdown Primary anchors: 3899 BC; 4199 BC; 5279 BC; 1661 BC; 1876 BC; 1885–1878 BC; 1670/1663/1656 BC; AD 1656/1663/1670; 1936 BC; 1816 BC; 1846 BC; 1446 BC; 1406 BC; literal/precise United Monarchy 1050t/n→1010t/n→970t/n→930t/n BC; Rounded United Monarchy 1051n→1011n→971n→931n BC; 967/966 BC; 1016 BC; 586 BC; AD 29395; AD 29465; AD 29515; 14006 BC; 14466 BC; 4831 BC; 5291 BC; 5296–5289 BC; 4858–4851 BC; 4856 BC; 4398–4391 BC; 4396 BC; 4278–4271 BC; 4825–4818 BC; 3136 BC; 3921 BC; 3011 BC; 2551 BC; 2336 BC; 2091 BC; 6306 BC; 13398 BC; 14896 BC; 3856 BC; 2906 BC; 2856 BC; 20886 BC; 27366 BC; 452886 BC; 459366 BC Related files: File_00; File_01; File_02; File_04; File_05; File_06; File_07; File_08; File_09; File_10; File_11; File_12; File_14; File_16; File_17; File_20; File_21; File_22; File_34; File_46; File_50c; File_51a; File_54; File_56; File_61; File_62; File_63; Restart Capsule v11.46; 490d Repository Style Guide v2.5; Project Procedures v3.5; State Vocabulary Register v1.47; File_69 Major operators: +60 Terah; +215 Sojourn; +275; 60 + 155 + 60; ±215; File_11 absolute Three-Gear +0/+2/+4; Shem-centered local −2/0/+2; SKL dilation −720/0/+720; nested local-on-macro subrails; regular restored 2nd Cainan +130; cumulative restored 2nd Cainan +460; 137 checksum 7 + 130; proportional unit 1656 ÷ 12 = 138; missing-four extension 4 × 138 = 552; completed extension 16 × 138 = 2208; Cainan-to-Moses lock 3450 = 138 × 25; Kenan / Cainan reinforcement 1370 = 10 × 137; Cainan lifespan-sum 910 + 460 = 1370; Cainan macro-vector 2300; Cainan / Famine envelope projection 2520; cross-tradition Shelah 60-multiple comparison 2400 / 2940; 60 × 42; 60 × 40; 60 × 49; 60 × 59; 60 × 99; 60 × 101; 60 × 108; 6 × 490; 3540; 5940; 6060; 6480; inclusive companion 2307; Enochian lower-bound vector 2730 = 7.5 × 364; Daniel 12 sandwich 1260 → 1290 → 1260; 360:1 SKL scale; +6480; selected macro +720 member; +30 Apparent Mode; selected local +2 member; bounded adjacent-macro 690/720/750; File_21 SKL rounded mod-10 Mirror display BC + AD − 2; File_21 SKL Short / Long relation 6530 − 50 = 6480; File_34 SKL-to-Berossus 2370 corridor by dependency; File_34 30 + 20 + 30 restoration corridor by dependency; paired slash-display arithmetic by dependency; phase-chain arithmetic by dependency; 25/23; 70/69; 300/299; 430; 480; +50 Jubilee Offset; same-side BC subtraction; civil cross-axis span BC + AD − 1 if opened; Lamech non-operative transmitted-188 comparison; hypothesis-level gain-transfer; appendix triad deltas +6 / −30 / −24; 454 − 24 = 430; LXX Exodus lock 299 × 45 by File_56 dependency; Flood Gears 3240 / 3238 / 3236 (+215 frame) by File_11 dependency; downstream full clutch T14(C) = C − 14, half-clutch midpoint H7(C) = C − 7, and fixed-offset Joseph translation by corrected File_61 / Final File_62 dependency only Major modal states: raw data source state; minimum baseline table state; Regular chronology; Cumulative chronology; MT Minimum-Regular; MT Standard-Normal; Abraham two-state / Terah four-state variant field; 2nd Cainan variant-boundary state; 12–8–4–2–0 generational variant-count ladder; multi-tradition Pentateuchal Funnel all-even structural harmony; restored/native 2nd Cainan 27-generation completion state; tebah / ark typological bridge state; 137 boundary checksum state; Shem dual-100 state; 16 × 8 expectation / cumulative-Cainan extension state; Kenan / Cainan tenfold reinforcement state; Cainan macro-vector state; Cainan / Famine envelope-to-envelope state; cross-tradition 60-multiple Shelah / Plenty-Famine alignment state; Mirror 60-spine / Terah-Cainan death-rail state; regular-Cainan 460-year cross-modal symmetry state; Cainan triple-target matrix state; Cainan-to-Exile Daniel 12 sandwich state; Cainan-sector branch-restraint state; SP Normal / G2; SP-local Noah/Shem primary–companion field; cross-tradition Flood Gear / start–close field; SP Ideal / Exclusive comparison; LXX Regular-Minimum; LXX Terah / Abraham 2 × 2 variant field; regular-localized Shem ±2; cumulative-propagated Shem ±2; absolute Three-Gear state; selected local +2 member state; SKL centered ±720 dilation; nested local-on-macro subrail state; regular restored 2nd Cainan; cumulative restored 2nd Cainan; literal/precise United Monarchy state; Rounded Scaffold United Monarchy state; shared-966 state; Kings dual-ledger state; Sumerian A / SKL Short; Sumerian B / SKL Long; SKL +30 Apparent Mode; selected SKL local +2 member; selected SKL macro +720 member; full nested ±2 / ±720 Three-Gear control; File_21 SKL Unified Protocol dependency state; File_34 post-final dependency state; File_34 SKL-to-Berossus 2370 corridor dependency state; File_34 30 + 20 + 30 restoration corridor dependency state; SKL rounded mod-10 Mirror display-state; Jachin / Boaz Temple-Time Pillar coordinate state; providential multi-tradition system state; LXX component-wise 182/753 main-chain state; non-operative transmitted-188 comparison state; Key-of-23 crossover hypothesis; appendix-only LXX 777 overlay state; 430-alignment justification state; Flood-marker convention set; Kohath / Amram silence state; corrected File_61 / Final File_62 downstream half-/full-clutch table-routing state; File_62 Joseph inherited-translation and fixed-Joshua 216 comparison state by dependency Revision basis: 490d Repository Style Guide v2.5; Restart Capsule v11.46; State Vocabulary Register v1.47 Part D §D.38; Project Procedures v3.5; prior finalized File_18 source; Files 11, 21, 34, and 50c; retained monarchy, File_63, File_61/File_62, File_09/File_69, and File_69 routes; August 25 2026 bounded nested Three-Gear control correction; Repository_Change_Archive and Publication Manifest retained as non-controlling prior publication records. Current refresh note: Prior monarchy, File_63, File_61/File_62, and File_09/File_69 table-source boundaries remain unchanged. The August 25 2026 bounded correction clarifies only the SKL rail ontology: the printed +2 and +720 rows are selected members of the complete centered −2/0/+2 and −720/0/+720 wheels, with optional local subteeth nested inside admitted macro members. The +30 Apparent Mode remains orthogonal, and no new raw date row or proof-bearing equation is introduced.

September 8 2026 Lamech correction: the former regular-777 / cumulative-753 split is superseded by 182/753 in both main reconstructions. Regular Lamech death changes from 3028 to 3052 BC in the minimum frame; the birth chain and all cumulative chain values remain fixed. 188 remains non-operative but may be examined as a qualified Key-of-23 transmission hypothesis; LXX 777 examples move to Appendix B.

Current pressure-test note: The June 28 2026 File_18 pressure test verified current control alignment, table-source boundaries, Machine Guards, dependency routing, no-comma Markdown formatting, and visible arithmetic / table arithmetic. The pass changed only stale trust-status and dependency-status wording; 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 were changed.

Bounded monarchy-correction note: The July 24 2026 amendment is independently focused-verified but is not a new full pressure test. The prior June 28 2026 full-pressure-test baseline remains historical control for all unaffected material.

September 18 2026 SP/Flood correction: in the native SP frame, G2 Lamech is 3545→2893, 653 inclusive; Noah primary/companion is 3493/3492; Flood start→close is 2893→2892; fixed Arphaxad remains 2891. Add 215 for the reports’ equalized SP frame: 3760→3108, Noah 3708/3707, Flood 3108→3107, Arphaxad 3106. Ordinary Flood Gears and each Gear’s one-year event span apply to MT, LXX, and SP; the adjacent −1 person-station rail applies only to SP Noah/Shem. The native-LXX comparison remains Cainan ON: G2 Creation 5494, Flood 3238→3237, Arphaxad 3236. §§0, 2.2.1, and 3, Appendix A, and clarification note 10 carry the bounded correction; cumulative and SKL data are unchanged.

File_18 — Chronological Data Tables

Related Repository Files

File_69 Cainan-count reciprocal note: Final File_69 uses File_18's restored/native second-Cainan 27-generation Adam-to-Moses inventory as the internal reverse fingerprint of its external 14+13 schematic spacing. File_18 remains the raw-table and count controller.

Machine Guard [FILE_18 FILE_25 FILE_69 CAINAN-FINGERPRINT ROUTING]: Final File_69 may use File_18's restored/native-second-Cainan 27-generation Adam-to-Moses inventory and File_25 / File_29's same-name Kenan–Cainan 70+840=910 corroboration to state the external 14+13 / internal 13+14 reverse fingerprint. File_18 remains the raw table and count controller; File_25 remains the Decimal Invariance / 910 reference controller. In LXX, do not add another +130 to native Cainan. The 26/27/28 states alter attribution or the figurative bookend only and do not move the fixed date grid.

File_69 Jeconiah–Cainan reciprocal note: Final File_69 now compares Jeconiah's forwarded 70+840=910 row with first Kenan and compares Jeconiah's 41↔42 slot operation with second Cainan's 26↔27 retention/expunction. This is a bounded analogy, not an identity of persons, texts, curses, or chronologies.

Machine Guard [FILE_18 FILE_25 FILE_29 FILE_53 FILE_69 JECONIAH–CAINAN ROUTING]: Final File_69 may compare Jeconiah's six-year-forwarded row with first Kenan's 70+840=910 anatomy and may compare Jeconiah's 41↔42 overlap with second Cainan's 26↔27 retention/expunction as analogous one-position count-clutches. File_18 retains the raw table and Adam-to-Moses count states; File_25 retains Decimal Invariance and the 910 reference field; File_29 retains the 7/13 theological grammar; File_53 retains Cainan-expunction and BJ claim-status control. Analogy does not create identity, and native LXX Cainan receives no additional +130.

Final File_09/File_69 cumulative-substrate reciprocal note

Final File_09 derives the restored-Cainan/Apparent-Adam companion by applying the already controlled +460 cumulative Cainan translation to the base Apparent-Adam row, equivalently by applying localized +30 Apparent Age to the restored-Cainan Creation row. Final File_69 uses that companion only by dependency inside its cumulative-substrate synthesis. File_18 records the row as derived companion data, not as an independently transmitted chronology row.

Machine Guard [FILE_18 FILE_09 FILE_69 RESTORED-CAINAN / APPARENT-ADAM ROUTING]: 14501–14494 BC, Moses-side center 14496 BC, Aaron whole-year node 14499 BC, and Aaron phase-resolved node 14499.5 BC are derived companion values generated from File_18 source rows under +460 and localized +30. They are not inherited raw data, do not revise the base Apparent-Adam or restored-Cainan Creation rows, and are not repository Primary anchors. Final File_09 controls their cumulative derivation; Final File_69 controls only the downstream genealogical interpretation.

0. File-function

File_18 contains the raw chronological data required to verify calculations and apply axioms defined in File_00 through File_17. It is the repository's number source paired with the rule source supplied by the axiom and entity files.

Three data systems are always required for any inquiry:

Design principle: Tables present minimum baseline dates. All variants are derived by applying the documented mechanisms, especially +60 Terah, +215 Sojourn, or both.

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

Source-control note: LXX chronology is materially active in this file. Henry B. Smith Jr.'s reconstruction of the LXX Genesis 5 and 11 chronology is therefore an important external source-reconstruction witness for the LXX layer. Smith is not the source of this file's harmonic interpretation, SKL / Berossus integration, providential synthesis, or theological reading.

Publication-cleanup note: This public-clean source preserves the Final, post-final pressure-tested, focused-amendment, later cross-file-update, and current post-equalization full pressure-test status in the header. Detailed pass logs, pressure-test records, bounded update ledgers, pointer-refresh history, and replacement-workflow notes are archived rather than repeated in the public body.

Nested Three-Gear correction note: The August 25 2026 update is a state/guard correction only. It changes no table datum and adds no chronology row.

0.1 Working state register

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

0.1a Node-class and display-state register

0.1b Operator and sign-convention register

0.1c Slash-pair, range, envelope, and display-state register

0.1d Modal-state processing rules

1. File_18 is a table-source file. A table value should be read under its local state before it is used as proof in another file.
2. Regular and Cumulative chronologies are different methods. Regular uses begetting ages; Cumulative stacks lifespans.
3. A shared date-label does not create identity. This is especially important for 1876 BC, 1406 BC, 4831 BC, 5291 BC, and 3856 BC.
4. Creation endpoint states and Year-6 / Adam states remain distinct. Endpoint rows mark Day 7 / Year 7 completion; Year-6 / Adam rows are separate node-classes.
5. The MT Minimum-Regular, MT Standard-Normal / +215 Sojourn, MT +60 Terah, and MT +275 positions are simultaneous variant states, not corrections of one another.
6. The Abraham → Levi / Joseph ±215 field gives two possible date states. Terah then opens the +60 Terah hinge, doubling the field to four states in the normal no-2nd-Cainan Adam-to-Terah field. If restored 2nd Cainan is explicitly inserted, 2nd Cainan through Terah remains four-position, while Arphaxad / Flood through Adam becomes eight-position.
7. The 12–8–4–2–0 shorthand must be read as a structural funnel: generation-count blocks 12 → 8 → 4 → 2, paired with possible-date states 8 → 4 → 2 → 0 when restored 2nd Cainan is explicitly opened. It is not a mere boundary list.
8. The restored/native 2nd Cainan 27-generation completion state extends the Pentateuchal Funnel to Moses: 12 + 8 + 4 + 2 + 1 = 27 = 3 × 3 × 3. This is a secondary generation-count / typological layer. Do not let it overshadow the primary 12–8–4–2–0 variant-count ladder or the operative 8-date / 4-date / 2-date / 0-date block logic. Do not use this theological / structural state to add dates to Kohath, Amram, Aaron, or Moses, and do not erase the ordinary fixed-anchor rule from Aaron / Moses onward.
9. The fixed epoch from Aaron onward uses fixed anchors unless a dependency explicitly opens another state.
10. SP Noah/Shem alone receive the adjacent −1 companion rail. Flood start→close is an independent event-year span within ordinary three-Gear transport in MT, LXX, and SP. SP cap counts are inclusive to Flood start. With other variant settings held, Arphaxad onward remains fixed under Gear and the SP companion mechanism.
11. The September 8 2026 ruling uses Lamech 182/753 in the main LXX Regular and Cumulative reconstructions. 571 is calculated only; 188 is non-operative transmitted data; LXX 777 and its dependent comparisons are appendix-only. See §4A and Appendix B.
12. Regular restored 2nd Cainan uses +130; cumulative restored 2nd Cainan uses +460; LXX native Cainan requires no restoration.
13. Cumulative .5 labels belong to the Aaron / Tishri trunk and must not be silently rounded.
14. Cumulative 7-year spans are envelopes. A stated upper, lower, or internal member must be preserved as a member-label. The MT cumulative Peleg row has a Nisan envelope 3501n–3494n BC and a parallel Tishri envelope 3502t–3495t BC; its Mirror relation to the Conquest / land-rest envelope must be evaluated component-wise.
15. Sumerian A / SKL Short, Sumerian B / SKL Long, +30 Apparent Mode, the selected local +2 member, the full local −2/0/+2 wheel, the selected macro +720 member, the full SKL −720/0/+720 dilation, and +6480 variant-tier logic must remain distinct by unit and state.
16. The SKL appended 3 months and 3.5 days datum is preserved as a textual / dependency-controlled state, not as a local whole-year operator.
17. The Cainan macro-vector state is a File_16 dependency layer, not a new File_18 table-generation operator. 2300, 2307, 2520, 2730, and 1260 → 1290 → 1260 may be cited from File_18 table values only when the active vector state and target node-class are named.
18. No broad Mirror protocol or inverse-number operator is active in the main body of File_18. The author-clarified MT cumulative Peleg row opens a bounded File_09-style phase-resolved Mirror coordinate-completion state only for that Peleg / Conquest relation. Mirror, civil cross-axis span, 10x scaling, and inverse-number reversal must still be named separately.
19. The 299 / 300 residue line is now author-clarified as a dependency-controlled residue / conceptual residual-display state. The active Enochian ratio is 300/299; legacy 299/300 wording is source-history / inverse-caption language; physical residue and conceptual residual-display must remain distinct.
20. The literal/precise United Monarchy is 1050t/n→1010t/n→970t/n→930t/n BC. The Rounded Scaffold United Monarchy is 1051n→1011n→971n→931n BC. The old mixed 1011→971/970→931 BC row must not be restored as Actual / Historical.
21. 966 BC is a shared year label: literal cardinal Temple foundation from 1446 BC, and Rounded 560-year landing from Moses 1526n BC. Shared label does not collapse state or operator.

0.2 File map

0.2A Current amendment hierarchy

This table states the current hierarchy for the post-final Cainan / Funnel material. It governs how §§1.3.1–1.3.7 should be read.

0.3 Terminology controls

0.4 Machine Guards for File_18

Machine Guard [FILE_18 RAW DATA SOURCE]:

File_18 supplies table values and baseline dates. It must not silently promote a baseline row into a proof of a later file's full argument. Where another file controls the argument or operator, retain the row as a data dependency.

Machine Guard [FILE_18 REGULAR / CUMULATIVE CAINAN]:

Regular restored 2nd Cainan uses +130. Cumulative restored 2nd Cainan uses +460. LXX already includes 2nd Cainan in the relevant baseline. Do not feed the regular +130 insertion into cumulative lifespan arithmetic.

Machine Guard [FILE_18 SHEM ±2]:

In Regular chronology, the localized Shem ±2 anomaly governs Noah/Shem bindings and qualified endpoint comparisons. Ordinary coherent Gear transport also applies to the Flood and other admitted pre-Flood biographies; see §3.1.4. At held variant settings, Arphaxad onward remains fixed under regular Gear. In Cumulative chronology, the anomaly propagates through the cumulative chain and creates the 7-year margin. Keep these mechanisms and domains distinct.

Machine Guard [FILE_18 KINGS DUAL LEDGER]:

966 BC is the historical Temple foundation anchor. 1016 BC is the schematic Triple-430 pivot generated by the +50 Jubilee Offset. Do not let either ledger overwrite the other.

Machine Guard [FILE_18 LITERAL / ROUNDED MONARCHY NON-COLLAPSE]:

The literal/precise United Monarchy is 1050t/n→1010t/n→970t/n→930t/n BC. The Rounded Scaffold rail is 1051n→1011n→971n→931n BC. Do not label the Rounded rail Actual / Historical, and do not move the precise phase rail backward by one year.

Machine Guard [FILE_18 966 SHARED-LABEL]:

966n BC may function as the literal cardinal Temple foundation and as the Rounded 1526n→966n=560 landing. Shared year label does not create identity of source state, origin, or operator.

Machine Guard [FILE_18 SKL NESTED THREE-GEAR RAILS]: File_11's ordinary Three-Gear field is +0/+2/+4 in absolute notation and −2/0/+2 when centered on Gear 2 / Shem. Under the SKL 360:1 scalar, the centered field is −720/0/+720. Sumerian A / SKL Short, Sumerian B / SKL Long, +30 Apparent Mode, the local and macro wheels, and +6480 remain distinct states and units. Existing +2 and +720 table rows are selected-member displays, not the complete topology; each admitted macro member may carry a nested local −2/0/+2 subrail only when explicitly opened. No nested subrail creates a new raw table row, source witness, or Primary anchor.

Machine Guard [FILE_18 CREATION ENDPOINT / YEAR-6]:

Creation endpoint rows mark Day 7 / Year 7 completion. Year-6 / Adam states are related but distinct node-classes. Do not use 3899 BC, 4114 BC, 4174 BC, or 5279 BC as if they were the same node-class as Year-6 / Adam states such as 3900 BC, 4116 BC, or cumulative 14006 BC.

Machine Guard [FILE_18 TERAH FOUR-POSITION FIELD]:

Abraham has two birth states, 1951 BC and 2166 BC, generated by the ±215 Sojourn fork. Terah has four birth/death states because +60 Terah doubles that field: 2021–1816 BC, 2081–1876 BC, 2236–2031 BC, and 2296–2091 BC. Do not force a single Terah begetting-age display across all four states. The no-+60 rows use the 70 begetting-state; the +60 Terah rows use the 130 begetting-state. Restored 2nd Cainan may double Arphaxad / Flood through Adam only where explicitly opened; it does not make 2nd Cainan itself eight-position.

Machine Guard [FILE_18 1876 YEAR-LABEL]:

1876 BC is a shared year-label. Depending on active state, it may mark Jacob's Entry under MT 430, Abraham's Call / Death of Terah under Sojourn-division paths, Jacob's return from Haran under LXX 33 + 397 by dependency, or another convergence witness. Do not collapse these node-classes.

Machine Guard [FILE_18 SP NOAH/SHEM LOCALITY + FLOOD GEAR SEPARATION]:

The SP companion operator is primary minus one for Noah/Shem person-stations only. Native G2 Noah is 3493/3492, Shem 2993/2992, Noah death 2543/2542, and Shem death 2393/2392. G1 Shem 2991/2990 with deaths 2391/2390 remains available under named bindings; only 2991→2891 is the displayed full-100 Arphaxad-bound relation. Do not propagate the companion into Adam through Lamech or Arphaxad onward, and do not transfer it to MT/LXX. Native G2 Lamech is 3545→2893, 653 inclusive. Flood 2893→2892 is a start→close event pair, not a companion pair. All three traditions retain ordinary Flood Gears and independent one-year Flood spans; §3.1.4 supplies the exact table. LXX is native Cainan ON in that comparison. Keep the G2 654+654 midpoint to fixed Arphaxad separate from the G1 Lamech-death / Flood-start / Arphaxad coordinate convergence.

Machine Guard [FILE_18 CUMULATIVE ENVELOPES]:

Cumulative 7-year spans such as 14011–14004 BC, 4836–4829 BC, and 5296–5289 BC are envelopes. They are not single anchors, and .5 labels in the Aaron / Tishri line must not be silently rounded or converted into ordinary Nisan labels.

Machine Guard [FILE_18 MT CUMULATIVE PELEG MIRROR]:

The MT cumulative Peleg row must preserve both the Nisan span 3501n–3494n BC and the parallel Tishri span 3502t–3495t BC. The Conquest / land-rest counterpart is 1406n–1399n BC and 1407t–1400t BC. Under File_09 phase-resolved Mirror suffix inversion, the AD-side display is AD 1399t/1400n–1406t/1407n. Component checks use BC + AD − 1 and equal 4900; do not treat 3495t as an error or as an ordinary upper-member label.

Machine Guard [FILE_18 LXX REGULAR / CUMULATIVE]:

The main LXX reconstruction retains the attested/transmitted LXX lifespan 753 (Genesis 5:31) with restored operative begetting age 182 in both Regular and Cumulative execution. 753 itself is not reconstructed; its retention as the preferred original LXX lifespan is the author-adopted textual/structural judgment of §4A.1. The remainder 571 = 753 − 182 is calculated, not an identified manuscript reading. No surviving joint 182/753 attestation has been identified in the reviewed sources; this qualification concerns the combined biography, not the attestation of 753. Regular begetting paths and cumulative lifespan paths remain distinct methods, but Lamech's selected lifespan no longer changes between them. LXX use of MT 777 is an appendix overlay confined to Appendix B and appendix-routed downstream comparisons; its cumulative overlay is row-local and must not propagate into the 753 chain. MT 777 and Nahor's controlled LXX 208 remain unchanged. The transmitted 188 is non-operative: its possible Key-of-23 origin is a structural/transmission hypothesis, not an admitted main-chain variant.

Machine Guard [FILE_18 LAMECH KEY / TRANSMISSION]:

File_18 §4A records exact arithmetic within declared chronological states and an author-favored Key-of-23 crossover hypothesis. Neither harmonic compatibility nor a generated +6 endpoint proves a historical scribal sequence or a joint 182/753 manuscript. The continuous LXX 3336 → 3267 → 2738 BC comparison is cross-Gear (69 + 529 = 598), not a replacement of Shem's 600-year lifespan. The MT 3127 → 3058 BC = 69 and 3056 → 2458 BC = 598 are separately located intervals; their relationship must not be presented as one attested continuous MT three-node partition. Gain-transfer, anchored expansion, and whole-biography translation must be distinguished. 188-based comparison outputs remain non-operative, and applying 188 to the otherwise unchanged birth chain does not preserve its 1656 total.

Machine Guard [FILE_18 RESIDUE / KEY-OF-23]:

Ordinary Key-of-23 whole-year conversion is distinct from the Residue Protocol. The active Enochian ratio is 300/299. Legacy 299/300 wording remains only source-history / inverse-caption language. The displayed 365.24 form does not by itself yield 7.5 days; File_12's true-solar reference yields 7.4178 days, while File_11 classifies the 7.5 days value as Enochian conceptual residual-display and distinguishes it from physical residue. Do not feed day-display residue values into civil-year arithmetic unless a local Residue Protocol or calibration operator is explicitly opened.

Machine Guard [FILE_18 137 CHECKSUM]:

The 137 recurrence is a boundary checksum, not a new chronological operator. It may be cited as 7 + 130 where a seven-year completion field and a 130 patriarchal hinge are both active. Do not use 137 to create additional birth-date states for Kohath, Amram, Aaron, or Moses. Do not collapse explicit lifespan 137 values with 7 + 130 begetting-wrapper values unless the active state is named.

Machine Guard [FILE_18 SHEM DUAL-100 STATE]:

Do not force Shem's 100 into a single chronological state. Shem is 100 at the Flood in the Noah-bound / Flood-bound state, and 100 at Arphaxad's birth in the Arphaxad-bound / text-bound state. The repository preserves both as valid modal states, analogous to Terah's 70/130 begetting-state display. Do not use either state to erase the other.

Machine Guard [FILE_18 16-EXPECTATION RESTRAINT]:

The 16 × 8 expectation is a structural diagnostic, not a revision of the File_18 table-source pattern. The visible funnel remains 12 × 8, and the 12 has its own Pentateuchal logic. The proposed missing-four extension must not be used to add four patriarchs before Adam or to alter the regular genealogy. Its function is proportional: 4 × 138 = 552, producing a pre-Adamic extension that lands on the cumulative 2nd Cainan field. Classify the result as structural inference / providential synchronization unless later proof promotes it.

Machine Guard [FILE_18 EXTENSION / OPERATOR FIREWALL]:

The 137, 138, 552, 2208, 3450, and 4856 BC relations are diagnostics and structural checks. They do not become new operators. Regular restored Cainan still uses +130; cumulative restored Cainan still uses +460; civil cross-axis spans still use BC + AD − 1; same-side BC spans still use subtraction.

Machine Guard [FILE_18 CAINAN-SECTOR RESTRAINT]:

The 1Kenan / 2nd Cainan reinforcement is included only to support the 137 checksum and the 16 × 8 / 552 → cumulative Cainan extension. Do not expand File_18 into every Cainan-sector branch. Relations such as 8970, 9100, 130 + 330, 7800, 2300, and 6900 remain controlled by File_11, File_16, File_22, or later Cainan-sector files unless explicitly opened.

Machine Guard [FILE_18 CAINAN MACRO-VECTOR FIELD]:

File_18 supplies the cumulative Cainan table-source values used by the File_16 Cainan macro-vector: 4858–4851 BC, 4398–4391 BC, selected member 4396 BC, regular Cainan lifespan members 2551–2091 BC and 2336–1876 BC, and lower-bound Entry 1661 BC. The macro-vector calculations are Category B pattern-vector material by File_16 dependency. They do not alter the primary 12–8–4–2–0 Pentateuchal Funnel, do not add new table rows, and do not replace regular +130 or cumulative +460 Cainan handling.

Machine Guard [FILE_18 SHELAH MIRROR 60-SPINE]:

The Mirror 3540 = 60 × 59 companion is table-source support only. It uses civil cross-axis arithmetic with reversed endpoint order: 1885n BC ↔ AD 1656n, 1878n BC ↔ AD 1663n, and 1871n BC ↔ AD 1670n. Same-order pairing of 1885/1878/1871 BC with AD 1670/1663/1656 does not yield a constant 3540. The Terah / Cainan death rail 1936n BC → 1876n BC → 1816n BC preserves variant death-date labels only; it does not identify Terah and Cainan as the same node-class and does not create a File_18 proof operator.

Machine Guard [FILE_18 2307 / SOLAR AUDIT]:

The 2307 inclusive companion and the solar 7.5 × 365 comparison are retained as audit-controlled companion notes unless a later sanctuary / Hanukkah / phase-resolved calendar file opens the operator explicitly. The exact executable Enochian lower-bound line in this file is 4391 − 1661 = 2730 = 7.5 × 364.

Machine Guard [CANONICAL MARKDOWN / DERIVED AI FORMATS]:

This source remains canonical Markdown. RAG metadata, Knowledge Graph records, JSON, JSONL, prompt-response pairs, and embedding metadata are derived extraction layers and must not replace the source file's arithmetic, modal states, operators, node-classes, claim-status labels, or dependency boundaries.

0A. The Fractal Self-Constraint Principle

Source status: Master Axiom.

Claim-status note: This subsection states the file's architectural axiom. It is preserved as structural inference and theological / methodological framing. It does not replace table arithmetic, local state labels, or dependency-controlled derivations.

0A.1 Core statement

Under this source axiom, patterns established at one scale are not isolated. They propagate both upward to cosmic scales and downward to historical / literal scales. The claim is methodological and architectural: local values must remain compatible with the broader scale-state framework.

0A.2 Implication for methodology

Under the Fractal Self-Constraint Principle, dates and values are treated as discovered within the source's pattern constraints rather than freely chosen. Local consistency therefore remains subordinate to global state consistency.

Example: The 720-year span from Days 6–7 at the Creation-week level is treated by the source as requiring corresponding expressions at other active scales:

0A.3 Test of authenticity

Claim-status: Structural inference and theological / methodological axiom.

A proposed date or value is treated as weak if it solves a local table problem while breaking the stated pattern at another active scale. A proposed date or value is treated as stronger when it remains compatible across the relevant scale states, traditions, and operators. The source's design language is preserved as the theological interpretation of that multi-scale constraint.

0A.4 Relationship to the multi-witness principle

Under the source's multi-witness framework, MT, LXX, SP, and SKL are expected to harmonize horizontally across traditions and vertically across scale states. This is preserved as structural inference and providential-synchronization language, not as a claim that every alignment proves direct scribal intent.

0A.5 Predictive power

The source uses this principle to propose candidate values before verification. A candidate value becomes argumentatively useful only after the relevant table, state, operator, or dependency check supports it.

1. The Variant Mechanism

1.1 The 60 + 155 + 60 pattern

Active state: Regular chronology; four-position variant matrix.

All three manuscript traditions share this fork structure from Adam to Terah's death.

Note: The +155 gap occurs because 215 − 60 = 155 when variants are applied sequentially.

1.2 Inter-tradition gaps

Active state: Literal versus harmonic gap comparison.

The shift of the SP baseline to 4200 BC creates literal integer gaps, 301 and 1079, that differ from the harmonic ideals, 300 and 1080, by exactly 1 year. These are resolved through Gear 2 and reckoning mechanisms.

1.2.1 The 7.5-day Creation residue

Active state: Residue / Enochian comparison after Arithmetic Pass; audit-controlled.

The 299-year solar interval, derived from the 301-year literal gap through Gear 2, generates a specific residue when converted to the 300-year harmonic.

Source-retained math:

(299 × 365.24) − (300 × 364) ≈ 7.5 days

Source-retained result: Claim-status: structural inference / residue-display claim. The source interprets the gap as generating the Full Creation Week, 7 days plus 0.5 straddle, thereby supporting the 301-year distance once the active residue-display state is named.

Arithmetic note: Arithmetic-control checking verified that the displayed source expression does not produce 7.5 days by ordinary arithmetic: (299 × 365.24) − (300 × 364) = 6.76 days. Using the true-solar reference named by File_12, (299 × 365.2422) − (300 × 364) = 7.4178 days. Current source-state control classifies the source's ≈ 7.5 days as conceptual residual-display / calibration language rather than ordinary arithmetic from the abbreviated 365.24 display. Current dependency controls identify File_17 for the exact 300/299 ratio, File_12 for legacy 299/300 wording and true-solar display, and File_11 for physical-residue versus conceptual residual-display distinctions. The supplied source also cites File_28, Section 1, which remains a legacy dependency not needed to proceed with the current File_18 revision.

Cross-reference: Gear logic: File_11, §3. Exact ratio: File_17; legacy 299/300 wording and true-solar display: File_12; physical-residue / conceptual residual-display distinction: File_11, Appendix B; legacy source also cites File_28, §1.

1.3 Epoch structure and Cainan / Funnel control module

Active state: Variant-application epochs; restored/native 2nd Cainan state where named.

This section contains the primary variant-count architecture and its bounded secondary diagnostics.

Hierarchy rule: The primary File_18 pattern is the 12–8–4–2–0 variant-count ladder and its corresponding 8–4–2–0 possible-date countdown. The 27-generation completion, tebah / ark typology, 137 checksum, Shem dual-100, 16 × 8 expectation, cumulative-Cainan extension, and 1Kenan / 2nd Cainan reinforcement are subordinate layers. They may support the architecture, but they must not alter the table-source mechanics.

Primary epoch map:

1.3.1 Abraham / Terah / 2nd Cainan variant multiplication

Author clarification: From Levi / Joseph back to Abraham, the active field has two possible dates because of the 215-year Sojourn variant. Terah introduces the next variant, +60 Terah, doubling the field from two to four. In the ordinary no-2nd-Cainan regular table, those four positions extend from Terah back to Adam. When the 2nd Cainan hinge is active, the boundary changes: 2nd Cainan himself still has four possible dates, like Terah; Arphaxad / Flood and every patriarch back to Adam absorb the additional 2nd-Cainan hinge and therefore become eight-position.

Tradition-scope clarification: This multiplication is not MT-local. MT, SP, and LXX encounter the fork sequence at the same genealogical locations: the Sojourn / Egypt-position +215 fork, the +60 Terah fork, and the 2nd Cainan +130 boundary. The arithmetic status differs by tradition. MT / SP receive Cainan by restoration when that state is opened. LXX already contains Cainan in its regular baseline, so the LXX form is a native-Cainan boundary state unless a theoretical removal / reinsertion state is explicitly opened.

Restored 2nd Cainan dates under the four-position downstream field:

Terah begetting-age display:

1.3.2 Pentateuchal Funnel and all-even structural harmony

When the 2nd Cainan hinge is active, the regular-chronology variant mechanics form a structural funnel. The pattern is not only a set of boundary lines and is not local to MT. It aligns the number of generations and the number of possible date states with the four major Pentateuchal narrative arcs as the chronology approaches the fixed Exodus and Conquest anchors. MT, SP, and LXX each come to the same fork points: the Sojourn / Egypt-position +215 fork, the +60 Terah fork, and the 2nd Cainan +130 boundary.

Tradition-specific handling:

Claim-status: the generation counts and variant-date fields are structural data of the table state. The mapping of those counts to the four Pentateuchal arcs is a structural inference. The cross-tradition recurrence in MT, SP, and LXX is shared-tradition evidence / providential synchronization where the theological meaning is invoked. Where the pattern is interpreted as evidence of providential design, classify it as providential synchronization rather than as an unqualified proof of direct scribal intent.

Machine Guard [FILE_18 PENTATEUCHAL FUNNEL]: Do not collapse the 12–8–4–2–0 variant-count ladder into a mere boundary note or an MT-only phenomenon. When the 2nd Cainan hinge is active, the ladder forms an all-even structural funnel that maps onto Creation → Flood, Flood → Abraham, Abraham → Entry into Egypt, and Egypt → Conquest / Moses death across MT, SP, and LXX. Also do not give 2nd Cainan eight possible dates. 2nd Cainan remains in the four-position block; Arphaxad / Flood is the first upstream eight-position row. In LXX, Cainan is native to the baseline; do not add +130 to the active LXX baseline unless a theoretical removal / reinsertion state is explicitly opened.

1.3.3 27-generation completion and the tebah / ark bridge

Active state: Restored/native 2nd Cainan 27-generation completion state.

When restored 2nd Cainan is explicitly opened in MT / SP, or when native 2nd Cainan is retained in LXX, the Pentateuchal Funnel completes as a 27-generation structure from Adam to Moses. This is not a new date operator. It is a generation-count and typological state layered onto the variant-boundary structure already defined in §§1.3.1–1.3.2.

Hierarchy guard: The primary File_18 pattern remains the 12–8–4–2–0 variant-count ladder and its possible-date countdown: 8 date states, 4 date states, 2 date states, then 0 direct regular pivot dates. The 12 + 8 + 4 + 2 + 1 = 27 pattern is a secondary generation-count completion state that includes Moses as the final deliverer generation. It must not be used to obscure or replace the primary date-state mechanics.

Arithmetic fact:

12 + 8 + 4 + 2 + 1 = 27
27 = 3 × 3 × 3

Structural inference: The sequence reads backward from Moses as a narrowing / doubling structure: 1, 2 = 1 + 1, 4 = 2 + 2, and 8 = 4 + 4, with the 12-generation Adam-to-Arphaxad / Flood block serving as the primeval root block. This supports the Pentateuchal Funnel as a structured countdown into the fixed Exodus / Conquest anchors rather than as a mere list of boundary lines.

2nd Cainan keystone rule: Without restored/native 2nd Cainan, the count from Adam to Moses is 26, not 27. The post-Flood block becomes seven generations rather than eight, and the 8-generation / 8-soul ark correspondence is not present in the same form. Therefore restored 2nd Cainan is required in MT / SP to obtain the 27-generation structure; in LXX the structure is already present because 2nd Cainan is native to the source-table baseline.

Typological note: The Hebrew tebah ark motif connects Noah and Moses: Noah's ark saves eight souls through the waters of judgment, and Moses' ark / basket preserves the single deliverer who will lead Israel through the waters of judgment and deliverance. This typological bridge explains why the 8 and 1 endpoints of the funnel are theologically meaningful. It does not carry the arithmetic burden.

Theological note: The structure is compatible with the Genesis multiplication theme: the movement from 1 to 2 to 4 to 8, joined to the 12-generation primeval root, functions as a numerical expression of multiplication as the timeline moves from Adam through the Flood toward Moses. Claim-status: structural inference and providential synchronization where the theological interpretation is invoked.

Machine Guard [FILE_18 27-GENERATION / TEBAH PATTERN]: Do not cite the 27-generation pattern unless restored/native 2nd Cainan is active. In MT / SP, restored 2nd Cainan is required for 27 = 3 × 3 × 3; without it the count is 26. In LXX, Cainan is already native, so do not add another +130. The tebah / ark correspondence is typological and theological; it explains meaning but does not replace the arithmetic count or create a new chronological operator. This secondary 12 + 8 + 4 + 2 + 1 completion layer must not overshadow the primary 12–8–4–2–0 variant-count ladder or the 8-date / 4-date / 2-date / 0-date table-source mechanics.

1.3.4 The 137 = 7 + 130 boundary checksum

Tier: diagnostic checksum layer.

Active state: Restored/native 2nd Cainan Pentateuchal Funnel, with the figurative Creation-week state opened only where named.

The value 137 functions as a boundary checksum:

137 = 7 + 130

The 7 belongs to the completion / Sabbath / Creation-week register. The 130 belongs to the mortal-line, curse, exile, or unresolved-humanity register. Joined together, 7 + 130 may be read as a reconciliation / atonement checksum. This theological meaning does not replace the arithmetic; it explains why the recurrence of 137 is structurally meaningful.

Typological note: Sarah functions as an Eve-like companion figure at the Abrahamic boundary. Sarah's own lifespan is 127, but because Sarah is 10 years younger than Abraham, her death occurs when Abraham is 137. As Eve derives from Adam's side while remaining distinct from Adam, Sarah's death-date is measured both from her own birth and from Abraham's birth. The arithmetic is direct; the Adam/Eve reading is typological.

Aaron terminal imprint: Aaron does not directly live to 130; he dies at 123. The Conquest / land-rest process supplies the missing seven years as a priestly terminal imprint:

123 + 7 = 130

In Nisan-state display this may be stated as 1529n BC → 1399n BC = 130. In the phase-resolved Tishri-state display it may be stated as 1530t BC → 1400t BC = 130. This does not alter Aaron's lifespan. It identifies the priestly atonement imprint reaching completion at the land-rest boundary.

Claim-status: The boundary values are arithmetic facts or conditional arithmetic facts under their named states. The meaning “reconciliation / atonement” is a theological / typological note. The recurrence of 7 + 130 at the boundary points of the Pentateuchal Funnel is a structural inference and must not be promoted to a new chronological operator.

1.3.5 Shem dual-100 state

Tier: diagnostic modal-state support.

Active state: Regular chronology; Shem ±2; Noah-bound and Arphaxad-bound Shem states.

Shem carries two valid 100 states.

These states are not corrections of one another. They function like the Terah 70/130 begetting-state field: both readings are retained under named modal states.

The two-year difference is the Shem ±2 binding hinge. In Regular chronology this local binding distinction concerns Noah/Shem; ordinary coherent Flood Gear transport remains separately available (§3.1.4). In Cumulative chronology the anomaly may propagate through the cumulative chain where that state is opened.

1.3.6 The 16 × 8 expectation and the cumulative Cainan extension

Tier: diagnostic extension layer.

Active state: Regular restored/native 2nd Cainan Pentateuchal Funnel, with MT Cumulative + 2nd Cainan opened only as a comparison register.

The visible File_18 funnel gives:

12 × 8
8 × 4
4 × 2
2 × 0

The 12 is meaningful in its own right. Adam → Arphaxad / Flood supplies the first 12-name block. The following 8 + 4 blocks form another 12-name movement toward Jacob's family entering Egypt and the emergence of the 12 tribes. Thus the 12 is not a defect.

Yet the backward doubling pattern also suggests an idealized head-block:

16 × 8
8 × 4
4 × 2
2 × 0

Therefore the visible head-block is short by four proportional units:

16 − 12 = 4

The expected 16 is not supplied by adding four hidden patriarchs. It appears as a proportional extension.

If the MT pre-Flood span 1656 represents the 12-name Adam → Arphaxad / Flood field, then:

1656 ÷ 12 = 138

The missing four units are:

4 × 138 = 552

The completed sixteen-unit extension is:

16 × 138 = 2208

Using the restored regular Flood Gear rails with +60 Terah and regular restored Cainan +130 opened:

2646/2648/2650 BC + 2208 = 4854/4856/4858 BC

These values land inside the MT Cumulative + 2nd Cainan field, especially the cumulative Cainan span 4858–4851 BC and the rounded / control value 4856 BC.

This does not add four missing patriarchs. It identifies a proportional pre-Adamic extension that lands on the cumulative 2nd Cainan register.

The 4856 BC coordinate is not isolated. From cumulative Cainan to the Moses-death / Conquest terminus:

4856 − 1406 = 3450
3450 = 138 × 25 = 138 × 5 × 5

The coordinate is further reinforced by Key-of-23 and Danielic values:

3450 = 3 × 1150
3450 × 70/69 = 3500
4856 + 50 = 4906 BC
4906 − 6 = 4900

Cainan's death also preserves the 130 signal:

4856 − 460 = 4396 BC
4396 − 1406 = 2990 = 23 × 130

LXX corroboration: The same missing-four logic appears in the LXX. LXX Regular-Minimum Creation to Flood is:

5279 − 3023 = 2256
2256 ÷ 3 = 752

Extending the LXX Maximum node 5554 BC by the missing fourth unit gives:

5554 + 752 = 6306 BC
6306 − 1406 = 4900

This LXX route does not depend on the MT 1656 ÷ 12 = 138 calculation. It supplies an independent corroboration that the missing-four extension can land on a major Conquest-facing 4900 structure.

Claim-status: The arithmetic checks are exact under the named states. The interpretation that the missing-four extension is intentionally answered by the cumulative Cainan coordinate is structural inference / providential synchronization. No formal probability model is supplied here.

1.3.7 1Kenan / 2nd Cainan tenfold reinforcement

Tier: reinforcement and branch-restraint layer.

Active state: Regular restored 2nd Cainan under Gear 3; Kenan / 2nd Cainan sector by File_11 dependency.

The 1Kenan / 2nd Cainan sector reinforces the same 7 + 130 pattern at 10x scale.

In Gear 3, 1Kenan is born at 3921 BC. Kenan begets his son at age 70:

3921 − 70 = 3851 BC

Regular 2nd Cainan, the same Hebrew name in the restored line, is born at 2551 BC.

Thus the span from the birth of 1Kenan to the birth of 2nd Cainan is:

3921 − 2551 = 1370
1370 = 70 + 1300
1370 = 10 × 137

From Kenan's son to 2nd Cainan is:

3851 − 2551 = 1300 = 10 × 130

Since 1Kenan lives 910 = 7 × 130, and since:

1370 − 460 = 910

the death of 1Kenan occurs 460 years before the birth of 2nd Cainan:

3921 − 910 = 3011 BC
3011 − 2551 = 460

2nd Cainan then lives 460 years:

2551 − 2091 = 460

The two same-name Cainan / Kenan lifespans also total 1370:

910 + 460 = 1370
1370 = 10 × 137

This is a lifespan-sum witness distinct from the birth-to-birth 1370 span. It helps conceptualize the consistent use of 137 around the Cainan variants at 10x scale.

Thus the same-name Kenan / Cainan sector gives the larger sequence:

910 + 460 + 460 = 1830

This agrees with the established Gear-3 Cainan-sector control and reinforces the 7 + 130 checksum at 10x scale:

1370 = 10 × (7 + 130)

Claim-status: The arithmetic is direct once the Gear-3 restored-Cainan state is opened. The same-name Kenan / Cainan interpretation, the two-lifespan sum 910 + 460 = 1370, and the 10x 137 reinforcement are structural inference. This note supports the 137 checksum and cumulative Cainan extension but should not be expanded into a separate Cainan-sector proof inside File_18.

Audit / scope note: The deeper Cainan-sector branches involving 8970, 9100, 130 + 330, and related expanded fields are arithmetically coherent but are not needed for the present File_18 funnel amendment. They should remain outside the main argument unless a later Cainan-sector file opens them directly.

1.3.8 Cumulative Cainan macro-vector to 2091 BC, 1876 BC, and 1661 BC

Tier: macro-vector dependency layer.

Active state: MT Cumulative + 2nd Cainan table-source state, regular restored 2nd Cainan comparison state, and File_16 1876 BC Nexus dependency.

File_18 supplies the table-source values. File_16 controls the Nexus argument, Category B classification, Bullseye Protocol use, and theological synthesis.

The MT Cumulative + 2nd Cainan table places Cainan at 4858–4851 BC and the downstream Shelah convergence envelope at 4398–4391 BC. These values are table-source values. They may be used as macro-vector source coordinates only when the active vector state is named.

Arithmetic ledger:

4851 − 2300 = 2551
4391 − 2300 = 2091
4398 − 2520 = 1878
4396 − 2520 = 1876
4391 − 2520 = 1871
4391 − 2730 = 1661
2730 = 7.5 × 364
4396 − 1260 = 3136
3136 − 1290 = 1846
1846 − 1260 = 586
1260 + 1290 + 1260 = 3810
4396 − 3810 = 586
1876 − 1290 = 586

Regular-Cainan 460 cross-modal symmetry:

2551 − 2091 = 460
2336 − 1876 = 460

Cross-tradition 60-multiple Shelah / Plenty-Famine comparison:

Arithmetic check:

4398 − 2520 = 1878
4391 − 2520 = 1871
2520 = 60 × 42

4278 − 2400 = 1878
4271 − 2400 = 1871
2400 = 60 × 40

4825 − 2940 = 1885
4818 − 2940 = 1878
2940 = 60 × 49 = 6 × 490

Claim-status note: This row is collaborative structural evidence for design alignment among MT, SP, and LXX cumulative Shelah fields. It is not a new File_18 table-generation operator. File_16 controls any Bullseye Protocol use. The direct +60 Terah state remains a separate regular-chronology fork that also intersects the 1876 BC year-label.

Mirror 60-spine companion:

The Plenty / Famine triad 1885n/1878n/1871n BC has a −215 companion triad 1670n/1663n/1656n BC.

Same-side companion relation:

1885 − 215 = 1670
1878 − 215 = 1663
1871 − 215 = 1656

When the −215 triad is placed on the AD side in reversed endpoint order, each civil cross-axis component is 3540 = 60 × 59:

Audit note: The constant 3540 requires reversed endpoint order on the AD side. Same-order pairing of 1885/1878/1871 BC with AD 1670/1663/1656 does not produce 3540 in all three rows.

Combined Mirror span display:

3540 + 2400 = 5940 = 60 × 99
3540 + 2520 = 6060 = 60 × 101
3540 + 2940 = 6480 = 60 × 108
6480 = 25920 ÷ 4

The same 60 register also appears in the Terah / regular restored 2nd Cainan death-date rail around 1876n BC:

1936 − 1876 = 60
1876 − 1816 = 60

State-control note: The 1936n BC → 1876n BC → 1816n BC display is a death-date variant rail. It does not identify Terah and Cainan as the same node-class. File_18 preserves the source values and arithmetic controls; File_16 controls the Nexus interpretation.

State-control note: The two regular 460 spans may mirror the cumulative +460 Cainan lifespan value, but they do not replace the regular restored 2nd Cainan +130 begetting-age insertion. The active regular operator remains +130; the active cumulative operator remains +460.

Claim-status: The same-side arithmetic is direct under the named states. The classification of the 2520, 2300, 2730, and Daniel 12 sandwich relations as a macro-prophetic witness belongs to File_16. In File_18, the material is table-source support plus structural dependency notation.

Audit note: The inclusive companion relation checks as same-side arithmetic:

4858 − 2551 = 2307
4398 − 2091 = 2307

This 2307 companion is retained as sanctuary / Hanukkah-style exploratory material unless a later dependency opens the inclusive operator explicitly.

Audit note: The solar companion is not promoted as an exact File_18 operator. The visible same-side span is:

4398 − 1661 = 2737

The comparison with 7.5 × 365 or true-solar 365.2422 requires a phase-resolved calendar state and should remain audit-controlled unless File_12 or a future calendar-control file opens the exact operator.

1.4 Deriving any date

1. Find the patriarch in the appropriate baseline table, §§2–4.
2. Identify which epoch the date falls within.
3. Apply the appropriate variant:
   • Adam → Terah: add 60, 215, or 275 as needed.
   • Abraham → Levi / Joseph: add 215 if using the 430-in-Egypt position.
   • Terah: preserve all four states when needed: 2021–1816 BC, 2081–1876 BC, 2236–2031 BC, and 2296–2091 BC.
   • Aaron onward: use the date as given.

1.5 The Shem ±2 anomaly

Active state: Regular-localized Shem ±2 and cumulative-propagated Shem ±2 distinguished.

Genesis 11:10 creates a two-year ambiguity at Shem, Arphaxad, and the Flood.

• In Regular chronology, this binding anomaly is local to Noah/Shem. Ordinary coherent Gear transport of the Flood and other admitted pre-Flood biographies is separately retained; it does not move the Arphaxad-forward suffix at held variant settings (§3.1.4).
• In Cumulative chronology, the same anomaly propagates through the entire chain and creates the 7-year cumulative margin, 2 + 3 + 2.

1.6 The 2nd Cainan switch

Active states: Regular restored 2nd Cainan and cumulative restored 2nd Cainan.

The 2nd Cainan, Luke 3:36 and LXX Genesis 11:12–13, is native to LXX and intentionally omitted from MT / SP. When restoring Cainan to MT / SP, the adjustment value depends on the chronological method used.

1.6.1 Why two different values

This is a general principle applying to all patriarchs, not a value unique to Cainan.

1.6.2 Application by tradition

AI-processing rules:

Cross-reference: Data table: File_18, §6B for MT Cumulative + 2nd Cainan tables; §§6C–6D for SP and LXX cumulative comparison. Convergence logic: File_16, §3. Axiom definition: File_00, 2nd Cainan Switch.

2. MT Regular Baseline

Active state: MT Minimum-Regular baseline.

Anchor: Exodus 1446 BC; Entry into Egypt 1661 BC, 215 years in Egypt.

Website adjustment: From the 490d.com table state, subtract 215 years from Adam through Levi to recover this minimum baseline.

2.1 Creation to Flood: MT Minimum-Regular

2.1.1 Dual-scale Creation Week

The Creation Week functions at two scales simultaneously, as Daniel's 70th week may function as both 7 days and 7 years.

Both scales converge on 3899 BC. The Adam row represents:

• the year containing the literal Creation week, with Adam created on Day 6;
• the endpoint of the figurative Creation week, with Year 7 complete.

For figurative Year 6, Adam's creation as a year:

3899 + 1 = 3900 BC

For the start of the figurative week, Year 1:

3899 + 7 = 3906 BC

The same dual-scale principle applies at all variant positions: +60 Terah, +215 Sojourn, and +275.

2.1.2 MT terminology clarification

The 215-year difference is the Sojourn variant, 215 years in Canaan before Egypt.

Both 3899 BC, minimum, and 4114 BC, +215, mark the end of Creation Week: the completion of Day 7 / Year 7. The literal seven-day Creation and figurative seven-year Creation converge at these endpoints.

AI-processing note: When external sources reference MT Creation at 4114 BC, this corresponds to the MT Standard-Normal / +215 Sojourn position in this repository's nomenclature. Always verify which variant position is being used.

2.1.3 MT Minimum-Regular table

2.2 Post-Flood to Patriarchs: MT Minimum-Regular

2.2.1 Noah and Shem ±2 anomaly

Active state: Regular-localized Shem ±2.

Genesis 11:10 supplies the two-year distinction used in the regular Noah/Shem binding comparisons. This localized comparison permission does not restrict ordinary coherent Gear transport of the Flood; see §3.1.4. In Cumulative chronology, the ±2 propagates through the chain; see §6 and File_02.

The literal dates represent the minimum baseline. The idealistic dates represent the alternative reading of Genesis 11:10. Both are valid.

For LXX, retain the independently sourced ±2 comparisons at its own native-Cainan positions:

The corrected SP field additionally has a local one-year companion. Its native-frame G2 pairs are:

These columns differ by one year and must not be labelled ±2. The ordinary SP G1 Shem biography 2991–2391 remains the displayed Arphaxad-bound row, distinct from G2 2993–2393 by two years. §3.2.1 gives all three Gears and the named bindings. MT and LXX do not inherit this SP-only adjacent rail.

Cross-reference: Axiom definition: File_00, Shem ±2. Entity logic: File_02, Shem ±2 anomaly.

2.3 Patriarchal period: MT Minimum-Regular; ±215 fork begins

Note: Joseph, born 1700 BC, is born 4 years after Levi, born 1704 BC, but Joseph dies 23 years before Levi, 1590 BC versus 1567 BC, because Levi lived 137 years while Joseph lived 110.

2.4 Fixed epoch: MT; no variants

Note: Aaron's date can optionally shift 0.5 years back to Tishri / Fall, which cascades back through all dates to Adam. Nisan / Spring remains the primary New Year season used in this baseline.

2.5 Kings of Judah baseline: literal, Rounded, and schematic ledgers

Active states: literal/precise United Monarchy; Rounded Scaffold United Monarchy; post-Solomon conventional table; Kings +50 schematic ledger.

Anchor: Fall of Jerusalem 586 BC for the broader Kings table; Exodus 1446 BC for the Temple foundation.

2.5.1 Literal / precise United Monarchy

The literal royal phase fields are:

Nisan:  1050n → 1010n → 970n → 930n BC
Tishri: 1050t → 1010t → 970t → 930t BC.

Checks:

1050−1010=40
1010−970=40
970−930=40
1010n→970t=40.5.

2.5.2 Rounded Scaffold United Monarchy

The mod-5 companion rail is:

1051n → 1011n → 971n → 931n BC.

The rounded Aaron/Moses comparisons are:

1531n−971n=560=14×40
1526n−966n=560=14×40.

The Rounded rail is a File_51a state. It is not the literal / precise monarchy.

2.5.3 Post-Solomon conventional Kings table

The one-year royal state split is not automatically propagated through every later king. The division boundary remains an adjacent 931n/930t/n BC field: 931n BC belongs to the Rounded/conventional accession display, while 930t/n BC closes the precise Solomonic rail.

2.5.4 Arithmetic verification of the Temple states

Literal cardinal state: 1446n−966n=480
Literal ordinal state: 1446n−967n=479 completed years; foundation in the following 480th year
Rounded Moses lock:     1526n−966n=560=14×40
Rounded Aaron lock:     1531n−971n=560=14×40.

966n BC is a shared label under different operators. 967n BC remains the ordinal 480th-year state; 966n BC remains the cardinal elapsed-480 state and the Rounded 560-year Moses landing.

2.5.5 Arithmetic verification of the +50 Offset

Schematic link, File_16: 1446 BC−430 years=1016 BC
Historical link, File_18: 1446 BC−480 years=966 BC
Offset: 1016−966=50 years.

The 50-year offset allows the Triple-430 harmonic, 1876→1446→1016→586, to coexist with the literal 480-year Temple count. It is a third ledger and must not be confused with the one-year Rounded monarchy offset.

3. SP Regular Baseline

Active state: SP Normal / G2, native Sojourn 215, Terah +60 OFF, second Cainan OFF.

Anchors: Exodus 1446 BC; Entry into Egypt 1661 BC; preferred Creation / genealogical chain head 4199 BC; Lamech birth 3545 BC; Flood start 2893 BC; Flood close 2892 BC; fixed Arphaxad 2891 BC.

Frame conversion: Add 215 to the affected regular dates for the reports’ full-430 comparison: Creation 4414, Lamech 3760, Flood 3108→3107, Arphaxad 3106. Appendix A distinguishes this current website setting from the older +275 setting.

Counting convention: Qualify each interval as ordinary completed-year subtraction or inclusive endpoint counting. The legacy name SP Normal / Toggle ON does not impose one convention on every interval or create a global one-year operator. The legacy SP Ideal / Exclusive 4200 comparison is one above the preferred head 4199; this numerical relation does not generate the SP-local Noah/Shem companion rail or change upstream birth nodes.

The preferred SP head remains exactly 300 years earlier than MT Minimum-Regular: 4199−3899=300. Creation-week, Adam-Day, and genealogical node classes remain distinct. The superseded 4415 Adam → 4414 Creation repair is not restored in the preferred chain.

3.1 Creation to Flood: SP Normal / G2

The table uses the native SP frame. Jared, Methuselah, and Lamech retain their lifespan numbers under the inclusive Flood-cap convention. Their selected deaths lie at Flood start; ordinary subtraction to Flood close is the equivalent capacity calculation, not an alternative physical-death assignment.

For the Flood row, the two coordinate columns mean start and close. The remaining uncapped lifespan rows retain their ordinary subtraction conventions; inclusive cap counting does not impose an extra year on every lifespan.

Arithmetic verification:

The three admitted local paths use the one-year counting distinction once:

52+500+100 = 53+499+100 = 53+500+99 = 652. The Flood therefore lies in Lamech’s 653rd counted year. The annual coordinates do not supply an otherwise unstated birthday or fractional-year phase. Genesis 7:6 supplies the cardinal age expression; Genesis 7:11 supplies the ordinal 600th-year expression. Their coordination in this SP field is the study’s reconstruction.

3.1.1 Methodological note: BJ / Jubilees corroboration

Claim-status: derivative/corroborating witness and structural inference in the project model. SP supplies the underlying architecture; the arithmetic alone does not prove the historical direction of literary dependence.

BJ / Jubilees places Shem’s birth at 2650 BC, Ham’s at 2648 BC, and Japheth’s at 2645 BC. It places Ark preparation at 2550, Flood start at 2549, the earth-dry / closing boundary at 2548, and Arphaxad at 2547.

The retained conditional calculation reads the 601st-year closing boundary after 600 completed units: 2548+600=3148, yielding a derived BJ Noah station. It gives 3148−2648=500 to Ham and 3148−2549=599 to Flood start. This illustrates interval-specific ordinal/completed reckoning; it does not generate SP’s upstream birth dates or a Flood companion rail.

BJ event coordinates translate by +344 into the native SP frame and by +559 into the equalized SP frame: 2550/2549/2548/2547 + 344 = 2894/2893/2892/2891, or +559 = 3109/3108/3107/3106. The SP Ark-preparation interval remains conjectural, supported by the BJ parallel. The native SP 2894 / equalized 3109 is independently also the G3 Flood close; sharing a coordinate does not identify these event classes.

3.1.2 Methodological note: 100-year harmonic preservation

Claim-status: derivative/corroborating structural comparison. BJ retains the following intervals while giving Shem the firstborn chronological position:

Keep birth-position correspondence separate from event correspondence. BJ births plus 345 reach native SP 2995/2993/2990, selecting G3 primary / G2 primary / G1 companion from the Shem field. In the equalized frame the same birth-position translation is +560, reaching 3210/3208/3205. It preserves BJ’s 2+3 spacing. The ordinary SP upper son-order reconstruction remains Japheth 3210 → Shem 3208 → Ham 3206, with 2+2 spacing. Birth-order position, named person, and representative status are distinct; Report V and its companion supply the fuller interpretation.

3.1.3 SP Flood cap and patriarchal deaths

For the nine pre-Noah rows Adam through Lamech, native G2 inclusive capacity is birth−2893+1, equivalently birth−2892. Noah is outside this cap domain.

Capacities are not nine asserted lifespans. The retained SP lifespans of Jared, Methuselah, and Lamech meet their capacities and place their selected deaths at the G2 Flood start:

The equivalent closing-boundary calculation does not move their selected deaths to 2892. The inclusive +1 counts the endpoint year; it does not give Adam through Lamech a Noah/Shem companion birth rail.

For coherent Gear displacement δ = −2, 0, +2, transport each selected birth and Flood start together. The capacity stays (birth+δ)−(2893+δ)+1 = birth−2893+1; close is independently 2892+δ. A cap takes the minimum of the current lifespan count and this qualified capacity. Gear carries the current capped lifespan unchanged and does not restore discarded information. This is guarded/source-qualified commutation, with no wider state-count claim.

3.1.4 Ordinary Flood Gears, fixed Arphaxad, and the SP midpoint

This table uses the full-430 comparison frame, Terah +60 OFF, MT/SP second Cainan OFF, and LXX native second Cainan ON. The LXX G2 Creation head is 5494, consistent with 5494−3238=2256; Cainan-OFF 5364 must not be paired with native-ON Flood 3238.

Every row has the ladder G3 start → G2 start → G1 start → G1 close = 2+2+1 = 5. At this layer LXX is MT +780, including Arphaxad. Each Flood close arises from that Gear’s one-year event span, independently of SP Noah/Shem primary→companion. At held Sojourn, Terah, and Cainan settings, regular Arphaxad onward through Moses does not move with Gear; the separately scoped variant mechanisms retain their own permissions.

Subtract 215 from this table for the corresponding minimum/native frames. The native SP starts G3/G2/G1 are 2895/2893/2891, with closes 2894/2892/2890; fixed Arphaxad is 2891.

The coherent SP Lamech biographies are:

Preserve two separate observations:

1. G2 midpoint to fixed Arphaxad: 4414→3760→3106 = 654+654, equivalently native 4199→3545→2891. Lamech’s G2 birth is the midpoint; this is not a Flood midpoint.
2. G1 convergence: Lamech death / Flood start / fixed Arphaxad birth share 3106, equivalently native 2891, as three distinct node classes. No midpoint language belongs to this convergence.

3.2 Post-Flood to Patriarchs: SP Minimum / Arphaxad-bound suffix

At the held native settings, G2 Flood start 2893 is two ordinary years before fixed Arphaxad 2891. Flood close 2892 is the intervening boundary. No SP companion operator acts on Arphaxad or the subsequent regular rows.

3.2.1 SP Noah/Shem field and named bindings

Each slash-pair below is ordered primary / lower companion. The companion is one year farther forward in time. The rows display ordinary Gear combined with SP-local person-station adjacency; they are not six independently attested source states or a new unrestricted execution generator.

Add 215 for the reports’ equalized dates. Noah’s primary death column carries the inclusive/harmonic qualification and the lower column the ordinary-companion qualification. Matched birth/death endpoints preserve Noah 950 and Shem 600; matched Noah/Shem births preserve 500. The mixed G2 companion-Noah / primary-Shem path is 3492−2993=499, the ordinal 500th-year alternative.

The native G2 post-Flood spans are 2893−2543=350 and 2892−2542=350. The second uses Flood close and Noah’s companion death; it does not type the Flood close as a companion. The cross-pair 2893−2542=351 is not an unqualified 350.

The following bindings preserve the prior usable stations while making their Gears explicit:

G2 primary Shem 2993 is 102 from fixed Arphaxad 2891. These comparisons retain their endpoint roles and bindings. Noah/Shem alone have the full qualified cross-Gear endpoint-comparison permission in this domain; other patriarchs retain coherent-Gear biographies. Qualified Noah↔Flood comparisons are allowed, while the Flood remains an event start/close structure.

The post-Flood begetting table selects the G1 primary / Arphaxad-bound Shem row:

Arithmetic verification, Arphaxad-bound standard intervals:

Convergence note: SP Abraham, 1951 BC, matches MT Minimum-Regular Abraham, 1951 BC.

3.2.2 Terah Dual-Lock: 145 versus 205

In the SP post-Flood timeline, Terah functions as a dual-harmonic pivot.

Both values target Abraham's birth at 1951 BC and Terah's death at 1876 BC. The SP text officially contracts Terah's lifespan, 205 → 145, to land his death on Abram's call at age 75. Architecturally, however, the 205 state remains visible: the SP has not eliminated the Terah problem so much as shifted it from begetting-age tension to lifespan tension. Therefore the SP +60 Terah possibility remains state-valid where opened, while SP cumulative tables retain the official 145 span.

3.2.3 External alignment: BJ / Jubilees

The SP Creation, 4199 BC Normal, is separated from the BJ / Jubilees Creation, 3856 BC, by 343 years.

Repository perspective:

343 years = 7 Jubilees

BJ / Jubilees consistently employs inclusive reckoning by source argument.

Claim-status: structural inference and shared-tradition evidence. The 343-year gap, 7 Jubilees, fits the architectural requirement of the SP baseline while preserving the theological interval native to the Jubilees tradition.

3.3 Patriarchal period: SP Minimum

State note: Same as MT Minimum-Regular in the Abraham → Levi / Joseph minimum state. Abraham has two birth states, 1951 BC and 2166 BC, by the ±215 Sojourn fork. This field is not affected by +60 Terah until the Terah boundary.

3.4 Fixed epoch: SP; same as MT

Identical to MT §2.4. The timeline is unified from Abraham forward.

4. LXX Regular Baseline

Active state: LXX Regular-Minimum.

Anchor: Exodus 1446 BC; Entry into Egypt 1661 BC.

Website adjustment: Subtract 275 from Adam through Levi.

Note: LXX Regular-Minimum = MT Minimum-Regular + 1380 years.

4.1 Creation to Flood: LXX Regular-Minimum

Source note: The main LXX reconstruction pairs restored begetting 182 with attested LXX lifespan 753 in both Regular and Cumulative execution. The remainder 571 is calculated. The lack of an identified surviving joint 182/753 attestation concerns the combination, not 753 itself; §4A.1 explains its retention as the author-preferred original LXX lifespan. Methuselah still dies in the Flood year (3023 BC); Lamech dies 29 years before (3052 BC). See §4A for the source distinction and qualified Key-of-23 explanation, and Appendix B for the MT-derived LXX 777 overlay and retained external references. No other row in this birth chain changes.

4.2 Post-Flood to Patriarchs: LXX Regular-Minimum

Note: The Terah / Abraham relation is resolved by the author-clarified four-position field. The displayed LXX Regular-Minimum Terah row, 2021–1816 BC, is the no-+60 Terah, no-+215 Sojourn minimum row. In that state, Terah begets Abraham at 70, producing Abraham 1951 BC. When +60 Terah is active, Terah shifts to 2081–1876 BC; the 130 begetting-state then also produces Abraham 1951 BC. With the +215 Sojourn state active, the corresponding pair is 2236–2031 BC with begetting-state 70, producing Abraham 2166 BC, and 2296–2091 BC with begetting-state 130, also producing Abraham 2166 BC.

Therefore Abraham has two birth states, 1951 BC and 2166 BC, while Terah has four birth/death states.

Author-confirmed LXX table correction (September 2026): the former §4.2 Peleg/Reu/Serug lifespan cells 239/239/230 were copy errors, not manuscript variants. The controlling LXX Regular-Minimum values are 339/339/330; births remain 2492/2362/2230 BC, so the corrected deaths are 2153/2023/1900 BC. Begetting ages remain 130/132/130. This correction is independent of the Lamech 182/753 source hierarchy.

See MT §2.2.1 for ±2 anomaly details at tradition-specific dates.

4.3 Patriarchal period: LXX Regular-Minimum

Same as MT Minimum-Regular in the Abraham → Levi / Joseph minimum state. Abraham has two birth states, 1951 BC and 2166 BC, by the ±215 Sojourn fork. This field is not affected by +60 Terah until the Terah boundary.

4.4 Fixed epoch: LXX

Identical to MT §2.4.

4A. Lamech: common 182/753 reconstruction and the Key-of-23 crossover hypothesis

Active state: author-adopted LXX main reconstruction, September 8 2026. 182 is the restored regular begetting input; 753 is the retained attested LXX lifespan in both Regular and Cumulative execution. This supersedes the former regular-777 / cumulative-753 dual-locality ruling. Unless specified otherwise, the displays below use the website +215 Sojourn, no-+60 Terah, native-LXX-Cainan frame. Appendix A retains the minimum-frame conversion. Appendix B preserves the MT-derived LXX 777 overlay, overlap geometry, and lesser corroborations outside the main chronology.

4A.1 Source hierarchy and the component-wise reconstruction

The standard transmitted LXX record is 188 + 565 = 753. 753 itself is the attested/transmitted LXX lifespan in Genesis 5:31, not a reconstructed number. This study retains it as the preferred original LXX lifespan, an author-adopted textual/structural conclusion supported especially by §4A.3. Its attestation is a textual fact; the judgment that it preserves the original LXX lifespan is distinct from that fact and does not establish the earliest Hebrew reading or a complete scribal transmission history.

The component-wise reconstruction pairs this retained 753 with the restored operative begetting age 182, supported by the repository's MT/external-witness argument and source-selected birth chain. It gives 182 + 571 = 753, with 571 calculated. No surviving manuscript witness jointly attesting 182/753, or independently reading 571, has been identified in the sources reviewed here. That qualification concerns the combined biography, not the attestation of 753, and is not a claim that such a joint text could never have existed.

Smith is an external reconstruction witness, not an endorsement of this combined selection. His different full-biography restoration and its source qualifications are retained in Appendix B.1/B.7. MT-like ancestry is the author's working transmission hypothesis, not a historical priority established by the numerical comparisons.

Claim-status: attested LXX lifespan 753; author-adopted judgment that it preserves the original LXX lifespan; restored begetting 182; component-wise 182/753 reconstruction; calculated remainder 571. Structural analysis supports retention of the attested lifespan but does not create joint manuscript attestation.

4A.2 What changes, and what stays fixed

3805 − 3052 = 4020 − 3267 = 753
3805 − 3623 = 4020 − 3838 = 182
3052 − 3023 = 3267 − 3238 = 29

Lamech now dies 29 years before the regular LXX Flood. The selected Methuselah 187 / Lamech 182 birth chain still puts Methuselah's death at the Flood: 187 + 182 + 600 = 969. No regular birth date, Creation endpoint, Noah biography, Flood anchor, or Cainan/Terah/Sojourn operator is changed by the lifespan decision.

The six LXX centenary begetting changes remain lifespan-preserving at their own rows. The whole regular LXX lifespan vector is no longer identical to MT: Lamech contributes a separate difference of −24. A Flood-cap rule does not generate the attested LXX 753; that lifespan enters as LXX source data, not as a fitted numerical exception. Failure to derive it from an unmodified MT lifespan vector limits that proposed generator, not the LXX datum or its adopted source hierarchy.

4A.3 Primary structural rationale: the 69 | 529 = 598 family

The author ranks this family first among the structural reasons for retaining 753; it is not ranked as independent manuscript evidence.

The LXX main Lamech death supplies an internal divider between declared Shem endpoints:

3336 − 3267 = 69 = 3 × 23
3267 − 2738 = 529 = 23 × 23
3336 − 2738 = 598 = 69 + 529 = 2 × 299
598 × 300/299 = 600
69 × 70/69 = 70
69 × 25/23 = 75
529 × 25/23 = 575

Endpoint register: 3336 BC is the Shem birth on the 3336–2736 BC biography; 2738 BC is the death on the alternate 3338–2738 BC biography. Each matched biography retains 600. The selected 3336 → 2738 span is therefore a cross-Gear 598 comparison, not Shem's ordinary lifespan. 3267 BC is the main Lamech death (4020 − 753) and is not shifted to manufacture the partition.

The MT supplies the corresponding Key ingredients under its own controlled states:

3127 − 3058 = 69
3056 − 2458 = 598
598 = 69 + 529
598 × 300/299 = 600

Here 3127 → 3058 is Enoch's ascension/end-of-life to Noah's standard birth; 3056 → 2458 is the alternate Noah birth to the standard Flood. File_02 §6.2–6.3 controls the latter 598 → 600 configuration. These are two separately located MT intervals; the scalar decomposition of 598 must not invent an intervening MT event or be represented as the same continuous three-node sequence as the LXX display.

The proposed crossover is that a Key grammar already visible in MT's Enoch–Noah/Flood field is concentrated in the LXX Lamech–Shem comparison. Shared inherited grammar, partial scribal awareness, or providential synchronization are possible interpretations. Exact arithmetic alone does not decide between them or establish a direction of transmission.

4A.4 Supporting lifespan relations: 24 and the SP century

4114 − 2458 = 1656
1656 × 70/69 = 1680 = 5 × 336
1680 − 1656 = 24
777 − 753 = 24
753 − 653 = 100
454 − 24 = 430

The 777 in this main-body comparison is MT Lamech's unchanged lifespan; 753 is the adopted LXX lifespan and 653 is SP Lamech's lifespan. The 24 gain and the LXX–SP 100 difference give structural support to the choice of 753. They do not imply that multiplying 753 by a Key yields 777, or prove that SP was historically produced from the LXX. The cumulative 454 → 430 consequence remains controlled by §6D and uses the retained 753 input, rather than explaining that input independently of its selection.

4A.5 Supporting six-year anchored comparisons and their targets

An anchored expansion holds the later endpoint fixed. In positive BC labels, the earlier comparison endpoint is a + (300/299)(b − a).

All three input spans expand to 1800 = 300 × 6, gaining 6. The first LXX route deliberately crosses Terah settings: 4020 belongs to no +60, whereas 2226 = 2296 − 70 is the firstborn threshold of the +60 Terah state. The Sarah alternative uses 3950 = 4020 − 130 + 60; Sarah remains 2156 BC. Files 69 §5B.5 and 70 §2.3 control that firstborn/Sarah framework. These are translated realizations of one span mechanism, not automatically independent witnesses.

The paired promoted birth comparisons then expose the anchor consequences emphasized by the author:

3246 − 1446 = 1800 = 5 × 360
4026 − 1446 = 2580 = 1290 + 1290 = 6 × 430
4026 − 1876 = 2150 = 5 × 430
1876 − 1446 = 430
4020 − 3240 = 4026 − 3246 = 780 = 390 + 390
4026 − 130 = 3896
3896 − 3246 = 650 = 5 × 130
3896 − 1446 = 2450 = 5 × 490 = 50 × 49

The exact 2450 belongs to the promoted Cainan-OFF comparison, not the unshifted 3890 member. 4026 and 3896 also occur as SOR labels elsewhere; those remain distinct node-classes controlled by File_20. These generated endpoints do not enter the main regular table or the Primary-anchor inventory.

4A.6 Possible origin of the transmitted 188

The author's favored explanation is a cross-register gain-transfer: a six-year Key comparison around Lamech may have been preserved alongside the underlying begetting figure, then incorporated into transmission as though the adjusted value were the original. A marginal calculation, alternative comparison register, or subsequent conflation is a possible mechanism; no surviving sequence of scribal acts establishing one of these routes is supplied here.

182 + 6 = 188
4020 − 182 = 4026 − 188 = 3838

These equations express equal Noah endpoints under different Lamech birth labels, not numerical synonymy of 182 and 188. The nearby 69 → 75 supplies another possible six-year gain, but moving the whole Lamech biography six years earlier is a gain-transfer, not expansion of that same Shem interval. With Shem's birth fixed at 3336, literal expansion of 69 to 75 would give death 3261, not 3273; the transferred +6 biography is instead 4026 → 3273, and its Shem gap is 63.

The non-operative 188 comparison must also preserve path accounting. With Noah fixed, retaining all other begetting intervals moves the earlier chain by six years and changes the Creation-to-Noah total from 1656 to 1662. With Methuselah's 187, 187 + 188 + 600 = 975, which places his 969-year death six years before, not after, the Flood. The distinct 167/188 combination has 167 + 188 + 600 = 955 and a fourteen-year survival excess. Neither execution replaces the main 187/182 reconstruction.

Claim-status: exact arithmetic for the comparisons; author-favored but unproved transmission hypothesis for their entry into the text. The model does not establish historical MT priority, intentional ancient use of these exact anchors, or a probability of scribal causation.

4A.7 Main-chain / appendix hierarchy

Use 182/753 consistently in the actual regular and cumulative LXX reconstructions. Keep 571 explicitly calculated. Retain transmitted 188 as non-operative source data and as the object of the qualified hypothesis in §4A.6, not as a newly licensed toggle. LXX 777 biographies and cumulative extensions belong in Appendix B; their downstream operator examples belong in the relevant file's appendix. A short routing reference does not import those examples as main-chain evidence. The MT 777, unrelated symbolic 777 structures, existing rounded protocols, and all main cumulative totals remain unchanged.

5. Source-numbering note

The supplied source has no Section 5. Public-clean handling preserves the jump from Section 4 to Section 6 because cross-file references already cite Section 6 for cumulative tables. This section is reserved only to document the source-numbering gap.

6. Cumulative Chronology Matrix

Active state: Cumulative chronology.

Full tables source retained: 490d.com/mt-lxx-sp-lifespan-accumulative-long-chronology-table.

Methodology: Lifespans are added end-to-end from Adam to Moses to generate deep-time scalars.

Joseph and half-clutch routing note: The §6 tables remain the direct Adam–Moses/Aaron lifespan-stacking trunk and therefore do not add Joseph as a new patriarchal row. Corrected Final File_61 derives Joseph's original collateral double portion from the unchanged rows: backward from Kohath (1906 → 1796 and 1909.5 → 1799.5 = 110) and forward from Levi (1933 → 1823 and 1936.5 → 1826.5 = 110). Because these are fixed-offset ±110 constructions, File_61 and Final File_62 also derive the following downstream translations without changing the table source:

Forward — Moses/Nisan:
original 1933 → 1823
H7       1926 → 1816
T14      1919 → 1809

Forward — Aaron/Tishri exact:
original 1936.5 → 1826.5
H7       1929.5 → 1819.5
T14      1922.5 → 1812.5

Backward — Moses/Nisan:
original 1906 → 1796
H7       1899 → 1789
T14      1892 → 1782

Backward — Aaron/Tishri exact:
original 1909.5 → 1799.5
H7       1902.5 → 1792.5
T14      1895.5 → 1785.5

Every portion remains 110. These dates are downstream File_61/File_62 coordinates, not new File_18 rows; Joseph remains collateral rather than a direct trunk member.

6A. MT Cumulative Chronology: the main trunk

Anchor: Conquest / Death of Moses = 1406 BC.

Scalar: 12600 years = 10 × 1260 to Creation.

Column key:

6B. MT Cumulative + 2nd Cainan

Active state: Cumulative restored 2nd Cainan.

Logic: Reinserts the 460-year lifespan of 2nd Cainan, LXX / Luke 3:36, into the MT Cumulative chain.

Effect: Shifts all dates from Adam to Arphaxad earlier by 460 years.

Derived companion execution:

14036 + 460 = 14496
14039.5 + 460 = 14499.5
14041–14034 + 460 = 14501–14494

14466 + 30 = 14496
14469.5 + 30 = 14499.5
14471–14464 + 30 = 14501–14494

The ordinary whole-year Aaron member is 14499 BC; the exact phase-resolved member remains 14499.5 BC. This companion is admitted only as an explicitly derived row.

Cainan macro-vector note: This table supplies the source field for the File_16 Cainan macro-vector. The active table-source values are Cainan 4858–4851 BC, Shelah / convergence envelope 4398–4391 BC, and selected member 4396 BC. File_18 supplies these values; File_16 controls the 1876 BC Nexus argument, Category B classification, and Bullseye Protocol use.

Comparative 60-multiple note: When the comparative SP and LXX cumulative Shelah envelopes are opened by dependency, MT, SP, and LXX all yield seven-year target windows by spans divisible by 60: MT 60 × 42 to the Famine window, SP 60 × 40 to the Famine window, and LXX 60 × 49 = 6 × 490 to the preceding years of Plenty. This note is structural comparison only and does not alter the §6B table rows.

6C. SP Cumulative Chronology

Active state: SP cumulative chronology.

Anchor: Death of Joshua = 1296 BC, SP tradition, 110 years.

Scalar: 12100 = 110 × 110 years to Creation, lower bound.

Logic: Uses SP lifespans, including Terah 145 and Lamech 653.

6C.1 Day-4 phase-anchor display (File_56 dependency; routed July 2 2026, applied July 6 2026)

Active state: SP Enochian Day-4 phase-anchor state, cumulative-only.

Under the File_56 state, the SP cumulative decade reads:

This display coexists with the default Day-1 / Year-7 reading of the §6C table. Every numerical value is shared; only day-labels shift by 3. File_56 controls the phase-anchor state. SP regular chronology is unaffected.

6D. LXX Cumulative Chronology

Active state: LXX cumulative chronology.

Anchor: Conquest / Moses Death = 1406 BC.

Logic: Uses LXX lifespans, including Lamech's attested/transmitted 753, retained as the author-preferred original LXX lifespan in agreement with Regular execution (§4A.1), and Nahor 208. Includes 2nd Cainan. The former main-table overlay is preserved separately in Appendix B.2; all main-chain values remain unchanged.

Appendix routing: The 777 cumulative overlay formerly printed here is preserved in Appendix B.2. It shares the Noah endpoint with the 753 chain and must not propagate upward. The LXX Flood's chief cumulative marker remains the death of Methuselah, matching the selected regular 187/182 alignment. The 14901 − 1446 = 13455 = 299 × 45 lock (File_56 dependency) and all main §6D coordinates remain unchanged.

430-alignment justification state (bounded addition): Leveling the MT with the LXX by restoring Cainan (+460, §6B), the two cumulative chronologies differ by exactly 430 from Lamech back to Adam (14896 − 14466), but only with Lamech at 753: the accumulated difference below him is 454, and his −24 trims it to Ezekiel's figure, carried unbroken to the head (8048 − 7618 = 430 at Lamech). The four Adam heads — each tradition with and without Cainan: 14896 / 14466 / 14436 / 14006 BC — read 430 + 30 + 430 (the Adam field; narrative at File_22 / File_46 §6A.5). Claim-status: arithmetic fact; the functional-choice reading is structural inference.

Flood-marker convention set (bounded addition): MT cumulative — dual marking (death of Methuselah; birth of Arphaxad two years after; §6A). LXX cumulative — chief marker the death of Methuselah. SP cumulative — death-side marker unassigned, since Jared, Methuselah, and Lamech all die in the Flood year (§3); the Arphaxad marker stands universally. Claim-status: author-declared convention over textual data.

Cross-reference: Entity logic: File_02, Shem ±2 anomaly, Regular and Cumulative distinctions. Axiom definition: File_00, localized baseline variants. Overlay locks and deep-time expansions: File_46 §6A; File_44 §6A; File_51b §7A.

7. Sumerian King List Integration

Active states: Sumerian A / SKL Short; Sumerian B / SKL Long; 360:1 scale.

Source: 1260d.com / 490d.com merged chronology.

Scaling key: 360 Sumerian years = 1 Biblical year; source phrase: “A day is as a year.”

7.1 Primary anchors

State note: The Primary Date column corresponds to Sumerian A / SKL Short where 17980 whole years are active. The Variant column corresponds to Sumerian B / SKL Long where the +6480 relation and 24510 whole-year state are active.

7.2 The 6480-year variant

Active state: Sumerian B / SKL Long and File_34-controlled precessional envelope.

An alternative text records “24510 years, 3 months and 3.5 days” instead of “17980 years” for the 23 post-Flood kings. The whole-year difference is 6530. Under the File_21 / File_02 SKL Short / Long control, the exact shift relation is:

24510 − 17980 = 6530
2906 − 2856 = 50
6530 − 50 = 6480
27366 − 20886 = 6480

This preserves the source-retained 24510 / 17980 whole-year totals while explaining why the active SKL Flood-anchor displacement is 6480 after the 50-year end-anchor gap is accounted for.

The primary anchor dates, 2906/2856 BC, also carry their own ±2, ±30, and +720 fine-tuning. Example:

2906 + 720 = 3626 BC

With adjustments, the source gives:

3658/3656/3608/3606 BC

Note: 3606 BC = 6 × 360 years to the 1446 BC Exodus. Full elaboration of anchor fine-tuning is beyond the scope of this baseline reference.

Source note: Claim-status: dependency-controlled textual datum and structural inference. The “3.5 days” is significant by source argument. The source relates it to the 3.5 days / years prophetic period in Revelation 11–13 and Daniel 7, 9, and 12.

7.2.1 The Precessional Envelope: Berossus-SKL unification

Active state: File_34-controlled SKL / Berossus dependency.

The 6480-year variant gap functions as the key that unifies the Sumerian King List with Berossus chronology. Both systems use the same “3 months,” 90 days of precession, but interpret its vector differently.

Tier separation: Each tier is exactly 6480 years from the next.

Alignment formula:

Berossus_Flood = SKL_Lower_Flood + 12960

AI-processing rule: Berossus and SKL are not independent chronologies in this source's integration state. They are the same system read with different precessional offsets.

Cross-reference: Full derivation and manuscript tradition mapping: File_34, §5, The Precessional Envelope. Post-final File_34 also controls Appendix B.5 for the SKL-to-Berossus 2370 corridor and 30 + 20 + 30 restoration corridor where those labels are referenced by SKL files.

7.3 The +720 scale-state

Active state: SKL +720 scale-state.

The ±2-year anomaly at Shem scales to 720 years:

2 × 360 = 720

This creates parallel date variants throughout.

Example, Adam / Alulim:

The 6480-year gap can expand to 7200 years, 10 × 720, for scaling purposes. Compare the MT-LXX gap range from 1380 to 1440, +60, where 1440 = 1/5 of 7200.

7.4 The +2 and +30 fine-tuning mechanism

Active states: SKL +2 local rail; SKL +30 Apparent Mode; SKL +720 scale-state.

All SKL dates carry both the ±2 literal years and the ±30 literal years, paralleling Adam's apparent age in biblical chronology, applied throughout.

Example, Adam / Alulim full range:

The same mechanism applies to +6480 variant dates.

7.4.1 Gap range

7.4.2 The “3 months” as unifying mechanism

Claim-status: dependency-controlled textual datum and structural inference. The SKL phrase “24510 years, 3 months and 3.5 days” functions, by source argument, as evidence that the two variants form one system, just as MT, SP, and LXX are complementary witnesses. The +3 months links the chronologies through gear-switching.

File_21 cross-file control: the Jachin / Boaz Pillar coordinates are not derived solely from the SKL row. File_21 treats the SKL 90 × 360 = 32400 alignment as providential synchronization with the Temple-Time / Ezekiel temple measurement framework. Jachin extends to AD 29515, Boaz extends to AD 29465, and both converge at AD 29395. Source-context link: https://www.1260d.com/temple-time.pdf

7.4.3 The “3.5 days” connection: MT-SKL Creation bridge

Claim-status: dependency-controlled textual datum and structural inference. The “3.5 days” in the SKL phrase provides, by source argument, the key that links MT to SKL.

3.5 days × 360 = 1260 years

SKL 2886/2856 BC + 1260 = MT 4146/4116 BC

The full 7.5 days of Creation at 1:360 scale:

7.5 × 360 = 2700 years

LXX 5586/5556 BC → SKL 2886/2856 BC = 2700 years

7.4.4 Breakdown of the 2700-year span

Active state: Regular chronology comparison.

The terminal 720-year segment, Days 6–7, encodes:

• Day 6: Adam created.
• Day 7: God rested, Sabbath.

7.4.5 Cumulative chronology alignment

Note: The 2550/2580 difference reflects leap-month variants, 30/60 years, not imprecision. Both values place Shem exactly at Day 1. 2580 = 36 days of precession. The 360-calendar's 40-year cycle includes 7 leap months.

Typological note: Day 1, Shem: “Let there be Light.” Shem, שֵׁם, “Name,” prefigures Christ as “Light of the World,” John 8:12, and “the Name above every name,” Phil 2:9, by source reading.

Typological note: Day 2, Flood: God separated waters above from waters below, Gen 1:6–8. The Flood dissolved this separation temporarily, “windows of heaven opened,” Gen 7:11. The Cumulative Flood is positioned at Day 2 because it undoes Day 2's work.

SP integration: SP offset from LXX = 1080 years = 3 × 360 = exactly 3 days. SP participates in the same Creation Week framework in both Regular and Cumulative states.

Multi-witness design argument, source-retained and classified:

The source interprets the Creation Week as distributed across all witnesses, requiring their integration to see the complete picture. The theological claim that MT, LXX, and SP function as complementary witnesses to unified divine authorship is preserved as a theological note and providential synchronization. It does not by itself prove direct scribal intent.

Source-retained conclusion, classified: The SKL anchor, 2886/2856 BC, marks the cosmic end of the Creation Week: the point where God's rest is complete. The SKL text's “3.5 days” functions, by source argument, as a dependency-controlled bridge from MT Creation to SKL. The claim that the systems were designed as an integrated whole is preserved as providential synchronization and theological interpretation, while the local arithmetic burden remains with the stated 3.5 × 360, 7.5 × 360, and SKL rail calculations.

Function: These fine-tuning mechanisms result from scaling the small biblical ±2 and +30 states into Sumerian cosmic time. The gear analogy is retained as explanatory language; the argument remains structural inference unless the active rail and dependency are named.

7.5 Applying the variants

To apply the +6480 variant, add 6480 years to all dates from Flood backward to Pre-Creation.

7.6 Antediluvian kings as biblical patriarchs

Source note: An asterisk in the legacy table designated a new dynasty in SKL.

7.7 Post-Flood notable figures

7.8 The Pillars of Time

File_21 cross-file control: The Pillars are Projective Boundary / Temple-Time coordinate states, not ordinary historical chronology. File_21 standardizes the live repository spelling as Jachin, paired with Boaz. The inherited SKL chart / earlier File_21 source used Jochin; retain that form only as source-history spelling unless quoting the original chart.

State note: The shared inside-skin convergence coordinate is AD 29395; Boaz extends to AD 29465; Jachin extends to AD 29515. File_21 treats the SKL 3 months = 90 × 360 = 32400 relation as providential synchronization with the Temple-Time / Ezekiel temple measurement framework, not as the sole derivation. Source-context link: https://www.1260d.com/temple-time.pdf

7.9 Key harmonic connections

8. Arithmetic Verification Table

Arithmetic-control scope: These source-retained rows were checked during the Arithmetic Pass. Same-side BC spans use subtraction. Civil cross-axis spans use BC + AD − 1 only where an AD target is explicitly opened. This pass is not a pressure test and does not resolve source-state contradictions reserved for later review.

8.1 Section-level arithmetic ledger

8.2 Audit-controlled arithmetic displays

9. Cross-Reference Index

9.1 Source-retained cross-reference index

9.2 Dependency-control additions

These additions are not presented as legacy source rows. They are dependency controls required by the current repository files.

Appendix A. Website Table Adjustments

Source-history function: This appendix records how to convert website tables, 490d.com, to the minimum baseline used in File_18.

Note on SP: The ordinal 599+ and conventional cardinal 600 readings are reconciled through qualified SP Noah/Shem stations. They do not generate a one-year Flood uncertainty range or shift Adam through Lamech. §3 gives native G2 Flood start→close 2893→2892, while Arphaxad stays 2891; add 215 for 3108→3107 and 3106. The Flood has ordinary three-Gear transport in MT, LXX, and SP. LXX remains native Cainan ON in the full-430 comparison, including Creation 5494, Flood 3238→3237, and Arphaxad 3236.

July 2026 replacement pages (bounded addition): The rewritten website pages supersede the settings above for the live site. Both pages present the three traditions level at the normative state: +215 Sojourn, no +60 Terah.

Appendix B. LXX Lamech 777 overlay, source comparison, and subsidiary corroborations

Status: appendix-only comparison and preservation layer, subordinate to the main 182/753 ruling in §4A. No row here replaces Lamech's main lifespan, adds a regular begetting interval, propagates an extra 24 through the cumulative chain, or proves a historical transmission sequence.

B.1 The alternative full biography and the five-before-Flood comparison

The MT record and Smith's proposed LXX restoration are 182 + 595 = 777. In this repository, applying MT 777 to the LXX is an appendix-only overlay, not the preferred original LXX lifespan. Smith's restoration is retained as an external reconstruction, not as a jointly attested original established here. The main LXX reconstruction retains attested 753 with restored 182 and does not claim Smith's support for that pair.

MT independently retains 3240 → 2463 BC, with Flood 2458 BC, and its own five-year pre-Flood margin. The former claim that the main MT and LXX biographies both end five years before their Floods is superseded: the LXX part is now confined to this 777 comparison, while main LXX 753 ends 29 years before.

B.2 The cumulative overlay: shared endpoint, no propagation

Both starts lead to the same Noah envelope:

8053 − 753 = 8077 − 777 = 7300
8048 − 753 = 8072 − 777 = 7295
8046 − 753 = 8070 − 777 = 7293
9022 − 969 = 8053
8077 − 8053 = 24

Thus the 777 overlay overlaps Methuselah's final 24 cumulative years rather than inserting new time before Noah. The unchanged 753 chain preserves 14901 − 1446 = 13455 = 299 × 45 (File_56 dependency) and the §6D 430 alignment. File_46 Appendix A now holds the preserved 8070 twenty-of-years, staged-Flood, and double-expansion examples; its §6A.1–§6A.3 remain routing points only where those overlay instances are concerned.

B.3 Triad comparison and the two Key gains

(182, 595, 777) + (6, −30, −24) = (188, 565, 753)
6 − 30 = −24
1794 × 300/299 − 1794 = 6
1656 × 70/69 − 1656 = 24

These exact differences compare the MT/Smith biography with the transmitted LXX triad. The signs and assignment of gains from different spans to one biographical record are the proposed crossover, not a single demonstrated textual operator. In particular, a +24 span expansion does not automatically cause a −24 lifespan change. The main chronology does not execute this triad as a reversible textual-history theorem.

B.4 The two equal 782 arms and the 874 co-shift

4020 − 3238 = 3238 − 2456 = 782 = 23 × 34
4020 − 2456 = 1564 = 23 × 68
2458 + 1680 = 4138
4138 − 3264 = 4114 − 3240 = 874 = 23 × 38

4020 is LXX Lamech's main birth, 3238 the LXX Flood, and 2456 MT Arphaxad's birth/two-years-after-the-standard-Flood state. The 874 construction shifts Creation and Lamech's birth together by 24, preserving their separation. This co-shift and the 777 − 753 duration difference are two uses of the same increment, not one mechanically causing the other. The earlier 874 = 23 × 34 wording was a slip; 23 × 34 is 782.

B.5 The 777 separation / overlap geometry

4020 − 3243 = 777
3243 − 3240 = 3
3240 − 2463 = 777

The unshifted appendix LXX and MT biographies therefore form 777 | 3 | 777.

If the entire MT biography, including its death, is translated six years earlier, it becomes 3246 → 2469 BC. Against the unshifted LXX comparison this gives:

4020 − 3246 = 774
3246 − 3243 = 3
3243 − 2469 = 774

The union now reads 774 | 3 | 774. Translating the MT death with its birth is an additional declared whole-biography choice; the birth-to-Exodus expansion alone does not prescribe it. The longer sequence 774 + 3 + 3 + 771 + 6 = 1557, from 4020 to 2463, is arithmetically valid but is not itself a palindrome.

B.6 Former Flood-Gear-from-above explanation: retained qualification

The previous §4A.6 used the LXX Flood Gears 3240 / 3238 / 3236 BC (minimum 3025 / 3023 / 3021) and the 3240 − 1446 = 1794 span, then spoke of advancing the Gear-2 Flood by six years. The exact anchored conversion applies to the 3240 Gear-3 endpoint; it gives 3246. Applying its gain to Gear 2 is a further cross-Gear gain-transfer, not that same direct anchored expansion. This route is retained only as a qualified subsidiary comparison and is not needed for the main rule or the better-specified §4A.5 comparisons.

B.7 Source register and evidential boundary

Historical inference ceiling: these patterns make the selected numbers structurally intelligible within the repository, but do not prove that a scribe used its BC anchors, that 188 was consciously encoded, that MT historically preceded every other witness, or that the lost joint 182/753 text existed. Providential interpretation remains the author's interpretive framework rather than an arithmetic parameter.

Audit Notes

Audit note 1 — Section numbering: The supplied source skips Section 5. Recommended handling: preserve Section 6 numbering and reserve §5 as a source-numbering note. Author decision required only if the author wants the legacy source renumbered.

Audit note 2 — Cainan cross-reference: The source says §6B contains the full Cumulative + Cainan tables but later cross-references §6C as “Cumulative + Cainan tables.” Current source-control applies the high-probability correction: §6B is MT Cumulative + 2nd Cainan; §§6C–6D are SP / LXX cumulative comparison. Author decision required only if §6C was intended to carry a different local meaning.

Author clarification note 3 — 299 / 300 residue line: The source-retained line (299 × 365.24) − (300 × 364) ≈ 7.5 days remains preserved, but Current source-state control classifies it as dependency-controlled conceptual residual-display / calibration language. File_17 defines the exact 300/299 operator; File_12 preserves legacy 299/300 wording only as source-history / inverse-caption language and gives the true-solar display 7.4178; File_11 distinguishes physical residue from conceptual residual-display and gives physical 300/299 residue as 299/40 = 7.475 days. File_28 remains optional legacy provenance rather than a current blocker.

Audit note 5 — Lamech supersession record: The September 8 2026 author ruling supersedes the July regular-777 / cumulative-753 split and the September prohibition on considering 188 as structural evidence for a qualified transmission hypothesis. Main execution is 182/753; 188 remains non-operative; the LXX 777 layer is appendix-only. The earlier blanket claim that no historical stage ever paired 182/753 is replaced by the narrower reviewed-source non-attestation disclosure. Earlier editions are preserved in the revision package; the Repository Change Archive is not rewritten by this amendment.

Dependency note 4 — File_28 dependency: The source cites File_28, §1 for physics. Current repository status treats File_28 as a retired placeholder / legacy provenance pointer, not an active proof file. Current source-state control no longer treats File_28 as blocking the residue-control issue because the active project controls now assign the exact ratio to File_17, legacy wording / true-solar display to File_12, and physical-residue / conceptual residual-display to File_11. Use File_28 for archive / provenance review only unless a future author decision reactivates its material through another controlling file.

Audit note 5 — SKL / Berossus compression: §7 compresses SKL Short, SKL Long, Berossus, +6480, +720, +30, +2, and the appended 3 months and 3.5 days datum. Visible arithmetic is checked only where locally executable. Full derivation remains dependency-controlled by File_34.

Audit note 6 — Theological design language: Current claim-status control classifies source-retained design-proof language as structural inference, shared-tradition evidence, theological note, providential synchronization, or dependency-controlled claim as appropriate. The design language is preserved, but it does not carry the arithmetic burden by itself.

Audit note 7 — External LXX source-control: Smith has been added once as an external LXX source-reconstruction witness because LXX Genesis chronology is materially active. The LAB / Josephus / Bible Archaeology material remains source-retained and may need source-control review if it becomes proof-bearing.

Author clarification note 8 — MT cumulative Peleg 3495t member-label: Resolved. MT cumulative Peleg spans 3501n–3494n BC, with the parallel Tishri span 3502t–3495t BC. The Conquest / land-rest span is 1406n–1399n BC, with the parallel Tishri span 1407t–1400t BC. Under File_09 Mirror suffix inversion, the AD-side display is AD 1399t/1400n–1406t/1407n. Component checks equal 4900 = 70 × 70 = 100 Jubilees. Therefore 3495t is the Tishri terminal member participating in 3495t → AD 1406t = 4900, not an erroneous upper-member label.

Author clarification note 9 — LXX Regular-Minimum versus LXX cumulative source-table state: Resolved under the September 8 2026 ruling: both main LXX reconstructions select lifespan 753, with begetting 182 in the regular chain and calculated remainder 571. No joint attestation is claimed. Nahor's controlled 208 is unchanged. Appendix B preserves Smith's different full-biography reconstruction and the row-local 777 cumulative comparison without promoting either into main execution.

Author clarification note 10 — SP locality, ordinary Flood Gears, and ordinal/completed counting: Superseded in scope by the September 18 2026 author ruling. The SP −1 companion belongs only to Noah/Shem person-stations; the former upstream-ripple wording is withdrawn. Native G2 Noah 3493/3492 and Shem 2993/2992 give qualified paths to Flood start 2893; Flood close 2892 comes independently from the event-year span. Lamech 3545→2893 is 653 inclusive. Ordinary Flood Gears apply across MT/LXX/SP, while regular Arphaxad 2891 stays fixed under Gear at held variant settings. G1 Shem 2991/2990 and deaths 2391/2390 remain under the named bindings in §3.2.1. The G2 654+654 midpoint ends at fixed Arphaxad and remains distinct from the G1 triple coordinate convergence. BJ provides derivative/corroborating structural evidence in the project model; no SP companion operator transfers to MT or LXX.

Author clarification note 11 — SP Terah 145 (205) dual-lock: Resolved. 145 is the official SP textual lifespan and lands Terah's death at Abram's call. 205 is the architectural lifespan mirroring MT/LXX and showing that the Terah difficulty remains as a swapped lifespan / begetting-age issue rather than disappearing. The SP still permits a +60 Terah state where opened, while SP cumulative tables use the official 145 span.

Author clarification note 12 — Abraham / Terah four-position field: Resolved. From Levi / Joseph back to Abraham, events have two possible date states because of the 215-year Sojourn variant. Terah introduces +60 Terah, doubling the field to four: 2021–1816 BC, 2081–1876 BC, 2236–2031 BC, and 2296–2091 BC. Abraham's birth is therefore 1951 BC or 2166 BC, while Terah has four birth/death states. The File_18 LXX Regular-Minimum table now marks Terah's begetting age as 70/130 state-dependent rather than forcing 130 onto the minimum 2021–1816 BC row.

Author clarification note 12A — 2nd Cainan variant-boundary state: Resolved. When restored 2nd Cainan is inserted into MT / SP regular chronology, 2nd Cainan himself has four possible date states, not eight. The four 2nd Cainan birth states are 2611/2551 BC and 2396/2336 BC, derived from Shelah birth states 2481/2421 BC and 2266/2206 BC by adding the 130 begetting-age hinge. The four 2nd Cainan death states are 2151/2091 BC and 1936/1876 BC, derived by subtracting the 460 lifespan. The eight-position propagation begins with Arphaxad / Flood and continues back to Adam only when restored 2nd Cainan is explicitly opened. The resulting generational variant-count ladder is 12–8–4–2–0: Adam through Arphaxad / Flood have eight possible dates; 2nd Cainan through Terah have four; Abraham through Joseph / Levi have two; Kohath and Amram have zero direct regular pivot dates; Aaron / Moses onward remain fixed / unaffected.

Author clarification note 12B — Pentateuchal Funnel state: Resolved. The 12–8–4–2–0 generational variant-count ladder is structurally important and should not be treated merely as boundary-line bookkeeping. When the Cainan hinge is active, it maps onto the Pentateuchal arcs as follows: Creation → Flood corresponds to Adam through Arphaxad / Flood, 12 generations with eight date states; Flood → Abraham corresponds to 2nd Cainan through Terah, 8 generations with four date states; Abraham → Entry into Egypt corresponds to Abraham, Isaac, Jacob, and Joseph / Levi, 4 patriarchal nodes with two date states; Egypt → Conquest / Moses death corresponds to Kohath and Amram as 2 floating no-direct-date generations, with Aaron / Moses fixed downstream. Claim-status: structural inference, with providential synchronization where the theological meaning is invoked.

Author clarification note 12C — multi-tradition scope of the Pentateuchal Funnel: Resolved. The Pentateuchal Funnel is not local to MT. MT, SP, and LXX each encounter the same structural fork sequence at the same genealogical locations: the Sojourn / Egypt-position +215 fork, the +60 Terah fork, and the 2nd Cainan +130 boundary. The tradition-specific status differs: MT / SP restore Cainan when that state is opened; LXX already includes Cainan in the active baseline and therefore uses the Cainan boundary as native source-table structure unless theoretical removal / reinsertion is explicitly opened. This clarification does not change the variant-count ladder, the +130 regular Cainan value, the +460 cumulative Cainan value, or any table anchor.

Author clarification note 12D — restored/native 2nd Cainan 27-generation completion and tebah / ark bridge: Resolved and focused-pressure-tested. The Pentateuchal Funnel reaches 27 = 3 × 3 × 3 generations from Adam to Moses only when restored/native 2nd Cainan is active: Adam through Arphaxad / Flood = 12; 2nd Cainan through Terah = 8; Abraham through Joseph / Levi = 4; Kohath and Amram = 2 floating generations; Moses = 1 final deliverer generation. Without restored/native 2nd Cainan, the count is 26 and the post-Flood block is 7, breaking the 8-generation block and the 27-generation completion. In MT / SP, restored 2nd Cainan is therefore required for this pattern. In LXX, 2nd Cainan is native and no additional +130 is applied. The tebah / ark connection between Noah and Moses is retained as a typological / theological note explaining the meaning of the 8 and 1 endpoints, not as an arithmetic operator. This secondary generation-count pattern must not overshadow the primary 12–8–4–2–0 variant-count ladder or the 8-date / 4-date / 2-date / 0-date mechanics.

Audit note 13 — Pillars 90-day relation: The §7.4.2 Pillars relation to AD 29465/29515 does not produce 32400 years from base 2906/2856 BC by civil cross-axis arithmetic. It does check if the +30 Apparent Mode anchors 2936 BC and 2886 BC are active. File_21 resolves the argument role: this is a Projective Boundary / Temple-Time Pillar coordinate synchronization, not the sole derivation of the Pillars. Preserve the row and state that the +30 Apparent Mode rail is active before using the 90-day result.

Audit note 14 — Cumulative Flood / SKL Day-2 target: The §7.4.5 line Flood (4836 BC) → SKL = 1980 years = 5.5 × 360 checks against SKL Long 2856 BC, because 4836 − 2856 = 1980. It does not check against SKL Short 2886 BC, where the span is 1950. Recommended handling: preserve the row and name the active SKL Long target unless a later dependency opens another operator.

Audit note 15 — Tammuz → Abraham 129600: The §7.9 key-harmonic row Tammuz → Abraham = 360 × 360 = 129600 years is not derivable from the visible Tammuz rows and the standard Abraham anchors alone. Recommended handling: preserve as File_34-controlled SKL / Berossus material unless a later File_34 revision opens a more specific derivation.

Audit note 16 — Total SKL span 453600: The §7.9 row Total SKL span = 453600 = 1260 × 360 checks when the SKL Short Pre-Creation +720 rail 453606 BC is active against 6 BC, because 453606 − 6 = 453600. It is not produced directly from the base rail 452886 BC. Recommended handling: preserve and name the active +720 rail.

Unresolved Issues

No author-decision blocker remains. The following retained notes are dependency-boundary or source-history controls. They are not blockers to Final status if retained in the publication copy.

1. File_28 remains a retired placeholder / legacy physics provenance pointer. It is not blocking the current residue-control issue after current source-state control, but it may still be useful for archive / provenance review if a future author decision routes any former material through an active controlling file.
2. Section 7's SKL / Berossus derivation remains dependency-controlled by File_34; Current source-state controls clarify rail labels but do not locally rederive SKL / Berossus.
3. The appendix website-adjustment table was reconstructed from malformed source text. The reconstructed rows remain visible for later review.
4. Tammuz → Abraham 129600 remains File_34-controlled because it is not derivable from the visible Tammuz rows and standard Abraham anchors alone.
5. The 2307 inclusive companion and the solar 7.5 × 365 comparison remain audit-controlled. They are not blockers because the executable File_18 update uses same-side arithmetic, the Enochian 2730 = 7.5 × 364 state, and File_16 dependency classification.

Revision and archive note

This public-clean Markdown source retains the prior Final and full-pressure-tested baseline while applying the bounded July 24 2026 monarchy-state correction.

The amendment:

• assigns 1050t/n→1010t/n→970t/n→930t/n BC to the literal/precise United Monarchy;
• assigns 1051n→1011n→971n→931n BC to the File_51a Rounded Scaffold;
• records 1531n→971n=560 and 1526n→966n=560 as Rounded comparisons;
• preserves 967/966 BC as ordinal/cardinal literal Temple states;
• preserves 1016 BC as the separate Verbatim / Schematic +50 pivot;
• leaves all unrelated regular, cumulative, Cainan, SKL, post-Solomon, Mirror, and theological material unchanged.

Detailed revision history belongs in the Repository_Change_Archive. The bounded amendment is independently focused-verified; no new full pressure test is claimed. The prior June 28 2026 full-pressure-test baseline remains retained for unaffected material.

Revision Log — September 8 2026 bounded Lamech settlement

Author-directed correction: main LXX 182/753 in both methods; one regular death/lifespan row changed; cumulative overlay relocated to Appendix B; §4A replaced with source distinctions and qualified Key-of-23 hypothesis. Register v1.53 §D.43 / Capsule v11.52 §10.30 control this amendment. Focused arithmetic, diff, guard, dependency, and protected-region checks are recorded in the accompanying verification report. No new full-file pressure test, separate re-Finalization, website deployment, manifest update, or external archival capture is claimed.

Bounded wording clarification — September 8 2026

Attested LXX 753 is now explicitly distinguished from restored 182, calculated 571, and the combined reconstruction at the source note, state row, existing Machine Guard, §4A.1, and §6D. The preferred-original judgment is retained as the author's textual/structural conclusion; MT-derived LXX 777 remains appendix-only. Register v1.54 §D.43 / Capsule v11.53 §10.30 route the clarification. No numeric table cell, equation, anchor, or operator changes; focused diff, guard-fidelity, and arithmetic checks only. The two live WordPress pages were reviewed; supplied wording replacements are not claimed deployed.

Revision Log — September 18 2026 bounded SP / Flood-Gear correction

• Authority: author’s reviewed Report V / Canonical Register correction and explicit instruction to correct both reports and File_18; native LXX Cainan ON confirmed for both Creation and Flood.
• Scope: SP regular rows, named Noah/Shem bindings, relevant state/display/operator tables and Machine Guards, §2.2.1 comparison labels, §3, Appendix A, and clarification note 10. Unrelated table systems remain inherited.
• Numerical correction: native G2 Flood start/close 2892→2891 replaced by 2893→2892; selected capped deaths of Jared/Methuselah/Lamech use 2893 with inclusive counts 847/720/653. Noah 3493/3492 and deaths 2543/2542 are correctly ordered primary/companion. Creation 4199, Lamech birth 3545, and Arphaxad 2891 are retained.
• Mechanism correction: distinguish cross-tradition Flood Gears and event-year boundaries from the SP-only Noah/Shem −1 companion. Withdraw whole-chain toggle/ripple language; retain interval-specific ordinal/completed readings and the qualified older Shem stations.
• LXX frame: normal native Cainan ON gives equalized G2 Creation 5494, Flood 3238→3237, and Arphaxad 3236; no existing LXX main-table number changes.
• Verification: affected arithmetic and table comparisons, unchanged-region source diff, and Markdown structure checked. This is focused verification of an authorized amendment, not a new full-file pressure test or re-Finalization.
• Cross-file status: both companion reports corrected in the same task. Central State Vocabulary Register, Restart Capsule, earlier research checkpoints, publication records, and website deployment remain separate work; no update to those items is claimed.
• Unresolved author decisions within this correction: none. The conjectural SP Ark-preparation year retains its existing claim-status.