File: File_04 Title: Jacob as Jubilee Standard and the LXX 33 + 397 Sojourn Interpretation Entity: Jacob (Israel) Classification: Patriarch / The Jubilee Clock UUID: PATRIARCH_JACOB Status: Final; bounded September 13 2026 Terah-inclusive −33 scope pointer applied; bounded September 13 Payne/Zondervan provenance clarification applied; post-final pressure test complete; File_18 2nd Cainan variant-boundary and Pentateuchal Funnel structural-harmony clarifications applied; 1876 Cainan macro-vector cross-file update applied; bounded File_62 male 7+33 / localized −33 reciprocal pointer applied July 23 2026; bounded File_64 Jacob final-70 / paired-930 reciprocal pointer applied July 27 2026 Publication-cleanup status: Public-clean Markdown source; archival amendment history routed to Repository_Change_Archive. Pressure-test status: Current; publication-clean verification complete; detailed pressure-test record archived rather than repeated in the public file body; focused reciprocal-routing verification complete July 27 2026 for the bounded File_64 pointer; no new full pressure test claimed for the File_62 or File_64 pointer-only updates. Reciprocal-routing verification status: Final File_62 pointer applied and bounded machine-diff checked July 23 2026; Final full post-final pressure-tested File_64 pointer applied and focused machine-diff, dependency, state-firewall, Machine-Guard, Markdown-structure, and publication-clean checks completed July 27 2026; no new full pressure test was performed for either pointer-only update. Register Agreement status: Checked against State_Vocabulary_Register v1.34 and Restart Capsule v11.33; bounded File_62 and File_64 dependency routing only. The July 27 expanded File_64 amendment states remain Final-local pending separate Register / Capsule routing. The File_64 pointer adds no File_64-derived coordinate to File_04's Primary-anchor inventory or biography tables and changes no pre-existing File_04 arithmetic, anchors, modal-state logic, node-class, operator, sign convention, slash-pair, range, envelope, Mirror protocol, claim-status label, theological claim, or dependency boundary. Primary domain: Regular; Comparative; Cumulative; Theological Traditions: MT; SP; LXX Canonical source: Markdown Primary anchors: 2006 BC; 1973 BC; 1929 BC; 1896 BC; 1909 BC; 1876 BC; 1843 BC; 1859 BC; 1826 BC; 1782 BC; 1749 BC; 1446 BC; 1406 BC; 1936/1933 BC Related files: File_00; File_01; File_02; File_03; File_16; File_17; File_18; File_51a; File_54; File_61; File_62; File_64; Restart Capsule v11.33; State Vocabulary Register v1.34 Major operators: same-side BC span; +215 Position; MT Minimum −215; LXX −33; LXX 33 + 397; 147 = 3 × 49; +60 Terah; 2nd Cainan; Cainan macro-vector B6 by File_16 dependency; subordinate Ramesside path; 70 × 7; 7³; Aaron/Moses L = 3.5; EnvNorm 7; EnvSpread 7.5 Major modal states: +215 Position; MT Minimum; LXX −33; LXX 33 + 397; shared 1876 BC year-label; subordinate Ramesside Exodus state; +60 Terah; dependency-controlled 2nd Cainan; Cainan macro-vector B6 dependency state; File_18 2nd Cainan variant-boundary state by dependency; File_18 Pentateuchal Funnel state by dependency; Levi death-state pair; Aaron/Moses Nisan/Tishri birth-phase register; File_62 male 7+33 downstream hybrid state; File_64 Jacob final-70 / paired-930 downstream dependency state Revision basis: 490d Repository Style Guide v2.5; Restart Capsule v11.33; State Vocabulary Register v1.34; Project Procedures v3.5; File_00; File_01; File_02; File_03; File_16; File_17; File_18; File_51a; File_54; corrected Final File_61; Final File_62; Final full post-final pressure-tested File_64; prior finalized source; bounded File_64 reciprocal-routing audit July 27 2026; Repository_Change_Archive (non-controlling history) Current refresh note: Bounded File_62 / File_64 reciprocal routing aligns active control pointers to 490d Repository Style Guide v2.5, Restart Capsule v11.33, State_Vocabulary_Register v1.34, and Project Procedures v3.5. File_64 uses File_04's standard 1929/1909/1859 BC final-life rail and localized LXX 1896/1876/1826 BC rail in its downstream Jacob final-70, triple-430, and paired-930 synthesis. File_64 locally derives the intermediate 1922/1889 BC marriage coordinates from Genesis 29's seven-year service; those dates remain File_64 comparison coordinates and are not inserted into File_04's Primary anchors or biography tables. The update changes no File_04 proof-bearing arithmetic, chronology row, modal-state logic, node-class, operator, sign convention, slash-pair, range, envelope, Mirror protocol, claim-status label, theological claim, or dependency boundary. Detailed history remains in Repository_Change_Archive.

