File: File_18
Title: Chronological Data Tables
Status: Final; post-final pressure tested; focused Cainan / Pentateuchal Funnel amendments integrated; structural cleanup applied; 1876 Cainan macro-vector update applied and focused pressure tested; 60-multiple Shelah / Plenty-Famine table-source note and Mirror 60-spine addendum added and focused pressure tested during trust-status equalization; File_21 SKL Unified Protocol and File_34 post-final citation-control cross-file updates applied and focused pressure tested during trust-status equalization; File_18 post-equalization full pressure test complete
Pressure-test status: Current; full pressure test complete June 28 2026 for File_18 as chronological table-source, dependency-control, and SKL interface file; focused pressure tests for the 60-multiple Shelah / Plenty-Famine table-source note, Mirror 60-spine addendum, File_21 SKL Unified Protocol update, File_34 post-final citation-control update, and public-clean cleanup retained; prior post-final and focused Cainan / Funnel checks retained; no publication blocker.
Register Agreement status: Checked against State_Vocabulary_Register v1.17 and active companion controls; convergence / pointer update only; no arithmetic, anchors, modal states, node-classes, operators, sign conventions, slash-pairs, ranges, envelopes, Mirror protocols, Machine Guards, claim-status labels, theological claims, or dependency boundaries changed.
Publication-cleanup status: Public-clean Markdown source; archival amendment history routed to Repository_Change_Archive.
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; 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_21; File_22; File_34; File_51a; File_54; Restart Capsule v11.15; 490d Repository Style Guide v2.5; Project Procedures v3.2; State Vocabulary Register v1.17
Major operators: `+60 Terah`; `+215 Sojourn`; `+275`; `60 + 155 + 60`; `±215`; Shem `±2`; 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`; `+720 scale-state`; `+30 Apparent Mode`; `+2 local rail`; 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
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 / Toggle ON; SP Ideal / Exclusive; LXX Regular-Minimum; LXX Terah / Abraham `2 × 2` variant field; regular-localized Shem `±2`; cumulative-propagated Shem `±2`; regular restored 2nd Cainan; cumulative restored 2nd Cainan; Kings dual-ledger state; Sumerian A / SKL Short; Sumerian B / SKL Long; SKL `+30 Apparent Mode`; SKL `+2 local rail`; SKL `+720 scale-state`; 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
Revision basis: 490d Repository Style Guide v2.5; Restart Capsule v11.15; State Vocabulary Register v1.17; Project Procedures v3.2; prior finalized source; Repository_Change_Archive (non-controlling history)
Current refresh note: Public-clean trust-status equalization aligns active control pointers to 490d Repository Style Guide v2.5, Restart Capsule v11.15, State_Vocabulary_Register v1.17, and Project Procedures v3.2. Register Agreement status is recorded in the header; no arithmetic, anchors, modal states, node-classes, operators, sign conventions, slash-pairs, ranges, envelopes, Mirror protocols, Machine Guards, claim-status labels, theological claims, or dependency boundaries are changed. Detailed pass logs, pressure-test records where applicable, pointer-refresh history, and replacement-workflow notes are preserved in Repository_Change_Archive.

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.

# File_18 — Chronological Data Tables

## Related Repository Files

| File | Function for `File_18` |
|---|---|
| `File_00` | Axiom Engine, structural variators, source-map discipline, civil / Mirror / inverse firewalling, and source-control rules. |
| `File_01` | Abraham entity data and `1876 BC` convergence year-label where Abraham rows are used. |
| `File_02` | Flood terminology; MT Minimum-Regular / MT Standard-Normal distinction; SP Normal / Toggle ON; LXX Regular-Minimum; SKL Short / Long terminology; Shem `±2` state distinction. |
| `File_04` | Jacob, Entry, LXX `33 + 397`, Levi death-state handling, and the `1876 BC` shared year-label. |
| `File_05` | Primary `1446 BC` Exodus state; subordinate `1231 BC` Ramesside state; Sojourn 215 / Exodus 215 firewall. |
| `File_07` | Creation-week endpoint / Year-6 distinction, restored Cainan `+130` / `+460`, and Creation microstructure. |
| `File_08` | Kings dual-ledger state, historical `966 BC`, schematic `1016 BC`, and Fall of Jerusalem date-state controls. |
| `File_09` | Cumulative architecture and restored cumulative 2nd Cainan Flood Week controls. |
| `File_10` | External validation, Smith / Rudd source-control, SKL / Berossus witness framing, and providential multi-tradition system language. |
| `File_11` | Three-Gear Protocol, `299 → 300`, `300/299`, and Residue Protocol distinction. |
| `File_12` | Calendrical physics, Enochian `300/299`, Solar / Enochian year display, `7` / `7.5`, and residue controls. |
| `File_14` | Biological-fractal terminology where variant-gap, `275`, `276`, `280`, and LXX Maximum states are opened by dependency. |
| `File_16` | `1876 BC` Nexus, Cainan convergence, Triple `430`, `+50` Jubilee Offset, and Bullseye claim-status discipline. |
| `File_17` | Prophetic span-component terminology and exact-ratio controls. |
| `File_21` | Controls the SKL Unified Protocol as an application layer: `360:1` scalar, four-state SKL matrix, SKL rounded mod-10 Mirror display-state, Residue Protocol `6480.25`, Projective Boundary / Temple-Time Pillar coordinates, and Jachin / Boaz spelling control. It does not replace `File_34` for full SKL / Berossus derivation. |
| `File_22` | Decimal Bridge and cumulative / Aaron-Moses dependency where exact cumulative tables are opened. |
| `File_34` | Full SKL / Berossus derivation, precessional envelope, `6480` tier logic, Berossus computational-anchor state, SKL-to-Berossus `2370` corridor, `30 + 20 + 30` restoration corridor, paired slash-display arithmetic, and phase-chain / Pillar cross-axis controls. |
| `File_51a`; `File_54` | State-register, File map, Machine Guard, claim-status, Mirror / inverse restraint, and later-file style precedent. |

## 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:

| Data system | Legacy term | Function |
|---|---|---|
| Regular chronologies | Short chronologies | Historical / begetting-age timeline for MT, SP, and LXX. |
| Cumulative chronologies | Long chronologies | Theological / schematic lifespan-added timeline. |
| Sumerian Integration | Cosmic timeline | SKL / Sumerian 360:1 day-year scale. |

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.

### 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.

| State | Primary values / forms | Node-class / function | Handling in `File_18` |
|---|---:|---|---|
| Raw data source state | whole file | table-source / lookup-reference file | `File_18` supplies baseline values and verification tables. It does not locally re-prove every operator it tabulates. |
| Minimum baseline table state | `3899 BC`; `4199 BC`; `5279 BC`; `1661 BC` | minimum display rows | Baseline rows are forward-most table values. Variant rows are generated by stated operators rather than by silently altering the baseline. |
| Regular chronology state | begetting ages | historical / genealogical timeline | Use for MT, SP, and LXX begetting-age rows. Do not collapse with cumulative lifespan stacking. |
| Cumulative chronology state | lifespans added end-to-end | theological / schematic deep-time timeline | Use for §6 tables. Do not treat cumulative dates as ordinary historical birth dates unless a local dependency opens that node-class. |
| Literal Creation-week state | 7 days | literal Genesis 1 week | Converges with the figurative week at the displayed Creation endpoint. |
| Figurative Creation-week state | 7 years | day-year Creation-week | Converges with the literal week at the displayed endpoint. The Year-6 / Adam state remains distinct from the endpoint. |
| Creation endpoint state | `3899 BC`; `4114 BC`; `4174 BC`; `5279 BC`; related endpoints | Day 7 / Year 7 complete | Do not collapse Creation endpoint states with Year-6 / Adam states such as `3900 BC` or cumulative `14006 BC`. |
| MT Minimum-Regular state | `3899 BC`; `2243 BC`; `1661 BC` | forward-most MT regular baseline | Active in §2. No `+60 Terah` or `+215 Sojourn` is applied unless the section names it. |
| MT Standard-Normal / `+215 Sojourn` state | `4114 BC`; `2458 BC` by dependency | full-430 Egypt / normative MT state | Distinct from MT Minimum-Regular. `4114 BC` is not a correction of `3899 BC`; it is `3899 + 215`. |
| MT `+60 Terah` state | `3959 BC` from `3899 + 60` | Terah-only variant | Applies to Adam → Terah field where opened. Does not alter fixed Aaron-forward rows. |
| MT maximum / `+275` state | `4174 BC` from `3899 + 275` | combined `+60 Terah` and `+215 Sojourn` | Preserve the source's combined position while also preserving sequential `60 + 155 + 60` anatomy. |
| Epoch-boundary state | Adam → Terah; Abraham → Levi / Joseph; Aaron onward | variant-scope boundary | Abraham through Levi / Joseph admits two positions through the `±215` Sojourn fork. Terah opens the `+60 Terah` fork and doubles the field to four positions from Terah back to Adam in the normal no-2nd-Cainan table state. If restored 2nd Cainan is explicitly inserted, Terah through 2nd Cainan remains four-position, while Arphaxad / Flood through Adam becomes eight-position. Aaron onward is fixed. |
| Abraham → Levi / Joseph `±215` field | Abraham `1951/2166 BC`; Entry `1661/1876 BC`; Jacob / Joseph / Levi rows | Sojourn-position fork | Events from Levi / Joseph back to Abraham have two possible dates because of the `215`-year Sojourn variant. Do not apply `+60 Terah` until the Terah boundary. |
| Terah four-position field | Terah births `2021/2081/2236/2296 BC`; Terah deaths `1816/1876/2031/2091 BC`; Abraham births `1951/2166 BC` | `±215 × +60 Terah` hinge | Author-clarified. Abraham has two birth states, `1951 BC` and `2166 BC`. Terah has four birth/death states because `+60 Terah` doubles the Abraham field. Restored 2nd Cainan does not make 2nd Cainan itself eight-position; 2nd Cainan remains in the four-position Terah-to-Shelah field. The eight-position field begins with Arphaxad / Flood and propagates back to Adam only when restored 2nd Cainan is explicitly opened. |
| 2nd Cainan variant-boundary state | Shelah births `2481/2421 BC` and `2266/2206 BC`; 2nd Cainan births `2611/2551 BC` and `2396/2336 BC`; 2nd Cainan deaths `2151/2091 BC` and `1936/1876 BC` | restored regular 2nd Cainan boundary | Author-clarified. 2nd Cainan has four possible date states, like Terah. His father Arphaxad, whose birth is synonymous with the Flood / Ark-exit conception boundary, is the first row to absorb the additional restored-Cainan hinge and therefore becomes eight-position, with that eight-position state propagating back to Adam. |
| Multi-tradition Pentateuchal Funnel all-even structural harmony | Generation-count ladder `12 → 8 → 4 → 2`; possible-date ladder `8 → 4 → 2 → 0` when the Cainan hinge is active, whether restored in MT / SP or native / explicitly toggled in LXX | structural inference / Pentateuchal macro-architecture across MT, SP, and LXX | Author-clarified. The variant-boundary pattern is not merely a list of boundary lines and is not local to MT. MT, SP, and LXX 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 contains Cainan in the baseline and uses removal / expunction only as a theoretical state. The pattern maps onto Creation → Flood; Flood → Abraham; Abraham → Entry into Egypt; Egypt → Conquest / death of Moses. Claim-status: structural inference, with theological / providential significance available where the local argument opens it. |
| Restored/native 2nd Cainan 27-generation completion state | `12 + 8 + 4 + 2 + 1 = 27 = 3 × 3 × 3` | secondary generation-count completion / structural keystone | Author-clarified and pressure-tested. With restored 2nd Cainan opened in MT / SP, or native 2nd Cainan retained in LXX, the Pentateuchal generation count from Adam to Moses completes at `27`. This state is secondary to the primary `12–8–4–2–0` variant-count ladder and must not obscure the main 8-date / 4-date / 2-date / 0-date block logic. Without restored/native 2nd Cainan, the count drops to `26`, the 2nd Cainan → Terah block becomes `7` rather than `8`, and the all-even funnel no longer has the same structure. Claim-status: arithmetic fact for the count; structural inference for its architectural role. |
| Tebah / ark typological bridge state | Noah's ark; Moses' ark/basket; `8` souls; Moses as final deliverer | typological note / theological bridge | The Hebrew `tebah` ark motif links the Flood boundary and Moses narrative by typological correspondence. The `8`-generation post-Flood block and the `8` souls saved through Noah's ark provide a theological / typological explanation of the numeric structure, but do not carry the arithmetic burden. |
| `137 = 7 + 130` boundary checksum state | Adam → Seth; Flood / Arphaxad; Abraham / Sarah; Levi / Amram; Aaron terminal imprint where opened | boundary checksum / theological note | The value `137` may be read as `7 + 130`, joining the completion / Sabbath register to the mortal-line / curse-register. Treat the meaning as typological / theological support, not as a chronological operator. |
| Shem dual-`100` state | Noah-bound `100`; Arphaxad-bound `100` | Shem `±2` modal state | Shem is `100` at the Flood when bound to Noah's `500 → 600` chronology, and `100` at Arphaxad's birth when bound to Genesis 11:10. Both states are retained, analogous to Terah's `70/130` begetting-state display. |
| `16 × 8` expectation / cumulative-Cainan extension state | expected `16 × 8`; actual `12 × 8`; `4 × 138 = 552`; `4854/4856/4858 BC` | structural diagnostic / cumulative comparison | The visible funnel remains `12 × 8`; the idealized `16 × 8` expectation is a diagnostic only. The missing-four extension lands on the MT Cumulative + 2nd Cainan Cainan field when the restored regular Flood Gear rails are extended by `2208 = 16 × 138`. |
| Kenan / Cainan tenfold reinforcement state | 1Kenan `3921 BC`; son `3851 BC`; 2nd Cainan `2551 BC`; `1370 = 10 × 137`; Cainan lifespan-sum `910 + 460 = 1370`; `910 + 460 + 460 = 1830` | Cainan-sector support note | This state reinforces the `137` checksum at 10x scale. It supports the bounded File_18 amendment but does not open the full Cainan-sector branch. |
| Cainan macro-vector state | `4858–4851 BC`; `4398–4391 BC`; `2300`; `2520`; `2730`; `2307`; `1260 → 1290 → 1260` | File_16 dependency / Funnel support state | `File_18` supplies the table-source values and state controls. `File_16` controls the Nexus argument, Category B classification, and Bullseye Protocol use. |
| Cainan / Famine envelope-to-envelope state | `4398–4391 BC → 1878–1871 BC`; selected core `4396 BC → 1876 BC` | cumulative-to-historical envelope projection | Uses `2520 = 7 × 360` as a macro-prophetic projection by `File_16` dependency. This does not change the MT `430` Egypt state or make the cumulative Cainan death itself a regular-history event. |
| Cross-tradition 60-multiple Shelah / Plenty-Famine alignment state | MT `4398–4391 BC → 1878–1871 BC` by `60 × 42`; SP `4278–4271 BC → 1878–1871 BC` by `60 × 40`; LXX `4825–4818 BC → 1885–1878 BC` by `60 × 49` | table-source support / structural inference | `File_18` preserves the comparative source coordinates. `File_16` controls the Nexus interpretation. The common `60` factor is not a table-generation operator and does not collapse the Plenty window with the Famine window. |
| Mirror 60-spine / Terah-Cainan death-rail state | `1885n/1878n/1871n BC`; `1670n/1663n/1656n BC`; AD-side reversed mirror labels `AD 1656n/1663n/1670n`; `3540 = 60 × 59`; `1936n BC → 1876n BC → 1816n BC` | table-source support / Mirror corroboration | `File_18` preserves the date labels and arithmetic controls only. `File_16` controls the Nexus interpretation. The constant `3540` requires civil cross-axis arithmetic and reversed endpoint order on the AD side; it is not a table-generation operator. |
| Regular-Cainan `460` cross-modal symmetry state | `2551–2091 BC`; `2336–1876 BC` | regular restored 2nd Cainan lifespan members compared with cumulative `+460` | These are same-side 460-year regular spans. They may mirror the cumulative `+460` value, but they do not substitute cumulative lifespan insertion for the regular `+130` begetting-age operator. |
| Cainan triple-target matrix state | `2091 BC`; `1876 BC`; `1661 BC` | macro-vector alignment to Call / Super-Anchor / lower-bound Entry states | `2300`, `2520`, and `2730` point from the cumulative Cainan / Shelah field to three distinct target node-classes. The targets must remain state-labeled and non-collapsed. |
| Cainan-to-Exile Daniel 12 sandwich state | `4396 BC → 3136 BC → 1846 BC → 586 BC`; companion `1876 BC → 586 BC` | macro-prophetic witness by File_16 dependency | Classify as Category B / macro-prophetic witness. It does not turn `1846 BC` into Entry or `1876 BC` into Affliction start. |
| Cainan-sector branch-restraint state | `8970`; `9100`; `130 + 330`; `7800`; `2300`; `6900` by dependency | restraint / dependency-control state | Deeper Cainan-sector branches remain controlled by File_11, File_16, File_22, or later Cainan-sector files unless explicitly opened. |
| Fixed epoch state | Aaron birth; Moses birth; Exodus; Conquest | fixed post-variant anchor field | Values from Aaron onward are fixed unless another file explicitly opens a subordinate state. |
| `1876 BC` shared year-label state | `1876 BC` | Entry / Call / return / convergence year-label by dependency | In `File_18`, `1876 BC` may mark Entry under MT `430`, Abraham Call / Death of Terah under Sojourn-division paths, or another dependency-controlled convergence label. Do not collapse node-classes. |
| Primary Exodus state | `1446 BC` | primary Exodus anchor | Governs the tables unless a subordinate Ramesside state is explicitly opened by dependency. |
| Conquest / Moses-death state | `1406 BC` | Conquest / Moses endpoint anchor | Active in regular and cumulative tables. Do not collapse with Joshua death `1296 BC` in SP cumulative state. |
| Kings dual-ledger state | `966 BC`; `1016 BC`; `+50` | historical Temple ledger versus schematic Triple-`430` ledger | Preserve both ledger states in §2.5. `1016 BC` does not replace historical `966 BC`. |
| Fall of Jerusalem endpoint state | `586 BC` | Kings / exile endpoint | In `File_18`, `586 BC` remains the displayed endpoint unless another dependency opens adjacent `587/586 BC` date-states. |
| SP Normal / Toggle ON state | `4199 BC`; `2892 BC` | SP inclusive-reckoning state | Active through the Flood in §3. Treat `4199 BC` as SP Normal / Toggle ON, not as SP Ideal. |
| SP Ideal / Exclusive state | `4200 BC` | exclusive / harmonic companion | Mentioned by comparison. Does not replace the §3 baseline. |
| SP Toggle OFF / post-Flood state | `2991 BC`; `2891 BC`; post-Flood rows | post-Flood standard SP interval state | The Toggle ON antediluvian state stops at the Flood; post-Flood rows resume standard intervals. |
| SP Shem Superposition state | `2990/2991 BC`; `2390/2391 BC`; Noah's `600th year` read as either full `600` or inclusive `599+` | Shem bound to Noah and Arphaxad in different toggle states | Author-clarified. Preserve both toggle bindings. The inclusive SP reading may ripple backward toward Adam inside the antediluvian SP state, while the post-Flood Arphaxad-bound row does not inherit that backward ripple. |
| SP Terah dual-lock state | `145`; `205`; `2021 BC`; `1876 BC`; `1951 BC` | textual lifespan / architectural lifespan pair | Author-clarified. SP text gives Terah's official lifespan as `145`, landing death at Abram's call; the architectural `205` mirrors MT/LXX and shows that the same Terah problem remains as a swapped lifespan / begetting-age issue. In SP cumulative tables, `145` remains the official span. |
| BJ / Jubilees comparison state | `3856 BC`; `343`; 7 Jubilees | external comparative witness | Used as SP / BJ alignment witness. Do not turn BJ into the SP table itself. |
| LXX Regular-Minimum state | `5279 BC`; `3023 BC`; native 2nd Cainan | LXX regular comparison state | Active in §4. Smith is an external LXX reconstruction witness, not the source of the repository interpretation. |
| LXX corrected Lamech state | begetting age `182`; lifespan `753`; Flood `3023 BC` | LXX regular source-control state | Author-clarified. Use `182` for Lamech's begetting age and retain the LXX lifespan `753`; do not use Smith's `777` lifespan amendment in the File_18 LXX regular table. |
| LXX Terah / Abraham `2 × 2` variant field | Abraham `1951/2166 BC`; Terah `2021/2081/2236/2296 BC` | independent `+215 Sojourn` and `+60 Terah` variant field | Author-clarified. Abraham has two birth labels because the `+215 Sojourn` state applies from Levi / Joseph back to Abraham. Terah has four birth labels because `+60 Terah` activates at Terah and doubles that two-date field. If restored 2nd Cainan is inserted, 2nd Cainan remains four-position; the eight-position effect begins at Arphaxad / Flood and propagates backward to Adam. |
| LXX cumulative source-table state | `14896 BC`; `5745 BC`; Cainan `5280 BC`; Peleg `3856 BC`; Lamech `753`; Nahor `208` | cumulative LXX table state | Author-clarified. The LXX cumulative table and LXX regular table both use Lamech lifespan `753`; Nahor uses `208` where the corrected LXX source-table state is active. |
| Regular-localized Shem `±2` state | Noah / Shem only | local regular anomaly | Applies in regular chronology only. |
| Cumulative-propagated Shem `±2` state | `2 + 3 + 2`; 7-year margin | chain-wide cumulative anomaly | Generates cumulative envelopes; do not reduce to the regular-localized anomaly. |
| Regular restored 2nd Cainan state | `+130` | begetting-age insertion | Applies to regular MT/SP restoration only. LXX already includes Cainan. |
| Cumulative restored 2nd Cainan state | `+460` | lifespan insertion | Applies to cumulative MT/SP restoration only. Do not substitute `+130`. |
| LXX native 2nd Cainan state | LXX includes Cainan | native LXX baseline | No adjustment is applied in LXX regular or cumulative baseline. Theoretical LXX removal remains non-standard. |
| Theoretical LXX Cainan removal state | `5279 − 130 = 5149 BC` | theoretical removal / non-standard table state | Retained as architecturally valid but not tracked in standard tables. |
| MT cumulative Moses / Nisan trunk | `14006 BC`; `4831 BC`; `1526 BC` | primary cumulative trunk | Nisan / Spring line. |
| MT cumulative Aaron / Tishri trunk | `+3.5`; `.5` labels | secondary cumulative trunk | Tishri / Fall line. Preserve exact `.5` labels as display-state values. |
| Cumulative apparent birth / Year-6 +30 state | `14036 BC`; `14039.5 BC`; span `14041–14034 BC` | apparent-age cumulative overlay | Overlay only; does not replace the Adam Year-6 row. |
| Restored cumulative 2nd Cainan Flood Week | `5296–5289 BC`; `5291 BC` | restored cumulative Flood envelope | Controlled by §6B and `File_09` / `File_02` dependencies. |
| SP cumulative square state | `13398 BC`; `12100 = 110 × 110`; Joshua death `1296 BC` | SP cumulative square / Joshua target | Distinct from SP regular chronology and from MT cumulative trunk. |
| LXX cumulative / BJ Peleg state | `3856 BC` | LXX cumulative Peleg / BJ Creation correspondence | Comparative witness state; does not make BJ the LXX table. |
| MT cumulative Peleg phase-resolved Mirror state | `3501n–3494n BC`; parallel `3502t–3495t BC`; Mirror AD `1399t/1400n–1406t/1407n` | cumulative Peleg / Conquest Mirror coordinate-completion | Author-clarified. The Peleg envelope mirrors the Conquest / land-rest envelope by File_09 phase-resolved suffix inversion. Component spans equal `4900 = 70 × 70 = 100` Jubilees. |
| Sumerian A / SKL Short state | `2906 BC`; `20886 BC`; `452886 BC`; `17980` | primary SKL Short whole-year state | Preserve as Sumerian A / SKL Short. |
| Sumerian B / SKL Long state | `2856 BC`; `27366 BC`; `459366 BC`; `24510`; `+6480` | alternate SKL Long whole-year state | Preserve as Sumerian B / SKL Long. |
| SKL appended month/day datum state | `3 months and 3.5 days` | SKL textual-datum / dependency-controlled calendar detail | Retained as source datum. Whole-year local arithmetic remains separate unless `File_34` / `File_12` opens granular execution. |
| SKL `+30 Apparent Mode` state | `+30`; examples `2936/2886 BC` by dependency | apparent-age rail | Do not collapse with local `+2` or scaled `+720`. |
| SKL `+2 local rail` state | `+2`; examples `2908/2858 BC` by dependency | local fine-tuning rail | Local rail only. Not the same as `+720 scale-state`. |
| SKL `+720 scale-state` | `2 × 360`; examples `262086/262806 BC` | scaled Shem `±2` expression | Scale-state only. Distinct from local `+2`. |
| Precessional envelope / Berossus state | `6480`; `12960`; Berossus by `File_34` dependency | SKL / Berossus unification field | Preserved as dependency-controlled; §7 does not fully rederive it. |
| File_34 post-final dependency state | `2370`; `30 + 20 + 30`; `568/566 BC`; `538/536 BC`; `518/516 BC`; `488/486 BC` | post-final SKL / Berossus citation-control state | `File_18` may register these as File_34-controlled dependency labels. It does not rederive the corridor or change local SKL table rows. |
| Same-side BC span state | higher BC minus lower BC | same-axis chronology span | Main arithmetic display in §8. Arithmetic verification is recorded in §0.8 and §8. |
| Civil cross-axis span state | `BC + AD − 1` | BC/AD span | Active where AD targets are opened, including the author-clarified MT cumulative Peleg / Conquest Mirror component checks. |
| Residue / conceptual residual-display state | `300/299`; legacy `299/300`; `365.24`; `365.2422`; `7.5 days`; physical `299/40 = 7.475 days` | Enochian ratio / residue-control field | Author-clarified. File_17 controls the exact `300/299` operator, File_12 controls legacy `299/300` wording and true-solar display, and File_11 controls physical-residue versus conceptual residual-display language. |
| Providential multi-tradition system state | MT; SP; LXX; BJ / Jubilees; SKL; Berossus | interpretive synthesis state | Preserve distinct textual / chronological witness states. Do not overstate demonstrable scribal intent. |
| Formal Mirror state | not active in main `File_18` table source | inactive protocol | Mirror / inverse material remains dependency-controlled unless explicitly opened by a later pass or file. |

### 0.1a Node-class and display-state register

| Date / value / display | Node-class | Active state | Do not collapse with |
|---|---|---|---|
| `3899 BC` | Creation endpoint / Adam table baseline | MT Minimum-Regular | MT Standard-Normal `4114 BC`; Year-6 `3900 BC`; cumulative Adam `14006 BC` |
| `3906–3899 BC` | figurative Creation-week wrapper | MT Minimum-Regular | literal seven-day Creation week by itself |
| `3900 BC` | figurative Year-6 / Adam-as-year display | MT Minimum-Regular | endpoint `3899 BC` |
| `4114 BC` | Creation endpoint under `+215 Sojourn` | MT Standard-Normal | `3899 BC`; Year-6 anchors in `File_07`; rounded MT `4106 BC` |
| `3959 BC` | Terah-only Creation endpoint | MT `+60 Terah` | `3899 BC`; `4114 BC`; `4174 BC` |
| `4174 BC` | maximum Creation endpoint | MT `+275` | Year-6 `4176 BC`; LXX Maximum node-labels in `File_14` |
| `4199 BC` | SP Normal Creation endpoint | SP Normal / Toggle ON | SP Ideal `4200 BC`; MT `3899 BC` |
| `4206–4199 BC` | SP Creation-week wrapper | SP Normal / Toggle ON | SP Ideal wrapper if separately opened |
| `2990/2991 BC` | Shem superposed birth labels | SP Shem Superposition | ordinary regular-localized `±2` labels unless the toggle binding is named |
| `5279 BC` | LXX Creation endpoint | LXX Regular-Minimum | File_13 LXX actual `5494 BC`; File_54 rounded `5486 BC` |
| `5286–5279 BC` | LXX Creation-week wrapper | LXX Regular-Minimum | LXX cumulative Adam `14896 BC` |
| `3023 BC` | LXX Regular-Minimum Flood | LXX corrected Lamech state | LXX cumulative Flood `5745 BC` |
| `1661 BC` | minimum Entry into Egypt | minimum / Sojourn-division state | `1876 BC` shared year-label; `1843 BC` LXX `33 + 397` by dependency |
| `1876 BC` | shared year-label | Entry / Call / convergence by active state | a single event-node |
| `1446 BC` | primary Exodus anchor | fixed epoch | subordinate `1231 BC` Ramesside state by dependency |
| `1406 BC` | Conquest / Moses death | fixed epoch and cumulative anchor | Joshua death `1296 BC` in SP cumulative state |
| `966 BC` | historical Temple foundation | Kings dual-ledger | schematic `1016 BC` |
| `1016 BC` | schematic Triple-`430` Temple pivot | Kings dual-ledger | historical `966 BC` |
| `586 BC` | Fall of Jerusalem endpoint | Kings / Triple-`430` endpoint | adjacent `587/586 BC` states unless opened by dependency |
| `14006 BC` | MT cumulative Adam / Year-6 center | cumulative Moses / Nisan trunk | regular MT Creation endpoint `3899 BC`; apparent `14036 BC` |
| `14009.5 BC` | MT cumulative Adam on Aaron / Tishri trunk | cumulative Aaron line | integer Moses line `14006 BC` |
| `14011–14004 BC` | MT cumulative Adam envelope | cumulative 7-year span | one single date |
| `14036 BC` | cumulative apparent birth | Year-6 +30 overlay | Adam Year-6 `14006 BC` |
| `4831 BC` | MT cumulative Flood / Arphaxad table label | cumulative MT | regular Flood rows `2243 BC`, `2892 BC`, `3023 BC` |
| `5291 BC` | restored cumulative Cainan Flood / Arphaxad label | cumulative restored 2nd Cainan | regular restored Cainan `+130` state |
| `5296–5289 BC` | restored cumulative 2nd Cainan Flood Week | cumulative envelope | LXX Creation endpoint `5279 BC`; LXX cumulative Cainan `5280 BC` |
| `4858–4851 BC` | MT Cumulative + 2nd Cainan Cainan envelope | cumulative restored 2nd Cainan | regular restored Cainan `+130`; LXX cumulative Cainan `5280 BC` |
| `4856 BC` | rounded / control coordinate inside the cumulative Cainan field | `16 × 8` expectation / cumulative-Cainan extension state | ordinary regular Cainan birth rows; Protocol 1 Mirror targets |
| `4398–4391 BC` | extended death-window / Shelah convergence envelope | cumulative restored 2nd Cainan; Cainan / Famine envelope-to-envelope state | ordinary regular death rows; the `1878–1871 BC` Famine window unless the `2520` projection is active |
| `4278–4271 BC` | SP cumulative Shelah envelope | cross-tradition 60-multiple Shelah / Plenty-Famine alignment state | MT Cainan / Shelah envelope; LXX Shelah envelope; inactive unless SP cumulative comparison is opened |
| `4825–4818 BC` | LXX cumulative Shelah envelope | cross-tradition 60-multiple Shelah / Plenty-Famine alignment state | MT and SP Shelah envelopes; inactive unless LXX cumulative comparison is opened |
| `1885–1878 BC` | seven years of Plenty | Joseph / Plenty target window by File_16 dependency | Famine window `1878–1871 BC`; the shared `1878 BC` boundary must not collapse Plenty and Famine into one event |
| `1670/1663/1656 BC` | `−215` companion triad to the Plenty / Famine labels | Mirror 60-spine / Terah-Cainan death-rail state | AD-side Mirror labels `AD 1656/1663/1670`; same-order pairing if the constant `3540` is being asserted |
| `1936n BC → 1876n BC → 1816n BC` | Terah / regular restored 2nd Cainan death-date rail | Mirror 60-spine / Terah-Cainan death-rail state | a single event-node or identity of Terah and Cainan |
| `4396 BC` | Cainan death-window member | cumulative restored 2nd Cainan / File_16 dependency | ordinary regular Cainan death rows unless the cumulative state is active |
| `4391 BC` | lower member of the extended Cainan / Shelah convergence envelope | cumulative restored 2nd Cainan; Daniel 8 / Enochian lower-bound comparison by dependency | regular death at `2091 BC`; minimum Entry `1661 BC`; do not collapse without active vector operator |
| `2551–2091 BC` | regular restored 2nd Cainan lifespan member | regular restored 2nd Cainan; `2300` Cainan vector | cumulative Cainan envelope `4858–4851 BC`; the `2336–1876 BC` minimum-span member |
| `2336–1876 BC` | regular restored 2nd Cainan minimum lifespan member | regular-Cainan `460` cross-modal symmetry state | MT Entry node-class at `1876 BC`; cumulative `+460` operator; Cainan death-window state |
| `3921 BC`; `3011 BC`; `2551 BC` | 1Kenan birth, 1Kenan death, and restored 2nd Cainan birth by dependency | Kenan / Cainan tenfold reinforcement state | ordinary MT Minimum-Regular Kenan row unless Gear 3 / restored Cainan is active |
| `6306 BC` | LXX missing-four extension coordinate | LXX Maximum node-label comparison state | LXX Regular-Minimum Creation `5279 BC`; LXX cumulative Adam `14896 BC` |
| `14466 BC` | MT cumulative Adam with restored Cainan | cumulative `+460` | regular restored Cainan `4029 BC`; `1446 BC` Exodus label resemblance |
| `13398 BC` | SP cumulative Adam | SP cumulative square state | SP regular Creation `4199 BC` |
| `1296 BC` | SP Joshua death target | SP cumulative state | Conquest / Moses-death anchor `1406 BC` |
| `14896 BC` | LXX cumulative Adam | LXX cumulative source-table state | LXX regular Creation endpoint `5279 BC` |
| `3856 BC` | LXX cumulative Peleg / BJ Creation correspondence | LXX cumulative / BJ comparative state | LXX regular Peleg; BJ table itself |
| `2906 BC` | Tower / SKL Short base | Sumerian A / SKL Short | SKL Long `2856 BC`; local `+2`; `+30`; `+720` states |
| `2856 BC` | Tower / SKL Long base | Sumerian B / SKL Long | SKL Short `2906 BC` |
| `20886 BC` | SKL Short Flood | Sumerian A / SKL Short | cumulative Floods; SKL Long `27366 BC` |
| `27366 BC` | SKL Long Flood | Sumerian B / SKL Long | SKL Short `20886 BC` |
| `452886 BC` | SKL Short Pre-Creation | Sumerian A / SKL Short | SKL Long Pre-Creation `459366 BC`; +720 rail by dependency |
| `459366 BC` | SKL Long Pre-Creation | Sumerian B / SKL Long | SKL Short Pre-Creation `452886 BC` |
| `262086/262806 BC` | Adam / Alulim rail pair | SKL `+720 scale-state` | local `+2` rail or regular Adam rows |

### 0.1b Operator and sign-convention register

| Operator or sign convention | Active form | Scope in `File_18` | Guard |
|---|---|---|---|
| Same-side BC subtraction | higher BC date minus lower BC date | §8 and visible verification rows | Main arithmetic display; locally executable visible rows check under stated operators. |
| Civil cross-axis span | `BC + AD − 1` | Only where AD targets are opened | Not Mirror protocol and not inverse-number logic. |
| `+60 Terah` | add 60 years backward beginning at Terah | regular variant matrix | Doubles the Abraham `±215` field from two states to four states at Terah and then propagates back toward Adam. Does not affect the Abraham → Levi / Joseph field before Terah or the Aaron-forward fixed epoch. |
| `+215 Sojourn` | add 215 years backward where full 430 Egypt position is opened | variant matrix and Entry field | Distinct from Exodus 215 / subordinate Ramesside shift. |
| `+275` | `+60 + 215`; also sequential `60 + 155 + 60` display | four-position variant matrix | Preserve both combined and sequential displays. |
| `±215` | Sojourn-position fork | Abraham → Levi / Joseph field | Produces two date states for Abraham through Levi / Joseph. Not a generic global adjustment and not identical to `+60 Terah`. |
| Shem `±2` | localized in regular; propagated in cumulative | Noah / Shem; cumulative envelope | Must name active mode before applying. |
| SP Toggle ON | inclusive reckoning through Flood | SP regular antediluvian table | Stops at Flood; post-Flood resumes standard intervals. |
| Regular restored 2nd Cainan | `+130` | regular MT/SP restoration | Begetting-age insertion only. |
| Cumulative restored 2nd Cainan | `+460` | cumulative MT/SP restoration | Lifespan insertion only. |
| `137` checksum | `7 + 130` | boundary checksum where completion and patriarchal `130` states are both opened | Diagnostic only; not a new chronological operator. |
| `138` proportional unit | `1656 ÷ 12 = 138` | `16 × 8` expectation diagnostic | Arithmetic diagnostic only; do not replace the actual `12–8–4–2–0` table-source pattern. |
| Missing-four extension | `4 × 138 = 552` | proportional pre-Adamic extension | Structural diagnostic; does not add four patriarchs. |
| Completed extension | `16 × 138 = 2208` | extension from restored regular Flood Gear rails to cumulative Cainan field | Same-side BC extension only. |
| Cainan-to-Moses lock | `4856 − 1406 = 3450 = 138 × 25` | cumulative Cainan to Moses-death / Conquest terminus | Same-side BC subtraction; not Mirror protocol. |
| Cainan / Famine `2520` projection | `4398/4396/4391 BC − 2520 = 1878/1876/1871 BC` | cumulative Cainan / Shelah envelope to Famine window by `File_16` dependency | Category B pattern-vector witness only; not an alteration of the MT `430` Egypt state. |
| Cross-tradition Shelah `60`-multiple comparison | MT `2520 = 60 × 42`; SP `2400 = 60 × 40`; LXX `2940 = 60 × 49 = 6 × 490` | comparative Shelah-envelope support in §1.3.8 and §6B note | Structural inference / providential synchronization only. MT and SP target the Famine window; LXX targets the Plenty window. Do not collapse target windows or add Category A event nodes. |
| Mirror 60-spine companion | `3540 = 60 × 59`; `3540 + 2400 = 5940 = 60 × 99`; `3540 + 2520 = 6060 = 60 × 101`; `3540 + 2940 = 6480 = 60 × 108` | Mirror companion to cross-tradition Shelah `60`-multiple comparison | Civil cross-axis arithmetic only where AD targets are explicitly opened. The `3540` component requires reversed AD-side endpoint order: `1885 ↔ AD 1656`, `1878 ↔ AD 1663`, `1871 ↔ AD 1670`. Not a table-generation operator. |
| Cainan Daniel 8 `2300` vector | `4851 − 2300 = 2551`; `4391 − 2300 = 2091` | cumulative Cainan envelope to regular restored Cainan lifespan member | Same-side BC subtraction; `2300` does not replace regular `+130` or cumulative `+460`. |
| Inclusive companion `2307` | `4858 − 2551 = 2307`; `4398 − 2091 = 2307` | sanctuary / Hanukkah-style inclusive companion where later dependency opens it | Retained as exploratory / audit companion. It is not promoted to a File_18 operator. |
| Enochian lower-bound `2730` vector | `4391 − 1661 = 2730`; `2730 = 7.5 × 364` | cumulative envelope to minimum Entry lower-bound where EnvSpread / Enochian state is active | Dependency-controlled by File_12 / File_17 / File_16. The solar companion remains audit-controlled. |
| Daniel 12 sandwich | `1260 → 1290 → 1260`; total `3810` | Cainan-to-Exile macro-prophetic witness by File_16 dependency | Same-side BC subtraction; Category B macro-prophetic witness, not a table-generation operator. |
| Kenan / Cainan tenfold relation | `1370 = 10 × 137`; `1370 − 460 = 910`; `910 + 460 = 1370` | Cainan-sector support note | Dependency-controlled by Gear 3 / restored-Cainan state. |
| Aaron/Moses phase offset | `+3.5` | cumulative Aaron / Tishri line | Exact display state; not rounded to `3` or `4`. |
| Apparent age overlay | `+30` | cumulative and SKL apparent modes | Overlay only unless a local section says it propagates. |
| SKL scale | `360:1` | Sumerian Integration | Scale-state; do not use as ordinary biblical-year chronology. |
| SKL `+6480` | variant tier separation | SKL Short / Long and Berossus relation | Full derivation controlled by `File_34`. |
| SKL `+720` | `2 × 360` | scaled Shem `±2` state | Distinct from local `+2`. |
| SKL local `+2` | literal-year local rail | SKL Tower / anchor fine-tuning | Distinct from scaled `+720`. |
| `25/23`; `70/69`; `300/299` | exact-rational operators by dependency | Key-of-23, prophetic, Enochian contexts | Do not decimalize or invert without naming the active state. |
| Residue Protocol | physical / residual display only where opened | 299/300 residue audit line | Not ordinary Key-of-23 whole-year conversion. |
| Kings `+50` Jubilee Offset | `1016 − 966 = 50` by dependency | Kings dual-ledger state | Does not change historical `966 BC`. |

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

| Form | Type | Active state | Handling |
|---|---|---|---|
| `3906–3899 BC`; `4206–4199 BC`; `5286–5279 BC` | Creation-week wrapper ranges | regular Creation endpoint states | Ranges / blocks, not single anchors. |
| `70/130` | Terah begetting-age slash-pair | MT regular table | Ordered source display for Terah's dual begetting logic; not a range. |
| `2990/2991 BC`; `2390/2391 BC` | SP Shem superposed slash-pair | SP Shem Superposition | Two toggle-bound labels, not an average or correction. |
| `145 (205)` | SP Terah lifespan pair | SP Terah dual-lock | Textual / architectural pair; preserve both. |
| `.5` labels | half-year display | Aaron / Tishri cumulative track | Exact display states; do not floor unless a display operator is named. |
| `14011–14004 BC`; `4836–4829 BC`; `5296–5289 BC` | cumulative 7-year envelopes | cumulative MT / restored Cainan | Envelopes with internal members; not one date. |
| `4716–4709 BC`; `14901–14894 BC` | cumulative comparison envelopes | SP / LXX cumulative | Preserve as table envelopes. |
| `1878–1871 BC` by dependency | famine-window envelope | File_16 dependency | Not locally tabulated as a main File_18 anchor unless opened by dependency. |
| `4398–4391 BC → 1878–1871 BC` by dependency | projected envelope-to-envelope relation | Cainan / Famine macro-vector state | Uses `2520`; component labels must remain distinct and non-collapsed. |
| `971/970 BC`; `587/586 BC`; `967/966 BC` by dependency | adjacent date-state slash-pairs | Kings / File_08 / File_14 dependencies | Preserve as adjacent states if opened; File_18's local table uses `966 BC` and `586 BC`. |
| `2906/2856 BC`; `20886/27366 BC`; `452886/459366 BC` | SKL Short / Long paired states | Sumerian A / B | Paired states, not ordinary uncertainty ranges. |
| `262086/262806 BC` | SKL +720 rail pair | scaled Shem `±2` | Scale-state pair, not local `±2`. |
| `3658/3656/3608/3606 BC` | SKL fine-tuning display cluster | +720 / +30 / +2 dependency field | Source-retained display cluster; full derivation remains `File_34`-controlled. |
| `599–600` | inclusive reading range | SP Noah / Flood display | Source-history website adjustment state; do not force one member in this file. |
| `3 months and 3.5 days` | SKL textual-datum display | Sumerian B / SKL Long dependency | Month/day datum is preserved separately from whole-year local arithmetic. |

### 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. The SP Toggle ON state is antediluvian through the Flood. The SP post-Flood rows resume standard intervals. Shem may occupy both toggle bindings in the SP Shem Superposition state.
11. The LXX Regular-Minimum corrected Lamech state and the LXX cumulative source-table state are now author-clarified to use Lamech lifespan `753`. Lamech's begetting age remains `182`; Smith's `777` lifespan amendment is source-history support only and is not adopted in the File_18 LXX table.
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`, `+2 local rail`, `+720 scale-state`, and `+6480` variant-tier logic must remain distinct.
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.

