Trust status: Final. The full post-final pressure-test baseline was completed August 4 2026. Bounded amendments through August 7 2026 — the MT Adjusted / SP-215 Abrahamic translation, Jeremiah pre-Fall ministry field, Ramesside-Origin Appendix F, Appendix G Mirror Closure, Isaiah 36–39 / Danielic refinement, and Manasseh–Zechariah 125/70 continuation — were separately focused pressure tested. The final center/midpoint terminology correction and latent 656 BC Manasseh mercy-node refinement are approved and focused-verified for the next canonical merge.
Canonical Markdown: File_66.Dial_of_Ahaz_Hezekiah_Jerusalem_Fifth_Expansion.md
Purpose
File_66 argues that the Dial-of-Ahaz sign is the interpretive key to the Hezekiah-centered relationship between Judah’s Actual/Historical and Verbatim/Schematic chronologies. The ten backward steps and fifteen added years form a complete 25-year sign-field. That seed expands backward through the A7 50-year royal gap, forward through Jerusalem’s 115 → 125 postponement, and outward through Abraham, Jeremiah, exile, restoration, the 185000/185150 precessional field, the 25800/25920/25921 celestial register, and the terminal royal ledger.
The file defines this as a finite arithmetic fractal: exact bounded self-similarity under declared dilation, translation, completion, and reflection/overlap operators. It does not claim an infinite geometric fractal, and it does not permit unused numerical cells to be promoted into chronology simply because they complete a pattern.
Principal architecture
10 + 15 = 25
10 × 5 = 50
15 × 5 = 75
50 + 75 = 125
701 → 586 = 115
115 × 25/23 = 125
711 → 586 = 125
1150 × 25/23 = 1250
1150 = 10 × 115
1250 = 10 × 125
1951 → 1876 → 1851 → 1776
75 25 75
801 → 726 → 701 → 626
75 25 75
185000 = 430² + 100
801 → 701 → 686 → 586 = 100 + 15 + 100 = 215
185150 × 7 = 50 × 25921
55 + 55 = 110
666 months / 6 kings = 111 months
Abrahamic and Jeremiah extension
The August 5 continuation exposes a second Abrahamic palindrome in the MT Adjusted / SP-215 comparison state:
1951 BC → 1876 BC → 1851 BC → 1776 BC
75 25 75
75 + 25 + 75 = 175
Uniform subtraction of 1150 preserves the entire form:
801 BC → 726 BC → 701 BC → 626 BC
75 25 75
The lower row lands successively on File_19’s backward 185000 landing, the schematic Samaria Node, Hezekiah’s historical crisis and deliverance, and the preferred Jeremiah-call / pre-Fall warning head. The previously formal fivefold forward limb is therefore occupied:
701 → 626 = 75 = 5 × 15
626 → 586 = 40
The 40 is the pre-Fall warning field, not Jeremiah’s total lifetime ministry.
Appendix F — the Ramesside-origin hypothesis
Appendix F tests a stronger but deliberately non-load-bearing historical-chronographic hypothesis: 1231 BC may preserve a latent Ramesside Exodus event horizon, while 1446 BC remains the repository’s primary canonical Exodus anchor and may represent a 215-year backward chronographic retrojection within the sign architecture.
1446 → 1231 → 1016 → 801 → 586
215 215 215 215
inner pincer: 1231 → 1016 → 801 = 215 + 215
outer pincer: 1446 → 1016 → 586 = 430 + 430
3 × 71⅔ = 215
3 × 72 = 216
6 × 71⅔ = 430
6 × 72 = 432
1231 → 1191 = 40
1191 → 701 = 490
The appendix preserves the source-critical burden of 1 Kings 6:1. It does not claim that the arithmetic by itself proves the historical priority of 1231 BC, nor does “retrojection” assert physical retrocausation.
Appendix G — Mirror closure and the delayed-judgment field
Appendix G tests whether the already established same-side structure remains coherent across the BC/AD polarity. It is system-level Mirror corroboration, not a premise required to make the main theorem work. The current integrated source includes the doubled 1290/1296 arms, the 427/429/430/432 = 2|1|2 corridor, paired 2150/2160 rails, the 1505 three-arm ladder, the Isaiah 36–39 deportation inclusio, Daniel’s first-deportation / restoration-era horizon, and the Manasseh–Zerubbabel continuation:
711 → 696 → 641 → 586
15 55 55
711 → 641 = 70
641 → 516 = 125
586 → 516 = 70
The preferred Actual/Historical death of Manasseh remains 642 BC; 641 BC is the A7 Verbatim/Schematic boundary. The file therefore keeps historical and schematic states separate.
Latest Manasseh mercy-node refinement
The approved August 7 refinement adds a generated 656 BC A7 mercy node inside Manasseh’s schematic 55-year field. Second Chronicles 33:11–13 supplies the undated narrative class — seizure, distress, humbling, prayer, divine hearing, and restoration to Jerusalem — but does not date either the removal or return. The proposed date therefore remains a strong structural / providential inference, not historical chronology.
711 → 696 → 656 → 641 → 586
15 40 15 55
15 + 40 + 15 = 70
55 + 15 + 55 = 125
70 + 70 − 15 = 125
711 + 586 = 1297
656 + 641 = 1297
1297 − 1 = 1296
1296 = 648 + 648
The two 648 values are civil half-spans, not year labels.
Textual and statistical controls
- Hezekiah is age
25when he becomes king, and in Month 1, Year 1 he opens and repairs the Temple. - The biblical promise joins fifteen added years, third-day Temple ascent, Hezekiah’s deliverance, and the deliverance of “this city.”
- The Hezekiah sign field is
711 → 701 → 686 = 10 + 15 = 25. - A7 is primary; A6 remains the completed-duration audit state. A7 gives the exact
1016 BCcenter of430 + 430; A61015 BCis an audit pivot, not an equal-arm center. - Under the declared A7 whole-year ledger,
29of171contiguous spans are divisible by11; the conditional permutation tail remains approximatelyp = 0.00612. The effect disappears under A6. - The source-complete terminal six-king ledger is
666months, averaging111months per king. - The Ramesside-origin interpretation remains appendix-only and preserves
1446 BCas the normal repository anchor. - The
656 BCManasseh mercy node is generated and providentially interpreted; it is not a historically attested captivity or release date and is not a Primary anchor. - Historical, schematic, reconstructed, latent, generated, astronomical, Mirror, and providential node-classes remain separate.
Visual companion
Kings of Judah — Actual versus Verbatim/Schematic chronology with divergence panel
The chart is explanatory. The proof-bearing layer remains the canonical Markdown file’s tables, declared operators, node-class controls, Machine Guards, and executed arithmetic manifest.