File: File_67 Title: The Flanking Kings of the Hezekiah Sign Subtitle: The Ahaziah–Athaliah `22+1=23` Fold, the Ahaz–Hezekiah–Manasseh Verbatim Chronology, and the Ramesside `480/490` Royal Field Status: Final; author-invoked Finalization and full post-final pressure-test baseline complete August 10 2026; bounded cumulative Creation mod-5 hub-pair amendment focused verified; State Vocabulary Register v1.39 / Restart Capsule v11.38 registration complete; seven bounded reciprocal-source replacements focused verified; Repository Change Archive v1.48 and Publication Manifest v20 release packages, raw-source index, sitemap, WordPress landing page, and publication layers prepared; no publication blocker; live deployment and external archival capture pending; bounded Final File_68 reciprocal pointer applied August 13 2026 Finalization status: Complete August 10 2026 — temporary Draft/Pass language removed or normalized; source-state and coordinate inventories expanded; Final-local Machine Guards added for derived Ramesside coordinates and whole-year/month-ledger separation; four omitted exact companion relations integrated (`441=21²`, `1951−701=1250`, `1851−701=1150`, and `1150×25/23=1250`); bounded post-Finalization amendment adds the co-registered cumulative `14011/14006 BC` mod-5 boundary pair, its uniform `13310` translation to the central `701/696 BC` Hezekiah hub pair, the `751→696→641→586 BC = 55+55+55` terminal rail, and the `14006→586 = 13420 = 122×110` continuation without reopening the original proof spine Verification status: The pre-Finalization Pass 2 draft verification `208/208 PASS` is retained as source history; Finalization added four exact companion rows, giving the full post-final pressure-test baseline of `212`; the bounded cumulative Creation mod-5 hub-pair amendment and central-hub refinement add nine exact arithmetic rows, giving a current manifest inventory of `221`; the amendment received focused arithmetic, state-firewall, Machine-Guard, Markdown-structure, dependency, and publication-clean verification; no second full-file pressure test is claimed Pressure-test status: Prior full post-final pressure test complete August 10 2026 and retained for the unchanged baseline — `212/212` arithmetic, `116/116` formal invariants, and `14/14` targeted dependency assertions PASS. The bounded cumulative Creation mod-5 hub-pair amendment and central-hub refinement received focused verification: nine new arithmetic rows PASS; the co-registration/state firewall, Machine Guard, tables, headings, fences, display-math balance, metadata, and publication-clean source PASS; no proof-bearing correction required; no second full-file pressure test is claimed; no publication blocker; focused reciprocal-routing verification complete August 13 2026 for the bounded File_68 pointer; no new full pressure test claimed Reciprocal-routing verification status: Bounded Final File_68 pointer applied and focused machine-diff, dependency, guard, and Markdown checks completed August 13 2026; no new full pressure test. Register Agreement status: Registered at State_Vocabulary_Register v1.39 Part D §D.31 and routed through Restart Capsule v11.38. All `21` File_67 Machine Guards are reproduced verbatim; seven reciprocal guards are registered for Files 08, 17, 22, 34, 51a, 65, and 66. No File_67 derived coordinate is promoted to the repository Primary-anchor inventory; File_22/File_51a co-registration and all parent proof burdens remain preserved; File_68 reciprocal guard registered at State Vocabulary Register v1.40 Part D §D.32 and routed through Restart Capsule v11.39; no pre-existing proof-bearing state or Primary anchor changed Publication-cleanup status: Public-clean Final canonical Markdown; current source incorporated into the coordinated File_67 v20 release package. State Vocabulary Register v1.39, Restart Capsule v11.38, pointer-only Style Guide v2.5 and Project Procedures v3.5 replacements, seven reciprocal source replacements, Repository Change Archive v1.48 addendum/assembler, Publication Manifest v20 CSV/XLSX, raw-source index, sitemap, landing-page source, publication snippets, checksums, and deployment audit files are prepared. No live overwrite, WordPress publication, cache purge, GitHub operation, or external archival capture is claimed. Source-history status: New repository file generated from the author-directed File_66 continuation discussion of August 10 2026; Finalization and full post-final pressure testing completed the same day; bounded cumulative mod-5 hub-pair amendment integrated after the baseline pressure test Primary domain: Regular; Comparative; Prophetic; Calendar; Theological Traditions: MT Hebrew Bible; Kings / Chronicles regnal traditions; Isaiah; subordinate Ramesside comparison; SKL and Berossus by appendix dependency; NT / Christological comparison by appendix Canonical source: Markdown Classification: Chronological Synthesis / Verbatim Royal Ledger / Applied Hezekiah-Sign Extension UUID: PROTOCOL_FLANKING_KINGS_HEZEKIAH_SIGN Primary textual corpus: Genesis 12–25 and 41–49; Exodus 3–40; Numbers 18; Joshua 24; 1 Kings 6, 8, 11, and 14; 2 Kings 8, 11, 16, 18–21, and 24–25; 1–2 Chronicles, especially 2 Chronicles 21–22, 28–33, and 36; Isaiah 7–8 and 36–39; Jeremiah 25 and 52; Daniel 9; Revelation 11–12 by appendix comparison Primary dependency-controlled and inherited anchors: 3901 BC; 2091 BC; 1951 BC; 1876 BC; 1826 BC; 1776 BC; 1526 BC; 1496 BC; 1476 BC; 1446 BC; 1445 BC; 1406 BC; 1261 BC; 1231 BC; 1191 BC; 1016 BC; 980 BC; 967/966 BC; 930 BC; 886n BC; 885n BC; 801 BC; 701 BC; 686 BC; 606/605 BC; 587/586 BC; 537/536 BC; 486 BC; co-registered cumulative Creation mod-5 boundary pair `14011/14006 BC` Local Verbatim/Schematic coordinates: Rehoboam birth label `1021 BC`; Ahaziah birth label `908 BC`; Ahaz birth label `761 BC`; Hezekiah birth label `750 BC`; Hezekiah accession `725 BC`; Hezekiah sign `711 BC`; Manasseh birth label `708 BC`; Hezekiah death / Manasseh accession seam `696 BC`; Manasseh terminal boundary `641 BC`; Amon birth label `663 BC`; Josiah death boundary `608 BC`; Zedekiah birth label `618 BC`; Zedekiah accession `597 BC`; Jerusalem boundary `586 BC` Actual/Historical comparison coordinates: Rehoboam birth label `971 BC` by comparison; Ahaz approximately `755 BC` under the co-regency age placement or `752 BC` under the simplified sole-accession chart; Ahaz co-regency approximately `735 BC`, sole accession `732/731 BC`, terminal `715 BC`; Hezekiah birth `740 BC`, co-regency `729/728 BC`, sole accession `715 BC`, crisis `701 BC`, death `686 BC`; Manasseh birth `709/708 BC`, co-regency `697/696 BC`, death `642 BC` Derived comparison coordinates: Adam death member `2971 BC`; File_66-derived Isaac birth `1851 BC`; Ramesside-origin Entry member `1661 BC`; Ramesside Moses birth `1311 BC`; Moses age-40 member `1271 BC`; Ramesside-translated Tabernacle `1230 BC`; generated `1181 BC` relay; Joshua death comparison `1151 BC`; Jubilee-`50` comparison member `751 BC`; standard-precessional relay `746 BC`; 536-based Berossus Flood companion `34616 BC` Appendix dependency-controlled deep-time anchors: SKL Short/Long Floods `20886/27366 BC`; SKL physical terminal anchors `2906/2856 BC`; SKL `+30` rails `2936/2886 BC`; Berossus Flood `34566 BC` Primary values: 1; 2; 3; 5; 7; 10; 11; 12; 13; 14; 15; 20; 21; 22; 23; 25; 29; 30; 32; 33; 36; 40; 41; 49; 50; 55; 69; 70; 71⅔; 72; 77; 91; 100; 110; 115; 120; 121; 122; 125; 147; 161; 165; 175; 207; 215; 216; 240; 273; 299; 300; 322; 345; 363; 400; 430; 441; 460; 480; 483; 490; 506; 520; 529; 550; 560; 600; 605; 644; 828; 840; 860; 908; 910; 930; 1020; 1075; 1080; 1100; 1150; 1200; 1210; 1250; 1290; 1470; 1518; 1656; 1950; 2300; 2350; 2400; 2450; 3174; 3900; 6480; 13310; 13420; 19656; 26136; 33120; 33600 Related files: File_00; File_01; File_04; File_05; File_06; File_08; File_10; File_12; File_13; File_15; File_16; File_17; File_18; File_19; File_20 by appendix dependency; File_21; File_22; File_24; File_26; File_29; File_34; File_51a; File_54; File_63; File_64; File_65; File_66; File_68 Major operators: same-side BC subtraction; uniform translation `T_d(x)=x-d`; vector translation; symmetric rail `R_h(c)=(c+h,c,c-h)`; Priestly completion `25/23`; Prophetic completion `70/69`; Enochian completion `300/299`; Key-gain formula `23m→25m` with gain `2m`; Key-gain formula `69m→70m` with gain `m`; Jubilee `49/50`; whole-system Ramesside translation `−215`; alternate and standard precessional-day maps `n×71⅔` and `n×72`; decimal `10×` comparison; whole-year regnal execution; civil cross-axis span `BC + AD − 1` only where explicitly opened in Appendix E Major modal states: File_66 downstream sign-extension state; Actual/Historical comparison state; Verbatim/Schematic exact-execution state; Ahaz–Hezekiah–Manasseh flanking-kings state; righteous-center / wicked-flanks theological state; Ahaziah `22+1=23` biographical-completion state; Ahaziah `22/42` textual-control state; `886/885 BC` completed/raw head distinction; Ramesside-origin hypothesis state; primary `1446 BC` / subordinate `1231 BC` hierarchy; Ramesside `1231/1191 BC` Exodus–Conquest rail; `886–725–711` Priestly fold; `120/110/100` royal-lifespan field; Moses/Joshua `550` translation state; co-registered cumulative Creation mod-5 boundary-pair state; central `701/696 BC` five-year hub-pair state; nested dual-rail elevenfold `110→1210→13310` carrier state; triple-`55` terminal rail state; `13420=122×110` continuation state; Rehoboam first-exclusively-Judahite boundary state; Zedekiah terminal-king boundary state; fourfold `480` comparison state; Jubilee `751/750 = 50/49` pair; symmetric `50`-rail carrier; finite `1290` closure state; decimal-fractal appendix state; precessional-companion appendix state; SKL/Berossus deep-time appendix state; Christological corroboration appendix state; open Judah-continuation state Revision basis: 490d Repository Style Guide v2.5; Project Procedures v3.5; Restart Capsule v11.37; State_Vocabulary_Register v1.38; Final File_66 through August 8 2026; Final File_65; Final File_64; File_22 and File_51a cumulative Creation controls; controlling dependencies listed above; author-directed discussion through August 10 2026; author-invoked Finalization and post-final pressure test August 10 2026; bounded cumulative mod-5 hub-pair amendment August 10 2026; State Vocabulary Register v1.39; Restart Capsule v11.38; bounded File_67 reciprocal-source replacements; Repository Change Archive v1.48 assembly package; Publication Manifest v20; Final File_68 after the August 13 2026 Finalization refresh; State Vocabulary Register v1.40; Restart Capsule v11.39 # File_67 — The Flanking Kings of the Hezekiah Sign *The Ahaziah–Athaliah `22+1=23` Fold, the Ahaz–Hezekiah–Manasseh Verbatim Chronology, and the Ramesside `480/490` Royal Field* ## Related Repository Files | File | Function for `File_67` | |---|---| | `File_00` | Controls repository-wide modal-state discipline, same-side versus cross-axis arithmetic, Key-of-23 family distinctions, source-map restraint, and providential claim-status language. | | `File_01` | Controls Abraham’s `1951/1876/1776 BC` MT Adjusted / SP-215 biography and the primary `2166/2091/1991 BC` MT Regular biography. | | `File_04` | Controls Jacob’s standard and localized `−33` rails, especially `1896/1876/1826 BC`, Jacob’s `147`, and the Entry / return / death node-class distinctions. | | `File_05` | Controls `1446 BC` as the primary Exodus anchor, `1231 BC` as the subordinate Ramesside state, the Sojourn-`215` / Exodus-`215` firewall, and the unresolved 1 Kings 6:1 proof burden. | | `File_06` | Controls primary and subordinate Conquest states, including `1191 BC` and the subordinate Joshua birth comparison `1261 BC`. | | `File_08` | Controls the Actual/Historical and Verbatim/Schematic Kings ledgers, `966/1016 BC` Temple states, and `930/980 BC` divided-kingdom states. | | `File_10` | Controls external-validation and providential multi-tradition language, including Berossus/SKL comparison restraints. | | `File_12` | Controls Priestly `336`, Prophetic `360`, Enochian `364`, solar/Julian states, and alternate/standard precessional-day vocabulary. | | `File_13` | Controls Christological date states, especially the preferred `AD 33n`, possible `AD 30n`, `1 BC` traditional hinge, and non-collapse of Passion and conception/birth display states. | | `File_15` | Controls the Abrahamic `100`, Jacobean `70`, and Mosaic `40` authorized generational units. | | `File_16` | Controls the `1876 BC` Nexus, Triple `430`, localized `−33`, and the great/lesser-Nexus dependency boundaries. | | `File_17` | Controls `25/23`, `70/69`, `300/299`, `480`, `490`, `1260`, `1290`, and precessional component grammar. | | `File_18` | Supplies chronological tables, including the `980 BC` Verbatim divided-kingdom head, `1445 BC` Tabernacle, `3901 BC` Minimum Year-6 state, and SKL base anchors. | | `File_19` | Controls the `701/686 BC` Hezekiah field, Dial of Ahaz, solar/time-sign comparison, `801 BC`, and the local precessional interface. | | `File_20` | Supplies the dependency-controlled `1671 BC` shifted Isaac-death comparison used only in Appendix B.5; File_67 does not reopen File_20’s chronology. | | `File_22` | Controls the actual cumulative `14011 BC` Day-1/start head, the `14006 BC` Year-6/Adam-state member, and their cumulative node-class distinction where §5.6 opens the paired landing. | | `File_21`; `File_24`; `File_34` | Control the SKL Short/Long states, intrinsic `50` terminal-anchor separation, `+30 Apparent Mode`, Berossus `486 BC` computational anchor, and the deep-time `480` relations used only in Appendix D. | | `File_26` | Controls `215/216`, `430/432`, `8600/8640`, and precessional-month/season comparisons. | | `File_29` | Controls the `7/13` Reconciliation Fractal and theological interpretation of `91`, `130`, `910`, and related values. | | `File_51a` | Controls Rounded Scaffold non-retrojection, the cumulative Rounded Creation mod-5 block `14011–14006 BC`, the `363` boundary-state calendar register, and appendix-level comparison restraint. | | `File_54` | Supplies comparative claim-status, Mirror-role, and appendix-only restraint. | | `File_63` | Controls scale-neutral `480/483/490` carrier precedent and the `1446/1496 BC` comparison field. | | `File_64` | Controls the lesser `1016 BC` Judges–Sanctuary Nexus and the inherited `1896/1876/1826 → 606/586/536 BC` triple-`1290` lattice. | | `File_65` | Controls A7/A6, the reverse Ahaziah–Athaliah `299/300` pincer, `886n/885n BC`, and the preferred comparative state boundaries. | | `File_66` | Immediate parent and controller of the `10`-back / `15`-forward sign engine, twin Hezekiah rails, A7 `50`, `115→125`, `185000/185150`, modulus-`11`, terminal `110`, and the Ramesside-origin hypothesis. | | `File_68` | Downstream Final use of File_67's finite Kings `20|50/1290` boundary, `1016/966` Temple pair, and appendix-only SKL `30×50` rectangle. File_67 retains the Verbatim/Schematic and boundary-kings proof burdens. | ### File_68 finite `20|50` / SKL `30×50` reciprocal note Final `File_68` uses File_67's finite Kings `20|50/1290` boundary and appendix-only SKL `30×50` rectangle as the outer and external controls of its Sanctuary/Kings synthesis. File_67 remains the controller of the Verbatim/Schematic royal field, boundary kings, finite allowance, and SKL/Berossus comparison state. Machine Guard [FILE_67 FILE_68 FINITE `20|50` / SKL `30×50` ROUTING]: Final File_68 may use File_67's `1896/1876/1826→606/586/536 BC` finite boundary and `2936/2886→2906/2856 BC` appendix rectangle inside its downstream Sanctuary-contraction argument. It does not extend File_67's fourth `1776→486=1290` column into invented Enochic coordinates, redefine the A7 or Verbatim/Schematic chronology, alter the Kings `+50` limit, promote `486 BC` to a historical restoration date, or import File_68 generated coordinates as File_67 Primary anchors. ## 0. File-function and controls ### 0.1 File-function `File_67` tests the extended effect of the File_66 Dial-of-Ahaz sign upon the kings immediately flanking Hezekiah and upon the opening and closing kings of the divided Judahite monarchy. The file begins from File_66’s controlling seed: ```text 10 backward + 15 forward = 25. ``` It does not re-prove that seed. It asks whether the Verbatim/Schematic chronology generated from the biblical accession ages and reign notices forms a coherent finite field around: - Ahaziah and Athaliah as the preceding dynastic fold; - Ahaz, Hezekiah, and Manasseh as the central theological triad; - Rehoboam as the first exclusively Judahite king after the division; - Zedekiah as the last reigning king before Jerusalem’s fall. The principal result is that the age-derived royal birth labels are not inert. They repeatedly lock to: - the subordinate Ramesside `1231/1191 BC` Exodus–Conquest rail; - the `886–725–711 BC` Priestly Key fold; - the `120/110/100` lifespan field; - the `50/49`, `480/490`, `215/216`, and `1290` carriers; - the established `586/536/486 BC` Fall–Restoration–Berossus field. ### 0.2 Thesis The exact Verbatim/Schematic chronology supplies the arithmetic precision that Actual/Historical reconstruction cannot supply by itself. Actual chronology remains indispensable for locating the Assyrian crisis at `701 BC` and for historical comparison. Its co-regencies, accession systems, synchronisms, and adjacent-year margins are expected features of reconstruction. Verbatim chronology instead executes the biblical reign notices at face value as an exact literary ledger. The file’s principal thesis is: > The Ahaziah–Athaliah fold and the Ahaz–Hezekiah–Manasseh triad provide the strongest concentrated Judahite corroboration yet found for the File_66 Ramesside-origin hypothesis. The canonical `1446 BC` Exodus remains primary at repository level, but the Verbatim royal dates repeatedly resolve with exact arithmetic against the subordinate `1231/1191 BC` Exodus–Conquest rail. ### 0.3 Scope and non-replacement rule `File_67` does not replace: - `File_66` as controller of the sign engine, A7 chronology, statistical result, `185000/185150`, or Appendix F historical hypothesis; - `File_05` as controller of `1446 BC` canonical priority and `1231 BC` subordinate status; - `File_08` and `File_18` as controllers of the Kings chronology; - `File_65` as controller of `886/885 BC` and A7/A6; - `File_34` as controller of SKL/Berossus derivation; - `File_13` as controller of Christological date states. The file strengthens a hypothesis by exact internal corroboration. It does not settle the source-critical meaning of the `480th year` in 1 Kings 6:1. ### 0.4 Mathematical grammar For same-side BC labels \(a>b\), define: \[ \Delta(a,b)=a-b. \] Define uniform forward-time translation: \[ T_d(x)=x-d. \] For vectors: \[ T_d(x_1,x_2,\ldots,x_n) = (x_1-d,x_2-d,\ldots,x_n-d). \] Define a symmetric three-node rail: \[ R_h(c)=(c+h,c,c-h). \] The principal rails are: \[ R_{50}(1826)=(1876, 1826, 1776), \] \[ R_{50}(751)=(801, 751, 701), \] \[ R_{50}(536)=(586, 536, 486). \] The Priestly Key gain formula is: \[ 23m\times\frac{25}{23}=25m, \] so the gain is: \[ 25m-23m=2m. \] The Prophetic Key gain formula is: \[ 69m\times\frac{70}{69}=70m, \] so the gain is: \[ 70m-69m=m. \] The alternate and standard precessional-day maps are: \[ P_a(n)=n\times71\tfrac23=n\times\frac{215}{3}, \] \[ P_s(n)=72n. \] Their difference is: \[ P_s(n)-P_a(n)=\frac n3. \] ### 0.5 Working state register | State | Primary form | Handling | |---|---|---| | File_66 downstream sign-extension state | `10+15=25` | Parent-controlled seed; not redefined. | | Verbatim/Schematic exact-execution state | biblical ages and reign durations | Primary arithmetic state of File_67. | | Actual/Historical comparison state | `701/686 BC` and reconstructed co-regencies | Historical control only; adjacent-year margins allowed. | | Ahaz–Hezekiah–Manasseh flanking-kings state | `761/750/708` births; `741/725/696` accessions; `641` boundary | Main royal field. | | Ahaziah biographical-completion state | `908→886→885=22+1=23` | Derived Verbatim birth label; Kings `22` controls. | | `886/885` dual-head state | completed `300` / raw `299` | Preserve both; do not collapse. | | Ramesside-origin hypothesis state | `1876/1661/1231/1191` original rail compared with `2091/1876/1446/1406` canonical rail | Author-proposed historical priority; non-load-bearing. | | `886–725–711` Priestly fold | `161=7×23→175=7×25` | Proof-bearing File_67 result. | | Royal lifespan field | `120/110/100` | Exact spans; distinct node-classes. | | Moses/Joshua translation state | `(1311, 1261, 1191)-550=(761, 711, 641)` | Exact shape-preserving translation. | | Co-registered cumulative Creation mod-5 hub-pair state | `T_{13310}(14011,14006)=(701,696)`; both pairs have width `5` | File_22 actual cumulative Day-1/Year-6 labels and File_51a cumulative Rounded Creation block boundaries share the same coordinate pair under declared states. The translation lands on the Actual/Verbatim central hub pair without collapsing the four state classes; `14006→696` carries the denser Verbatim continuation to `586`. | | Boundary-kings state | Rehoboam `1021`; Zedekiah `618` | Derived birth labels framing divided Judah. | | Fourfold `480` state | `1446→966`; `1496→1016`; `1231→751`; `1191→711` | Comparison-only; no event collapse. | | Symmetric `50`-rail carrier | `R50(1826)→R50(751)→R50(536)` | Uniform `1075`, then `215`, total `1290`. | | Inherited `20\|50` lattice | `1896/1876/1826→606/586/536` | File_64/File_65 dependency; distinct from symmetric rail. | | Appendix-only deep-time state | SKL/Berossus | Corroboration only; File_34 controls. | | Open Judah-continuation state | Amaziah and remaining kings | Heuristic only; no global proof. | ### 0.6 File map | Section | Function | Principal state / operator | |---|---|---| | §0 | File function, state controls, operators, guards | parent/child dependency; exact-execution rule | | §1 | Textual and theological flanking-kings frame | Ahaz–Hezekiah–Manasseh | | §2 | Verbatim and Actual chronology tables | `761/750/708`; `741/725/696/641` | | §3 | Ramesside `480/490` royal rail | `1231/1191`; `741/750/708/701` | | §4 | Ahaziah–Athaliah fold | `22+1=23`; `886/885`; `161→175` | | §5 | Royal `120/110/100` field | Moses/Joshua translation; nested `11`; cumulative mod-5 hub pair | | §6 | Rehoboam and Zedekiah boundary births | `41=5+36`; `12×69→12×70` | | §7 | 1 Kings 6:1 and the finite `50` carrier | four `480`s; `R50`; `1290` closure | | §8 | Synthesis and theological conclusion | scribal/providential tiers; finite scope | | Appendix A | Compact arithmetic manifest | proof-bearing equations | | Appendix B | Decimal/`10×` corroborations | secondary only | | Appendix C | Precessional/calendar companions | `215/216`; `1075/1080`; `161/162` | | Appendix D | SKL/Berossus closure | native `50`; `69×480→70×480` | | Appendix E | Christological corroboration | third day; solar sign; AD `33` lead | | Appendix F | Open continuation | Amaziah `25/29`; future Judah audit | ### 0.7 Claim-status register | Claim-status | File_67 use | |---|---| | Textual datum | accession ages, reign lengths, child-fire notices, third-day promise, ten-step sign, fifteen-year extension | | Source-retained chronology datum | parent-file anchors and reconstructed historical comparison dates | | Arithmetic fact | all displayed exact subtractions, factorizations, ratios, and translations | | Conditional arithmetic fact | results dependent upon Verbatim/Schematic, Ramesside, or generated comparison states | | Strong structural inference | repeated shape-preserving translations and exact Key gains | | Plausible scribal-design hypothesis | local arrangement of reign notices and boundary years | | Typological reading | Moses/Joshua, Abraham, exile/restoration, and Christological comparisons | | Providential synchronization | cross-system coherence exceeding demonstrable conscious scribal design | | Appendix-only | decimal, precessional, SKL/Berossus, and Christological corroborations not required by the main proof | | Audit note | node-class, source-state, textual, and chronology cautions | ### 0.8 Terminology controls **Flanking kings** means Ahaz and Manasseh immediately surrounding Hezekiah in the dynastic sequence. Ahaziah/Athaliah form the preceding fold; Rehoboam and Zedekiah form the divided-kingdom boundaries. **First exclusively Judahite king** means Rehoboam after the division. It does not imply moral purity. **Derived birth label** means accession boundary plus stated accession age. It is an exact Verbatim/Schematic coordinate, not a claim to an independently dated historical birth. **Cross-ledger center** means an Actual/Historical coordinate inserted into a Verbatim outer envelope. It is not a pure single-state midpoint. **Co-registered cumulative mod-5 boundary pair** means that the same `14011/14006 BC` labels function as actual cumulative Day-1/Year-6 coordinates under File_22 and as the boundaries of File_51a’s cumulative Rounded Creation mod-5 block. Shared labels do not collapse the actual-cumulative and Rounded states. **Ramesside-origin hypothesis** means File_66 Appendix F’s author-proposed historical priority of `1231 BC`, while `1446 BC` remains canonical and repository-operational. **Cross-system `50`-rail convergence** means independently existing `50` separations that align under larger exact carriers. It does not imply one historical mechanism generated every `50`. ### 0.9 Machine Guards Machine Guard [FILE_67 FILE_66 NON-REPLACEMENT]: `File_67` is a downstream application of `File_66`. It must not redefine the `10`-back / `15`-forward sign engine, A7 chronology, modulus-`11` result, `185000/185150`, or Ramesside-origin hypothesis. Machine Guard [FILE_67 ACTUAL / VERBATIM FIREWALL]: `701 BC` is Actual/Historical; `711 BC` is Verbatim/Schematic. The display `761→701→641=60+60` is a cross-ledger centering construction, whereas `761→711→641=50+70` is the pure Verbatim partition. Machine Guard [FILE_67 CUMULATIVE MOD-5 / HEZEKIAH HUB PAIR]: `14011/14006 BC` are co-registered coordinates: File_22 controls them as the actual cumulative Day-1/start and Year-6/Adam-state labels, while File_51a controls the same labels as the boundaries of the cumulative Rounded Creation mod-5 block. Their uniform `13310` translation to the `701/696 BC` Actual/Verbatim hub pair preserves a five-year width but does not identify the events, collapse actual-cumulative with Rounded states, collapse Actual with Verbatim chronology, or promote `701/696 BC` to cumulative Creation nodes. The `14006→696` column carries greater local File_67 weight because `696 BC` enters the triple-`55` terminal rail; it does not replace the companion `14011→701` column. Machine Guard [FILE_67 CANONICAL / RAMESSIDE HIERARCHY]: `1446 BC` remains the primary canonical Exodus anchor. `1231 BC` remains subordinate outside the File_66/File_67 Ramesside-origin hypothesis. File_67 strengthens but does not settle historical priority. Machine Guard [FILE_67 1 KINGS 6:1 BURDEN]: The four `480` comparisons do not resolve the ordinary historical meaning of the `480th year` in 1 Kings 6:1. The source-critical burden remains open. Machine Guard [FILE_67 DERIVED BIRTH LABEL]: `1021`, `908`, `761`, `750`, `708`, `663`, and `618 BC` are derived Verbatim/Schematic birth labels. Do not promote them to independently documented historical natal dates. Machine Guard [FILE_67 AHAZIAH `22/42` TEXTUAL CONTROL]: `22` in 2 Kings 8:26 is the controlling personal accession age. The `42` transmitted in MT 2 Chronicles 22:2 is a secondary scribal corruption: Ahaziah is called Jehoram’s youngest son, while 2 Chronicles 21:20 makes Jehoram approximately `40` at death. Do not execute `42` as an alternate biographical state or generate a `928 BC` birth label. Machine Guard [FILE_67 `886/885` DUAL HEAD]: `886n BC` is the completed `300` head; `885n BC` is the raw `299=13×23` head and succession boundary. Ahaziah’s `22+1=23` biography joins the heads without merging them. Machine Guard [FILE_67 `751 BC` NO-CONCEPTION CLAIM]: `751 BC` is a generated Jubilee-`50` / precessional comparison member. File_67 makes no historical claim for Hezekiah’s conception at `751 BC`. Machine Guard [FILE_67 KEY-FAMILY NON-COLLAPSE]: `25/23`, `70/69`, and `300/299` remain distinct operators. The appendix-only `162/161` calendar companion is not a fourth standard Key-of-23 operator. Machine Guard [FILE_67 PRECESSIONAL COMPANION]: `215/216` and `1075/1080` are alternate/standard precessional companions. Generated relay `746 BC` is not a historical node. Machine Guard [FILE_67 `20|50` / `50|50` NON-COLLAPSE]: The inherited `1896/1876/1826` lattice has interval vector `20|50`. The new `1876/1826/1776` rail has interval vector `50|50`. Shared coordinates do not make them one state. Machine Guard [FILE_67 BEROSSUS `536/486`]: `536 BC` is the historical restoration anchor; `486 BC` is the Berossus computational anchor. File_67 does not convert `486 BC` into a historical fall/restoration date. Machine Guard [FILE_67 SKL BASE / `+30` RAIL]: The native SKL terminal anchors are `2906/2856 BC`, separated by `50`. The `2936/2886 BC` pair is the already controlled `+30 Apparent Mode`, preserving the same `50`. Machine Guard [FILE_67 GENERATED DEEP-TIME COMPANION]: `34616 BC` is a generated `536`-based companion to the official Berossus Flood `34566 BC`. It is not a second textual or computational Berossus Flood anchor. Machine Guard [FILE_67 REHOBOAM `971` SHARED LABEL]: The derived Actual/Historical Rehoboam birth label `971 BC` must not be collapsed with File_51a’s Rounded `971n BC` monarchy member. Machine Guard [FILE_67 UNIFORM `215` / PINCER NON-COLLAPSE]: Uniform whole-system `215` translation preserves every interval. Fixed-center `215/430` pincer dilation moves endpoints in opposite directions around `1016 BC`. File_67 does not treat the two operators as interchangeable. Machine Guard [FILE_67 RAMESSIDE-DERIVED COORDINATES]: `1661`, `1311`, `1271`, `1230`, `1181`, and `1151 BC` are derived comparison coordinates within declared Ramesside or translated states. They are not independent textual dates or additions to the repository Primary-anchor inventory. Machine Guard [FILE_67 WHOLE-YEAR / MONTH-LEDGER FIREWALL]: The `663→641→608→586 BC = 22+33+22` display is a whole-year boundary construction. It does not replace File_66’s source-complete terminal month ledger or suppress the two three-month reigns that yield a `22.5`-year duration when month resolution is active. Machine Guard [FILE_67 APPENDIX NON-PROOF]: Appendices B–E corroborate but do not carry the principal proof. Removing them must leave §§1–8 intact. Machine Guard [FILE_67 GLOBAL JUDAH RESTRAINT]: File_67 does not prove that every king of Judah has been numerically resolved. Amaziah’s `25/29` remains an open clue. ### 0.10 Finalization and pressure-test note The Pass 2 inventory contained `208` exact relations. Finalization integrated four omitted companion relations, producing the `212`-relation full post-final pressure-test baseline; all `212` passed together with `116/116` independently declared formal invariants. The bounded cumulative mod-5 hub-pair amendment adds nine manifest rows, giving a current manifest inventory of `221`; all nine amendment rows, the co-registration firewall, and the refined dependency routing passed focused verification. No second full-file pressure test is claimed. No pre-existing proof-bearing equation was changed. ## 1. Hezekiah between Ahaz and Manasseh ### 1.1 The textual flanks Within the canonical royal notices, Ahaz and Manasseh are the two Judahite kings directly accused of causing a son or sons to pass through or burn in fire. For Ahaz: ```text וְגַם אֶת־בְּנוֹ הֶעֱבִיר בָּאֵשׁ “Even his son he caused to pass through the fire.” ``` (2 Kgs 16:3; compare the plural in 2 Chr 28:3.) For Manasseh: ```text וְהֶעֱבִיר אֶת־בְּנוֹ בָּאֵשׁ “He caused his son to pass through the fire.” ``` (2 Kgs 21:6; compare 2 Chr 33:6.) Hezekiah stands immediately between them and reverses their sanctuary conduct: - Ahaz closes and corrupts the Temple service; - Hezekiah opens the Temple in Year 1, Month 1 and restores worship; - Manasseh defiles the Temple precinct again. Ahaz’s apostasy is also political and architectural. Under attack from Aram and Israel, he appeals to Assyria, sends Temple and palace treasure, and imports the pattern of the Damascus altar into Jerusalem (2 Kgs 16). Hezekiah initially repeats the tribute response under Assyrian pressure, but tribute does not deliver the city; the decisive reversal comes through prayer, prophetic mediation, and YHWH’s intervention (2 Kgs 18–20; Isa 36–39). The sign on the steps of Ahaz therefore belongs naturally to the reversal of Ahaz’s Assyrian dependence. The Torah’s five-shekel redemption of the human firstborn may supply a cultic background to File_66’s fivefold grammar, but neither royal notice identifies the sacrificed child as a firstborn. File_67 does not use that point as proof. ### 1.2 Two temporal directions of mediation Hezekiah’s relation to Ahaz follows ordinary historical order: ```text Ahaz’s apostasy → inherited corruption → Hezekiah’s restoration. ``` His relation to Manasseh is proleptic: ```text Hezekiah’s extension → Manasseh’s birth → Manasseh’s accession → later apostasy and exile consequence. ``` The future does not cause the past. The theological claim is that divine providence is not constrained by the direction of ordinary human time. ### 1.3 The sign’s own bidirectional grammar File_66 already establishes: ```text 711 BC → 701 BC = 10 backward 701 BC → 686 BC = 15 forward 711 BC → 686 BC = 25. ``` The sign occurs on the: ```text מַעֲלוֹת אָחָז “steps of Ahaz.” ``` The structure associated with the apostate father becomes the place where YHWH demonstrates sovereignty over Assyria, the king’s death, Jerusalem’s delay, and measured time itself. Isaiah 37:30 further gives the deliverance a Sabbath/Jubilee resonance through `סָפִיחַ`, “self-grown produce,” the same noun used in Leviticus 25:5. Isaiah does not formally name a Jubilee; the lexical and numerical convergence supplies the controlled structural reading. The divine answer also joins the third day and the fifteen years: ```text בַּיּוֹם הַשְּׁלִישִׁי תַּעֲלֶה בֵּית יְהוָה “On the third day you shall go up to the house of YHWH.” ``` ```text וְהֹסַפְתִּי עַל־יָמֶיךָ חֲמֵשׁ עֶשְׂרֵה שָׁנָה “I will add fifteen years to your days.” ``` (2 Kgs 20:5–6.) ## 2. The Verbatim royal chronology ### 2.1 Primary Verbatim/Schematic table | King | Derived birth label | Age at accession | Accession | Internal hinge | Reign | Terminal boundary | |---|---:|---:|---:|---:|---:|---:| | Ahaz | `761 BC` | `20` | `741 BC` | — | `16` | `725 BC` | | Hezekiah | `750 BC` | `25` | `725 BC` | `711 BC` | `29=14+15` | `696 BC` | | Manasseh | `708 BC` | `12` | `696 BC` | — | `55` | `641 BC` | The arithmetic is exact: ```text 761 → 741 → 725 = 20 + 16 750 → 725 → 711 → 696 = 25 + 14 + 15 708 → 696 → 641 = 12 + 55. ``` ### 2.2 Actual/Historical comparison | King | Approximate birth | Co-regency / accession | Principal reign | Key event | Terminal | |---|---:|---:|---:|---:|---:| | Ahaz | approximately `755 BC` under co-regency age placement; `752 BC` under the simplified sole-accession chart | approximately `735`; `732/731` | to `715` | Assyrian alliance / altar field | `715` | | Hezekiah | `740 BC` | `729/728`; sole `715` | `715–686` | `701 BC` | `686` | | Manasseh | `709/708 BC` | `697/696`; sole about `686` | to `642` | — | `642` | The Actual table controls historical plausibility. The Verbatim table controls exact execution. A bounded literary hypothesis accompanies the distinction: Kings supplies denser synchronistic data and is especially useful for historical reconstruction, whereas Chronicles frequently foregrounds cultic and theological meaning. This is a difference of emphasis, not a global rule that Kings is merely historical and Chronicles merely schematic. ### 2.3 Manasseh partitions the fifteen The Verbatim labels give: \[ 711-708=3, \] \[ 708-696=12. \] Therefore: \[ \boxed{711\rightarrow708\rightarrow696=3+12=15.} \] The first three years follow Hezekiah’s sign. Manasseh is then born, and his stated twelve years to accession occupy the remainder of Hezekiah’s extension. This turns an abstract `3→15` relation into an exact chronological partition: \[ 3:12:15=1:4:5. \] ### 2.4 The `29` is structured, not inert Hezekiah’s reign is: \[ 29=14+15. \] File_66 also preserves: \[ 29=14+1+14. \] File_67 adds a third controlled context: the Priestly completion of `161` to `175` gains exactly `14`, landing from `725` on `711`. Section 4 executes that result. ## 3. The Ramesside royal rail ### 3.1 The Ramesside-origin rail and its canonical translation Under File_66 Appendix F’s Ramesside-origin hypothesis, File_67 derives the following complete original comparison rail: ```text 1876 BC Abraham Call 1661 BC Israel enters Egypt 1231 BC Exodus 1191 BC Conquest boundary. ``` Its durations are: \[ 1876-1661=215, \] \[ 1661-1231=430, \] \[ 1231-1191=40. \] Uniform backward translation by `215` in BC labels gives the canonical rail: ```text 2091 BC Abraham Call 1876 BC Israel enters Egypt 1446 BC Exodus 1406 BC Conquest boundary. ``` Thus: \[ 1876/1661/1231/1191 \xrightarrow{+215\text{ in BC labels}} 2091/1876/1446/1406. \] The translation preserves `215|430|40`. The `1661 BC` Entry member is derived within the hypothesis from the preserved `215/430` structure; it is not promoted to the repository Primary-anchor inventory. The comparison also explains why `1876 BC` is a Nexus coordinate: the proposed original Abraham Call and the canonical Israel Entry occupy the same year-label in the two rails. This remains the File_66 historical-chronographic hypothesis. File_67 tests its royal consequences. ### 3.2 The double-`490` rectangle The subordinate Ramesside chronology gives: \[ 1231-1191=40. \] The royal field gives: \[ 1231-741=490, \] \[ 1191-701=490, \] \[ 741-701=40. \] Thus: ```text 1231 BC ─────490─────▶ 741 BC │ │ 40 40 │ │ ▼ ▼ 1191 BC ─────490─────▶ 701 BC ``` The royal `40` is internally: \[ 741\rightarrow711\rightarrow701=30+10. \] Therefore: \[ 40+490=490+30+10. \] The wilderness delay and the Dial displacement occupy parallel sides of one exact field. ### 3.3 Hezekiah opens the final Jubilee; Manasseh opens the final heptad From the Ramesside Conquest: \[ 1191-750=441=9\times49=21^2, \] \[ 750-701=49. \] Therefore Hezekiah’s birth opens the tenth and final Jubilee: \[ 1191\rightarrow750\rightarrow701 = 9\times49+1\times49 = 490. \] Manasseh’s birth gives: \[ 1191-708=483=69\times7, \] \[ 708-701=7. \] Therefore: \[ 1191\rightarrow708\rightarrow701 = 69\times7+1\times7 = 70\times7 = 490. \] Hezekiah’s birth opens the final `49`; Manasseh’s birth opens the final `7`. Ahaz’s birth supplies the underlying Sojourn unit: \[ 1191-761=430. \] Hence: \[ 430+11+42+7=490. \] ### 3.4 Exodus, Flood, and Creation converge on Hezekiah’s accession The accession at `725 BC` is reached from three major heads: | Head | Span to `725 BC` | Exact form | |---|---:|---:| | Ramesside Exodus `1231 BC` | `506` | `22×23` | | Ramesside-shifted Flood `2243 BC` | `1518` | `22×69` | | Ramesside-shifted Creation `3899 BC` | `3174` | `2×23×69` | The Flood head is: \[ 2458-215=2243. \] Then: \[ 2243-725=1518=22\times69. \] The Creation-to-Flood span is: \[ 3899-2243=1656=24\times69. \] Therefore: \[ 3899-725 = (24+22)\times69 = 46\times69 = 2\times23\times69. \] The same accession is thus organized by the `23/69` Key family without generating a new endpoint. ### 3.5 The `12–15 ×40` ladder to the Verbatim sign The derived Ramesside Mosaic comparison rail is: ```text 1311 BC Moses birth 1271 BC Moses age 40 1231 BC Exodus / Moses age 80 1191 BC Moses death / Conquest boundary. ``` Measured to `711 BC`: \[ 1191-711=480=12\times40, \] \[ 1231-711=520=13\times40, \] \[ 1271-711=560=14\times40, \] \[ 1311-711=600=15\times40. \] The sequence is consecutive: \[ \boxed{12|13|14|15} \] in Mosaic `40`-year units. The Dial adds the ten-step companion: \[ 1191-701=480+10=490. \] ## 4. The Ahaziah–Athaliah fold ### 4.1 The `22/42` textual-control issue Second Kings 8:26 gives Ahaziah’s accession age as `22` and his reign as one year. The MT of 2 Chronicles 22:2 reads `42`, but this cannot be Ahaziah’s personal age: 1. 2 Chronicles 22:1 identifies him as Jehoram’s youngest son; 2. 2 Chronicles 21:20 makes Jehoram `32` at accession with an eight-year reign, approximately `40` at death; 3. a `42`-year-old Ahaziah would therefore be older than his father; 4. the coherent parallel in Kings gives `22`. File_67 treats `42` as a secondary scribal corruption and uses `22` as the controlling biographical datum. ### 4.2 The `22+1=23` biographical completion File_65 controls: - `886n BC` as the completed `300` head; - `885n BC` as the raw `299` head and succession boundary. Using the Kings age: \[ 908-886=22. \] The one-year reign is: \[ 886-885=1. \] Therefore: \[ \boxed{908\rightarrow886\rightarrow885=22+1=23.} \] The age notice and reign duration join the completed and raw heads. ### 4.3 The `908/885/701/586` Key-of-23 lattice From Ahaziah’s derived birth label: \[ 908-885=23, \] \[ 885-586=299=13\times23. \] Therefore: \[ 908-586 = 23+299 = 322 = 14\times23. \] The same outer span divides at the Hezekiah hinge: \[ 908-701=207=9\times23=3\times69, \] \[ 701-586=115=5\times23. \] Thus: \[ 14=1+13=9+5 \] in units of `23`. An adjacent display is: \[ 908\rightarrow885\rightarrow701\rightarrow586 = (1|8|5)\times23. \] ### 4.4 The Ramesside Tabernacle–Fall corridor The Ramesside-translated Tabernacle comparison is: \[ 1445-215=1230. \] Then: \[ 1230-908=322=14\times23, \] \[ 908-586=322=14\times23. \] So `908 BC` is the exact same-side midpoint: \[ \boxed{1230\rightarrow908\rightarrow586=322+322.} \] The complete corridor is: \[ 1230-586=644=28\times23. \] It admits three exact partitions: \[ 28=14+14 \] at Ahaziah’s birth; \[ 28=15+13 \] at the raw `885 BC` head; \[ 28=23+5 \] at the `701 BC` Hezekiah hinge. In full: \[ 1230\rightarrow908\rightarrow586=(14+14)\times23, \] \[ 1230\rightarrow885\rightarrow586=(15+13)\times23, \] \[ 1230\rightarrow701\rightarrow586=(23+5)\times23. \] The last gives: \[ 1230-701=529=23^2. \] ### 4.5 The one-year rectangle The Exodus–Tabernacle transition is: \[ 1231-1230=1. \] The Ahaziah–Athaliah transition is: \[ 886-885=1. \] And: \[ 1231-886=345=15\times23, \] \[ 1230-885=345=15\times23. \] Therefore: ```text 1231 BC ─────345─────▶ 886 BC │ │ 1 1 │ │ ▼ ▼ 1230 BC ─────345─────▶ 885 BC ``` ### 4.6 The `161→175` Priestly fold The complete Exodus-to-accession span is: \[ 1231-725=506=22\times23. \] The `886 BC` head partitions it: \[ 1231-886=345=15\times23, \] \[ 886-725=161=7\times23. \] Apply the Priestly Key only to the lower segment: \[ 161\times\frac{25}{23} = 7\times25 = 175. \] The gain is: \[ 175-161=14. \] Holding `886 BC` fixed: \[ 886-175=711. \] Thus: \[ \boxed{725\rightarrow711=14.} \] The accession route is: \[ 1231\rightarrow886\rightarrow725 = 15\times23+7\times23 = 22\times23. \] The sign route is: \[ 1231\rightarrow886\rightarrow711 = 15\times23+7\times25 = 345+175 = 520 = 13\times40. \] The Key-generated `14` coincides with: - Hezekiah’s Verbatim `725→711` pre-sign reign; - the first `14` in `29=14+15`; - the two `14` epochs in the historical co-regency / sole-reign comparison; - File_66’s `14+1+14=29` display. ### 4.7 The complementary `125/175` diamond The completed Ahaziah–Athaliah field is: \[ 886-586=300. \] It admits two complementary partitions: \[ 886\rightarrow761\rightarrow586 = 125+175, \] and: \[ 886\rightarrow711\rightarrow586 = 175+125. \] Therefore: \[ \boxed{300=125+175=175+125.} \] The four nodes are independently meaningful: - `886 BC`: completed dynastic head; - `761 BC`: Ahaz birth; - `711 BC`: Verbatim Hezekiah sign; - `586 BC`: Jerusalem’s fall. ## 5. The royal `120/110/100` field ### 5.1 The `120`-year Ahaz–Manasseh envelope The outer Verbatim field is: \[ 761-641=120. \] The pure Verbatim sign coordinate divides it: \[ 761-711=50, \] \[ 711-641=70. \] Therefore: \[ \boxed{761\rightarrow711\rightarrow641=50+70=120.} \] Insert the Actual/Historical hinge `701 BC`: \[ 761-701=60, \] \[ 701-641=60. \] Thus: \[ \boxed{761\rightarrow701\rightarrow641=60+60=120.} \] The Dial acts as a centering transformation: \[ (50, 70)\mapsto(50+10, 70-10)=(60, 60). \] The first display is pure Verbatim. The second is cross-ledger and shows the historical sign exactly centered within the Verbatim outer envelope. The continuation to Jerusalem gives: \[ 641-586=55, \] so: \[ 761-586 = 120+55 = 175. \] The royal field therefore reproduces Abraham’s lifespan as: \[ \boxed{60+60+55=120+55=175.} \] ### 5.2 The terminal `110` and the Manasseh `100` The Verbatim terminal body is: \[ 696-586=110. \] It divides: \[ 696-641=55, \] \[ 641-586=55. \] Therefore: \[ \boxed{696\rightarrow641\rightarrow586=55+55=110.} \] Manasseh’s birth to Josiah’s death boundary is: \[ 708-608=100. \] Thus the principal royal envelopes descend: \[ \boxed{120|110|100=10\times(12|11|10).} \] Their node-classes remain distinct: | Value | Royal span | Biblical comparison | |---:|---|---| | `120` | Ahaz birth → Manasseh boundary | Moses’ lifespan | | `110` | Manasseh accession → Jerusalem’s fall | Joshua’s lifespan | | `100` | Manasseh birth → Josiah death | Abrahamic post-call generation | ### 5.3 Amon, Josiah, and the `22|33|22` whole-year field Amon is `22` at accession. Under the Verbatim ledger: \[ 663-641=22. \] Amon’s reign plus Josiah’s reign is: \[ 2+31=33. \] Therefore: \[ 641-608=33. \] The whole-year boundary display to Jerusalem is: \[ 608-586=22. \] Hence: \[ \boxed{663\rightarrow641\rightarrow608\rightarrow586=22+33+22=77.} \] The first two members give: \[ 663-608=55. \] At source-complete month resolution, the two terminal three-month reigns add a half-year to part of the later sequence. The `22|33|22` display is explicitly whole-year and must not be used to erase the month ledger. ### 5.4 The `550` Moses/Joshua translation The Ramesside leader rail is: \[ 1311\rightarrow1261\rightarrow1191 = 50+70=120. \] Uniform translation by `550` gives: \[ T_{550}(1311, 1261, 1191) = (761, 711, 641). \] Therefore: \[ 1311-761=550, \] \[ 1261-711=550, \] \[ 1191-641=550. \] The lower rail preserves the same: \[ 50+70=120. \] Visually: ```text 1311 BC ──50──▶ 1261 BC ──70──▶ 1191 BC │ │ │ 550 550 550 │ │ │ ▼ ▼ ▼ 761 BC ──50──▶ 711 BC ──70──▶ 641 BC ``` Joshua’s subordinate death coordinate is: \[ 1261-110=1151. \] Then: \[ 1261-711=550=5\times110, \] \[ 1151-711=440=4\times110. \] Joshua’s lifespan is exactly the difference: \[ 550-440=110. \] ### 5.5 The `55` ladder from Conquest to exile From the Ramesside Conquest: \[ 1191-641=550=10\times55. \] The final royal segment is: \[ 641-586=55. \] Therefore: \[ 1191-586 = 550+55 = 605 = 11\times55. \] This extends the same modulus-`11` grammar already established in File_66 without treating the derived spans as independent statistical observations. ### 5.6 The cumulative Creation phase pair and nested elevenfold `110` carrier The adjusted/SP Abraham–Isaac birth interval is: \[ 1951-1851=100. \] The three-king reign envelope is: \[ 741-641=100. \] The two intervals are uniformly separated: \[ 1951-741=1210, \] \[ 1851-641=1210. \] And: \[ 1210=11\times110. \] Thus: ```text 1951 BC ─────100─────▶ 1851 BC │ │ 1210 1210 │ │ ▼ ▼ 741 BC ─────100─────▶ 641 BC ``` The `14011–14006 BC` pair is co-registered in two controlled cumulative states rather than functioning as one isolated head: - File_22 preserves `14011 BC` as the actual cumulative Day-1/start head and `14006 BC` as the internal Year-6/Adam-state member; - File_51a uses the same labels as the boundaries of the cumulative Rounded Creation mod-5 block. The shared labels do not merge the actual-cumulative and Rounded node-classes. Under either declared coordinate register, the pair has width: \[ 14011-14006=5. \] The central segment of the Hezekiah sign has the same width: \[ 701-696=5. \] Both cumulative coordinates translate by the same `13310` years: \[ 14011-701=13310, \] \[ 14006-696=13310. \] Therefore: \[ \boxed{T_{13310}(14011,14006)=(701,696)} \] and: \[ 14011-14006=701-696=5. \] The translated `701/696 BC` pair is the inner hub of File_66’s complete cross-ledger sign field: \[ \boxed{711\rightarrow701\rightarrow696\rightarrow686=10|5|10.} \] Equivalently: \[ (711,701,696,686)=(701+10,701,696,696-10). \] The carrier remains: \[ 13310 = 11\times1210 = 11^2\times110, \] so: \[ \boxed{110\rightarrow1210\rightarrow13310} \] is a nested dual-rail elevenfold carrier. The two landings have distinct local functions: - `14011→701` joins the cumulative Day-1/start head to the Actual/Historical sign hinge; - `14006→696` joins the cumulative Year-6/Adam member to the Verbatim Hezekiah-death / Manasseh-accession seam. Within File_67’s terminal royal field, `14006→696` is locally stronger because `696 BC` opens the established double-`55`/`110` sequence and also lies one additional `55` below the Jubilee-`50` comparison member `751 BC`: \[ 751-696=55, \] \[ 696-641=55, \] \[ 641-586=55. \] Thus: \[ \boxed{ 751\rightarrow696\rightarrow641\rightarrow586 = 55+55+55 = 165 = 3\times55 = 15\times11. } \] The `14006 BC` member then continues one complete `110` beyond its `13310` landing: \[ 14006-586 = 13310+110 = 13420 = 122\times110. \] This is the most concise reason `14006 BC` is locally stronger for the Verbatim terminal argument, while `14011 BC` remains equally necessary for the Actual/Historical `701 BC` landing. This remains a cross-modal and cross-register comparison: - `14011/14006 BC` are actual cumulative Day-1/Year-6 labels under File_22 and cumulative Rounded Creation mod-5 boundaries under File_51a; - `1951/1851 BC` are adjusted/SP comparison coordinates; - `741/641 BC` are Verbatim royal boundaries; - `701 BC` is Actual/Historical; - `696 BC` is the Verbatim terminal seam; - `751 BC` is a generated Jubilee-`50` comparison member. The arithmetic is exact; the unified design claim is structural/providential. ## 6. The boundary kings of divided Judah ### 6.1 Rehoboam’s `41=5+36` Rehoboam is `41` when he begins to reign. File_66’s Verbatim divided-kingdom head is `980 BC`. Therefore: \[ 1021-980=41. \] The schematic Temple foundation divides the age: \[ 1021-1016=5, \] \[ 1016-980=36. \] Thus: \[ \boxed{1021\rightarrow1016\rightarrow980=5+36=41.} \] On the Actual/Historical rail: \[ 971-966=5, \] \[ 966-930=36, \] \[ 971-930=41. \] The whole vector translates by `50`: \[ \boxed{T_{50}(1021, 1016, 980)=(971, 966, 930).} \] Visually: ```text 1021 BC ──5──▶ 1016 BC ──36──▶ 980 BC │ │ │ 50 50 50 │ │ │ ▼ ▼ ▼ 971 BC ──5──▶ 966 BC ──36──▶ 930 BC ``` The unsuffixed derived Rehoboam birth label `971 BC` must not be collapsed with File_51a’s Rounded `971n BC` monarchy member. Secondary Ramesside comparisons are: \[ 1231-1021=210=3\times70, \] \[ 1261-1021=240=6\times40. \] Rehoboam is therefore a load-bearing birth node at the opening of divided Judah. ### 6.2 The Adam–Abraham–Rehoboam–Christ alternating chain The Minimum Year-6/Adam state is `3901 BC`. Adam’s `930`-year lifespan gives the derived death member: \[ 3901-2971=930. \] Then: \[ 2971-1951=1020, \] \[ 1951-1021=930, \] \[ 1021-1=1020. \] Therefore: \[ \boxed{ 3901\rightarrow2971\rightarrow1951\rightarrow1021\rightarrow1 = 930|1020|930|1020. } \] The first three-node rail translates by `1950` into the second: \[ \boxed{ T_{1950}(3901, 2971, 1951) = (1951, 1021, 1). } \] Each half is: \[ 930+1020=1950. \] So: \[ 3901-1951=1950, \] \[ 1951-1=1950, \] \[ 3901-1=3900. \] The active node-classes are: - `3901 BC`: Minimum Year-6/Adam state; - `2971 BC`: derived Adam death member; - `1951 BC`: adjusted/SP Abraham birth; - `1021 BC`: Rehoboam’s derived Verbatim birth; - `1 BC`: traditional Christological hinge. Typologically the chain moves from Adam to Abraham as new-era patriarch, to Rehoboam as first exclusively Judahite king, to the one born King of the Jews. The typology does not carry the arithmetic. ### 6.3 Zedekiah’s `21+11=32` biography Zedekiah is `21` at accession and reigns `11` years. The Verbatim ledger gives: \[ 618-597=21, \] \[ 597-586=11. \] Therefore: \[ \boxed{618\rightarrow597\rightarrow586=21+11=32.} \] The derived `618 BC` birth label is the closing counterpart to Rehoboam’s `1021 BC` opening birth label. ### 6.4 The `12×69→12×70` completion From the canonical Exodus: \[ 1446-618=828. \] And: \[ 828=36\times23=12\times69. \] Apply the Prophetic Key: \[ 828\times\frac{70}{69} = 12\times70 = 840. \] The gain is: \[ 840-828=12. \] Holding `1446 BC` fixed moves the endpoint: \[ 1446-828=618, \] \[ 1446-840=606. \] Thus: \[ \boxed{618\rightarrow606=12.} \] The completed field is: \[ 1446-606=840=12\times70. \] The final exile/restoration unit is: \[ 606-536=70. \] Therefore: \[ \boxed{ 1446\rightarrow606\rightarrow536 = 12\times70+1\times70 = 13\times70 = 910. } \] `606 BC` closes the twelfth completed `70` and opens the thirteenth. This is the whole-year/schematic head. The adjacent historical `605 BC → 536 BC = 69` state remains distinct and reaches `70` through the already controlled `70/69` completion. ## 7. The `480` of 1 Kings 6:1 and the finite `50` carrier ### 7.1 The raw `115` and completed `125` The historical city delay is: \[ 701-586=115=5\times23. \] Apply the Priestly Key: \[ 115\times\frac{25}{23} = 125 = 5\times25. \] The gain is: \[ 125-115=10. \] Holding the `586 BC` Fall boundary fixed moves the head: \[ 701\rightarrow711. \] Therefore: \[ 711-586=125. \] Hezekiah’s Actual death partitions the completed field: \[ 711-686=25, \] \[ 686-586=100. \] Thus: \[ \boxed{711\rightarrow686\rightarrow586=25+100=125.} \] This parent-controlled File_66 completion is the immediate foundation for File_67’s `480` and `50/49` discussion. ### 7.2 Four exact `480` fields The repository already controls: \[ 1446-966=480 \] as the canonical Actual/Historical Exodus–Temple span, and: \[ 1496-1016=480 \] as the Kings Verbatim/Schematic counterpart. File_67 adds: \[ 1231-751=480, \] \[ 1191-711=480. \] Thus: | State | Head | Tail | Span | |---|---:|---:|---:| | Canonical historical | `1446` | `966` | `480` | | Kings schematic | `1496` | `1016` | `480` | | Ramesside–Hezekiah upper | `1231` | `751` | `480` | | Ramesside Conquest–sign | `1191` | `711` | `480` | The Ramesside result does not make `1231→966` equal `480`. It shows that the `480` measure survives on a translated Hezekiah-sign rail. ### 7.3 The `751/750 = 50/49` Jubilee pair From the Actual/Historical hinge: \[ 751-701=50. \] Hezekiah’s Verbatim birth gives: \[ 750-701=49. \] Therefore: \[ \boxed{751/750\rightarrow701=50/49.} \] The pair preserves the Jubilee boundary: - `751 BC`: full `50` comparison member; - `750 BC`: `49`-year Hezekiah birth member. The Ramesside Conquest-to-birth span is: \[ 1191-750=441=9\times49. \] The final `49` completes: \[ 441+49=490. \] ### 7.4 The Temple–patriarchal `215/50` carrier The historical Temple foundation gives: \[ 966-751=215. \] The adjusted/SP and localized Jacob field gives: \[ 1876\rightarrow1826\rightarrow1776=50+50=100. \] Define: \[ R_{50}(1826)=(1876, 1826, 1776), \] \[ R_{50}(751)=(801, 751, 701), \] \[ R_{50}(536)=(586, 536, 486). \] Then: \[ T_{1075}R_{50}(1826)=R_{50}(751), \] because: \[ 1876-801=1075, \] \[ 1826-751=1075, \] \[ 1776-701=1075. \] Next: \[ T_{215}R_{50}(751)=R_{50}(536), \] because: \[ 801-586=215, \] \[ 751-536=215, \] \[ 701-486=215. \] Therefore: \[ \boxed{ T_{1290}R_{50}(1826)=R_{50}(536). } \] The total is: \[ 1075+215=1290=6\times215. \] This is File_67’s `215/50` carrier in its simplest exact form. The upper rail is biographically meaningful: \[ 1876\rightarrow1776=100 \] is Abraham’s adjusted/SP post-call life, while Jacob’s localized `1826 BC` death sits exactly at its midpoint. ### 7.5 The inherited `20|50` lattice and the finite boundary File_64/File_65 already control: \[ 1896\rightarrow1876\rightarrow1826 = 20+50, \] translated by `1290` to: \[ 606\rightarrow586\rightarrow536. \] File_67 adds the fourth exact column: \[ 1776\rightarrow486=1290. \] Thus the combined corridor is: \[ \boxed{ (1896, 1876, 1826, 1776)-1290 = (606, 586, 536, 486). } \] Its interval vector is: \[ 20|50|50. \] This corridor defines the demonstrated boundary of the phase field. File_67 assumes no further propagation of the `50` beyond these independently occupied heads and termini. ### 7.6 The canonical inverse Moses/Joshua rectangle The Kings `50` also appears in the canonical Moses/Joshua field: \[ 1526-1476=50, \] \[ 1496-1446=50. \] The vertical spans are: \[ 1526-1496=30, \] \[ 1476-1446=30. \] Thus: ```text 1526 BC ─────50─────▶ 1476 BC │ │ 30 30 │ │ ▼ ▼ 1496 BC ─────50─────▶ 1446 BC ``` The center of Moses’ ordinary `80` years from birth to Exodus is: \[ 1526\rightarrow1486\rightarrow1446=40+40. \] The inner schematic/leader pair is: \[ 1496\rightarrow1486\rightarrow1476=10+10. \] Therefore: \[ \boxed{ 1526\rightarrow1496\rightarrow1486\rightarrow1476\rightarrow1446 = 30+10+10+30. } \] The canonical/Kings orientation moves Joshua’s birth backward `50` to Moses’ birth, while the Ramesside comparison moves Moses’ birth forward `50` to Joshua’s birth. The opposing orientations fit the bidirectional grammar of the sign. ## 8. Synthesis ### 8.1 Established arithmetic results The main body establishes: 1. the exact Verbatim royal biographies: \[ 761/741/725,\quad750/725/711/696,\quad708/696/641; \] 2. Manasseh’s: \[ 711\rightarrow708\rightarrow696=3+12=15; \] 3. the Ramesside double-`490`; 4. the Exodus/Flood/Creation accession anchors; 5. Ahaziah’s: \[ 908\rightarrow886\rightarrow885=22+1=23; \] 6. the `908/885/701/586` Key-of-23 lattice; 7. the `161→175` gain of `14`; 8. the `120/110/100` royal field; 9. the exact `550` Moses/Joshua translation; 10. the cumulative Creation phase-pair / central-hub carrier: \[ T_{13310}(14011,14006)=(701,696), \] with: \[ 110\rightarrow1210\rightarrow13310 \] and the terminal realization: \[ 751\rightarrow696\rightarrow641\rightarrow586=3\times55; \] 11. Rehoboam’s: \[ 41=5+36; \] 12. Zedekiah’s: \[ 12\times69\rightarrow12\times70; \] 13. four exact `480` fields; 14. the finite `215/50/1290` carrier. ### 8.2 Scribal and providential tiers Some local arrangements may reflect conscious scribal or compositional design: - selection and coordination of reign notices; - boundary-year handling; - the Ahaziah–Athaliah seam; - cultic and literary framing in Chronicles; - synchronistic density in Kings. The larger coherence may exceed demonstrable conscious design. File_67 therefore distinguishes: - arithmetic fact; - plausible scribal design; - providential synchronization. Providence does not erase human composition. Scribal ingenuity does not exhaust the proposed architecture. ### 8.3 Theological conclusion Hezekiah stands between two kings whose royal notices associate them with child fire and Temple apostasy. On the Ahaz side, Hezekiah repairs evil already committed. On the Manasseh side, the grace granted to Hezekiah precedes and contains the birth and accession-age interval of the son whose later reign becomes a principal cause assigned to exile. The Dial gives the theological grammar: ```text past evil → righteous mediation ← future evil ``` The shadow may move backward or forward. Hezekiah’s fifteen added years move forward naturally; the ten steps move backward. The same bidirectional field then governs the larger royal chronology. The file does not claim literal retrocausation. It claims providential governance in which past and future are equally open before God. ### 8.4 Finite scope and open continuation The remaining kings of Judah may participate in the same finite system. Amaziah’s age `25` and reign `29`, identical to Hezekiah’s pair, is a strong open clue. File_67 does not solve that continuation. Its bounded proof concerns: - the preceding Ahaziah–Athaliah fold; - Ahaz–Hezekiah–Manasseh; - the opening and closing divided-kingdom kings; - the continuation to `586/536/486 BC`. The remainder belongs to a later full-corpus Judah audit. ## Appendix A — Compact executed arithmetic manifest The full post-final pressure-test baseline contains `212` executable arithmetic relations: the `208` Pass 2 rows plus four Finalization-completion rows, all `212/212 PASS`. The bounded cumulative mod-5 hub-pair amendment adds nine manifest rows (`F6a–F6i`), all `9/9` focused PASS, giving a current manifest inventory of `221`. The following table retains the proof-bearing main-body rows. Appendix-only baseline rows remain in the original pressure-test report. ### A.1 Verbatim royal field | ID | Equation | Result | |---|---:|---:| | `A3` | `750 - 725` | `25` | | `A4` | `725 - 711` | `14` | | `A5` | `711 - 696` | `15` | | `A6` | `708 - 696` | `12` | | `A7` | `696 - 641` | `55` | | `A8` | `711 - 708` | `3` | | `A9` | `3 + 12` | `15` | | `A10` | `16 + 29 + 55` | `100` | | `A11` | `761 - 641` | `120` | | `A12` | `761 - 586` | `175` | | `A14` | `696 - 586` | `110` | | `A15` | `708 - 608` | `100` | | `A20` | `22 + 33 + 22` | `77` | ### A.2 Sign and Ramesside rail | ID | Equation | Result | |---|---:|---:| | `B4` | `1231 - 1191` | `40` | | `B5` | `1231 - 741` | `490` | | `B6` | `1191 - 701` | `490` | | `B7` | `741 - 701` | `40` | | `B9` | `1191 - 761` | `430` | | `B10` | `1191 - 750` | `441` | | `B10a` | `21 * 21` | `441` | | `B11` | `750 - 701` | `49` | | `B12` | `1191 - 708` | `483` | | `B13` | `708 - 701` | `7` | | `B14` | `1191 - 711` | `480` | | `B15` | `1231 - 711` | `520` | | `B18` | `480 + 10` | `490` | | `B19` | `441 + 49` | `490` | | `B20` | `483 + 7` | `490` | ### A.3 Exodus/Flood/Creation accession | ID | Equation | Result | |---|---:|---:| | `C1` | `2458 - 215` | `2243` | | `C2` | `2243 - 725` | `1518` | | `C3` | `1518 / 69` | `22` | | `C4` | `3899 - 725` | `3174` | | `C5` | `23 * 69 * 2` | `3174` | | `C6` | `3899 - 2243` | `1656` | | `C7` | `1656 / 69` | `24` | | `C8` | `1231 - 725` | `506` | | `C9` | `506 / 23` | `22` | ### A.4 Ahaziah–Athaliah and Priestly fold | ID | Equation | Result | |---|---:|---:| | `D1` | `908 - 886` | `22` | | `D2` | `886 - 885` | `1` | | `D3` | `908 - 885` | `23` | | `D4` | `885 - 586` | `299` | | `D6` | `908 - 586` | `322` | | `D8` | `908 - 701` | `207` | | `D10` | `701 - 586` | `115` | | `D12` | `1230 - 908` | `322` | | `D13` | `1230 - 586` | `644` | | `D15` | `1230 - 885` | `345` | | `D17` | `1230 - 701` | `529` | | `D19` | `1231 - 886` | `345` | | `D21` | `886 - 586` | `300` | | `D22` | `886 - 725` | `161` | | `D23` | `161 * 25 / 23` | `175` | | `D24` | `886 - 711` | `175` | | `D25` | `725 - 711` | `14` | | `D26` | `1231 - 711` | `520` | | `D28` | `886 - 761` | `125` | | `D29` | `761 - 586` | `175` | | `D30` | `711 - 586` | `125` | ### A.5 Moses/Joshua translation | ID | Equation | Result | |---|---:|---:| | `E1` | `1311 - 1261` | `50` | | `E2` | `1261 - 1191` | `70` | | `E3` | `1311 - 1191` | `120` | | `E4` | `1311 - 761` | `550` | | `E5` | `1261 - 711` | `550` | | `E6` | `1191 - 641` | `550` | | `E7` | `1151 - 711` | `440` | | `E8` | `1191 - 586` | `605` | | `E9` | `605 / 55` | `11` | ### A.6 Nested elevenfold carrier | ID | Equation | Result | |---|---:|---:| | `F1` | `1951 - 1851` | `100` | | `F2` | `741 - 641` | `100` | | `F3` | `1951 - 741` | `1210` | | `F4` | `1851 - 641` | `1210` | | `F5` | `1210 / 110` | `11` | | `F6` | `14011 - 701` | `13310` | | `F6a` | `14011 - 14006` | `5` | | `F6b` | `701 - 696` | `5` | | `F6c` | `14006 - 696` | `13310` | | `F6d` | `751 - 696` | `55` | | `F6e` | `641 - 586` | `55` | | `F6f` | `751 - 586` | `165` | | `F6g` | `165 / 55` | `3` | | `F6h` | `14006 - 586` | `13420` | | `F6i` | `13420 / 110` | `122` | | `F7` | `13310 / 1210` | `11` | | `F8` | `13310 / 110` | `121` | ### A.7 Rehoboam and Adam–Christ chain | ID | Equation | Result | |---|---:|---:| | `G1` | `1021 - 980` | `41` | | `G2` | `1021 - 1016` | `5` | | `G3` | `1016 - 980` | `36` | | `G7` | `1021 - 971` | `50` | | `G8` | `1016 - 966` | `50` | | `G9` | `980 - 930` | `50` | | `G12` | `3901 - 2971` | `930` | | `G13` | `2971 - 1951` | `1020` | | `G14` | `1951 - 1021` | `930` | | `G15` | `1021 - 1` | `1020` | | `G16` | `3901 - 1951` | `1950` | | `G17` | `1951 - 1` | `1950` | | `G18` | `3901 - 1` | `3900` | ### A.8 Zedekiah and Prophetic completion | ID | Equation | Result | |---|---:|---:| | `H1` | `618 - 597` | `21` | | `H2` | `597 - 586` | `11` | | `H3` | `618 - 586` | `32` | | `H4` | `1446 - 618` | `828` | | `H6` | `828 / 69` | `12` | | `H7` | `828 * 70 / 69` | `840` | | `H8` | `1446 - 606` | `840` | | `H9` | `618 - 606` | `12` | | `H10` | `606 - 536` | `70` | | `H11` | `1446 - 536` | `910` | | `H12` | `910 / 70` | `13` | ### A.9 Fourfold `480` and `215/50/1290` carrier | ID | Equation | Result | |---|---:|---:| | `I1` | `1446 - 966` | `480` | | `I2` | `1496 - 1016` | `480` | | `I3` | `1231 - 751` | `480` | | `I4` | `1191 - 711` | `480` | | `I5` | `751 - 701` | `50` | | `I6` | `750 - 701` | `49` | | `I7` | `966 - 751` | `215` | | `I8` | `966 - 750` | `216` | | `I15` | `1876 - 801` | `1075` | | `I16` | `1826 - 751` | `1075` | | `I17` | `1776 - 701` | `1075` | | `I18` | `801 - 586` | `215` | | `I19` | `751 - 536` | `215` | | `I20` | `701 - 486` | `215` | | `I21` | `1876 - 586` | `1290` | | `I22` | `1826 - 536` | `1290` | | `I23` | `1776 - 486` | `1290` | | `I24` | `1896 - 606` | `1290` | | `I25` | `1526 - 1476` | `50` | | `I26` | `1496 - 1446` | `50` | | `I27` | `1526 - 1496` | `30` | | `I28` | `1476 - 1446` | `30` | | `I29` | `1496 - 1486` | `10` | | `I30` | `1486 - 1476` | `10` | ## Appendix B — Decimal-scale and secondary finite-fractal corroborations ### B.1 Moses and Joshua at `10×` The adjusted/SP Abraham and derived Isaac birth members give: \[ 1951-751=1200=10\times120, \] \[ 1851-751=1100=10\times110. \] The File_66 `50` displacement gives: \[ 1951-701=1250, \] \[ 1851-701=1150. \] Thus: \[ 1200/1100\rightarrow1250/1150. \] The far Priestly completion already controlled by File_66 is: \[ 1150\times\frac{25}{23}=1250. \] Joshua’s subordinate death at `1151 BC` partitions the `1200` as: \[ 1951-1151=800, \] \[ 1151-751=400. \] Therefore: \[ \boxed{800+400=1200=10\times(80+40).} \] This is a tenfold copy of Moses’ `80+40=120` biography, with Joshua’s death supplying the internal boundary. ### B.2 Famine morphology Jacob enters the Egyptian field after two famine years, with five remaining: \[ 2+5=7. \] The localized Jacob rail gives: \[ 1896\rightarrow1876\rightarrow1826 = 20+50=70. \] Thus: \[ \boxed{2|5=7\quad\leftrightarrow\quad20|50=70.} \] The states are different; the coefficient morphology is the comparison. The lower national field is fittingly: \[ 606-536=70. \] Famine, siege, exile, and restoration therefore occupy compatible distress/restoration scales without requiring one event to be numerically identical with another. ### B.3 Jacob’s lifespan to restoration Jacob’s lifespan is: \[ 147=3\times49. \] From his regular birth to the restoration anchor: \[ 2006-536=1470. \] Thus: \[ \boxed{1470=10\times147=30\times49.} \] This places Jacob’s complete three-Jubilee lifespan at `10×` scale on the `536 BC` restoration terminus. Approximate fractional-year comparisons such as `77→7.7` are omitted from the Final source because the exact integer relations above are sufficient. ### B.4 The Ramesside Moses/Joshua `50` parallelogram The Hezekiah comparison pair carries the same `50` through a `480` draw-down: \[ 751+480=1231, \] \[ 701+480=1181. \] Adding Moses’ first `80` years gives: \[ 1231+80=1311, \] \[ 1181+80=1261. \] Thus: ```text 1311 BC ─────50─────▶ 1261 BC │ │ 80 80 │ │ ▼ ▼ 1231 BC ─────50─────▶ 1181 BC │ │ 480 480 │ │ ▼ ▼ 751 BC ─────50─────▶ 701 BC ``` `1181 BC` is a generated relay, not a historical anchor. The common `1261 BC` landing is independently Joshua’s subordinate birth comparison. The full vertical span is: \[ 560=14\times40. \] ### B.5 Isaac’s shifted death companion The adjusted/SP Isaac death comparison is `1671 BC`. Then: \[ 1671-751=920=23\times40. \] This is supporting corroboration only. ## Appendix C — Precessional and calendar companions ### C.1 The `3|12|15` precessional pair The royal partition is: \[ 3|12|15. \] Under the alternate `71⅔`-year precessional day: \[ 3\times71\tfrac23=215, \] \[ 12\times71\tfrac23=860, \] \[ 15\times71\tfrac23=1075. \] Therefore: \[ \boxed{3:12:15=215:860:1075.} \] Under the standard `72`-year day: \[ 3\times72=216, \] \[ 12\times72=864, \] \[ 15\times72=1080. \] The difference vector is: \[ 1|4|5. \] ### C.2 Existing-date absorption The historical Temple foundation generates: \[ 966-215=751, \] \[ 966-216=750. \] Thus the alternate/standard three-day pair lands directly on the already active `751/750` field. At fifteen days: \[ 1826-1075=751, \] \[ 1826-1080=746. \] Applying the same `50` translation: \[ 751-50=701, \] \[ 746-50=696. \] The standard relay `746 BC` is mechanically absorbed by the independently established Verbatim terminal seam `696 BC`; it is not promoted as a historical event. ### C.3 The `506→550` physical-calendar comparison The Priestly execution is exact: \[ 506\times\frac{25}{23}=550. \] Using File_12’s true-solar reference: \[ 506\times365.2422 = 184812.5532\text{ days}, \] while: \[ 550\times336 = 184800\text{ days}. \] The difference is only: \[ 12.5532\text{ days}. \] Thus `506` solar years are physically close to `550` Priestly `336`-day years across the complete span. This is calendar corroboration, not a replacement for the exact-rational proof. ### C.4 Brief palindromic `161/162` companion The established: \[ 161=7\times23 \] admits a minor calendar-side comparison: \[ 162\times363=58806\text{ days}, \] \[ 161\times365.25=58805.25\text{ days}. \] Residue: \[ 0.75\text{ day}. \] Optionally: \[ 4830\times\frac{162}{161}=4860=4830+30. \] The `162/161` companion is appendix-only. It is not a fourth standard Key-of-23 operator, and the `363`-day boundary-state register does not replace Priestly `336`, Prophetic `360`, Enochian `364`, or solar/Julian states. ## Appendix D — The `215/50` carrier and SKL/Berossus closure ### D.1 The native SKL `50` The physical SKL terminal anchors are: \[ 2906-2856=50. \] Their whole-year post-Flood reign totals are: \[ 20886-2906=17980, \] \[ 27366-2856=24510. \] The difference is: \[ 24510-17980=6530. \] Because the terminal anchors differ by `50`, the Floods differ by: \[ 6530-50=6480. \] And: \[ 27366-20886=6480. \] The `50` is therefore native to the SKL Short/Long system. The `+30 Apparent Mode` moves both anchors together: \[ 2906/2856\rightarrow2936/2886, \] preserving: \[ 2936-2886=50. \] ### D.2 Berossus and the two SKL Floods The controlled Berossus Flood is: \[ 34566\text{ BC}. \] Its distances from the SKL Floods are: \[ 34566-20886 = 13680 = 38\times360, \] \[ 34566-27366 = 7200 = 20\times360. \] Their difference remains: \[ 13680-7200=6480=18\times360. \] ### D.3 The `2936/2886` and `586/536/486` matrix Using the already controlled `+30` SKL rail: | SKL head | to `586` | to `536` | to `486` | |---:|---:|---:|---:| | `2936` | `2350` | `2400` | `2450` | | `2886` | `2300` | `2350` | `2400` | The lower row is generated from one fixed SKL head and the established `586/536/486` rail: \[ 2886-586=2300, \] \[ 2886-536=2350, \] \[ 2886-486=2400. \] `536 BC` remains historical restoration; `486 BC` remains computational Berossus anchor. ### D.4 The deep-time `480` theorem The official Berossus Flood is: \[ 486+34080=34566. \] For comparison only, the same total from the historical `536 BC` anchor gives: \[ 536+34080=34616. \] Thus: \[ 34616-34566=50. \] Now: \[ 33120 = 92\times360 = 69\times480 = 23\times1440. \] Subtracting: \[ 34616-33120=1496, \] \[ 34566-33120=1446. \] Therefore: \[ \boxed{ 34616/34566 \rightarrow 1496/1446 } \] by a uniform `69×480`. Apply the Prophetic Key: \[ 33120\times\frac{70}{69} = 33600 = 70\times480. \] The gain is exactly: \[ 480. \] Then: \[ 34616-33600=1016, \] \[ 34566-33600=966. \] Thus: ```text 34616/34566 │ 69×480 ▼ 1496/1446 │ 1×480 ▼ 1016/966 ``` At biblical scale, `480` separates Exodus and Temple. At Berossus scale, the same `480` is the gain from the sixty-ninth to the seventieth `480` block. `34616 BC` is generated comparison only; `34566 BC` remains the Berossus Flood controller. ### D.5 Ramesside Tabernacle and the `215/216` compatibility The primary Tabernacle anchor is `1445 BC`. Uniform Ramesside translation gives: \[ 1445-215=1230. \] Measured from the primary Exodus: \[ 1446-1230=216=3\times72. \] The SKL Long Flood gives: \[ 27366-1230 = 26136 = 363\times72 = 121\times216 = 66\times6\times66. \] The SKL Short Flood gives: \[ 20886-1230 = 19656 = 273\times72 = 91\times216. \] Their difference remains: \[ 26136-19656=6480. \] The `215` Ramesside translation therefore acquires its standard `216` companion through the natural one-year Exodus→Tabernacle succession without disturbing the SKL Short/Long architecture. ## Appendix E — Christological corroboration ### E.1 Date-state hierarchy `AD 33n` remains the repository’s preferred Passion state. `AD 30n` remains possible. The simpler whole-year display is: \[ 1231\text{ BC}\rightarrow AD\,30=1260 \] under the civil cross-axis convention. The fuller phase-resolved comparison uses the Ramesside Burning-Bush/plague-opening horizon and the preferred `AD 33n` Passion field by File_13 dependency. File_67 does not use either Christological result to prove the Judah chronology. ### E.2 Joshua and the traditional `1 BC` hinge The subordinate Joshua birth is: \[ 1261\text{ BC}. \] Under the traditional `1 BC` conception/Nativity phase member: \[ 1261-1=1260. \] Thus Joshua’s Ramesside birth stands exactly `1260` years before the traditional BC-side Christological hinge. ### E.3 The third-day solar-sign pattern Hezekiah’s field joins: - appointed death; - a supernatural solar/time sign; - healing; - third-day ascent to the Temple; - deliverance of Jerusalem; - Davidic covenant language. The Passion field joins: - the righteous Davidic king between two condemned men; - the title “King of the Jews” above him in three languages; - supernatural darkness beginning at noon; - the torn Temple veil at death; - resurrection on the third day. The comparison is typological/providential. It does not claim that the Gospel writers encoded File_67’s BC arithmetic. Revelation 12 supplies `1260` days; Revelation 11 separately supplies a `3.5`-day resurrection/standing comparison. Their combined use is appendix-level apocalyptic corroboration, not a textual claim that Revelation 12 itself contains the `3.5` days. ## Appendix F — Open continuation in the Judah ledger Amaziah is `25` when he begins to reign and reigns `29` years, the same conspicuous pair as Hezekiah. This may indicate that the full Judah ledger continues the same finite architecture. It is not yet proved. A later corpus-wide audit should predeclare: - the complete king list; - source ages and reign durations; - Actual and Verbatim states; - allowed operators; - generated-coordinate rules; - multiple-testing controls; - claim-status thresholds. Until that audit is executed, File_67’s proof remains bounded to the kings and corridors explicitly demonstrated here. ## Revision Log | Date | Stage | Result | |---|---|---| | August 10 2026 | Pass 1 — Unified drafting | Generated the complete File_67 source from the author-directed File_66 continuation discussion; established the flanking-kings, boundary-kings, `480/490`, `120/110/100`, `215/50`, and appendix structures. | | August 10 2026 | Pass 2 — Draft verification | Independently re-executed `208/208` arithmetic relations and verified the draft’s tables, headings, Machine Guards, fences, number formatting, and principal state firewalls. | | August 10 2026 | Author-invoked Finalization | Set `Status: Final`; removed temporary Draft/Pass language; expanded coordinate and deep-time inventories; added two Final-local Machine Guards; integrated four omitted exact companion relations without altering any prior result. | | August 10 2026 | Full post-final pressure test | Re-executed `212/212` arithmetic rows and `116/116` formal invariants; audited Finalization diff, source-state boundaries, dependencies, Machine Guards, Markdown structure, Hebrew/English quotation pairing, and publication cleanliness; no proof-bearing correction required. | | August 10 2026 | Bounded post-final cumulative Creation mod-5 hub-pair amendment | Added the co-registered `T_{13310}(14011,14006)=(701,696)` hub-pair translation, explicitly placed it on the inner `5` of the `10\|5\|10` Hezekiah field, added the `751→696→641→586 = 55+55+55` and `14006→586 = 13420 = 122×110` terminal realizations, one state Machine Guard, and nine arithmetic-manifest rows; focused verification complete; prior full pressure-test baseline retained. | ## Unresolved issues and deferred work - The historical priority of `1231 BC` over the canonical `1446 BC` Exodus remains the author-proposed File_66/File_67 Ramesside-origin hypothesis; 1 Kings 6:1 remains its principal source-critical counterweight. - File_67 does not prove a complete numerical resolution of every Judahite king. Amaziah’s `25/29` pair remains an open continuation clue. - File_67-specific vocabulary and all `21` Machine Guards are registered at State Vocabulary Register v1.39 §D.31 and routed through Restart Capsule v11.38. - Reciprocal-source review and seven bounded reciprocal replacements are complete. Repository Change Archive v1.48, Publication Manifest v20, index, landing-page, sitemap, and release artifacts are prepared; live publication and external archival capture remain external operations. ## Reciprocal-routing and release status The bounded reciprocal-routing pass is complete. 1. `File_66` registers File_67 as the downstream controller of the flanking-kings extension, including the `3+12=15` Manasseh partition, Ahaziah `22+1=23`, the co-registered cumulative mod-5 `T_{13310}(14011,14006)=(701,696)` hub pair, the royal `120/110/100` field, and the translated `480` comparisons. File_66 retains control of the Dial sign engine, A7 ledger, statistics, `185000/185150`, and Ramesside-origin hypothesis. 2. `File_65` registers the `908 BC` derived birth label and the `886/885 BC` completed/raw heads while retaining control of A7/A6 and the reverse Judah pincer. 3. Files 08, 17, 22, 34, and 51a register only the exact File_67 applications of their inherited chronology, Key-family, cumulative, SKL/Berossus, and Rounded controls. State Vocabulary Register v1.39 §D.31 and Restart Capsule v11.38 route the current File_67 state. Repository Change Archive v1.48 and Publication Manifest v20 assembly/publication artifacts are prepared. No live raw-source overwrite, WordPress publication, cache purge, GitHub operation, or external archival capture is claimed. ## Release-control note — August 10 2026 - Register / Capsule: v1.39 / v11.38 complete. - Reciprocal sources: Files 08/17/22/34/51a/65/66 bounded replacements complete and focused verified. - Archive / Manifest: v1.48 addendum/assembler and v20 full CSV/XLSX + patch package prepared. - Index / publication: raw-source index, sitemap, File_67 landing page, landing-index link, manifest-page update, deployment runbook, and external-capture list prepared. - Live deployment and external preservation: pending external operation.