File_04 — Jacob as Jubilee Standard and the LXX 33 + 397 Sojourn Interpretation

0. File-function

File_04 documents Jacob’s chronological role as the Jubilee standard, because Jacob’s lifespan is 147 = 3 × 49.

The file also documents the LXX alternate interpretation of Exodus 12:40 in which the 430-year Sojourn is parsed as 33 years in Canaan and 397 years in Egypt. Under this reading, Jacob’s return from Haran lands at 1876 BC, creating an additional direct chronological fork to the 1876 BC Super-Anchor.

Enumeration note: The LXX 33 + 397 reading is the fourth direct chronological fork in the broader File_16 convergence inventory. In this file, it appears inside a six-row local convergence subset. These are enumeration scopes, not competing claims.

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

Argument-control rule: Arithmetic facts and textual / chronology data carry the base layer of the argument. Structural inferences may support the argument when the active state, node-class, tradition, and operator are explicit. Theological, typological, and providential readings explain meaning but do not replace arithmetic or dependency control.

0.1 Working state register

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

0.2 File map

0.3 Modal-state processing rules

1. 1876 BC is a shared year-label, not a single event. Identity requires state, node-class, tradition, and operator agreement.
2. The +215 Position, MT Minimum −215, and LXX −33 rows are simultaneous comparison states. No row replaces another row.
3. The LXX −33 value and the LXX −33 scope are distinct. The value derives from Exodus 12:40 interpretation. The Abraham–Levi localization is the repository’s standard methodological default.
4. The LXX 33 + 397 state answers the question: when did the “children of Israel” first dwell together as a complete Jacob-family unit?
5. The Sojourn 215, Exodus 215, and LXX −33 states are not interchangeable. The Sojourn 215 divides the Sojourn. The Exodus 215 shifts the whole system into the subordinate Ramesside state. The LXX −33 identifies the family-unit interval within the Sojourn field.
6. The subordinate Ramesside path uses 1231 BC as a subordinate Exodus lens. It must not replace the primary 1446 BC Exodus anchor.
7. The 2nd Cainan row is dependency-controlled by File_16. File_04 may retain it as a convergence witness but does not locally re-prove the cumulative Cainan mechanism.
8. The Levi death-state pair, 1782 BC and 1749 BC, is derived locally from the Jacob–Levi arc.
9. The Aaron/Moses relation has two coordinated representations: a three-year Nisan/Nisan birth-label branch and a phase-resolved L = 3.5 Tishri/Nisan priestly straddle.
10. EnvNorm 7 and EnvSpread 7.5 are not competing corrections. EnvNorm is the normalized week label. EnvSpread is the phase-spread envelope when the half-year state is active.
11. No Mirror protocol is active in the main argument of File_04. Any Mirror validation of −33, Flood ±2, or global/local scope belongs to File_16 or File_00 unless explicitly imported later.
12. All local BC spans are same-side BC spans unless a later section explicitly opens a cross-axis state.
13. Final File_62 may use the localized −33 state in a downstream hybrid H → K → V = 7 + 33 = 40; this does not create a new File_04 biography row, broaden the standard −33 scope, or merge half-clutch, regular, and LXX coordinates into one manuscript chronology.

0.4 Machine Guards for File_04

Machine Guard [JACOB 1876 YEAR-LABEL]:

1876 BC is a shared year-label. In File_04, it may mark Jacob’s Entry under the +215 Position, Jacob’s return from Haran under LXX −33, Abraham’s Call / Death of Terah under SP-215 or +60 Terah, a subordinate Ramesside convergence point, or Death of Cainan under the File_16 dependency. These are related convergence witnesses, not one collapsed event.

Machine Guard [JACOB +215 / MINIMUM / LXX −33]:

The +215 Position, MT Minimum −215, and LXX −33 rows are modal states. Do not treat the MT Minimum row as a correction of the +215 Position, and do not treat the LXX −33 row as a replacement chronology. Each row must retain its state label.

Machine Guard [JACOB LXX 33 + 397]:

The LXX 33 + 397 reading is a family-unit Sojourn interpretation. It places Jacob’s return from Haran at 1876 BC and Jacob’s Entry into Egypt at 1843 BC. J. Barton Payne independently uses the same 33 + 397 logic and the same 1843 BC descent date; do not present this division as original to the repository. Do not collapse this with the MT 430-Egypt state, where Jacob’s Entry itself is 1876 BC.

Machine Guard [JACOB −33 SCOPE]:

The −33 value is textual and derives from the LXX Exodus 12:40 interpretation. The former Abraham–Levi-only scope is superseded: the operative bounded corridor now begins at Terah and continues through Abraham→Jacob/Levi. File_04 retains only the Jacob-family subset in its displayed tables. Global Noah/Adam −33 remains exploratory and dependency-controlled.

Machine Guard [JACOB SOJOURN / EXODUS / −33 FIREWALL]:

The Sojourn 215, Exodus 215, and LXX −33 states answer different questions. The Sojourn 215 concerns the internal Canaan/Egypt division under the primary 1446 BC Exodus anchor. The Exodus 215 concerns the subordinate 1231 BC Ramesside state. The LXX −33 concerns the “children of Israel” family-unit interval from Jacob’s return from Haran to the Entry. Do not combine them as one generic 215/33 adjustment field.

Machine Guard [JACOB LEVI DEATH STATES]:

1782 BC and 1749 BC are Levi death-state values. 1782 BC belongs to the +215 Levi death state. 1749 BC belongs to the LXX −33 Levi death state. They are not Jacob death dates, Entry dates, or Conquest dates.

Machine Guard [JACOB AARON/MOSES STRADDLE]:

The Aaron/Moses branch preserves both a three-year Nisan/Nisan birth-label relation and the phase-resolved L = 3.5 Tishri/Nisan priestly straddle. Printed integer labels such as 1936/1933 BC must not erase the L = 3.5 operator, and the L = 3.5 operator must not erase the legitimate three-year branch. The Aaron death pair is 1407 BC / 1406 BC; the 1447t/1446n label-state belongs to the plague-period field and is not the wilderness death pair.

Machine Guard [JACOB CAINAN DEPENDENCY]:

The 2nd Cainan convergence row is retained as a File_16 witness. File_04 does not locally re-prove the cumulative-to-regular Cainan mechanism and must not infer missing Cainan arithmetic.

Machine Guard [JACOB CAINAN MACRO-VECTOR DEPENDENCY]:

The Cainan macro-vector B6 state may be cited only as a File_16 / File_18 dependency. In File_04, it must not turn Jacob’s 1876 BC Entry / return labels, Abraham Call / Death of Terah labels, or Cainan death labels into one event. The 2520 envelope projection supports the 1876 Nexus by dependency and does not alter the local LXX 33 + 397, +215 Position, or −33 rows.

Machine Guard [JACOB / TERAH / 2ND CAINAN VARIANT BOUNDARY]:

File_04 controls the Abraham-to-Levi / Joseph two-date field and the +60 Terah variator by dependency. Where File_18 opens restored 2nd Cainan, 2nd Cainan remains in the four-state block with Shelah through Terah. The eight-state propagation begins upstream with Arphaxad / Flood and continues back to Adam. Do not apply the eight-state restored-Cainan field to Abraham, Jacob, Joseph, Levi, Terah, Shelah, or 2nd Cainan.