### 0.2 File map

| Section | Function | Active state / operator |
|---|---|---|
| §0 | File-function, audited modal-state register, current amendment hierarchy, node-class / display-state register, operator register, File map, terminology controls, Machine Guards, source-control notes, and argument controls | file-level controls; non-collapse guards; claim-status controls |
| §0A | Fractal Self-Constraint Principle | vertical scale-state / multi-witness framework |
| §1 | Variant mechanism, Pentateuchal Funnel, `137` checksum, bounded cumulative-Cainan extension, and Cainan macro-vector controls | `+60 Terah`; `+215 Sojourn`; `+275`; Shem `±2`; Cainan `+130` / `+460`; `137 = 7 + 130`; `16 × 8` diagnostic; `4 × 138 = 552`; `2300`; `2520`; `2730`; Pentateuchal Funnel state; File_16 dependency |
| §2 | MT Regular baseline | MT Minimum-Regular; Kings dual-ledger dependency |
| §3 | SP Regular baseline | SP Normal / Toggle ON; SP Ideal / Exclusive; Shem Superposition |
| §4 | LXX Regular baseline | LXX Regular-Minimum; Smith source-reconstruction witness; native 2nd Cainan; Abraham / Terah `2 × 2` variant field |
| §5 | Source-numbering note | supplied source has no Section 5 |
| §6 | Cumulative chronology matrix | cumulative MT; cumulative 2nd Cainan; SP cumulative; LXX cumulative |
| §7 | SKL Integration | Sumerian A / SKL Short; Sumerian B / SKL Long; `+6480`; `+720`; `+30`; `+2`; File_21 application controls |
| §8 | Arithmetic verification table and argument-control notes | same-side BC subtraction; exact spans checked where locally executable; claim-status controls |
| §9 | Cross-reference index | dependency tracking |
| Appendix A | Website table adjustments | source-history conversion notes |
| Audit notes | Retains unresolved dependency and audit controls | audit notes; dependency boundaries |
| Unresolved issues | Lists retained non-blocking controls | source-history and dependency controls |


