File_64 — The Jephthah–Judges Sanctuary Nexus

The 300/299 East-Jordan Key, the 430/450/490 Duration Ledgers, and the Lesser 1016 BC Jerusalem Nexus

This page is the public WordPress landing page for File_64 in the 490d Unified Chronology Knowledge Catalog.

Canonical Markdown source

The canonical Final, full post-final-pressure-tested Markdown source is here:

File_64.Jephthah_Judges_Sanctuary_Nexus.md

File function

File_64 applies the repository’s selected-list chronology method to the bounded duration corpus of Judges 3:8–16:31.

The file distinguishes two simultaneous registers:

  1. historical-theological chronology, in which regional oppressions, judgeships, rests, and deliverances may overlap in actual history;
  2. compositional-theological duration ledger, in which every eligible printed year-value is counted once under a declared literary-numerical operator.

Beginning with Jephthah’s 300-year east-Jordan statement, the file distinguishes the adjacent 300/299 rails, constructs the complete 111 + 299 = 410 Judges ledger, and demonstrates three different schematic routes—430, 450, and 490—that place 1016 BC at the opening, internal joint, and closure of the final Philistine–Samson 40 + 20 module.

The expanded synthesis then connects the lesser schematic 1016 BC Judges–Sanctuary Nexus with the great 1876 BC Genesis Nexus, Jacob’s final 70 years, Daniel’s terminal revelation, the Cainan–Terah rails, the Judah +50 and Israel +33 monarchy ledgers, paired 930 construction rails, and additional Joshua, census, and Flood comparisons.

Highlights

  • Distinguishes the three adjacent Jephthah states:1407 BC → 1107 BC = 3001406 BC → 1107 BC = 299 = 13 × 231406 BC → 1106 BC = 300The 1107 BC speech/accession state and the 1106 BC completed-boundary companion remain separate.
  • Computes the post-Jephthah source-order tail:6 + 7 + 10 + 8 + 40 + 20 = 91and therefore:1107 − 91 = 1016
  • Transcribes and conserves all eighteen eligible Judges year-periods:111 years of subjugation or oppression;299 years of rest, rule, or judgeship;111 + 299 = 410.Jephthah’s retrospective 300 is an interpretive key and is not counted as a nineteenth serial duration.
  • Establishes the three-position 1016 BC convergence:Direct Jephthah route40 + 299 + 91 = 430Explicit printed-duration route40 + 410 = 450Joshua-extended route40 + 40 + 410 = 490Under these three ledgers, 1016 BC marks respectively the closure, joint, and opening of the final 40 + 20 module.
  • Identifies 1016 BC as the lesser schematic Judges–Sanctuary Nexus, while preserving 967/966 BC as the historical Temple-foundation state.
  • Develops the great-and-lesser Nexus sequence:1876 BC → 1446 BC → 1016 BC → 586 BC430 + 430 + 430 = 1290The first 430 is the literal Entry-to-Exodus interval; the later two operate through the declared schematic sanctuary ledger.
  • Reads Judges 17–21 as the negative sanctuary image of the later Davidic–Solomonic resolution: private and rival worship, the corrupt Levite narratives, the rejection of Jebus, tribal civil war, and the repeated absence-of-a-king formula are answered canonically by Davidic kingship and the Jerusalem sanctuary.
  • Connects Jacob’s two final-70 rails with the sanctuary and restoration field:1929 → 1909 → 1859 BC = 20 + 50 = 701896 → 1876 → 1826 BC = 20 + 50 = 70and extends them through parallel 430 translations toward the Exodus, the lesser Nexus, Jerusalem’s fall, and restoration.
  • Preserves the Jacob–Daniel literary-theological closure: Jacob announces what will occur “in the latter days” before his death, while Daniel receives the terminal 1290/1335 revelation and is promised rest and an allotted inheritance at the end.
  • Distinguishes the principal Kings of Judah +50 sanctuary ledger from the lesser Kings of Israel +33 comparison and the already established Northern +36 route. These three constructions are related but non-collapsible.
  • Develops two parallel Jacob–construction rails separated coordinate-wise by 930 years:1929 / 1922 / 1909 BC → 999 / 992 / 979 BC1896 / 1889 / 1876 BC → 966 / 959 / 946 BCEach three-node rail follows the construction form 7 + 13 = 20.
  • Adds restrained comparisons involving the Bethel sleep-and-wife narrative, the double-400 land-rest and Joshua–Temple relations, the Joshua-centered triple-460 ladder, census–Judges palindromes, the Exodus-centered radius matrix, and subordinate Flood-Gear corroboration.

State and interpretation controls

The historical and schematic registers are complementary but must not be collapsed.

The east-Jordan 300, west-Jordan 299, and completed-boundary 300 are distinct states.

The direct 430, explicit 450, and Joshua-extended 490 are distinct ledgers. Their common use of 1016 BC does not make them one chronological operation.

The schematic 1016 BC Nexus does not replace the historical 967/966 BC Temple foundation and is not promoted to the repository Primary anchors inventory.

The Judah +50, Israel +33, and existing Northern +36 routes remain distinct. Alternative single-33 routes must not be accumulated.

The same-side BC radius matrix is an audit symmetry, not formal repository Mirror target-generation.

Arithmetic facts carry the primary proof. Structural inference, plausible scribal-design hypotheses, typological readings, literary-theological synthesis, and providential synchronization remain separately classified.

Verification and pressure-test status

File_64 is Final and full post-final pressure-tested.

The completed July 27 2026 audit records:

  • 3076/3076 core substantive checks PASS;
  • 3078/3078 final trust-status closure checks PASS;
  • 116/116 Appendix C rows verified;
  • 190/190 atomic Appendix C operations recomputed;
  • 318/318 parseable body arithmetic displays checked;
  • all eighteen Judges duration rows and running totals verified;
  • 54/54 Markdown tables and 714/714 table rows structurally valid;
  • fifty total Machine Guards present and unique;
  • 337/337 fenced blocks paired;
  • 67/67 protected baseline sections exact;
  • no proof-bearing arithmetic correction required;
  • no publication blocker.

Related repository files

Source-custody note

The Markdown file linked above is the canonical source. This WordPress page is a public landing and discovery page.

The Repository Change Archive preserves historical research, revision, verification, Finalization, pressure-test, reciprocal-routing, and control-registration records, but it is non-controlling.

Related catalog links