Machine Guard [JACOB FILE_18 PENTATEUCHAL FUNNEL]:

File_04 may participate in the Pentateuchal Funnel only through its controlled local block: Abraham, Isaac, Jacob, and Joseph / Levi under the ±215 Sojourn fork, plus the transition into Egypt. It must not import the full Adam → Arphaxad eight-position block or assign direct regular pivot dates to Kohath or Amram. The all-even 12–8–4–2–0 ladder, with 12–8–4–2 generation blocks and 8–4–2–0 date-state countdown, remains File_18-controlled and is classified as structural inference / providential synchronization.

Machine Guard [JACOB RAMESSES NON-REPLACEMENT]:

1231 BC is a subordinate Ramesside Exodus state. It is valid for the local convergence row 1231 + 430 + 215 = 1876, but it must not replace the primary 1446 BC Exodus anchor in the Jacob matrix or the LXX 33 + 397 calculation.

Machine Guard [JACOB FILE_62 HYBRID NON-RETROJECTION]:

Final File_62 may combine corrected File_61 half-clutch / full-clutch coordinates with File_04's localized LXX −33 endpoints in the downstream form H → K = 7, K → V = 33, H → V = 40. File_04 supplies only the controlled −33 state. The derived H7/T14 coordinates, including 2073/2066/2033, 1926/1919/1886, and 1789/1782/1749 BC, remain File_61/File_62 states and must not be inserted into File_04's standard biography tables, Primary anchors, Bullseye inventory, or one continuous manuscript chronology. File_04's local LXX Daniel lock 1896 → 1406 = 490 remains distinct from File_62's MT/Jacob extended-week carrier 1929 → 1439 = 490.

Machine Guard [JACOB FILE_64 DERIVED-MARRIAGE NON-RETROJECTION]:

Final File_64 may derive 1922 BC and 1889 BC as seven-year marriage-field comparisons between the File_04-controlled flight and return endpoints. Those labels, together with File_64's 999/992/979 BC construction rail and paired 930 comparisons, remain File_64-local downstream states. Do not insert 1922/1889 BC into File_04's Primary anchors or biography tables, and do not treat File_64's Jacob–Temple, Adamic, Danielic, royal, or sanctuary interpretation as a new local File_04 proof.

0.5 Arithmetic-control summary

Arithmetic-control result: The visible arithmetic in the Jacob biography rows, the LXX 33 + 397 logic, the local 1876 BC convergence rows, the +60 Terah calculation, the Levi death-state derivation, the Daniel lock, the cubic lock, and the Aaron/Moses display-state arithmetic all check under their stated operators. No arithmetic correction is required.

0.6 Claim-status register for File_04

Claim-status rule: Claim-status labels are used where they prevent confusion between arithmetic, textual basis, structural inference, dependency control, and typological or theological interpretation. They are not attached to every sentence.

0.7 Argument-control summary

File_04 argues by layering chronology data, arithmetic facts, state-controlled structural inference, and theological or typological meaning.

Argument-scope result: The file’s claims are preserved with reduced rhetorical force. The arithmetic and state controls remain primary; interpretive language is labeled and restrained.

0.8 Publication-cleanup control

This public-clean source preserves the Final and post-final pressure-tested file status. Detailed finalization, pressure-test, and cross-file update records are archived rather than repeated in the public body.

No arithmetic, anchors, modal states, node-classes, sign conventions, operators, slash-pairs, ranges, theological claims, or dependency boundaries are changed in this cleanup.

1. Chronological matrix

All dates in this section are BC unless otherwise labeled. Same-side BC spans are computed by subtraction.

State-control note: The following tables are biography-state tables. Each row must retain its state label. No table converts another table into an error.

1.1 Standard +215 and MT Minimum positions

Active states: +215 Position; MT Minimum −215.

Node-class: Jacob biography events.

The legacy heading STANDARD POSITIONS (MT/SP) is retained as source-history context. The table itself distinguishes the +215 Position from the MT Minimum −215 comparison state.

Arithmetic check, +215 Position:

2006 − 1929 = 77
2006 − 1909 = 97
2006 − 1876 = 130
2006 − 1859 = 147
1929 − 1909 = 20
1909 − 1876 = 33
1876 − 1859 = 17