### 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.

| Layer | Material | Claim-status / state | Handling |
|---|---|---|---|
| Primary table-source layer | Regular, cumulative, and SKL baseline tables | Governing table-source layer | Baseline rows remain the controlling data source. Variants require named operators. |
| Primary variant-count layer | `12–8–4–2–0` ladder and `8–4–2–0` possible-date countdown | Governing structural layer when restored/native 2nd Cainan is active | Controls the Pentateuchal Funnel and variant-date countdown. |
| Secondary completion layer | `12 + 8 + 4 + 2 + 1 = 27 = 3 × 3 × 3` | Arithmetic fact when restored/native 2nd Cainan is active; structural inference for its architectural role | Must not obscure the primary `12–8–4–2–0` table mechanics. |
| Typological bridge | Noah / Moses `tebah`; `8` souls; Moses as final deliverer | Typological / theological note | Explains meaning but does not create a chronological operator. |
| Diagnostic checksum layer | `137 = 7 + 130`; Shem dual-`100`; `16 × 8`; `4 × 138 = 552`; `16 × 138 = 2208` | Structural diagnostic / providential synchronization where invoked | Does not alter the genealogy, does not add four patriarchs, and does not replace the visible `12 × 8` pattern. |
| Cainan-sector reinforcement | 1Kenan / 2nd Cainan `1370 = 10 × 137`; `910 + 460 = 1370` | Structural reinforcement | Supports the bounded File_18 amendment only; deeper Cainan-sector branches remain dependency-controlled. |
| Cainan macro-vector layer | `2300`; `2520`; `2730`; `2307`; `1260 → 1290 → 1260` from the cumulative Cainan / Shelah field | Category B macro-prophetic witness by File_16 dependency | Supports the Pentateuchal Funnel / 1876 BC Nexus relation. It does not alter table rows, variant-count mechanics, or Cainan `+130` / `+460` operators. |