Arithmetic check, MT Minimum −215:

1791 − 1714 = 77
1791 − 1694 = 97
1791 − 1661 = 130
1791 − 1644 = 147
1714 − 1694 = 20
1694 − 1661 = 33
1661 − 1644 = 17

Position-gap check:

2006 − 1791 = 215
1929 − 1714 = 215
1909 − 1694 = 215
1876 − 1661 = 215
1859 − 1644 = 215

Claim-status note: The table values are source-retained chronology data. The subtraction checks are arithmetic facts. The comparison between the two columns is a modal-state comparison, not a correction of one column by the other.

State note: 1876 BC in this table is Jacob’s Entry into Egypt under the +215 Position. It is not Jacob’s return from Haran in this state.

1.2 LXX −33 position

Active state: LXX −33.

Node-class: Jacob biography events under the LXX Sojourn-period variant.

Current controlling reference: File_00, §3.7, The −33 variant: nature and scope.

Arithmetic check:

1973 − 1896 = 77
1973 − 1876 = 97
1973 − 1843 = 130
1973 − 1826 = 147
1896 − 1876 = 20
1876 − 1843 = 33
1843 − 1826 = 17

−33 shift check from the +215 Position:

2006 − 1973 = 33
1929 − 1896 = 33
1909 − 1876 = 33
1876 − 1843 = 33
1859 − 1826 = 33

The −33 shift causes Jacob’s return from Haran to land at 1876 BC, the Super-Anchor.

Claim-status note: The LXX row is a source-retained chronology state. The −33 differences are arithmetic facts under the active LXX state. The claim that this row contributes to the Super-Anchor is a structural inference and is dependency-supported by File_16.

State note: 1876 BC in this table is Jacob’s return from Haran under the LXX −33 state. It is not Jacob’s Entry into Egypt in this state.

1.3 State-control note on 1876 BC

1876 BC is a shared year-label in this file.

Arithmetic note: The shared year-label is produced by several different arithmetic paths, checked locally where the operator is active. The equality of the year-label does not create event identity.

State-control rule: The year-label 1876 BC must not be treated as one event merely because multiple systems land on it.

2. The LXX 33 + 397 interpretation

2.1 The alternate reading

Active state: LXX Exodus 12:40 alternate reading.

Node-class: Sojourn division by Jacob-family-unit formation.

The LXX phrase in Exodus 12:40 may be parsed as the sojourning of the children of Israel in Canaan and in Egypt for 430 years.

State note: The 1876 BC start in this table is Jacob’s return from Haran under the LXX −33 state. The 1843 BC date is Jacob’s Entry into Egypt under the same state.

Claim-status note: The LXX wording is the textual datum. The segmentation into 33 + 397 is a structural inference built from Jacob’s age data and the LXX family-unit reading, but the interpretation itself is not original to this repository. The arithmetic checks once that interpretation is active.

2.1A External scholarly precedent

J. Barton Payne, “Chronology of the Old Testament,” in The Zondervan Pictorial Encyclopedia of the Bible, Vol. 1, ed. Merrill C. Tenney (Grand Rapids: Zondervan, 1975), pp. 829–845, especially p. 832, independently uses the same logic. Payne states that under the LXX wording Jacob and his sons had been in Palestine for 33 years before removal to Egypt, leaving 397 years for the Egyptian sojourn and dating the descent to 1843 BC. He also retains the MT descent at 1876 BC.

Therefore, neither the 33 + 397 division nor the 1843 BC LXX descent is claimed here as the author's original discovery. The distinctive Unified Chronology proposal is the bounded scope of the localized −33: it is tracked upstream through Terah and downstream through Abraham→Jacob/Levi, while normal execution stops before Noah/Shem. File_00 §3.7.1 carries the broader external-validation note.

2.2 The logic

Active state: LXX 33 + 397 Sojourn division.

Therefore:

77 + 20 = 97
130 − 97 = 33
430 − 33 = 397
33 + 397 = 430

Modal-state note: The 33 years are not a separate variant added to the chronology. They are the Canaan segment produced by the LXX family-unit reading.

2.3 The convergence

Active state: LXX 33 + 397 inside the local 1876 BC convergence subset.

This interpretation places Jacob’s return from Haran, the moment when the children of Israel first dwell together in Canaan as a complete family unit, at 1876 BC.

This provides the fourth direct chronological fork in the broader File_16 convergence inventory. In this file, the row appears inside a six-row local convergence subset.

Node-class note: Rows 1 and 4 both concern Jacob but use different states and different event nodes. Row 1 is Jacob’s Entry under the MT / +215 Position. Row 4 is Jacob’s return from Haran under the LXX −33 / 33 + 397 state.

Dependency note: The 2nd Cainan row is retained as a File_16 convergence witness. File_04 does not locally re-prove the cumulative Cainan mechanism.

Argument note: The convergence table does not claim that all six rows are the same event. Its argument is that separate state-controlled mechanisms land different node-classes on the same year-label.

2.4 The +60 Terah mechanism

Active state: +60 Terah variator.

Node-class: Death of Terah = Call of Abraham.

Acts 7:4 states that Abraham left Haran after his father died. If Terah was 70 at Abraham’s birth, as a compressed reading of Genesis 11:26 may suggest, and if Terah lived 205 years, as Genesis 11:32 states, Abraham would have been 135 at Terah’s death:

205 − 70 = 135

This conflicts with Genesis 12:4, where Abraham is 75 at the Call.

The repository resolution is the +60 Terah mechanism: Abraham was born when Terah was 130, not 70. Therefore:

205 − 75 = 130
130 − 70 = 60
135 − 75 = 60

This makes Terah’s death coincide with Abraham’s Call at age 75. The +60 Terah adjustment is a separate variant mechanism that independently targets 1876 BC as the moment when Death of Terah = Call of Abraham.

Claim-status note: Acts 7:4, Genesis 11:26, Genesis 11:32, and Genesis 12:4 provide the textual data. The calculations are arithmetic facts. The +60 Terah resolution is a structural inference used by the repository to harmonize the textual data.

Arithmetic status: The local Terah arithmetic checks. The placement of the resulting convergence witness in the broader 1876 BC inventory remains cross-file controlled.

State note: The +60 Terah mechanism is not the LXX −33 mechanism and is not the Sojourn 215 mechanism. It belongs to the Abraham / Terah variator field.

2.5 Scope of the −33 adjustment

Active state: −33 scope register.

The standard repository scope is now the bounded Terah-through-Levi corridor. This supersedes the older Abraham–Levi-only shorthand. The textual 33 still comes from the LXX Exodus 12:40 “children of Israel” / Jacob-family-unit reading; extending the operator one generation upstream to Terah is an author-approved structural scope decision.

File_04 does not add Terah rows to its Jacob tables. Its local arithmetic remains the Jacob-family subset (1929/1909/1859 → 1896/1876/1826, Entry 1876→1843, Levi death 1782→1749). The detailed Terah 2203→1998 and composite 2263→2058 states are controlled by File_60; File_00 controls repository-wide scope.

Claim-status note: The −33 value is textual under the LXX reading. The Terah extension is structural/methodological. Global Noah/Adam −33 remains exploratory and dependency-controlled by File_00 and File_16.

Arithmetic note: No global −33 arithmetic is executed in File_04. The local −33 arithmetic is checked only in the Jacob matrix, the LXX 33 + 397 table, and the Levi death-state pair.

Cross-reference: File_00, §3.7, The −33 variant: nature and scope; File_02, Shem ±2 Anomaly; File_16, localized / global −33 validation.

2.6 Sojourn 215, Exodus 215, and LXX −33 firewall

Active state: variant-firewall register.

File_04 uses several state-producing mechanisms near the same anchor field. They must remain distinct.

State-control rule: Do not combine these mechanisms into a single undifferentiated variant. Each mechanism has its own question, node-class, and operator.

3. The logic engine

3.1 The Jubilee life

Active state: Jacob biography state.

Node-class: patriarchal lifespan.