### 0.3 Terminology controls

| Source form | Public-clean handling |
|---|---|
| `FILE_18`; `FILE_00`; etc. | Normalized to `File_18`, `File_00`, etc. |
| `MT Minimum`; `MT min` | Normalized where needed to `MT Minimum-Regular`; source-history wording retained where the source explicitly explains legacy usage. |
| `MT Standard`; `MT +215` | Normalized where needed to `MT Standard-Normal / +215 Sojourn`. |
| `Terah +60` | Normalized to `+60 Terah`. |
| `Sojourn +215` | Normalized to `+215 Sojourn`. |
| `Regular (Short)` | Preserved as Regular chronology with Short as legacy term. |
| `Cumulative (Long)` | Preserved as Cumulative chronology with Long as legacy term. |
| `SP Normal`; `Toggle ON` | Preserved as `SP Normal / Toggle ON`. |
| `SP Ideal`; exclusive reckoning | Preserved as `SP Ideal / Exclusive`. |
| `LXX Minimum` | Normalized to `LXX Regular-Minimum`. |
| `Sumerian`, primary rail | Normalized to `Sumerian A / SKL Short` where the 17980-year state is active. |
| `Sumerian`, +6480 rail | Normalized to `Sumerian B / SKL Long` where the 24510-year state is active. |
| `±30`; `±2`; `+720` in SKL | Labeled as `+30 Apparent Mode`, `+2 local rail`, and `+720 scale-state` where needed. |
| Comma-form numbers | Normalized to no-comma format, e.g. `6480`, `14466`, `453600`. |

### 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, Shem `±2` is localized to Noah / Shem. In Cumulative chronology, the same anomaly propagates through the cumulative chain and creates the 7-year margin. Do not treat the regular-localized and cumulative-propagated states as one mechanism.

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 SKL RAILS]:

Sumerian A / SKL Short, Sumerian B / SKL Long, `+30 Apparent Mode`, `+2 local rail`, and `+720 scale-state` are distinct states. The local `+2` rail is not the same operation as the scaled `+720` state.

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 TOGGLE / SHEM]:

SP Normal / Toggle ON governs the antediluvian SP state through the Flood, but the Noah `600th year` datum may be read as either full `600` or inclusive `599+`. The SP primarily preserves the inclusive option while retaining the round `600` for schematic purposes. This allowance can ripple backward toward Adam inside the SP antediluvian state, but it does not propagate forward beyond the Arphaxad-bound post-Flood row. Shem may legitimately appear as `2990/2991 BC` and `2390/2391 BC` because he is bound to Noah and Arphaxad by different toggle states.

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 LXX Regular-Minimum table and the LXX cumulative table are separate source-table states, but the author has clarified that both use Lamech lifespan `753`, not `777`. Lamech's begetting age is `182`, not `188`, in the active File_18 LXX table. Nahor uses `208` where the corrected LXX source-table state is active. Do not reinsert Smith's `777` lifespan amendment as the table value.

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:

| Scale | Expression |
|---|---:|
| Historical scale | 720 days = 2 years |
| Cosmic scale | 720 years |
| Ultra-cosmic scale | 259200 years = `720 × 360` |
| Fine-tuning layer | `±2` at every scale, e.g. `2886/2888 BC`, `3606/3608 BC` |

### 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.

| Position | Applied variants | Gap from previous | Example, MT Adam |
|---|---|---:|---:|
| Minimum | Neither | — | 3899 BC |
| `+60` only | `+60 Terah` | +60 | 3959 BC |
| `+215` only | `+215 Sojourn` | +155 | 4114 BC |
| Maximum | Both `+60 Terah` and `+215 Sojourn` | +60 | 4174 BC |

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.

| Gap vector | Literal gap | Harmonic goal | Resolution mechanism |
|---|---:|---:|---|
| MT → SP | 301 years | 300 years | Spider Gear `299 → 300`: the gap between SP `4200 BC` and MT Gear 2 `3901 BC` is 299 years. This converts to 300 Enochian years through the Key of 23. |
| SP → LXX | 1079 years | 1080 years | Reckoning differential: `1079` exclusive → `1080` inclusive. This matches the `3 × 360` prophetic cycle. |
| MT → LXX | 1380 years | 1380 years | Invariant total: `301 + 1079 = 1380 = 3 × 460`. |

#### 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:

```markdown
(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.

| Tier | Subsections | Function |
|---|---|---|
| Primary epoch boundary | §1.3 overview | Establishes where variants begin and stop. |
| Primary variant mechanics | §§1.3.1–1.3.2 | Abraham / Terah / 2nd Cainan boundary and Pentateuchal Funnel. |
| Secondary completion | §1.3.3 | 27-generation completion and tebah / ark typological bridge. |
| Diagnostic checksum and extension | §§1.3.4–1.3.6 | `137`, Shem dual-`100`, `16 × 8`, and cumulative-Cainan extension. |
| Reinforcement and restraint | §1.3.7 | 1Kenan / 2nd Cainan tenfold reinforcement; branch restraint retained. |
| Macro-vector dependency layer | §1.3.8 | Cumulative Cainan / Shelah envelope used as File_16 source field for `2300`, `2520`, `2730`, and Daniel 12 sandwich vectors. |

Primary epoch map:

| Epoch | Date range | Variants | Mechanism |
|---|---|---:|---|
| Adam → Terah's death | Creation to approximately 1816 BC | 4 in the no-2nd-Cainan table state; 8 upstream from Arphaxad / Flood where restored/native 2nd Cainan is active | Full `60 + 155 + 60` matrix; Cainan hinge where named. |
| Abraham → Levi / Joseph | 1951–1567 BC, minimum | 2 | `±215` only. |
| Aaron's birth onward | 1529 BC → | 1 | Fixed; no variants. |

#### 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.

| Epoch / boundary | Active variants | Possible explicit date states | Handling |
|---|---|---:|---|
| Adam → Arphaxad / Flood | `±215 Sojourn × +60 Terah × restored 2nd Cainan` where opened | eight states | Active only if restored 2nd Cainan is explicitly inserted. Arphaxad is synonymous with the Flood / Ark-exit conception boundary and is the first upstream row to absorb the Cainan hinge. |
| 2nd Cainan → Terah | `±215 Sojourn × +60 Terah` | four states | 2nd Cainan, Shelah, Eber, Peleg, Reu, Serug, Nahor, and Terah remain four-position. |
| Abraham → Joseph / Levi | `±215 Sojourn` only | two states | Abraham birth `1951/2166 BC`. |
| Kohath → Amram | no direct regular-date anchor | zero explicit pivot states | These generations float inside the Sojourn envelope because the repository uses the global `430/215` spans rather than daisy-chaining overlapping lifespans. |
| Aaron / Moses onward | none in this table | fixed anchors | Fixed anchors such as `1446 BC` and `1406 BC`; Aaron / Moses are unaffected by the regular Abraham / Terah / 2nd Cainan variant multiplication. |

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

| Shelah birth state | 2nd Cainan birth | 2nd Cainan death | Active variant-state |
|---:|---:|---:|---|
| 2481 BC | 2611 BC | 2151 BC | `+275`; `+60 Terah` and `+215 Sojourn` active |
| 2421 BC | 2551 BC | 2091 BC | `+215 Sojourn` active; no `+60 Terah` |
| 2266 BC | 2396 BC | 1936 BC | `+60 Terah` active; minimum Sojourn state |
| 2206 BC | 2336 BC | 1876 BC | minimum; no `+60 Terah`; no `+215 Sojourn` |

Terah begetting-age display:

| Terah state | Birth / death | Begetting state | Abraham birth produced |
|---|---|---:|---:|
| Minimum, no `+60`, no `+215` | `2021–1816 BC` | 70 | 1951 BC |
| `+60 Terah`, no `+215` | `2081–1876 BC` | 130 | 1951 BC |
| `+215 Sojourn`, no `+60` | `2236–2031 BC` | 70 | 2166 BC |
| `+275`, both variants | `2296–2091 BC` | 130 | 2166 BC |

#### 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.

| Pentateuchal arc | Generational block | Variant-date field | Active hinges |
|---|---|---|---|
| Creation → Flood | Adam through Arphaxad / Flood, 12 generations inclusive | 8 possible dates per patriarch / event where the Cainan hinge is active | Sojourn `±215`; `+60 Terah`; 2nd Cainan `+130`, restored in MT / SP and native or theoretically toggled in LXX |
| Flood → Abraham | 2nd Cainan through Terah, 8 generations inclusive | 4 possible dates per patriarch | Sojourn `±215`; `+60 Terah` |
| Abraham → Entry into Egypt | Abraham, Isaac, Jacob, Joseph / Levi, 4 patriarchal nodes | 2 possible dates per patriarchal node | Sojourn `±215` only |
| Egypt → Conquest / Moses death | Kohath and Amram as 2 floating gap generations; Aaron / Moses fixed downstream | 0 direct regular pivot dates for Kohath / Amram | global Sojourn envelope; fixed `1446 BC` Exodus and `1406 BC` Conquest / Moses-death anchors |

Tradition-specific handling:

| Tradition | Fork sequence location | Cainan-state handling | Guard |
|---|---|---|---|
| MT | Sojourn / Egypt-position `+215`; `+60 Terah`; restored 2nd Cainan `+130` | Cainan is absent from the ordinary MT baseline and is inserted only when restored 2nd Cainan is explicitly opened. | Do not treat the restored state as the ordinary MT baseline. |
| SP | Sojourn / Egypt-position `+215`; `+60 Terah`; restored 2nd Cainan `+130` | Cainan is absent from the ordinary SP baseline and is inserted only when restored 2nd Cainan is explicitly opened. | Preserve SP Terah `145 (205)` and SP Shem Superposition as distinct local states. |
| LXX | Sojourn / Egypt-position `+215`; `+60 Terah`; native 2nd Cainan `+130` boundary | Cainan is already present in the LXX baseline. The fork is structural / boundary-based unless theoretical Cainan removal is explicitly opened. | Do not add `+130` to active LXX baseline rows. |

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.

| Structural block | Count | Function in the funnel | Typological / narrative note |
|---|---:|---|---|
| Adam → Arphaxad / Flood | 12 | Primeval root block; first block with eight possible date states when the Cainan hinge is active | Culminates in the Flood / ark boundary. |
| 2nd Cainan → Terah | 8 | Post-Flood block with four possible date states | The count `8` corresponds typologically to the eight souls saved through Noah's ark. |
| Abraham → Joseph / Levi | 4 | Patriarchal block with two possible date states | The family-stage patriarchal arc narrows toward Egypt. |
| Kohath → Amram | 2 | Floating Egypt block with zero direct regular pivot dates | The generations float inside the global Sojourn envelope. |
| Moses | 1 | Final deliverer generation; fixed downstream anchor field | Moses is the second major `tebah` / ark figure by typological correspondence. |

Arithmetic fact:

```markdown
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:

```markdown
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.

| Boundary | Active state | Expression | Claim-status |
|---|---|---:|---|
| Adam → Seth | seven-year Creation-week wrapper plus Adam's begetting age | `7 + 130 = 137` | arithmetic fact under Creation-week state |
| Flood / Arphaxad boundary, MT | Noah-bound Shem `100`; Arphaxad born two years after Flood; Arphaxad begets at `35` | `100 + 2 + 35 = 137` | conditional arithmetic fact |
| Flood / native Cainan boundary, LXX | LXX native 2nd Cainan state | `2 + 135 = 137` | arithmetic fact under LXX source-table state |
| Abraham / Sarah | Sarah-Eve typological boundary | Sarah lifespan `127`; Abraham is 10 years older; `127 + 10 = 137` | arithmetic fact; typological note |
| Ishmael | Abrahamic side witness | lifespan `137` | collateral arithmetic witness |
| Levi | end of Abraham → Entry block | lifespan `137` | arithmetic fact |
| Levi / Kohath / Amram | hidden Egypt-era generations | Levi `137`; Kohath `133`; Amram `137` | arithmetic fact; structural frame |

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:

```markdown
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.

| Shem state | Textual basis | Meaning | Handling |
|---|---|---|---|
| Noah-bound / Flood-bound `100` | Noah is `500` when Shem is born; Noah is `600` at the Flood | Shem is `100` at the Flood | Valid harmonic / structural state |
| Arphaxad-bound / text-bound `100` | Genesis 11:10: Shem is `100` when he begets Arphaxad two years after the Flood | Shem is `100` at Arphaxad's birth | Valid textual state |

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` hinge. In Regular chronology it is localized to Noah / Shem. In Cumulative chronology it 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:

```markdown
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:

```markdown
16 × 8
8 × 4
4 × 2
2 × 0
```

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

```markdown
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:

```markdown
1656 ÷ 12 = 138
```

The missing four units are:

```markdown
4 × 138 = 552
```

The completed sixteen-unit extension is:

```markdown
16 × 138 = 2208
```

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

```markdown
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:

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

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

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

Cainan's death also preserves the `130` signal:

```markdown
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:

```markdown
5279 − 3023 = 2256
2256 ÷ 3 = 752
```

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

```markdown
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`:

```markdown
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:

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

From Kenan's son to 2nd Cainan is:

```markdown
3851 − 2551 = 1300 = 10 × 130
```

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

```markdown
1370 − 460 = 910
```

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

```markdown
3921 − 910 = 3011 BC
3011 − 2551 = 460
```

2nd Cainan then lives `460` years:

```markdown
2551 − 2091 = 460
```

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

```markdown
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:

```markdown
910 + 460 + 460 = 1830
```

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

```markdown
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.

| Vector state | Source coordinate | Operator | Target coordinate | Handling |
|---|---:|---:|---:|---|
| Daniel 8 birth-side vector | 4851 BC | −2300 | 2551 BC | regular restored 2nd Cainan birth member |
| Daniel 8 death-side vector | 4391 BC | −2300 | 2091 BC | regular restored 2nd Cainan death / Abraham Call member by dependency |
| Daniel 9 Famine envelope, upper member | 4398 BC | −2520 | 1878 BC | Famine-window commencement by File_16 dependency |
| Daniel 9 Famine envelope, core member | 4396 BC | −2520 | 1876 BC | Super-Anchor / Famine Year-2 / Entry hinge by File_16 dependency |
| Daniel 9 Famine envelope, lower member | 4391 BC | −2520 | 1871 BC | Famine-window termination by File_16 dependency |
| Enochian lower-bound vector | 4391 BC | −2730 | 1661 BC | minimum Entry lower-bound; EnvSpread / Enochian state required |
| Daniel 12 sandwich | 4396 BC → 3136 BC → 1846 BC → 586 BC | 1260 → 1290 → 1260 | 586 BC | Cainan-to-Exile macro-prophetic witness by File_16 dependency |

Arithmetic ledger:

```markdown
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:

```markdown
2551 − 2091 = 460
2336 − 1876 = 460
```

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

| Tradition | Cumulative Shelah / Arphaxad-Cainan boundary envelope | Operator | Historical seven-year target | Handling |
|---|---:|---:|---:|---|
| MT + 2nd Cainan | 4398–4391 BC | `−2520 = 60 × 42` | 1878–1871 BC | Famine window; File_16 B6 dependency |
| SP | 4278–4271 BC | `−2400 = 60 × 40` | 1878–1871 BC | Famine window; comparative table-source support |
| LXX | 4825–4818 BC | `−2940 = 60 × 49 = 6 × 490` | 1885–1878 BC | seven years of Plenty; comparative table-source support |

Arithmetic check:

```markdown
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:

```markdown
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`:

| BC-side Plenty / Famine label | AD-side `−215` Mirror label | Civil cross-axis span |
|---:|---:|---:|
| 1885n BC | AD 1656n | `1885 + 1656 − 1 = 3540 = 60 × 59` |
| 1878n BC | AD 1663n | `1878 + 1663 − 1 = 3540 = 60 × 59` |
| 1871n BC | AD 1670n | `1871 + 1670 − 1 = 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:

```markdown
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`:

```markdown
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:

```markdown
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:

```markdown
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 anomaly is local and does not propagate beyond Noah / Shem.
- 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

| Method | What is added | Cainan's value | Basis |
|---|---|---:|---|
| Regular | Begetting ages | +130 years | Age when Shelah was born. |
| Cumulative | Full lifespans | +460 years | Total years lived. |

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

| Patriarch | Begetting age | Lifespan | Difference |
|---|---:|---:|---:|
| 2nd Cainan | 130 | 460 | 330 |
| Shelah | 130 | 460 | 330 |
| Eber | 134 | 504 | 370 |
| etc. | — | — | — |

#### 1.6.2 Application by tradition

| Tradition / method | Handling |
|---|---|
| LXX Regular | Cainan is already in the baseline. `5279 BC` Adam minimum includes his `130` begetting years. No adjustment is needed. |
| MT / SP Regular | To restore Cainan, insert 2nd Cainan by adding the `+130` begetting-age hinge between Arphaxad and Shelah. Shelah and the downstream Terah field remain four-position; Arphaxad / Flood through Adam shift by `+130` and become eight-position where the restored-Cainan state is explicitly opened. MT with Cainan: `3899 + 130 = 4029 BC`. SP with Cainan: `4199 + 130 = 4329 BC`. |
| LXX Cumulative | Cainan is already in the baseline. His `460`-year lifespan is included in the chain. No adjustment is needed. |
| MT / SP Cumulative | To restore Cainan, insert the `+460` lifespan hinge between Arphaxad and Shelah. In the cumulative table this shifts Adam through Arphaxad / Flood by `+460`; Shelah and downstream rows remain unchanged. MT cumulative with Cainan: `14006 + 460 = 14466 BC`, Moses line center. |
| LXX theoretical removal | LXX could have Cainan removed: `5279 − 130 = 5149 BC`, Regular. This is not tracked in standard tables but remains architecturally valid. |

AI-processing rules:

| Rule | Handling |
|---|---|
| Regular chronology | Cainan = `+130` years, begetting age. |
| Cumulative chronology | Cainan = `+460` years, full lifespan. |
| LXX | Cainan already included; no adjustment. |
| MT / SP | Add the appropriate value to restore Cainan. |
| Method distinction | The `130` / `460` difference reflects method, not variant ambiguity. |

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.

| Scale | MT Minimum-Regular, Nisan | Span |
|---|---:|---|
| Literal, 7 days | 3899 BC | Adar 25 – Nisan 2 |
| Figurative, 7 years | 3906–3899 BC | Year 1 – Year 7 |

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:

```markdown
3899 + 1 = 3900 BC
```

For the start of the figurative week, Year 1:

```markdown
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

| Common term | Repository state | Date | Variants |
|---|---|---:|---|
| MT Standard, traditional | MT Standard-Normal / `+215 Sojourn` | 4114 BC | `+215 Sojourn` |
| — | MT Minimum-Regular | 3899 BC | None |

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.

| Derivation from `3899 BC` | Result | State |
|---|---:|---|
| `3899 + 215` | 4114 BC | MT Standard-Normal / `+215 Sojourn` |
| `3899 + 60` | 3959 BC | `+60 Terah` only; also the 4000-to-Christ position by source claim |
| `3899 + 275` | 4174 BC | Maximum; both variants |

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

| Patriarch / event | Birth BC | Death BC | Lifespan | Begetting age |
|---|---:|---:|---:|---:|
| Creation Week | 3906 | 3899 | 7 | — |
| Adam | 3899 | 2969 | 930 | 130 |
| Seth | 3769 | 2857 | 912 | 105 |
| Enosh | 3664 | 2759 | 905 | 90 |
| Kenan | 3574 | 2664 | 910 | 70 |
| Mahalalel | 3504 | 2609 | 895 | 65 |
| Jared | 3439 | 2477 | 962 | 162 |
| Enoch | 3277 | 2912 | 365 | 65 |
| Methuselah | 3212 | 2243 | 969 | 187 |
| Lamech | 3025 | 2248 | 777 | 182 |
| Noah | 2843 | 1893 | 950 | 500 |
| Flood | 2243 | 2242 | 1 | — |

### 2.2 Post-Flood to Patriarchs: MT Minimum-Regular

| Patriarch / event | Birth BC | Death BC | Lifespan | Begetting age |
|---|---:|---:|---:|---:|
| Shem | 2341 | 1741 | 600 | 100 |
| Arphaxad | 2241 | 1803 | 438 | 35 |
| Shelah | 2206 | 1773 | 433 | 30 |
| Eber | 2176 | 1712 | 464 | 34 |
| Peleg | 2142 | 1903 | 239 | 30 |
| Reu | 2112 | 1873 | 239 | 32 |
| Serug | 2080 | 1850 | 230 | 30 |
| Nahor | 2050 | 1902 | 148 | 29 |
| Terah | 2021 | 1816 | 205 | 70/130 |

#### 2.2.1 Noah and Shem `±2` anomaly

Active state:
Regular-localized Shem `±2`.

Genesis 11:10 creates a 2-year ambiguity affecting only Noah and Shem in Regular chronology. In Cumulative chronology, the `±2` propagates through the entire chain; see §6 and `File_02`.

| Patriarch | Literal, in table | Idealistic `±2` | Source direction label |
|---|---|---|---|
| Noah | 2843–1893 BC | 2841–1891 BC | Earlier |
| Shem | 2341–1741 BC | 2343–1743 BC | Later |

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

For SP and LXX, apply the same `±2` to Noah and Shem at their respective positions.

| Tradition | Patriarch | Literal | Idealistic `±2` |
|---|---|---|---|
| SP | Noah | 3492–2542 BC | 3493–2543 BC |
| SP | Shem | 2991–2391 BC | 2993–2393 BC |
| LXX | Noah | 3623–2673 BC | 3621–2671 BC |
| LXX | Shem | 3121–2521 BC | 3123–2523 BC |

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

| Patriarch / event | Birth BC | Death BC | Lifespan | Key events |
|---|---:|---:|---:|---|
| Abraham | 1951 | 1776 | 175 | Call `1876 BC`; `+215 → 2091`. |
| Sarah | 1941 | 1814 | 127 | — |
| Isaac | 1851 | 1671 | 180 | — |
| Jacob | 1791 | 1644 | 147 | Entry `1661 BC`; `+215 → 1876`. |
| Joseph | 1700 | 1590 | 110 | Stood before Pharaoh at age 30, Gen 41:46. |
| Levi | 1704 | 1567 | 137 | Last patriarch death before fixed epoch. |

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

| Event / person | Date BC | Notes |
|---|---:|---|
| Aaron birth | 1529 | 3 years historical / 3.5 years harmonic; see `File_22`, §6B.5 by source reference. |
| Moses birth | 1526 | — |
| Joshua birth | 1476 | — |
| Exodus | 1446 | Fixed anchor. |
| Tabernacle | 1445 | — |
| Aaron death | 1407 | Summer. |
| Moses death | 1406 | Winter. |
| Conquest begins | 1406 | — |
| Six years' war | 1406–1400 | Source-retained range; stray source brace removed as formatting residue. |
| First Sabbath | 1399 | First Sabbath year of rest. |
| Joshua death | 1366 | 110 years old. |

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: the `+50` Year Offset

Active state:
Kings dual-ledger state.

Anchor:
Fall of Jerusalem `586 BC`.

Logic:
The verbatim sum of regnal years exceeds actual history by about 50 years, one Jubilee. This `+50` Offset creates the Triple-`430` harmonic by dependency through `File_16`.

| King | Verbatim | Actual | Accession BC | End / death BC | Logic / chronological anchor |
|---|---:|---:|---:|---:|---|
| Saul | 40 | 40 | 1051 | 1011 | Acts 13:21 |
| David | 40 | 40.5 | 1011 | 971/970 | 2 Sam 5:5; 7.5 Hebron + 33 Jerusalem |
| Solomon | 40 | 40 | 971/970 | 931 | Temple foundation, Year 4: 966 BC |
| Rehoboam | 17 | 17 | 931 | 913 | Division of Kingdom, 931 |
| Abijam | 3 | 3 | 913 | 911 | — |
| Asa | 41 | 41 | 911 | 870 | — |
| Jehoshaphat | 25 | 25 | 870 | 848 | — |
| Jehoram | 8 | 8 | 848 | 841 | — |
| Ahaziah | 1 | 1 | 841 | 841 | — |
| Athaliah | 6 | 6 | 841 | 835 | Usurper Queen |
| Joash | 40 | 40 | 835 | 796 | — |
| Amaziah | 29 | 29 | 796 | 767 | — |
| Uzziah | 52 | 52 | 767 | 740 | Azariah |
| Jotham | 16 | 16 | 740 | 732 | — |
| Ahaz | 16 | 16 | 732 | 716 | Northern Kingdom falls, 722/721 |
| Hezekiah | 29 | 29 | 715 | 687 | Year 14 = 701 BC, Sennacherib |
| Manasseh | 55 | 55 | 687 | 643 | — |
| Amon | 2 | 2 | 643 | 641 | — |
| Josiah | 31 | 31 | 640 | 609 | — |
| Jehoahaz | 0.25 | 0.25 | 609 | 609 | 3 months |
| Jehoiakim | 11 | 11 | 609 | 598 | 1st Exile, 606; 2nd, 597 |
| Jehoiachin | 0.25 | 0.25 | 598 | 597 | 3 months |
| Zedekiah | 11 | 11 | 597 | 586 | Fall of Jerusalem |

#### 2.5.1 Arithmetic verification of the 480th year

```markdown
Exodus anchor: 1446 BC
Biblical span: 480 years, 1 Kings 6:1
Calculation: 1446 − 480 = 966 BC
Historical confirmation: Solomon accession 970 BC → Year 4 = 966 BC
```

#### 2.5.2 Arithmetic verification of the `+50` Offset

```markdown
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
```

Significance:
The 50-year offset acts as a Jubilee Expansion allowing the Triple-`430` harmonic, `1876 → 1446 → 1016 → 586`, to coexist with the 480-year historical count.

## 3. SP Regular Baseline

Active state:
SP Normal / Toggle ON.

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

Website adjustment:
Subtract `275` from Adam through Levi.

Normative definition:
Inclusive Reckoning / Toggle ON.

Logic:

```markdown
SP Normal / Toggle ON = SP Ideal / Exclusive 4200 BC − 1 year = 4199 BC
```

Note:
SP Normal / Toggle ON, `4199 BC`, equals MT Minimum-Regular, `3899 BC`, plus 300 years.

### 3.1 Creation to Flood: SP Normal / Toggle ON

This table reflects the SP normative Toggle ON state, `4199 BC`, exactly 300 years from the MT Minimum-Regular state, `3899 BC`.

| Patriarch / event | Birth BC | Death BC | Lifespan | Begetting age |
|---|---:|---:|---:|---:|
| Creation Week | 4206 | 4199 | 7 | — |
| Adam | 4199 | 3269 | 930 | 130 |
| Seth | 4069 | 3157 | 912 | 105 |
| Enosh | 3964 | 3059 | 905 | 90 |
| Kenan | 3874 | 2964 | 910 | 70 |
| Mahalalel | 3804 | 2909 | 895 | 65 |
| Jared | 3739 | 2892 | 847 | 62 |
| Enoch | 3677 | 3312 | 365 | 65 |
| Methuselah | 3612 | 2892 | 720 | 67 |
| Lamech | 3545 | 2892 | 653 | 53 |
| Noah | 3492 | 2542 | 950 | 502* |
| The Flood | 2892 | 2891 | 1 | — |

Arithmetic verification:

| Row | Verification |
|---|---|
| Adam | `4199 − 130 = 4069`, Seth. |
| Seth | `4069 − 105 = 3964`, Enosh. |
| Enosh | `3964 − 90 = 3874`, Kenan. |
| Kenan | `3874 − 70 = 3804`, Mahalalel. |
| Mahalalel | `3804 − 65 = 3739`, Jared. |
| Jared | `3739 − 62 = 3677`, Enoch. |
| Enoch | `3677 − 65 = 3612`, Methuselah. |
| Methuselah | `3612 − 67 = 3545`, Lamech. |
| Lamech | `3545 − 53 = 3492`, Noah. |
| Noah | `3492 − 600 = 2892`, Flood; Toggle ON: “600th year” = 600 elapsed. |

#### 3.1.1 Methodological note: BJ / Jubilees support for Toggle ON

Claim-status: shared-tradition evidence and structural inference.
The SP normative Toggle ON state, `4199 BC`, is supported by BJ / Jubilees under the source argument. BJ / Jubilees places Shem's birth at `2650 BC` and Ham's at `2648 BC`, 2 years later.

Source lock:
BJ / Jubilees places the drying of the Flood waters, Noah's “601st year,” in `2548 BC`.

Source calculation:
If “601st year” means 600 full years, Toggle ON, then Noah was born in `3148 BC`:

```markdown
2548 + 600 = 3148 BC
```

Arithmetic result:
Noah, born `3148 BC`, was exactly 500 years old when Ham was born in `2648 BC`.

As shared-tradition evidence, this supports the source's claim that the BJ / SP tradition preserves the classic 500/502-year patriarchal gap found in MT / LXX while pivoting it through Inclusive Reckoning. Within this source argument, `4199 BC` functions as the SP Normal / Toggle ON state.

#### 3.1.2 Methodological note: 100-year harmonic preservation

Claim-status: shared-tradition evidence.
BJ / Jubilees supports the SP logic by retaining standard 100-year intervals while re-anchoring them to accommodate Shem as firstborn.

| Son | Birth BC | Event | Event BC | Interval |
|---|---:|---|---:|---:|
| Shem, 1st | 2650 | Ark construction begins | 2550 | 100 years |
| Ham, 2nd | 2648 | Earth dry | 2548 | 100 years |
| Japheth, 3rd | 2645 | Arphaxad born | 2547 | 98 years, 2 Jubilees |

#### 3.1.3 SP Flood and patriarchal deaths

In this SP baseline, the Flood occurs in `2892 BC`. This date aligns with the standard reading of Genesis 7:6, “Noah was 600 years old,” placing the Flood exactly 600 years after Noah's birth:

```markdown
3492 − 600 = 2892 BC
```

Unique to the Samaritan Pentateuch, the lifespans of Jared, Methuselah, and Lamech are mathematically structured so that all three die in the exact year of the Flood, `2892 BC`.

| Patriarch | Death BC | Verification |
|---|---:|---|
| Jared | 2892 | `3739 − 847 = 2892`. |
| Methuselah | 2892 | `3612 − 720 = 2892`. |
| Lamech | 2892 | `3545 − 653 = 2892`. |

Shem anomaly:
To accommodate the fixed anchor of Arphaxad's birth “2 years after the Flood,” Genesis 11:10, and Shem's age of 100 at that time, Noah is calculated as 502 at Shem's birth.

### 3.2 Post-Flood to Patriarchs: SP Minimum / post-Flood Toggle OFF

Note:
The Toggle ON, `−1` year, stops at the Flood. Post-Flood dating resumes standard intervals with Arphaxad anchored at `2891 BC`: “2 years after the Flood” = one-year mathematical gap under inclusive interval reading.

#### 3.2.1 The Shem Superposition

Active state:
Shem Superposition in the SP tradition.

Shem uniquely occupies both Toggle states simultaneously in the SP tradition.

Author clarification:
The SP superposition turns on whether Noah's `600th year` is read as a full `600` years or as the inclusive `599+` form analogous to other biblical ordinal-year expressions. The SP appears to privilege the inclusive reading while retaining the round `600` for schematic purposes. This allowance can ripple backward toward Adam inside the antediluvian SP state, but it does not propagate forward into the Arphaxad-bound post-Flood row.

| Shem binding | Toggle state | Birth BC | Death BC | Derivation |
|---|---|---:|---:|---|
| To Noah, antediluvian | ON | 2990 | 2390 | `3492 − 502 = 2990`. |
| To Arphaxad, post-Flood | OFF | 2991 | 2391 | `2891 + 100 = 2991`. |

Why Shem is “equally either or”:

- Shem is bound to Noah by the “500 years old” begetting notation, Genesis 5:32, placing him in the Toggle ON antediluvian system.
- Shem is also bound to Arphaxad by “Shem was 100 years old,” Genesis 11:10, placing him in the Toggle OFF post-Flood system.
- The “601st year of Noah,” Genesis 8:13, may preserve the round `600` schematic state while the SP inclusive reading treats the Flood-year boundary as `599+`. This affects Shem's Noah-bound date but does not have to affect his Arphaxad-bound date.

State result:
Shem functions as the architectural pivot between eras, occupying both `2990 BC` and `2991 BC` under named toggle bindings.

| Patriarch / event | Birth BC | Death BC | Lifespan | Begetting age |
|---|---:|---:|---:|---:|
| Shem | 2991 or 2990 | 2391 or 2390 | 600 | 100 |
| Arphaxad | 2891 | 2453 | 438 | 135 |
| Shelah | 2756 | 2323 | 433 | 130 |
| Eber | 2626 | 2222 | 404 | 134 |
| Peleg | 2492 | 2253 | 239 | 130 |
| Reu | 2362 | 2123 | 239 | 132 |
| Serug | 2230 | 2000 | 230 | 130 |
| Nahor | 2100 | 1952 | 148 | 79 |
| Terah | 2021 | 1876 | 145, or 205 ideal | 70 |
| Abraham | 1951 | 1776 | 175 | — |

Arithmetic verification, Toggle OFF / post-Flood standard:

| Row | Verification |
|---|---|
| Shem | `2991 − 100 = 2891`, Arphaxad. |
| Arphaxad | `2891 − 135 = 2756`, Shelah. |
| Shelah | `2756 − 130 = 2626`, Eber. |
| Eber | `2626 − 134 = 2492`, Peleg. |
| Peleg | `2492 − 130 = 2362`, Reu. |
| Reu | `2362 − 132 = 2230`, Serug. |
| Serug | `2230 − 130 = 2100`, Nahor. |
| Nahor | `2100 − 79 = 2021`, Terah. |
| Terah | `2021 − 70 = 1951`, Abraham. |

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.

| State | Lifespan | Target |
|---|---:|---|
| Textual / Normal | 145 years | Death at `1876 BC`. |
| Architectural / Ideal | 205 years | Mirrors MT and enables the 1000-year harmonic from Arphaxad's birth to Abraham's birth, `100 + 1000 + 100`. |

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:

```markdown
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.