Jacob’s lifespan of 147 years equals three Jubilee cycles:

147 = 3 × 49

Arithmetic status: The factorization checks.

Jacob therefore functions in this file as the patriarchal Jubilee standard.

Claim-status note: The lifespan value is a textual datum. The factorization is an arithmetic fact. The claim that Jacob functions as the patriarchal Jubilee standard is a structural inference built on that arithmetic and on the file’s broader Jubilee logic.

3.2 The −33 gear shift

Active state: LXX −33 structural comparison.

The −33 adjustment preserves the 430-year total while generating several state-controlled comparisons.

The −33 shift preserves the 430-year total and creates a set of harmonic comparisons with the patriarchal lifespans 180, 147, and 110. Jacob’s death in the +215 Position, 1859 BC, to Levi’s death in the LXX −33 position, 1749 BC, spans 110 years, echoing Joseph. The relation 147 + 33 = 180 echoes Isaac.

Node-class note: This section compares lifespan values and death-state values. It does not convert Jacob’s death into Levi’s death, nor does it make the −33 value a lifespan.

Claim-status note: The arithmetic checks are facts. The claim that these values form a coherent harmonic set is a structural inference. The language “gear shift” is a repository structural label, not a separate arithmetic operator.

Arithmetic note: The Levi death-state value 1749 BC is derived in §3.4.

3.3 The Daniel lock

Active state: LXX −33 position.

Node-class: Jacob’s Flight to Haran compared with the Conquest anchor.

Operator label: same-side BC span.

1896 − 1406 = 490
490 = 70 × 7

Arithmetic status: The same-side BC span and factorization check.

The LXX Flight to Haran at 1896 BC to the Conquest at 1406 BC places a 70 × 7 register inside the patriarchal narrative. The section title “Daniel lock” identifies the canonical association with Daniel’s Seventy Weeks.

Modal-state note: The 1896 BC date belongs to the LXX −33 Jacob biography row. It must not be replaced with the +215 Position Flight to Haran date, 1929 BC, when this lock is active.

Claim-status note: 1896 − 1406 = 490 and 490 = 70 × 7 are arithmetic facts. Calling the relation a Danielic lock is a typological / canonical reading anchored in the 70 × 7 register. It does not claim that Daniel 9 is explicitly referring to Jacob’s Flight to Haran.

3.4 The cubic lock

Active state: LXX −33 position applied to Levi’s death.

Node-class: Levi death-state compared with the Conquest anchor.

The Levi death values use the Jacob–Levi arc:

77 + 70 + 77 = 224

In the +215 Position:

2006 − 224 = 1782 BC

Equivalently:

2006 − 1929 = 77
1929 − 1859 = 70
1859 − 1782 = 77
77 + 70 + 77 = 224

Applying the LXX −33 state to Levi’s death:

1782 − 33 = 1749 BC

Therefore:

The cubic value appears under the LXX −33 state:

343 = 7 × 7 × 7 = 7³

Arithmetic status: The Jacob–Levi arc, the +215 Levi death value, the LXX −33 Levi death value, and the cubic lock all check under same-side BC subtraction.

State note: The values 1782 BC and 1749 BC are Levi death-state values. They are not Jacob death dates and do not define an Entry state.

Claim-status note: The span 1749 − 1406 = 343 and the factorization 343 = 7³ are arithmetic facts. The description “cubic lock” is a structural inference. It supports the significance of the LXX −33 state but should not be overstated as a standalone proof of authorial intent.

3.5 The Aaron/Moses luminary straddle

Active state: Aaron/Moses birth-phase register; Nisan default with optional Tishri retro-shift.

Node-class: cumulative Aaron/Moses branch labels and phase-resolved priestly operator.

The cumulative labels 1936/1933 BC preserve the visible integer branch relation in the Aaron/Moses register. They should not be treated as the whole operator.

The ordinary Nisan/Nisan birth-label branch preserves the three-year Aaron/Moses separation. The phase-resolved priestly branch preserves L = 3.5, the Tishri ↔ Nisan straddle, especially where the Aaron branch shifts six months earlier.

Terminology note: The +3.5 state functions as a half-week splitter inside the final Jubilee field. It must not erase the legitimate three-year birth-label state, and the three-year labels must not erase the phase-resolved L = 3.5 operator.

Arithmetic note: The printed labels 1936/1933 BC check as a visible integer difference of 3 years. The exact L = 3.5 value is a phase-resolved operator opened by the Aaron/Moses Nisan/Tishri state. It must not be recomputed by subtracting the printed integer labels.

Calendar-state note: This section opens the Nisan/Tishri phase-state explicitly. Elsewhere in File_04, unsuffixed BC dates remain ordinary date labels and should not be silently converted into .5 values.

Death-pair clarification: The Aaron/Moses death pair belongs to the wilderness close: Aaron dies in summer 1407 BC, and Moses dies in winter / at the beginning of the 1406 BC Conquest frame. The plague-period state 1447t/1446n is a distinct label-state and is not active in this section.

Claim-status note: The three-year branch and L = 3.5 phase-state are simultaneous modal representations. The statement that this straddle echoes later prophetic half-week structures is a structural inference. The broader fractal scaling into SKL and precessional .5 registers is dependency-controlled by later files, especially File_17, and is not made load-bearing in File_04.

File_61 downstream cumulative-root pointer: Corrected Final File_61 uses the regular Jacob–Levi and Aaron/Moses states controlled here as inputs to its cumulative-root synthesis. It controls the full clutch T14(C)=C−14, the exact midpoint rail H7(C)=C−7, the cumulative Jacob-to-Levi and Levi-to-Kohath rails, their translated landings on regular Isaac / Levi coordinates, and the inherited Joseph branches. These derived cumulative coordinates do not alter File_04's regular, LXX, Levi-death, or Aaron/Moses controls.

File_62 downstream 7+33 pointer: Final File_62 combines the File_61 half-clutch / full-clutch relation with File_04's localized −33 state in the generational form:

H → K = 7
K → V = 33
H → V = 40

Its principal examples are 2073 → 2066 → 2033, 1926 → 1919 → 1886, and 1789 → 1782 → 1749 BC. These are downstream hybrid comparisons. File_04 controls the −33 operator and the regular / LXX endpoints; Files 61–62 control the derived clutch coordinates, node-class firewalls, and full interpretation. File_04's own 1896 → 1406 = 490 LXX Daniel lock remains unchanged and distinct from File_62's 1929 → 1439 = 490 MT/Jacob carrier.

File_64 downstream Jacob final-70 / paired-930 pointer: Final full post-final pressure-tested File_64 uses File_04's standard endpoint rail:

1929 → 1909 → 1859 BC = 20 + 50 = 70

and localized LXX endpoint rail:

1896 → 1876 → 1826 BC = 20 + 50 = 70.

File_64 then locally derives the intermediate marriage-field labels 1922 BC and 1889 BC from Genesis 29's seven-year service, producing the downstream 7 + 13 = 20 comparison rails 1929/1922/1909 BC and 1896/1889/1876 BC. It carries the localized final-70 rail through its triple-430 Jacob–sanctuary–restoration lattice and compares both Jacob rails with the File_08-controlled Temple / palace construction rails. File_04 supplies the endpoint chronology, the localized −33, and shared-1876 BC non-collapse rule. File_64 controls 1922/1889 BC, the paired 930 comparisons, the Adam–Bethel and Jacob–Daniel interpretations, and all Kings / sanctuary coordinates. None of those downstream coordinates is promoted into File_04's Primary-anchor inventory or source biography rows.

4. Cross-reference index

Dependency note: The cross-reference index functions as dependency control. It does not import full proofs from other files into File_04.

Claim-status note: Cross-file references do not make the referenced material locally proven inside File_04. They identify which file supplies the governing proof, operator, modal-state rule, or later expansion.

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.

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

No pre-existing arithmetic, Primary anchors, biography rows, node-classes, sign conventions, local operators, slash-pairs, ranges, envelopes, Mirror protocols, claim-status labels, theological claims, or dependency boundaries are changed. The bounded amendment adds one downstream dependency state and one non-retrojection Machine Guard for Final File_64.