| Patriarch / event | Birth BC | Death BC | Lifespan | Key events |
|---|---:|---:|---:|---|
| Abraham | 1951 | 1776 | 175 | Call `1876 BC`. |
| Sarah | 1941 | 1814 | 127 | — |
| Isaac | 1851 | 1671 | 180 | — |
| Jacob | 1791 | 1644 | 147 | Entry `1661 BC`; `+215 → 1876`. |
| Levi | 1704 | 1567 | 137 | — |

### 3.4 Fixed epoch: SP; same as MT

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

| Event / person | Date BC | Notes |
|---|---:|---|
| Aaron birth | 1529 | — |
| Moses birth | 1526 | — |
| Exodus | 1446 | Fixed anchor. |
| Conquest | 1406 | — |

## 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

| Patriarch / event | Birth BC | Death BC | Lifespan | Begetting age |
|---|---:|---:|---:|---:|
| Creation Week | 5286 | 5279 | 7 | — |
| Adam | 5279 | 4349 | 930 | 230 |
| Seth | 5049 | 4137 | 912 | 205 |
| Enosh | 4844 | 3939 | 905 | 190 |
| Kenan | 4654 | 3744 | 910 | 170 |
| Mahalalel | 4484 | 3589 | 895 | 165 |
| Jared | 4319 | 3357 | 962 | 162 |
| Enoch | 4157 | 3792 | 365 | 165 |
| Methuselah | 3992 | 3023 | 969 | 187 |
| Lamech | 3805 | 3052 | 753 | 182 |
| Noah | 3623 | 2673 | 950 | 500 |
| Flood | 3023 | 3022 | 1 | — |

Source note:
Claim-status: source-control note and source-retained chronology datum.
Author clarification supersedes the older compressed source note. The LXX chronology from Adam to the Flood uses Lamech begetting age `182`, not `188`, and Lamech lifespan `753`, not `777`. Smith's discussion remains important as an external LXX reconstruction witness, but File_18 does not adopt Smith's `777` lifespan amendment for Lamech. Under the active File_18 table state, Methuselah dies in the Flood year and Lamech dies before the Flood.

Source references retained:

- LAB 1:1–22; 5:8.
- Josephus, Antiquities 1:67, 82–87.
- biblearchaeology.org/research/biblical-chronologies/4353.

Source-control note:
Henry B. Smith Jr. is the controlling external source-reconstruction witness to mention once for the LXX Genesis 5 and 11 chronological layer. The LAB / Josephus / Bible Archaeology note remains source-retained and should be source-controlled in a later pass if quotation or proof use is required.

### 4.2 Post-Flood to Patriarchs: LXX Regular-Minimum

| Patriarch / event | Birth BC | Death BC | Lifespan | Begetting age |
|---|---:|---:|---:|---:|
| Shem | 3121 | 2521 | 600 | 100 |
| Arphaxad | 3021 | 2556 | 465 | 135 |
| 2nd Cainan | 2886 | 2426 | 460 | 130, LXX native |
| Shelah | 2756 | 2296 | 460 | 130 |
| Eber | 2626 | 2122 | 504 | 134 |
| Peleg | 2492 | 2253 | 239 | 130 |
| Reu | 2362 | 2123 | 239 | 132 |
| Serug | 2230 | 2000 | 230 | 130 |
| Nahor | 2100 | 1892 | 208 | 79 |
| Terah | 2021 | 1816 | 205 | 70/130 state-dependent |

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.

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.

## 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.

| Cumulative element | Handling |
|---|---|
| Moses Line, Nisan / Spring | Primary trunk. |
| Aaron Line, Tishri / Fall | Secondary trunk, `+3.5` years. |
| The 3.5-year straddle | Aaron is born 3 years before Moses, and Moses dies 0.5 years before Aaron, creating two parallel tracks. |
| Cumulative Shem `±2` anomaly | Propagates through the entire chain and creates a 7-year margin from lower bound to upper bound. |
| Adam Year 6 | `14006 BC` is treated as Year 6; Apparent Age is calculated from `14006 + 30 = 14036`. |

### 6A. MT Cumulative Chronology: the main trunk

Anchor:
Conquest / Death of Moses = `1406 BC`.

Scalar:
`12600` years = `10 × 1260` to Creation.

Column key:

| Column | Meaning |
|---|---|
| Moses Line, Nisan | Standard Spring reckoning. |
| Aaron Line, Tishri | Fall reckoning, `+3.5` years. |
| 7-year span | Harmonic window defined by Aaron Start – Moses End. |

| Patriarch / event | Lifespan | Moses Line, Nisan | Aaron Line, Tishri | 7-year span, start – end | Harmonic lock to 1406 BC |
|---|---:|---:|---:|---|---|
| Apparent Birth | — | 14036 BC | 14039.5 BC | 14041–14034 BC | Year 6 + 30 years |
| Adam, Year 6 | 930 | 14006 BC | 14009.5 BC | 14011–14004 BC | 12600 years = `10 × 1260` |
| Seth | 912 | 13076 BC | 13079.5 BC | 13081–13074 BC | — |
| Enosh | 905 | 12164 BC | 12167.5 BC | 12169–12162 BC | — |
| Kenan | 910 | 11259 BC | 11262.5 BC | 11264–11257 BC | — |
| Mahalalel | 895 | 10349 BC | 10352.5 BC | 10354–10347 BC | — |
| Jared | 962 | 9454 BC | 9457.5 BC | 9459–9452 BC | Watcher Era, 4600 to Flood |
| Enoch | 365 | 8492 BC | 8495.5 BC | 8497–8490 BC | — |
| Methuselah | 969 | 8127 BC | 8130.5 BC | 8132–8125 BC | — |
| Lamech | 777 | 7158 BC | 7161.5 BC | 7163–7156 BC | — |
| Noah | 950 | 6381 BC | 6384.5 BC | 6386–6379 BC | — |
| Shem | 600 | 5431 BC | 5434.5 BC | 5436–5429 BC | 480 + 120 structure |
| Ark Warning | 120 | 4951 BC | 4954.5 BC | 4956–4949 BC | Upper `4956` → Moses birth = 3430 |
| The Flood | — | 4831 BC | 4834.5 BC | 4836–4829 BC | Upper `4836` → Conquest = 3430 |
| Arphaxad | 438 | 4831 BC | 4834.5 BC | 4836–4829 BC | Born 2 years after Flood |
| Shelah | 433 | 4393 BC | 4396.5 BC | 4398–4391 BC | — |
| Eber | 464 | 3960 BC | 3963.5 BC | 3965–3958 BC | — |
| Peleg | 239 | 3496 BC | 3499.5 BC | 3501–3494 BC | Author-clarified: Nisan envelope `3501n–3494n BC`; parallel Tishri envelope `3502t–3495t BC`; `3495t → AD 1406t = 4900` by File_09 Mirror suffix inversion. |
| Reu | 239 | 3257 BC | 3260.5 BC | 3262–3255 BC | — |
| Serug | 230 | 3018 BC | 3021.5 BC | 3023–3016 BC | Lower `3016` → `7 × 230` |
| Nahor | 148 | 2788 BC | 2791.5 BC | 2793–2786 BC | Lower `2786` → `6 × 230` |
| Terah | 205 | 2640 BC | 2643.5 BC | 2645–2638 BC | — |
| Abraham | 175 | 2435 BC | 2438.5 BC | 2440–2433 BC | 989 to Exodus |
| Isaac | 180 | 2260 BC | 2263.5 BC | 2265–2258 BC | — |
| Jacob | 147 | 2080 BC | 2083.5 BC | 2085–2078 BC | — |
| Levi | 137 | 1933 BC | 1936.5 BC | 1938–1931 BC | Tribal Descent, `12 × 130` |
| Kohath | 133 | 1796 BC | 1799.5 BC | 1801–1794 BC | — |
| Amram | 137 | 1663 BC | 1666.5 BC | 1668–1661 BC | Lower `1661` = 215 Entry |
| Moses | 120 | 1526 BC | 1529.5 BC | 1531–1524 BC | — |
| Conquest | — | 1406 BC | 1406 BC | — | Target |

### 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.

| Patriarch | Lifespan | Standard, Moses | With Cainan, Moses Line | 7-year span with Cainan, start – end | Note |
|---|---:|---:|---:|---|---|
| Adam, Year 6 | 930 | 14006 | 14466 | 14471–14464 | `14466` versus `1446`, Exodus |
| Seth | 912 | 13076 | 13536 | 13541–13534 | — |
| … | … | … | … | … | … |
| Jared | 962 | 9454 | 9914 | 9919–9912 | — |
| Flood | — | 4831 | 5291 | 5296–5289 | `5290` → Christ, Key of 23 |
| Arphaxad | 438 | 4831 | 5291 | 5296–5289 | — |
| Cainan | 460 | N/A | 4853 | 4858–4851 | Inserted variable |
| Shelah | 433 | 4393 | 4393 | 4398–4391 | Convergence point |
| … | … | … | … | … | Matches standard from here |

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.

| Patriarch | Lifespan | Moses Line, Nisan | 7-year span, start – end | Harmonic lock |
|---|---:|---:|---|---|
| Adam | 930 | 13398 BC | 13403–13396 BC | Lower `13396` → Joshua = `110²` |
| Ark Warning | 120 | 4831 BC | 4836–4829 BC | Matches MT Flood |
| Flood | — | 4711 BC | 4716–4709 BC | 120 years after MT Flood |
| Peleg | 239 | 3436 BC | 3441–3434 BC | 70 Jubilees to Christ, 6 BC |
| Terah | 145 | 2580 BC | 2585–2578 BC | SP specific, 145 |
| Joshua | 110 | 1406 BC | 1411–1404 BC | Conquest |
| Death | — | 1296 BC | — | Target |

### 6D. LXX Cumulative Chronology

Active state:
LXX cumulative chronology.

Anchor:
Conquest / Moses Death = `1406 BC`.

Logic:
Uses LXX lifespans, including Lamech 753 and Nahor 208. Includes 2nd Cainan.

| Patriarch | Lifespan | Moses Line, Nisan | 7-year span, start – end | Note |
|---|---:|---:|---|---|
| Adam | 930 | 14896 BC | 14901–14894 BC | — |
| Flood | — | 5745 BC | 5750–5743 BC | — |
| Cainan | 460 | 5280 BC | 5285–5278 BC | Includes 2nd Cainan |
| Peleg | 339 | 3856 BC | 3861–3854 BC | `3856 BC` = BJ / Jubilees Creation |
| Conquest | — | 1406 BC | — | Target |

Cross-reference:
Entity logic: `File_02`, Shem `±2` anomaly, Regular and Cumulative distinctions. Axiom definition: `File_00`, localized baseline variants.

## 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.

| Event | Sumerian A / SKL Short | Sumerian B / SKL Long, `+6480` | Notes |
|---|---:|---:|---|
| Tower of Babel | 2906 BC | 2856 BC | Equally attested by source claim. |
| Flood | 20886 BC | 27366 BC | 360:1 from biblical Flood. |
| Pre-Creation | 452886 BC | 459366 BC | 432000 years to Flood. |

### 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:

```markdown
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:

```markdown
2906 + 720 = 3626 BC
```

With adjustments, the source gives:

```markdown
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.

| System | Interpretation | Vector | Flood anchor |
|---|---|---|---:|
| Berossus | `90 × 2` days Precession | Past | 34566 BC |
| SKL Upper | 90 days Precession | Past | 28086 BC |
| SKL Lower | 0, anchor | — | 21606 BC / 20886 BC |

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

Alignment formula:

```markdown
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:

```markdown
2 × 360 = 720
```

This creates parallel date variants throughout.

Example, Adam / Alulim:

| Pair | Dates | Difference |
|---|---|---:|
| Primary pair | 262086 BC and 262806 BC | 720 years |

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:

| Rail | Dates |
|---|---|
| Base | 262086 / 262806 BC, 720 apart |
| With `±2` | 262088 / 262808 BC |
| With `+30` | 262116 / 262118 BC and 262836 / 262838 BC |

The same mechanism applies to `+6480` variant dates.

#### 7.4.1 Gap range

| State | Years | Explanation |
|---|---:|---|
| Minimum | 6450 | `6480 − 30`; 3 months of precession under Great Year 25800; `15 × 430`. |
| Standard | 6480 | Standard precessional display. |
| Maximum | 6510 | `7 × 930`, echoing Adam's lifespan. |
| Extended | 7200 | `10 × 720`, full scaling. |

#### 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.

| Scale | Display |
|---|---|
| Scale 1 | 1 day = 72 years, or 71.666; 3 months = 90 days = `6480/6450` years. |
| Scale 2 | 1 day = 360 years; 90 days from the active `+30 Apparent Mode` rails `2936/2886 BC` to Pillars `AD 29465/29515`. The Pillar dates are Projective Boundary / Temple-Time coordinate states by `File_21` dependency. |

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.

```markdown
3.5 days × 360 = 1260 years
```

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

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

```markdown
7.5 × 360 = 2700 years
```

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

#### 7.4.4 Breakdown of the 2700-year span

Active state:
Regular chronology comparison.

| Segment | Years | Days, divided by 360 | Creation day(s) |
|---|---:|---:|---|
| LXX → MT | 1440 | 4 | Days 1–4 |
| MT → 3606/3576 BC | 540 | 1.5 | Days 5–5.5 |
| 3606/3576 → 2886/2856 BC | 720 | 2 | Days 6–7 |
| Total | 2700 | 7.5 | Full Creation Week |

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

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

#### 7.4.5 Cumulative chronology alignment

| Position | Date BC | Years to SKL | Calculation | Creation day |
|---|---:|---:|---|---|
| Shem birth | 5436 | 2550/2580 | `7 × 360 + 30/60` | Day 1, exact |
| Flood | 4836 | 1980 | `5.5 × 360` | Day 2 |

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:

| Witness field | Source reading | Claim-status |
|---|---|---|
| One tradition aligned with SKL | possible coincidence | limited structural observation |
| All three manuscript traditions, MT / LXX / SP, plus both modes, Regular / Cumulative | design | structural inference plus providential synchronization |

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.

| Conversion | Source date | Variant date |
|---|---:|---:|
| Flood | 20886 BC | 27366 BC |
| Adam / Alulim | 262086 BC | 268566 BC |
| Pre-Creation | 452886 BC | 459366 BC |

### 7.6 Antediluvian kings as biblical patriarchs

| SKL king | Biblical parallel | Reign, SKL | Date BC, primary |
|---|---|---:|---:|
| Alulim | Adam | 28800 years | 262086 |
| Alalngar | Seth | 36000 years | 233286 |
| Enmenluana | Enosh | 43200 years | 197286 |
| Enmengalana | Kenan | 28800 years | 154086 |
| Tammuz | Mahalalel | 36000 years | 125286 or 107286 |
| Ensipadzidana | Jared | 28800 years | 89286 |
| Enmendurana | Enoch | 21000 years | 60486 |
| Ubara-Tutu | Noah | 18600 years | 39486 |

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

### 7.7 Post-Flood notable figures

| SKL figure | Reign / span | Date BC | Biblical parallel / notes |
|---|---:|---|---|
| Etana | 1500 years | 11696–10136 | “Shepherd who ascended to heaven.” Source-retained reign value; same-side span of displayed range is `1560`. Proof-bearing File_21 harmonic uses opening anchor: `11696 − 1406 = 10290 = 210 × 49`. |
| Balih | 400 years | 10136–9736 | Etana's miracle son; Isaac type. |
| 23 kings | 17980 years | Flood → 2906 | Total post-Flood to Babel. |

### 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.

| Pillar | AD date range | Scale |
|---|---:|---|
| Jachin | AD 29395–AD 29515 | 1 cubit = 720 years |
| Boaz | AD 29395–AD 29465 | 1 cubit = 490 years |

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

| Span | Years | Connection |
|---|---:|---|
| Tammuz → Enoch | `180 × 360` | 64800 years |
| Tammuz → Abraham | `360 × 360` | 129600 years |
| Etana → Conquest, 1406 BC | 210 Jubilees | 10290 years |
| Balih → Conquest, 1406 BC | 170 Jubilees | 8330 years |
| Total SKL span | 453600 years | `1260 × 360` |

## 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.

| From | To | Span | Verification | Arithmetic-control result |
|---|---|---:|---|---|
| MT Minimum-Regular Adam | SP Normal / Toggle ON Adam | 300 years | `4199 − 3899 = 300` | checks |
| MT Minimum-Regular Adam | LXX Regular-Minimum Adam | 1380 years | `5279 − 3899 = 1380` | checks |
| SP Normal / Toggle ON Adam | LXX Regular-Minimum Adam | 1080 years | `5279 − 4199 = 1080` | checks |
| Entry, minimum | Entry, `+215` | 215 years | `1876 − 1661 = 215` | checks |
| MT Standard-Normal Adam | MT maximum Adam | 60 years | `4174 − 4114 = 60` | checks |
| MT Minimum-Regular Adam | MT Standard-Normal Adam | 215 years | `4114 − 3899 = 215` | checks |
| MT Minimum-Regular Adam | MT `+60 Terah` Adam | 60 years | `3959 − 3899 = 60` | checks |
| Entry, `1876 BC` | Exile, `586 BC` | 1290 years | `1876 − 586 = 1290` | checks |
| Entry, `1876 BC` | Exodus, `1446 BC` | 430 years | `1876 − 1446 = 430` | checks |
| Entry, `1661 BC` | Exodus, `1446 BC` | 215 years | `1661 − 1446 = 215` | checks |
| Cumulative Creation | Conquest | 12600 years | `14006 − 1406 = 12600` | checks |
| SKL Flood | Tower, primary | 17980 years | `20886 − 2906 = 17980` | checks |

### 8.1 Section-level arithmetic ledger

| Section | Arithmetic checked | Arithmetic-control result |
|---|---|---|
| §1.1 Variant matrix | `3899 + 60 = 3959`; `3899 + 215 = 4114`; `3899 + 275 = 4174`; `215 − 60 = 155` | checks |
| §1.2 Inter-tradition gaps | `4200 − 3899 = 301`; `5279 − 4200 = 1079`; `5279 − 3899 = 1380`; `301 + 1079 = 1380`; `4200 − 3901 = 299` | checks; residue line remains audit-controlled |
| §1.6 2nd Cainan | `460 − 130 = 330`; `504 − 134 = 370`; `3899 + 130 = 4029`; `4199 + 130 = 4329`; `5279 − 130 = 5149`; `14006 + 460 = 14466` | checks |
| §§2–4 Regular tables | Visible birth-to-death lifespans and begetting intervals | mostly check; SP Terah `145 (205)` and LXX Terah / Abraham are resolved as source-state displays within the Terah four-position field |
| §2.5 Kings ledger | `1446 − 480 = 966`; `1446 − 430 = 1016`; `1016 − 966 = 50` | checks |
| §3 SP / BJ relation | `4199 − 3856 = 343`; `2548 + 600 = 3148`; `3148 − 2648 = 500` | checks |
| §6A MT cumulative | Lifespan stacking from `14006 BC` to `1406 BC`; Aaron line `+3.5`; visible envelopes | checks; Peleg `3495t` is author-clarified as the Tishri terminal member of the parallel Peleg envelope and participates in the `4900` Mirror component check |
| §6B MT cumulative + Cainan | `14006 + 460 = 14466`; `4831 + 460 = 5291`; `5291 − 438 = 4853`; `4853 − 460 = 4393` | checks |
| §6C SP cumulative | `12100 = 110 × 110`; `13396 − 1296 = 12100`; `4831 − 4711 = 120`; `3436 − 6 = 3430`; `3430 = 70 × 49`; `1406 − 1296 = 110` | checks |
| §6D LXX cumulative | Visible LXX cumulative rows and envelopes | arithmetic display retained; Lamech / Nahor source-table values resolved by author clarification |
| §7 SKL primary anchors | `20886 − 2906 = 17980`; `27366 − 2856 = 24510`; `27366 − 20886 = 6480`; `452886 − 20886 = 432000`; `459366 − 27366 = 432000` | checks |
| §7 SKL scale states | `2 × 360 = 720`; `3.5 × 360 = 1260`; `7.5 × 360 = 2700`; `15 × 430 = 6450`; `7 × 930 = 6510`; `10 × 720 = 7200` | checks where active state is named |
| §7 SKL +6480 application | `20886 + 6480 = 27366`; `262086 + 6480 = 268566`; `452886 + 6480 = 459366` | checks |
| §7 SKL notable figures | Etana terminal to Conquest `11696 − 1406 = 10290 = 210 × 49`; Balih terminal to Conquest `9736 − 1406 = 8330 = 170 × 49` | checks when terminal member is active |

### 8.2 Audit-controlled arithmetic displays

| Display | Arithmetic-control finding | Handling |
|---|---|---|
| `(299 × 365.24) − (300 × 364) ≈ 7.5 days` | displayed form gives `6.76`; true-solar `365.2422` gives `7.4178`; File_11 physical residue gives `299/40 = 7.475` days | Author-clarified as conceptual residual-display / calibration language, not ordinary arithmetic from the abbreviated display. |
| Peleg Mirror note | `3495t + AD 1406t − 1 = 4900`; also `3502t + AD 1399t − 1 = 4900`, `3501n + AD 1400n − 1 = 4900`, and `3494n + AD 1407n − 1 = 4900` | Author-clarified. `3495t` is the Tishri terminal member, not an erroneous upper-member label. |
| SP Terah `145 (205)` | `2021 − 1876 = 145` checks; `205` from the same birth row would produce `1816 BC` | Author-clarified as textual `145` plus architectural `205` dual-lock; SP cumulative uses official `145`. |
| LXX Terah / Abraham four-position field | `2021 − 1816 = 205`; `2021 − 70 = 1951`; `2081 − 130 = 1951`; `2236 − 70 = 2166`; `2296 − 130 = 2166` | Resolved by author clarification. The displayed `70/130` begetting-state is state-dependent, not one executable value for the same Terah row. |
| Pillars 90-day relation | `2906 BC → AD 29465` and `2856 BC → AD 29515` produce `32370`, not `32400`; the relation checks if `+30 Apparent Mode` anchors `2936 BC` and `2886 BC` are active | Preserve; active `+30` rail should be named. File_21 classifies this as Projective Boundary / Temple-Time Pillar coordinate synchronization, not the sole derivation of the Pillars. |
| Cumulative Flood / SKL Day 2 | `4836 − 2856 = 1980 = 5.5 × 360`; `4836 − 2886 = 1950` | Preserve; row uses SKL Long target unless another dependency states otherwise. |
| Tammuz → Abraham `360 × 360 = 129600` | Not derivable from the visible Tammuz rows and standard Abraham anchors alone | Preserve as dependency-controlled SKL / Berossus display. |
| Total SKL span `453600 = 1260 × 360` | Checks when the SKL Short Pre-Creation `+720` rail `453606 BC` is active against `6 BC`; not directly from `452886 BC` base rail | Preserve; active `+720` rail should be named. |

## 9. Cross-Reference Index

### 9.1 Source-retained cross-reference index

| File | Section / topic | Data required from `File_18` |
|---|---|---|
| `File_00` | All axioms | Baseline dates for application. |
| `File_01` | Abraham entity | §2.3, MT; §3.3, SP; §4.3, LXX. |
| `File_02` | Flood entity | §§2.1–2.2; §6; §7. |
| `File_05` | Exodus entity | §§2.4–2.5. |
| `File_07` | Creation entity | §§2.1; 3.1; 4.1; 6. |
| `File_09` | Cumulative architecture | §6, all. |
| `File_10` | External validation | §7, Sumerian / SKL. |
| `File_16` | 1876 Nexus | §§2–5, convergence verification. |
| `File_17` | Time-span components | §8, arithmetic verification. |

### 9.2 Dependency-control additions

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

| File | Dependency function |
|---|---|
| `File_04` | Jacob / LXX `33 + 397` and Entry-state controls where patriarchal rows are used. |
| `File_08` | Kings dual-ledger and `+50` offset control for §2.5. |
| `File_11` | Three-Gear, `299 → 300`, `300/299`, and Residue Protocol controls. |
| `File_12` | Calendrical physics and Enochian / residue controls for §1.2.1 and §7. |
| `File_14` | Biological-fractal and variant-gap terminology where `275`, `276`, `280`, and LXX Maximum material is opened. |
| `File_34` | Full SKL / Berossus derivation for §7. |
| `File_51a`; `File_54` | File map, state register, Machine Guard, and claim-status precedent. |

## 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`.

| Website table | Current setting | Adjustment to minimum |
|---|---|---|
| MT Regular | 430 in Egypt; no `+60 Terah` | Subtract 215. |
| SP Regular | `+60 Terah`; `+215 Sojourn` | Subtract 275 from Adam through Levi. |
| SP Regular, Noah / Flood | Range caused by `600th year` ambiguity | Noah / Flood shown as range, `±1`. |
| LXX Regular | `+60 Terah`; `+215 Sojourn` | Subtract 275. |
| SP-215 hybrid | `+60 Terah` applied | Subtract 60. |

Note on SP:
The “600th year” ambiguity, 599–600, creates a one-year range at Noah and the Flood. Rather than forcing one reading, ranges are shown in §3.

## 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.

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. The active File_18 LXX Regular-Minimum table and LXX cumulative table both use Lamech lifespan `753`, with Lamech begetting age `182`. Nahor uses lifespan `208` where the corrected LXX source-table state is active. Smith remains the external LXX source-reconstruction witness; his `777` lifespan amendment is not adopted as the File_18 LXX table value.

Author clarification note 10 — SP ordinary `±2` labels versus SP Shem Superposition:
Resolved as a state distinction. Ordinary regular-localized `±2` remains distinct from SP Shem Superposition. In SP, the Noah `600th year` can be read as full `600` or inclusive `599+`; the allowance may ripple backward toward Adam under the antediluvian SP toggle but does not propagate forward past the Arphaxad-bound row. BJ / Jubilees echoes this same inclusive / schematic tension.

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 removes only archival amendment history, pass logs, pressure-test repetition, pointer-refresh records, and obsolete replacement-workflow notes.

Detailed revision history is preserved in the `Repository_Change_Archive`.

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

Final pressure-test status is preserved in the file header. Detailed pressure-test records are archived rather than repeated in the public file body.