File: File_19
Title: The Hezekiah Prophetic Complex
Status: Final; post-final literal Temple 430 coreference patch applied; pressure tested; Samaria Node cross-file update applied and focused pressure tested under current Register Agreement; File_34 Pillar-state citation-control update applied and focused pressure tested June 3 2026
Pressure-test status: Current; focused pressure test complete for the Samaria Node cross-file update and public-clean cleanup; File_34 Pillar-state citation-control update focused pressure tested June 3 2026; post-final Temple 430 coreference pressure test retained.
Register Agreement status: Checked against State_Vocabulary_Register v1.17 and active companion controls; convergence / pointer update only; no arithmetic, anchors, modal states, node-classes, operators, sign conventions, slash-pairs, ranges, envelopes, Mirror protocols, Machine Guards, claim-status labels, theological claims, or dependency boundaries changed.
Publication-cleanup status: Public-clean Markdown source; archival amendment history routed to Repository_Change_Archive.
Primary domain: Prophetic; Regular; Comparative; Calendar; Theological; Mirror
Traditions: Isaiah / Kings; Levitical / Jubilee; Exodus / Conquest; Daniel / Ezekiel; NT / Christological
Canonical source: Markdown
Primary anchors: 701 BC; 686 BC; 1421 BC; 1406 BC; 1191 BC; 1446 BC; 1231 BC; 1876 BC; 1017/1016 BC; 967/966 BC; 801 BC; 735/734 BC; 670 BC; 588 BC; 586 BC; 539 BC; 537/536 BC; AD 1; AD 20; AD 30; AD 35; AD 60; AD 184315; AD 29515; 185701 BC; 269286 BC; 4116 BC; 1445 BC; ~725 BC; 726–721 BC; late 722 BC ±1; 2091 BC
Related files: File_00; File_05; File_06; File_07; File_08; File_10; File_13; File_16; File_17; File_18; File_34; File_51a; File_54; Restart Capsule v11.15; 490d Repository Style Guide v2.5; Project Procedures v3.2; State Vocabulary Register v1.17
Major operators: count-to-chronology; same-side BC subtraction; same-side AD subtraction; civil cross-axis span `BC + AD − 1`; precessional degree `10 × 72 = 720`; Great Year `25920`; `490 + 15 + 215 = 720`; Samaria Node / Immanuel `720` overlay; `1446 → 726 = 720`; `726 → 6 = 720`; `721 → 1 = 720`; `430 × 430`; `430 × 432`; `430 × 429`; Jubilee `49`; Danielic `490`; `7 × 490`; `15 × 49`; `3.5 × 430`; `3.5 × 360`; `1260`; `1290`; Key of 23; `115 = 23 × 5`; alternate precessional-day display `71⅔ = 215/3`; `390 + 40 = 430`; `14 + 1 + 14 = 29`; `2150 = 5 × 430 = 10 × 215`; Kings ledger `394.5`; Temple block `36 + 394.5 = 430.5`; schematic Temple-month bridge `1016 BC` second month → Tammuz/Av `586 BC`; literal post-exilic coreference `967 BC` second month → `537 BC` second month = `430`; `49/50` dual-ledger separation; Exodus-to-Fall double block `1446 BC → 586 BC = 860 = 2 × 430 = 4 × 215`
Major modal states: Hezekiah 701/686 BC field; Dial of Ahaz precessional state; bidirectional prophetic span / sundial mirror; count-to-chronology state; deep-time 185000-year state; AD 29515 actual Pillar state; primary Exodus state; subordinate Ramesside Exodus state; primary Conquest state; subordinate Ramesside Conquest state; Jubilee / Sabbatical harmonic state; Creation Year-6 state; Immanuel conception/birth state; Immanuel 65/49 crossing state by File_17 dependency; Samaria Node / Immanuel 720 overlay state by File_00 dependency; time-manipulation witness state; Christological target state; Kings of Judah master-ledger state; Temple-month 430.5 bridge state; literal post-exilic 430 coreference state; 49/50 dual-ledger awareness state; Hezekiah 14 + 1 + 14 reign chiasm
Revision basis: 490d Repository Style Guide v2.5; Restart Capsule v11.15; State Vocabulary Register v1.17; Project Procedures v3.2; prior finalized source; Repository_Change_Archive (non-controlling history)
Current refresh note: Public-clean trust-status equalization aligns active control pointers to 490d Repository Style Guide v2.5, Restart Capsule v11.15, State_Vocabulary_Register v1.17, and Project Procedures v3.2. Register Agreement status is recorded in the header; no arithmetic, anchors, modal states, node-classes, operators, sign conventions, slash-pairs, ranges, envelopes, Mirror protocols, Machine Guards, claim-status labels, theological claims, or dependency boundaries are changed. Detailed pass logs, pressure-test records where applicable, pointer-refresh history, and replacement-workflow notes are preserved in Repository_Change_Archive.

# File_19 — The Hezekiah Prophetic Complex

## Related Repository Files

| File | Function for `File_19` |
|---|---|
| `File_00` | Controls the Count-to-Chronology Axiom, Key of 23, Variant Mechanism, Mirror / civil / inverse firewall, source-map discipline, and Samaria Node / Immanuel `720` overlay state. |
| `File_05` | Controls the primary `1446 BC` Exodus state, subordinate `1231 BC` Ramesside Exodus state, Sojourn 215 / Exodus 215 distinction, and `3.5 × 430` / `3.5 × 360` target logic where opened. |
| `File_06` | Controls subordinate Ramesside Conquest-side language, especially `1191 BC`, and Conquest-to-Christ cross-axis states where opened. |
| `File_07` | Controls Creation-week and Creation Year-6 states, including `4116 BC` and the Creation / Tabernacle comparison field. |
| `File_08` | Controls the Kings-era Hezekiah Jubilee / Sabbatical harmonic `1191 BC → 701 BC = 490`, the Kings / Fall of Jerusalem field, the parent monarchy ledger, the `1016 BC` schematic pivot, and the `967/966 BC` historical Temple foundation adjacent-state. |
| `File_10`; `File_34` | Deep-time / external-validation controls for registering `AD 29515` as the actual Pillar state and preventing bleed with distinct Pillar-adjacent nodes. File_34 is now cited as Final; post-final pressure-tested control for the Pillar / AD target state and civil cross-axis span guard. |
| `File_13` | Controls Christological anchor states where `AD 1`, `AD 30`, `AD 35`, `AD 60`, Passion, Incarnation, or NT fulfillment claims are opened. |
| `File_16` | Controls `1876 BC` Nexus logic, Danielic locks, Famine / Exile windows, Mirror classification, and Bullseye-style convergence claim restraint. Recommended cross-file update: classify the local Hezekiah language as bidirectional prophetic span / sundial mirror. |
| `File_17` | Controls Prophetic Time Span Anatomy, including `430`, `490`, `1260`, `1290`, precessional display states, Key-of-23 component grammar, the transferred Immanuel macro-chiasm, the monarchy ledger baseline, and the `537/536 BC` post-exilic return / foundation field where opened. |
| `File_18` | Supplies raw chronological data where table-source verification is required. |
| `File_51a`; `File_54` | Supply state-register, File map, Machine Guard, Mirror classification, appendix-only, and claim-status precedent for later-file style. |

Dependency note:
`File_19` is an applied prophetic demonstration file. It does not replace the anchor definitions in `File_05`, `File_07`, `File_08`, `File_13`, `File_16`, or `File_17`. Where the source invokes Exodus, Conquest, Creation Year-6, Immanuel, Christological, Mirror, Danielic, or monarchy-ledger states, those controls remain dependency-governed unless this file supplies the local arithmetic.

File_34 post-final Pillar-state citation-control note:
`File_34 Final; post-final pressure tested` confirms the current dependency boundary for the Pillar / AD target state. In `File_19`, `AD 29515` remains the only active Pillar node, and the local arithmetic remains `184315 − 29515 = 154800 = 430 × 360`. This update does not reopen File_34's SKL / Berossus derivation, Appendix B phase-chain machinery, or civil cross-axis Pillar spans inside File_19.

## 0. File-function

`File_19` records the Hezekiah prophetic complex as an applied demonstration of the Count-to-Chronology Axiom.

The file argues that the Hezekiah narrative gathers multiple numeric units into one prophetic time field:

| Narrative datum | Local function |
|---|---|
| `185000` slain Assyrians | count-to-chronology projection into `185000` years |
| `10` degrees / steps | precessional `720`-year state |
| `15` years of life extension | Hezekiah bridge from `701 BC` to `686 BC` |
| `3` days to the temple | delayed-judgment and alternate precessional-day encoding |

Publication-cleanup note:
This public-clean source preserves the Final, pressure-tested, focused-pressure-tested, and now-current bounded-update labels in the header. Detailed pass logs, bounded update records, pressure-test repetition, and replacement-workflow notes are archived rather than repeated in the public body.

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

Argument-control rule:
Arithmetic facts and textual data carry the base layer. Structural inferences explain how checked spans interlock. Theological and typological claims explain why a structure matters, but they do not replace arithmetic or dependency control. Probability language is retained only as a source claim and is classified as providential synchronization unless a formal statistical model is supplied.

### 0.1 Working state register

The following states are active in this Final source. They are simultaneous, non-competing states unless a later cross-file update narrows the working state.

| State | Primary values / forms | Node-class / function | Handling in `File_19` |
|---|---:|---|---|
| Hezekiah field | `701 BC`; `686 BC`; `15` | siege / deliverance field; extended death | `701 BC` and `686 BC` remain the local anchor pair. The `15`-year bridge must remain visible. |
| Dial of Ahaz precessional state | `10` degrees; `720`; `25920`; `72` | precessional demonstration | `10 × 72 = 720`; `25920 × 1/36 = 720`. |
| Bidirectional prophetic span / sundial mirror | forward and backward `720`; forward and backward `185000` | local sundial physics / Mirror corroboration | Local language is sundial-mirror language, not foundational Deep-Time Mirror protocol. |
| Count-to-chronology state | `185000`; `10`; `15`; `3` | narrative units lifted into prophetic time | Core local file state. |
| AD Pillar state | `AD 29515`; `154800`; `430 × 360` | actual Pillar landing from `AD 184315` | `184315 − 29515 = 154800 = 430 × 360`. No BC-side Pillar coordinate is retained in the local argument. |
| Adam cumulative deep-time row | `269286 BC`; `AD 184315`; `453600`; `1260 × 360` | cumulative / deep-time relation | Checks by civil cross-axis span: `269286 + 184315 − 1 = 453600`. |
| Primary Exodus state | `1446 BC` | primary Exodus anchor | Controlled by `File_05`. |
| Subordinate Ramesside Exodus state | `1231 BC` | subordinate Exodus harmonic | Controlled by `File_05`; does not replace `1446 BC`. |
| Primary Conquest state | `1406 BC` | primary Conquest anchor | Controlled by `File_06` / `File_08`. |
| Subordinate Ramesside Conquest state | `1191 BC` | subordinate Conquest harmonic | Supports `1191 BC → 701 BC = 490`; does not replace `1406 BC`. |
| Jubilee / Sabbatical harmonic state | `490`; `49`; `3430`; `70 × 49` | Jubilee / Sabbatical structure | Main body proof field, tied to Isaiah 37:30 and File_08. |
| Creation Year-6 state | `4116 BC` | Adam / Year-6 anchor | Controlled by `File_07`; distinct from Creation-week endpoints. |
| Samaria Node / Immanuel `720` overlay state | `1446 BC → 726 BC = 720`; `726 BC → 6 BC = 720`; `721 BC → 1 BC = 720`; actual late `722 BC ±1` inside schematic `726–721 BC` | File_00 dependency / Immanuel overlay | File_19 supplies the Dial of Ahaz `720` vocabulary. It does not make `726 BC` an actual fall date and does not replace the local `701 BC` / `686 BC` Hezekiah field. |
| Immanuel conception/birth state | `735/734 BC`; `670 BC`; `588 BC`; `539 BC`; `AD 1` | conception / birth / Jubilee measuring rod | `735/734 BC` is a slash-pair, not a range. The detailed macro-chiasm is delegated to `File_17`. |
| Hezekiah reign chiasm | `14 + 1 + 14 = 29`; `701 BC`; `686 BC` | reign-structure / grace-through-shadow motif | Retained and expanded as local structural inference tied to the Dial of Ahaz. |
| Abraham-to-Rome macro-string | `2091 BC → AD 60 = 2150`; `5 × 430`; `10 × 215` | long-wave structural note | Cross-axis check: `2091 + 60 − 1 = 2150`. |
| Kings of Judah master-ledger state | `394.5`; `36`; `430.5` | monarchy-ledger arithmetic | Local table supplies reign lengths only, not accession ages. The literal `430.5` ledger is preserved beside, not replaced by, the schematic Temple-month `430` bridge. |
| Temple-month bridge state | `1016 BC` second month; Tammuz/Av `586 BC`; `1446 BC`; `1876 BC`; `430`; `860` | month-aware schematic bridge | The schematic `430` bridge is a close calendrical approximation from Temple foundation toward destruction. It joins the Entry → Exodus → Temple → destruction chain inside the `215` / `430` base scheme without becoming a granular month/day conversion operator. |
| Literal post-exilic 430 coreference state | `967 BC` second month; `537 BC` second month; `430`; adjacent display `967/966 BC → 537/536 BC` | historical foundation-to-foundation parallel | The actual Temple foundation line reaches the post-exilic foundation-laying field by an exact second-month-to-second-month `430`. This state supports the dual-ledger awareness claim without replacing the schematic `1016 BC` → `586 BC` bridge. |
| Time-manipulation witness state | Joshua; Hezekiah; Crucifixion | typological / theological support | Preserved without the removed minor unit conversion. |
| Christological target state | `AD 1`; `AD 20`; `AD 30`; `AD 35`; `AD 60` | Incarnation / ministry / Passion / Pauline target field | Controlled primarily by `File_13`, `File_05`, and `File_17`. |


### 0.1A Samaria Node / Immanuel 720 dependency state

Active state: Samaria Node / Immanuel `720` overlay by `File_00` dependency.

`File_00` may cite `File_19` for the Dial of Ahaz `720` vocabulary when the Samaria Node is opened. The dependency relation is:

```markdown
1446 BC → 726 BC = 720
726 BC → 6 BC = 720
721 BC → 1 BC = 720
10 × 72 = 720
```

State-control note:
This does not move File_19's local Hezekiah field away from `701 BC` / `686 BC`, and it does not make `726 BC` an actual Fall-of-Samaria date. `726 BC` remains the File_00 schematic onset / collapse label of the Samaria Node; `721 BC` remains the terminal / latest-fall label.

Machine Guard [FILE_19 SAMARIA / IMMANUEL 720 FIREWALL]:
When the Samaria Node cites the Dial of Ahaz `720`, treat the relation as File_00 dependency vocabulary. Do not replace File_19's `701 BC` / `686 BC` Hezekiah field, do not alter File_13's `6 BC` / `1 BC` Christological controls, and do not use `726 BC` as a forced actual fall date for Samaria.

### 0.2 Node-class and display-state register

| Date / value / display | Node-class | Active state | Do not collapse with |
|---|---|---|---|
| `701 BC` | Assyrian siege / deliverance field | Hezekiah field | `686 BC` extended death |
| `686 BC` | Hezekiah extended death | Hezekiah field | `701 BC` siege / deliverance |
| `1406 BC` | primary Conquest | primary Conquest state | `1191 BC` subordinate Ramesside Conquest |
| `1191 BC` | subordinate Conquest | Hezekiah Jubilee harmonic | primary `1406 BC` |
| `1446 BC` | primary Exodus | Exodus state | `1231 BC` subordinate Ramesside Exodus |
| `1231 BC` | subordinate Ramesside Exodus | Exodus / Danielic target field | primary `1446 BC` |
| `4116 BC` | Creation Year-6 / Adam | Creation Year-6 state | Creation-week wrapper `4121–4114 BC` |
| `735/734 BC` | conception/birth slash-pair | Immanuel state | range, average, or single collapsed date |
| `AD 29515` | actual Pillar node | AD Pillar state | any legacy BC-side coordinate convention |
| `394.5` | post-Solomonic Judah ledger | Kings master-ledger state | rounded `430` schematic constant by itself |
| `430.5` | Temple-to-destruction block | Kings master-ledger state | schematic `430` Temple-month bridge unless the month-aware approximation state is named |
| `1016 BC` second month | schematic Temple construction beginning | Temple-month bridge state | historical `966 BC` unless Kings dual-ledger state is opened |
| `967 BC` second month | actual Temple foundation boundary-state | literal post-exilic 430 coreference state | schematic `1016 BC`; ordinary historical display `966 BC` unless adjacent-state is active |
| `537 BC` second month | post-exilic foundation-laying boundary-state | literal post-exilic 430 coreference state | fall of Babylon `539 BC`; ordinary return / restoration display `536 BC` unless adjacent-state is active |
| `586 BC` Tammuz/Av | breach / burning season of Jerusalem | Temple-month bridge state | undifferentiated `586 BC` endpoint unless month-aware state is named |
| `71⅔` | alternate precessional-day display | alternate precessional-day state | standard `72`-year precessional day |
| `115` | delayed-judgment span | Key-of-23 row | transferred Immanuel macro-chiasm |

### 0.3 File map

| Section | Function | Active state / operator |
|---|---|---|
| §0 | File-function, state controls, arithmetic-control summary, File map, terminology controls, Machine Guards, and claim-status controls | file-level modal states; dependency tracking |
| §1 | Introduces numeric units as prophetic time | count-to-chronology state |
| §2 | Records the `720`-year Dial of Ahaz framework | precessional degree; same-side spans; civil cross-axis spans; sundial mirror |
| §3 | Records the `185000`-year forward and backward projection | count-to-chronology; `AD 29515`; `430 × 430`; `430 × 432`; `430 × 360` |
| §4 | Records Jubilee / Sabbatical language and the `490` / `3430` structures | Jubilee `49`; Danielic `490`; Creation Year-6 state |
| §5 | Gives the local `720 = 490 + 15 + 215` logic engine | decomposition of Dial of Ahaz state |
| §6 | Records delayed-judgment and third-day encoding | `100`; `115`; Key of 23; alternate precessional-day display `71⅔ = 215/3` |
| §7 | Records the Immanuel conception/birth Jubilee timeline | `735/734 BC`; `15 × 49`; Christological dependency; File_17 macro-chiasm cross-reference |
| §8 | Preserves biblical precedents for divine time manipulation | theological / typological witness state |
| §9 | Records the `3.5 × 430` and `3.5 × 360` parallel | primary/subordinate Exodus states; `1260`; `1290` |
| §10 | Preserves synthesis, validation matrix, Hezekiah reign chiasm, and Kings ledger | arithmetic facts; structural inference; monarchy ledger; theological summary |
| Audit notes | Records retained audit and dependency notes | audit notes; dependency boundaries |

### 0.4 Terminology controls

| Source form | Revised handling |
|---|---|
| `FILE_00`, `FILE_07`, etc. | Normalized to `File_00`, `File_07`, etc. |
| Source comma-form numbers | Normalized to no-comma number formatting, including `185000`, `25920`, `AD 184315`, `185701 BC`, `269286 BC`, and `453600`. |
| `Standard Exodus`; `Alternative Exodus` | Normalized in controls as primary Exodus state and subordinate Ramesside Exodus state; source-facing labels preserved in tables where clarity requires. |
| `Standard Conquest`; `Alt. Conquest` | Normalized in controls as primary Conquest state and subordinate Ramesside Conquest state; source-facing labels preserved in tables where clarity requires. |
| `Creation Week 4121-4114 BC` | Normalized to `4121–4114 BC`. |
| `Mirror spans` | Retained as source terminology only where bidirectional sundial logic is active; classified locally as bidirectional prophetic span / sundial mirror. |
| Legacy BC-side Pillar coordinate | Removed from the local argument by author decision. |
| Early Christological cross-references | Consolidated to `File_13` as the active Christological controller. |
| Decimal precessional-day display | Replaced by author-approved `71⅔ × 3 = 215`; exact state `215/3` retained. |
| Kings accession-age notes | Removed from the local Kings ledger. The table lists reign lengths, not accession ages. |

### 0.5 Modal-state processing rules

1. `701 BC` and `686 BC` are the controlling Hezekiah field anchors. The `15`-year bridge must remain visible whenever the argument shifts between siege, life-extension, death, `720`, `185000`, or Jubilee states.
2. `1446 BC` / `1231 BC` and `1406 BC` / `1191 BC` are primary/subordinate pairs. The subordinate Ramesside states may support harmonic logic but must not replace the primary Exodus or Conquest anchors.
3. Same-side BC spans use subtraction. Same-side AD spans use ordinary AD subtraction where both endpoints are AD dates. Civil cross-axis spans use `BC + AD − 1`.
4. Bidirectional span language is not automatically formal Deep-Time Mirror protocol. In this file, local sundial language functions as bidirectional prophetic span / sundial mirror.
5. The actual Pillar state is `AD 29515`. No BC-side Pillar coordinate is active in the local argument.
6. The `185000` forward projection and backward projection are count-to-chronology states. Do not use one direction to correct the other unless the local operator is restated.
7. `4116 BC` is a Creation Year-6 / Adam state. It must not be collapsed with the Creation-week wrapper `4121–4114 BC` or with Creation endpoints in other files.
8. `735/734 BC` is a conception/birth slash-pair. It is not a range, an average, or a date to be collapsed.
9. `71⅔` is the preferred alternate precessional-day display in this file, with `215/3` as the exact state. It is not a correction of the standard `72`-year precessional-day display.
10. The detailed Immanuel macro-chiasm belongs to `File_17`. `File_19` retains only the cross-reference note that the local Hezekiah complex operates within the broader Isaiah midpoint framework.
11. The Kings of Judah ledger in §10 lists reign lengths only. Accession-age data is excluded by author decision.
12. The literal `430.5` Temple-to-destruction ledger and the schematic Temple-month `430` bridge are coordinated states. The Temple-month bridge runs from `1016 BC` second month toward Tammuz/Av `586 BC`, joining the schematic `430` and `860` structures within the `215`-year base scheme. It is not a new exact month/day conversion operator inside `File_19`.
13. The literal post-exilic coreference `967 BC` second month → `537 BC` second month = `430` is a historical foundation-to-foundation parallel. It does not correct the schematic `1016 BC` bridge or the ordinary historical `966 BC` display. It shows that the actual Temple-foundation route and the idealized Kings route can satisfy Ezekiel’s `430` pattern in parallel, separated by `49/50` years according to the active adjacent-date state.

### 0.6 Machine Guards for `File_19`

Machine Guard [FILE_19 HEZEKIAH FIELD]:
`701 BC` and `686 BC` are the controlling Hezekiah field anchors. `701 BC` is the Assyrian siege / deliverance field. `686 BC` is Hezekiah’s extended death. The `15`-year bridge must not be erased by either the `720` state or the `185000` state.

Machine Guard [FILE_19 PRIMARY / SUBORDINATE STATES]:
`1446 BC` is the primary Exodus state. `1231 BC` is the subordinate Ramesside Exodus state. `1406 BC` is the primary Conquest state. `1191 BC` is the subordinate Ramesside Conquest state. The subordinate states may function as designed harmonic lenses, but they must not replace the primary anchors.

Machine Guard [FILE_19 720 / CIVIL / SUNDIAL-MIRROR FIREWALL]:
The `720`-year spans may be displayed forward and backward. Same-side BC spans use subtraction. Cross-axis civil spans use `BC + AD − 1`. Formal Mirror protocol, bidirectional sundial-span language, precessional scale, and civil-span counting remain distinct. In this file, the local bidirectional language functions as bidirectional prophetic span / sundial mirror.

Machine Guard [FILE_19 185000 DEEP-TIME STATE]:
The `185000` slain Assyrians are preserved as a count-to-chronology state. Forward projection from `686 BC` to `AD 184315` and backward projection from `701 BC` to `185701 BC` are preserved as source logic. Do not collapse the forward and backward directions into one operator.

Machine Guard [FILE_19 AD PILLAR]:
`AD 29515` is the actual Pillar node in this file. No BC-side Pillar coordinate is retained in the local argument. If another file preserves a legacy BC-side convention, it is outside the local proof burden of `File_19`.

Machine Guard [FILE_19 JUBILEE / CREATION YEAR-6 STATE]:
`4116 BC` is a Creation Year-6 / Adam state by `File_07` dependency, not a Creation endpoint. The `4121–4114 BC` Creation-week wrapper and the `4116 BC` Year-6 anchor must remain distinct.

Machine Guard [FILE_19 IMMANUEL 735/734 SLASH-PAIR]:
`735/734 BC` is a conception/birth slash-pair, not a range to be averaged or collapsed. `735 BC` is the conception / prophecy state; `734 BC` is the birth display state.

Machine Guard [FILE_19 ALTERNATE PRECESSIONAL-DAY DISPLAY]:
The local display is `71⅔ × 3 = 215`, with exact state `215/3`. Do not revert to decimal display except as source-history, and do not use the alternate state to correct the standard `72`-year precessional-day state.

Machine Guard [FILE_19 KINGS LEDGER]:
The local Kings of Judah ledger lists reign lengths only. Do not import accession ages into this table. The ledger total is `394.5`; the Temple-to-destruction block is `36 + 394.5 = 430.5`. The month-aware Temple bridge may relate `1016 BC` second month to Tammuz/Av `586 BC` as a close schematic `430` relation inside the wider `860 = 2 × 430 = 4 × 215` field, but that display must not erase the local `430.5` ledger.

Machine Guard [FILE_19 LITERAL POST-EXILIC 430 COREFERENCE]:
`967 BC` second month → `537 BC` second month = `430` is a literal historical foundation-to-foundation coreference. It demonstrates a parallel to the schematic `1016 BC` second-month → Tammuz/Av `586 BC` bridge. Do not collapse `967 BC` into `1016 BC`; do not collapse `537 BC` into `586 BC`; do not use the literal post-exilic coreference to erase the Kings dual-ledger `+50` / adjacent `49` state.

### 0.7 Arithmetic-control summary

| Arithmetic field | Result |
|---|---|
| Precessional degree | `25920 × 1/36 = 720`; `10 × 72 = 720`. |
| Forward `720` rows | `701 BC → AD 20 = 720`; `686 BC → AD 35 = 720`, by civil cross-axis counting. |
| Backward `720` rows | `701 BC → 1421 BC = 720`; `686 BC → 1406 BC = 720`, by same-side BC subtraction. |
| Forward `185000` row | `686 + 184315 − 1 = 185000`. |
| Backward `185000` row | `185701 − 701 = 185000`. |
| `430 × 430` and `430 × 432` rows | `184900 = 430 × 430`; `185760 = 430 × 432`; `184470 = 430 × 429`. |
| Actual Pillar row | `184315 − 29515 = 154800`; `154800 = 430 × 360`. |
| Adam cumulative row | `269286 + 184315 − 1 = 453600`; `453600 = 1260 × 360`. |
| Jubilee harmonic | `1191 BC → 701 BC = 490`; `4116 BC → 686 BC = 3430 = 7 × 490 = 70 × 49`. |
| Dial decomposition | `490 + 15 + 215 = 720`. |
| Delayed-judgment pattern | `801 → 701 = 100`; `801 → 686 = 115`; `701 → 586 = 115`; `686 → 586 = 100`; `115 = 23 × 5`. |
| Alternate precessional day | `71⅔ = 215/3`; `(215/3) × 3 = 215`. |
| Immanuel Jubilee timeline | `735 + 1 − 1 = 735 = 15 × 49`; `735 − 539 = 196 = 4 × 49`. |
| Exodus / Christ parallel | `1446 BC → AD 60 = 1505 = 3.5 × 430`; `1231 BC → AD 30 = 1260 = 3.5 × 360`; `1231 BC → AD 60 = 1290`. |
| Abraham-to-Rome macro-string | `2091 BC → AD 60 = 2150 = 5 × 430 = 10 × 215`. |
| Kings ledger | post-Solomonic ledger total `394.5`; `36 + 394.5 = 430.5`; month-aware bridge from `1016 BC` second month toward Tammuz/Av `586 BC` as a close schematic `430`; literal `967 BC` second month → `537 BC` second month = `430`; `1446 BC → 586 BC = 860 = 2 × 430 = 4 × 215`. |

### 0.8 Claim-status register

| Label | Function in `File_19` |
|---|---|
| Textual datum | Direct biblical or source-retained datum, such as the `185000`, `10` steps, `15` years, `3` days, Isaiah 37:30, or Isaiah 7:14. |
| Arithmetic fact | Direct calculation from stated anchors or values. |
| Structural inference | Pattern inferred from repeated checked alignments, such as the `720` decomposition or the `185000` bidirectional structure. |
| Typological reading | Theological or literary correspondence, such as the Dial of Ahaz and divine time manipulation. |
| Theological note | Theological meaning preserved without carrying the arithmetic burden. |
| Providential synchronization | Coherence beyond demonstrable authorial intent; not formal statistical proof. |
| Dependency-controlled | Claim retained locally because another file controls the endpoint, state, or operator. |
| Source-history note | Legacy source trace retained where needed, without active proof weight. |
| Audit note | Value, state, source label, or dependency requiring later review. No local author-decision blocker remains after Finalization. |

## 1. Introduction — Units as Prophetic Time

A core principle of the repository states that numeric units in biblical texts may function as days or years at prophetic scale. The Hezekiah narrative, in Isaiah 36–39 and 2 Kings 18–20, supplies an applied demonstration of that principle.

| Unit in text | Literal meaning | Prophetic meaning in `File_19` |
|---|---|---|
| `185000` slain soldiers | men killed | `185000` years |
| `10` degrees / steps | shadow movement | `720` years, precessional display |
| `15` years | Hezekiah’s life extension | anchor bridge `701 BC → 686 BC` |
| `3` days | recovery / temple ascent | delayed judgment and alternate precessional-day encoding |

Argument-control note:
All four units are preserved as count-to-chronology data. Their evidential role depends on the checked arithmetic rows that follow, not on rhetoric.

Cross-reference: `File_00`, Count-to-Chronology Axiom.

## 2. The 720-Year Framework — 10 Degrees of Precession

### 2.1 Textual basis

Textual datum:
“Then the prophet Isaiah called on the LORD, and the LORD made the shadow go back the ten steps it had gone down on the stairway of Ahaz.” — 2 Kings 20:11

### 2.2 Precessional calculation

| Calculation | Result |
|---|---:|
| Great Year of Precession | `25920` years |
| `1` degree | `72` years |
| `10` degrees | `720` years |
| `25920 × 1/36` | `720` years |
| `10 × 72` | `720` years |

Arithmetic fact:
`10` degrees equals `1/36` of a `360`-degree cycle. Therefore `25920 × 1/36 = 720`, and `10 × 72 = 720`.

### 2.3 Bidirectional 720-year spans

The shadow going backward signals that the `720`-year state operates in both directions. This is local bidirectional prophetic span / sundial-mirror language, not automatic Deep-Time Mirror protocol.

Backward from Hezekiah:

| From | Span | To | Event |
|---|---:|---:|---|
| `701 BC` | `720` | `1421 BC` | Conquest-era display |
| `686 BC` | `720` | `1406 BC` | Joshua’s Conquest / Long Day |

Forward from Hezekiah:

| From | Span | To | Event |
|---|---:|---:|---|
| `701 BC` | `720` | `AD 20` | Christ-ministry display |
| `686 BC` | `720` | `AD 35` | shortly after Crucifixion / early-church display |

From the Conquest:

| From | Span | To | Event |
|---|---:|---:|---|
| `1406 BC` | `720` | `686 BC` | Hezekiah’s death |

Arithmetic note:
Same-side BC spans check by subtraction: `1421 − 701 = 720`, `1406 − 686 = 720`, and `1406 − 686 = 720`. Cross-axis spans check by civil counting: `701 + 20 − 1 = 720`; `686 + 35 − 1 = 720`.

### 2.4 The 15-year window preserved

| Hezekiah era | Span | Christ-era display |
|---|---:|---:|
| `701 BC` | `720` | `AD 20` |
| `686 BC` | `720` | `AD 35` |

The same `15`-year window appears on both sides of the `720`-year display:

```markdown
701 BC − 686 BC = 15
AD 35 − AD 20 = 15
```

Structural inference:
Hezekiah’s `15`-year life extension maps onto the displayed `15`-year Christological window. Exact Christological date-state proof remains governed by `File_13`.

### 2.5 Child-prophecy connection around 725 BC

Isaiah’s prophecy about the child knowing “my father and my mother” indicates approximately `2` years, or about `720` days.

| From | Span | To | Event |
|---|---:|---:|---|
| `~725 BC` | `720` | `1445 BC` | Tabernacle erected |

Typological note:
The source interprets the child’s development period as mapping backward to the Tabernacle field, connecting the Immanuel theme, “God with us,” to the earlier tabernacling of YHWH with Israel.

Cross-reference: `File_07`, Creation / Tabernacle; `File_05`, Exodus anchor.

## 3. The 185000 as 185000 Years

### 3.1 Textual basis

Textual datum:
“That night the angel of the LORD went out and put to death a hundred and eighty-five thousand in the Assyrian camp.” — 2 Kings 19:35

### 3.2 Forward from 686 BC — Hezekiah’s extended life ends

| From | Span | To | Calculation / relation |
|---|---:|---:|---|
| `686 BC` | `+185000` | `AD 184315` | count-to-chronology projection |
| `AD 184315` | to `586 BC` | `184900` years | `430 × 430` |
| `AD 184315` | to `1446 BC` | `185760` years | `430 × 432` |

Arithmetic note:
The forward projection checks by civil cross-axis span: `686 + 184315 − 1 = 185000`. The secondary rows check as `184315 + 586 − 1 = 184900 = 430 × 430` and `184315 + 1446 − 1 = 185760 = 430 × 432`.

### 3.3 Backward from 701 BC — shadow reverses, time reverses

| From | Span | To | Calculation / relation |
|---|---:|---:|---|
| `701 BC` | `−185000` | `185701 BC` | backward projection |
| `185701 BC` | to `AD 60` | `185760` years | `430 × 432` |
| `185701 BC` | to `801 BC` | `184900` years | `430 × 430` |
| `185701 BC` | to `1231 BC` | `184470` years | `430 × 429` |

Arithmetic note:
The backward projection checks by same-side BC subtraction: `185701 − 701 = 185000`. The secondary rows check as `185701 + 60 − 1 = 185760 = 430 × 432`, `185701 − 801 = 184900 = 430 × 430`, and `185701 − 1231 = 184470 = 430 × 429`.

### 3.4 The 430 × 430 and 430 × 432 pairing

| Direction | `430 × 430` lands on | `430 × 432` lands on | Difference |
|---|---:|---:|---:|
| Forward, from `686 BC` | `586 BC` | `1446 BC` | `860` years, `430 × 2` |
| Backward, from `701 BC` | `801 BC` | `AD 60` | `860` years, `430 × 2` |

The difference between paired landings is displayed as follows:

| Span | Value | Source interpretation |
|---|---:|---|
| `801 BC → 586 BC` | `215` years | half of `430`; `3` alternate precessional days |
| `1446 BC → AD 60` | `1505` years | `430 × 3.5`; or `7 × 215` |

Arithmetic note:
The paired differences check as `1446 − 586 = 860 = 430 × 2`, `801 + 60 − 1 = 860 = 430 × 2`, `801 − 586 = 215`, and `1446 + 60 − 1 = 1505 = 430 × 3.5 = 7 × 215`.

### 3.5 Pillar and Adam connections

Active state: `AD 29515` actual Pillar state.

| From | To | Span | Calculation / state |
|---|---:|---:|---|
| `AD 184315` | `AD 29515` — actual Pillar | `154800` years | `430 × 360` |
| `269286 BC` — Adam Cumulative | `AD 184315` | `453600` years | `1260 × 360` |

Arithmetic note:
The AD Pillar row checks as a same-side AD span: `184315 − 29515 = 154800 = 430 × 360`. The Adam cumulative row checks under civil cross-axis span-counting: `269286 + 184315 − 1 = 453600 = 1260 × 360`.

Author-decision note:
`AD 29515` is the local actual Pillar state. The earlier BC-side display convention is not retained in `File_19` because it added no local analytical value and risked civil-span confusion. Any legacy BC-side convention belongs, if anywhere, in a separate Mirror-control or deep-time control file as non-load-bearing source-history.

### 3.6 What the 185000 supports

| Element | Controlled claim-status role |
|---|---|
| The `215`-year variant | Structural inference supported by the checked `430 × 430` / `430 × 432` spacing. |
| The `1231 BC` alternative | Dependency-controlled subordinate Ramesside state supported locally by the checked `430 × 429` row. |
| The `430`-year Sojourn cycle | Dependency-controlled foundational unit from `File_05` / `File_17`; locally corroborated by repeated factorization. |
| Bidirectional prophetic span / sundial mirror | Local bidirectional logic after the forward and backward arithmetic rows are stated. |
| The Cross as fulcrum | Structural inference from `3.5 × 430` to `AD 60` and `3.5 × 360` to `AD 30`; Christological proof weight remains `File_13` controlled. |

Cross-reference: `File_00`, Variant Mechanism and Key of 23; `File_16`, Mirror classification; `File_17`, prophetic span anatomy.

## 4. The 490 Jubilees and Sabbatical Language

### 4.1 Textual basis

Textual datum:
“This year you will eat what grows by itself, and the second year what springs from that. But in the third year sow and reap, plant vineyards and eat their fruit.” — Isaiah 37:30

### 4.2 Jubilee / Sabbatical language comparison

| Isaiah’s prophecy | Leviticus 25, Jubilee law |
|---|---|
| “Eat what grows by itself” — `saphiah` | “You shall not sow… not reap the secondary growth” — Lev 25:5, 11 |
| two years of rest | Sabbatical + Jubilee years |
| third year: restoration | return of land to original families |
| survival through siege | divine provision during rest |

The explicit Jubilee terminology supports the `490`-year span as more than an isolated arithmetic alignment.

### 4.3 The 490-year span — 10 Jubilees

| From | To | Span | Calculation |
|---|---:|---:|---:|
| `1191 BC` — subordinate Ramesside Conquest | `701 BC` — siege lifted | `490` years | `10` Jubilees |

Arithmetic fact:
`1191 − 701 = 490`.

Dependency note:
This state is governed by `File_08` as the Hezekiah Jubilee / Sabbatical harmonic.

### 4.4 Thematic unity

| Jubilee theme | Leviticus 25 | Isaiah / Hezekiah | Chronological role |
|---|---|---|---|
| Land rests | every seventh / fiftieth year | two years of siege provision | `490 = 10` Jubilees; `3430 = 70` Jubilees |
| Debts released | economic reset | Assyrian judgment removed | judgment on enemy |
| Slaves freed | freedom proclaimed | Jerusalem delivered | deliverance |
| Land restored | return to families | “third year sow” | restoration |

Theological note:
The Jubilee language explains why the `490`-year harmonic matters, but the arithmetic remains the proof-bearing layer.

### 4.5 The sevenfold Jubilee — 7 × 490

| Span | From | To | Interpretation |
|---|---:|---:|---|
| `1 × 490` | `1191 BC` — subordinate Conquest | `701 BC` — deliverance | `10` Jubilees |
| `7 × 490` | `4116 BC` — Creation Year-6 | `686 BC` — extended death | `70` Jubilees |

Verification:

```markdown
4116 − 686 = 3430
3430 = 7 × 490 = 70 × 49
```

### 4.6 Theological framework

| Element | Regular dating | Subordinate / variant dating |
|---|---:|---:|
| Conquest | `1406 BC` | `1191 BC` |
| Deliverance | — | `701 BC`, `490` from `1191 BC` |
| Creation-week wrapper | `4121–4114 BC` | — |
| Adam, Year-6 | `4116 BC` | man created on sixth day |
| Extended death | — | `686 BC`, `7 × 490` from `4116 BC` |

The start, Creation’s sixth-day / Adam state, and the finish, Hezekiah’s death after his `15`-year extension, span exactly `70` Jubilees.

Cross-reference: `File_00`, Variant Mechanism; `File_07`, Creation dates; `File_08`, Hezekiah harmonic.

## 5. The 720 Decomposition — 490 + 15 + 215

### 5.1 Formula

The `720` years on the Dial of Ahaz decomposes into three repository components:

| Component | Value | Source |
|---|---:|---|
| Jubilee span | `490` | subordinate Conquest `1191 BC → 701 BC` |
| Hezekiah extension | `15` | `701 BC → 686 BC` |
| Variant difference | `215` | `1406 BC − 1191 BC` |
| Total | `720` | `10` degrees of precession |

```markdown
490 + 15 + 215 = 720
```

### 5.2 Verification

| Anchor | Span | To | Result |
|---|---:|---:|---|
| `1406 BC` — primary Conquest | `720` years | `686 BC` | checks |
| `1191 BC` — subordinate Conquest | `490` years | `701 BC` | checks |
| `1406 BC − 1191 BC` | `215` years | — | variant difference |
| `701 BC − 686 BC` | `15` years | — | life extension |

### 5.3 What this supports

The Dial of Ahaz encodes three local components:

| Component | Function |
|---|---|
| `490` | Danielic / Jubilee register, reinforced by Jubilee language in Isaiah 37:30 |
| `215` | repository variant structure, governed by the primary/subordinate state distinction |
| `15` | bridge between siege and extended death, and between the Hezekiah and Christological display windows |

Cross-reference: `File_00`, Variant Mechanism; `File_17`, Prophetic Time Span Anatomy.

## 6. The Delayed Judgment — 100 / 115 Pattern

### 6.1 The third-day prophecy

Textual datum:
Hezekiah asks, “What will be the sign that the LORD will heal me and that I will go up to the temple of the LORD on the third day from now?” — 2 Kings 20:8

### 6.2 Chiastic 100 / 115 structure

| From | To | Span | Factor |
|---|---:|---:|---:|
| `801 BC` | `701 BC` | `100` years | — |
| `801 BC` | `686 BC` | `115` years | `23 × 5` |
| `701 BC` | `586 BC` | `115` years | `23 × 5` |
| `686 BC` | `586 BC` | `100` years | — |

The pattern is chiastic:

```markdown
100 — 115 — 115 — 100
```

### 6.3 Delayed judgment

God showed mercy in `701 BC` by destroying the Assyrian army. The judgment on Jerusalem was delayed, not cancelled.

| Event | Date | Delay from `701 BC` |
|---|---:|---:|
| Assyrian threat | `701 BC` | — |
| Hezekiah’s death | `686 BC` | `15` years |
| Jerusalem falls | `586 BC` | `115` years, `23 × 5` |

### 6.4 The third day encoded

| Literal datum | Prophetic encoding |
|---|---|
| `3` days to recovery | `115` years to Jerusalem’s fall |
| `3` alternate precessional days | `71⅔ × 3 = 215` years |
| temple visit on third day | temple destroyed `115` years later |

The Key of 23 appears:

```markdown
115 = 23 × 5
```

Arithmetic note:
The alternate precessional-day display checks exactly: `71⅔ = 215/3`, so `(215/3) × 3 = 215`.

Display-state note:
The author-resolved display is `71⅔ × 3 = 215 years`, with exact state `215/3`. This preserves the alternate precessional-day precedent controlled by `File_05` and `File_17` without replacing the standard `72`-year precessional-day state.

Cross-reference: `File_00`, Key of 23; `File_17`, precessional display states.

## 7. Immanuel’s Jubilee Timeline

### 7.1 Textual basis

Textual datum:
“Therefore the Lord himself will give you a sign: The virgin will conceive and give birth to a son, and will call him Immanuel.” — Isaiah 7:14

### 7.2 Conception versus birth — 735/734 BC

The prophecy begins at conception, not birth.

| Event | Date | Significance |
|---|---:|---|
| Immanuel conceived | `735 BC` | prophecy given; “a virgin shall conceive” |
| Immanuel born | `734 BC` | approximately `9` months later |

Modal-state note:
`735/734 BC` is a slash-pair: conception / prophecy state followed by birth display state. It is not a range or an average.

### 7.3 Immanuel as prophetic measuring rod

Isaiah’s son becomes a Jubilee-based measuring rod from conception.

| Age from conception | Year | Event | Jubilee count |
|---|---:|---|---:|
| Conception | `735 BC` | sign given to Ahaz | `0` |
| Birth, approximately `1` year | `734 BC` | Immanuel born | — |
| Approximately `2` years | `733 BC` | “knows father/mother,” approximately `720` days from conception | — |
| `49` years | `686 BC` | death of Hezekiah | `1` Jubilee |
| `65` years | `670 BC` | “shattering” fulfilled, Isaiah 7:8 | — |
| `147` years | `588 BC` | siege of Jerusalem | `3` Jubilees |
| `196` years | `539 BC` | Fall of Babylon | `4` Jubilees |
| `735` years | `AD 1` | birth of Christ | `15` Jubilees |

Arithmetic note:
The table checks under the displayed operators: `735 − 734 = 1`; `735 − 733 = 2`; `735 − 686 = 49`; `735 − 670 = 65`; `735 − 588 = 147 = 3 × 49`; `735 − 539 = 196 = 4 × 49`; and `735 + 1 − 1 = 735 = 15 × 49`.

### 7.4 The 65-year prophecy — Isaiah 7:8

Textual datum:
“Within sixty-five years Ephraim will be shattered, no longer a people.”

Source calculation:

```markdown
735 BC − 65 = 670 BC
```

Arithmetic note:
The displayed same-side BC calculation checks: `735 − 65 = 670`.

### 7.5 The 15 Jubilees to Christ

| From | To | Span | Calculation |
|---|---:|---:|---:|
| `735 BC` — Immanuel conceived | `AD 1` — Christ born | `735` years | `15 × 49` |

Arithmetic note:
The cross-axis span and factorization check: `735 + 1 − 1 = 735`; `15 × 49 = 735`.

The source claim is that `15` Jubilees span from the sign child’s conception to the true Immanuel’s birth.

### 7.6 Theological coherence

| The sign | The fulfillment |
|---|---|
| Isaiah’s son named “Immanuel” | Jesus called “Immanuel” in Matthew 1:23 |
| Conceived `735 BC` | born `AD 1`, traditional display |
| span: `735` years | `15` Jubilees |
| sign child points forward | Christ is the reality |

Theological note:
The source states that the sign was not merely a child, but a chronological key unlocking `735` years, or `15` Jubilees, from conception to the true “God with us.” Claim-status classification: the `735`-year span is an arithmetic fact; the “chronological key” claim is structural inference; the Jesus / Immanuel fulfillment claim is a typological / theological reading governed by `File_13` where Christological date-state precision is required.

Cross-reference: `File_13`, Christological Matrix. The detailed Immanuel macro-chiasm belongs to `File_17`; `File_19` retains only the note that the Hezekiah prophetic complex operates inside that broader Isaiah midpoint framework.

## 8. Biblical Precedents for Time Manipulation

The Hezekiah narrative belongs to a pattern of divine time manipulation.

### 8.1 The three witnesses

| Event | Text | Time mechanism |
|---|---|---|
| Joshua’s Long Day | Joshua 10:12–14 | sun stands still, approximately `1` day added |
| Hezekiah’s Sign | 2 Kings 20:8–11 | shadow goes back `10` degrees |
| The Crucifixion | Matthew 27:45 | darkness from noon to `3` PM |

All three involve the sun being affected: stopped, reversed, or darkened.

### 8.2 Assyrian context

Rabshakeh’s insults invoke Sumerian / Akkadian astral religion. God’s response, reversing the shadow on a dial designed for sun worship, is a direct rebuke to pagan cosmology. YHWH controls the heavens.

### 8.3 Multi-scale operation

| Scale | Mechanism | Expression |
|---|---|---|
| Days | Joshua’s extra day | `+1` day literally added |
| Years | `720` years | `10` degrees of precession |
| Prophetic | `185000` years | bidirectional prophetic spans |

Theological note:
The source states that time being warped, stopped, reversed, and darkened is native to biblical theology, not a foreign concept imposed on the text. Current claim-status handling preserves the theological note but removes the minor unit-conversion display because it was not load-bearing.

Cross-reference: `File_16`, bidirectional prophetic span / sundial mirror classification recommended.

## 9. The 3.5 × 430 and 3.5 × 360 Parallel

The `185000`-year pattern supports both Exodus dating systems when state labels are preserved.

### 9.1 Parallel structures

| From | To | Span | Calculation / state |
|---|---:|---:|---|
| `1446 BC` — primary Exodus | `AD 60` — Paul in Rome | `1505` years | `3.5 × 430` |
| `1231 BC` — subordinate Exodus | `AD 30` — Christ-death target | `1260` years | `3.5 × 360` |
| `1231 BC` — subordinate Exodus | `AD 60` — Paul in Rome | `1290` years | Daniel’s `1290` |

Arithmetic note:
The cross-axis spans check: `1446 + 60 − 1 = 1505`; `1231 + 30 − 1 = 1260`; `1231 + 60 − 1 = 1290`.

### 9.2 Cross as fulcrum

| Exodus anchor | Span | Lands on | Event |
|---|---:|---:|---|
| `1446 BC`, `430`-based | `1505` | `AD 60` | Paul in Rome |
| `1231 BC`, `360`-based | `1260` | `AD 30` | Christ-death target |

Christological note:
The source identifies the Cross era as the fulcrum where the `360`-day prophetic calendar meets history. The exact Passion-date state is governed by `File_13`; this file preserves the `AD 30` target as a structural / Christological target state.

### 9.3 The 1290 bridge

```markdown
1231 BC → AD 60 = 1290
1290 = 1260 + 30
```

The source reads the `30` years as the bridge from the `AD 30` Christ-death target to Paul’s arrival in Rome at `AD 60`.

### 9.4 What this supports

| Element | Claim-status role |
|---|---|
| The `215`-year variant | Arithmetic fact: `1446 − 1231 = 215`. |
| The `1231 BC` subordinate state | Corroborated by `430 × 429` and `3.5 × 360`; still subordinate, not replacement. |
| The `430` / `360` dual system | Structural inference from paired `3.5`-unit spans. |
| The Cross as fulcrum | Christological structural inference governed by `File_13`. |
| Daniel’s `1260` / `1290` | Operational at yearly scale; component logic governed by `File_17`. |

Cross-reference: `File_00`, Variant Mechanism; `File_05`, Exodus anchors; `File_17`, `1260` / `1290` patterns.

## 10. Synthesis — The Dial as Microcosm

### 10.1 Components

The Dial of Ahaz encodes the local repository framework in miniature.

| Element | Value | Repository principle |
|---|---:|---|
| `10` degrees | `720` years | precessional time |
| `720` decomposition | `490 + 15 + 215` | Jubilee + extension + variant |
| `185000` slain | `185000` years | count-to-chronology |
| shadow backward | bidirectional | sundial-mirror span logic |
| `3` days to temple | `115 / 215` years | Key of 23; alternate precessional days |
| Jubilee language | `10` Jubilees, `490` | textual support |
| Sevenfold Jubilee | `70` Jubilees, `7 × 490` | Creation Year-6 to extended death |
| Immanuel timeline | `15` Jubilees to Christ | Messianic measuring rod |
| `65/49` cycles | `195/196` crossing | shattering / Jubilee crossing; detailed macro-chiasm by `File_17` |
| Ezekiel / Temple ledger | `36 + 394.5 = 430.5`; `967 BC → 537 BC = 430` | Temple-to-destruction span; close schematic `1016 BC` second-month → Tammuz/Av `586 BC` bridge; literal post-exilic foundation-to-foundation `430` coreference |
| Hezekiah’s reign | `14 + 1 + 14` | backward shadow as forward grace |

### 10.2 Validation matrix

| Repository element | Supported by |
|---|---|
| `215`-year variant | `720` decomposition; `430 × 430` / `430 × 432` spacing |
| `1231 BC` subordinate Exodus state | `490` years to `701 BC`; `430 × 429` span; `3.5 × 360` to `AD 30` |
| Key of 23 | `115 = 23 × 5`; transferred Immanuel macro-chiasm by `File_17` |
| Bidirectional prophetic spans | `185000` forward and backward; `720` forward and backward |
| Units as time | soldiers, degrees, days, and years all function temporally within the source narrative |
| Cross as fulcrum | `3.5 × 360` and `3.5 × 430` converge at `AD 30` / `AD 60` target field |
| Jubilee structure | Sabbatical language in Isaiah 37:30 |
| `70` Jubilees | `4116 BC → 686 BC = 7 × 490` |
| `65/49` crossing | both cycles touch the `539 BC` Babylon-fall field |
| Ezekiel connection | Temple-to-destruction ledger supplies `430.5`, with a close month-aware `1016 BC` second-month → Tammuz/Av `586 BC` bridge and a literal `967 BC` second-month → `537 BC` second-month `430` foundation-to-foundation coreference |
| Conception/birth pivot | `735/734 BC` resolves local cycle intersections |

### 10.3 Hezekiah 14 + 1 + 14 chiasm and Abraham-to-Rome macro-string

Author-decision integration:
The Hezekiah `14 + 1 + 14` reign chiasm is retained as a local structural observation because it mirrors the forward-and-backward physics of the Dial of Ahaz miracle.

| Structure | Value | Function |
|---|---:|---|
| Hezekiah reign display | `14 + 1 + 14 = 29` | pivot-centered reign symmetry |
| Hezekiah extension | `15` | pivot year plus `14` years of added grace |
| Abraham-to-Rome macro-string | `2091 BC → AD 60 = 2150` | `5 × 430 = 10 × 215` |

Arithmetic fact:

```markdown
2091 + 60 − 1 = 2150
2150 = 5 × 430 = 10 × 215
```

Structural inference:
The local chiasm and the long-wave Abraham-to-Rome string both preserve the same forward/backward logic. The Hezekiah field supplies the local narrative sign; the Abraham-to-Rome span supplies the macro-string ending at the `AD 60` Pauline horizon.

Cross-reference: `File_08`, Kings / Hezekiah harmonic; `File_13`, AD 60 Christological / NT horizon; `File_17`, `430` and `215` span-component controls.

### 10.4 Kings of Judah master ledger

Author-decision integration:
The Kings of Judah ledger is integrated locally to support the Ezekiel `390 + 40 = 430` / Temple-to-destruction connection. The ledger lists reign lengths only. Accession ages are not included.

| # | Monarch of Judah | Reign length | Structural marker |
|---:|---|---:|---|
| 4 | Rehoboam | `17` years | monarchy fracture; Temple plundered in Year 5 |
| 5 | Abijah | `3` years | sequential regnal count |
| 6 | Asa | `41` years | Judean stability anchor |
| 7 | Jehoshaphat | `25` years | sequential regnal count |
| 8 | Jehoram | `8` years | sequential regnal count |
| 9 | Ahaziah | `1` year | sequential regnal count |
| 10 | Athaliah | `7` years | usurpation / interregnum span |
| 11 | Jehoash / Joash | `40` years | sequential regnal count |
| 12 | Amaziah | `29` years | sequential regnal count |
| 13 | Uzziah / Azariah | `52` years | sequential regnal count |
| 14 | Jotham | `16` years | sequential regnal count |
| 15 | Ahaz | `16` years | Syro-Ephraimitic crisis field |
| 16 | Hezekiah | `29` years | `15`-year life extension; Dial of Ahaz field |
| 17 | Manasseh | `55` years | longest single reign in this ledger |
| 18 | Amon | `2` years | sequential regnal count |
| 19 | Josiah | `31` years | Deuteronomic reform field |
| 20 | Jehoahaz | `1/4` year | `3` months; deposed by Egypt |
| 21 | Jehoiakim | `11` years | first Babylonian deportation field |
| 22 | Jehoiachin | `1/4` year | `3` months; second Babylonian deportation field |
| 23 | Zedekiah | `11` years | final siege; First Temple burned |
| — | Ledger total | `394.5` years | post-Solomonic royal ledger |

Arithmetic note:
The displayed reign lengths sum to `394.5` years. The two `1/4`-year reigns together contribute `1/2` year to the ledger total.

### 10.5 Standardized Temple-to-destruction derivation

To calculate the First Temple-era block from initial construction to final destruction, the repository couples the sequential ledger with Solomon’s pre-fracture Temple years.

| Component | Value | Calculation |
|---|---:|---|
| Solomon’s total reign | `40` years | source datum |
| Temple foundation | Solomon’s fourth year / second month | source datum; schematic `1016 BC` state |
| Solomon’s post-foundation reign | `36` years | `40 − 4 = 36` |
| Post-Solomonic Kings ledger | `394.5` years | local ledger total |
| Temple-to-destruction block | `430.5` years | `36 + 394.5 = 430.5` |

Final formula:

```markdown
36 + 394.5 = 430.5
```

Author-clarified Temple-month state:
The `430.5`-year literal block is preserved beside the schematic Temple-month bridge. In that display, the schematic Temple construction state is `1016 BC` in the second month, and the collapse of Jerusalem reaches the Tammuz/Av field of `586 BC`. The result is a close `430`-year approximation joining years and months rather than a separate exact month/day operator inside this file.

The same block sits inside the wider Exodus / Entry field:

```markdown
1876 BC Entry in Nisan → 1446 BC Exodus in Nisan = 430
1446 BC Exodus in Nisan → 586 BC Fall field = 860 = 2 × 430 = 4 × 215
1016 BC second-month Temple construction state → Tammuz/Av 586 BC ≈ 430
```

Argument-control note:
The rounded `430` must not erase the local `430.5` ledger, and the `430.5` ledger must not erase either the schematic `430` state or the literal post-exilic `430` coreference. The final form preserves all three: `430.5` as the reign-ledger / Temple-block calculation, close `430` as the month-aware schematic bridge within the `215`-year base scheme, and exact `430` as the actual 2nd-month-to-2nd-month foundation coreference.

### 10.6 Literal post-exilic 430-year coreference

Author-clarified post-final coreference:
The schematic `1016 BC` second-month → Tammuz/Av `586 BC` bridge is not the only Temple-month witness. The actual historical Temple-foundation line preserves a literal second-month-to-second-month `430` from foundation laid to foundation laid again.

| State | From | To | Span | Function |
|---|---:|---:|---:|---|
| Schematic Temple-month bridge | `1016 BC` second month | Tammuz/Av `586 BC` | close `430` | schematic Kings / Ezekiel field |
| Literal post-exilic coreference | `967 BC` second month | `537 BC` second month | `430` | actual foundation laid → foundation laid again |
| Ordinary historical display | `966 BC` | `536 BC` | `430` | year-label display of the same foundation-to-foundation field |

Arithmetic fact:

```markdown
967 − 537 = 430
966 − 536 = 430
```

State-control note:
The literal `967 BC → 537 BC` second-month cycle does not correct the schematic `1016 BC → 586 BC` bridge. It shows a parallel historical coreference: the actual Temple foundation line preserves the `430` pattern while the repository schematic line satisfies the idealized Kings route. The two routes stand `49/50` years apart according to the active adjacent-date state: `1016 BC → 967 BC = 49`, while the ordinary `1016 BC → 966 BC` display preserves the `50`-year Kings dual-ledger offset.

Structural inference:
This parallel supports the authorial / scribal-awareness claim at a measured level. The scribes appear aware of the difference between the actual `967/966 BC` Temple foundation state and the schematic `1017/1016 BC` Kings route because the `430` Ezekiel / Temple pattern is satisfied in both the idealized line and the literal post-exilic return-foundation line.

Cross-reference: `File_08`, Kings dual-ledger and `967/966 BC` adjacent Temple foundation state; `File_17`, `537/536 BC` post-exilic / return-foundation field and prophetic span anatomy.

### 10.7 Theological summary

| Source claim | Final handling |
|---|---|
| Units are prophetic time: soldiers, degrees, days, and years represent temporal spans at prophetic scale. | Count-to-chronology structural inference grounded in textual data and checked arithmetic rows. |
| Design, not coincidence: the narrative’s numeric elements interlock with Exodus, Conquest, Christ, Paul, and Babylon anchors. | Preserved as source theological claim; classified as structural inference / providential synchronization, not formal probability proof. |
| The text validates itself through Jubilee language in Isaiah 37:30. | Textual datum supporting probable authorial design for the `490` Hezekiah harmonic. |
| Bidirectional precision: the backward shadow signals calculations working in both temporal directions. | Typological / structural reading; local Mirror role = bidirectional prophetic span / sundial mirror. |
| Time manipulation is biblical: Joshua’s long day, Hezekiah’s dial, and the Crucifixion darkness form a divine-control-of-time pattern. | Typological / theological note. |
| Christ is the fulcrum: `720`, `735`, `3.5 × 360`, and `3.5 × 430` converge on the Cross and its era. | Christological structural inference; exact Passion-date state remains `File_13` controlled. |
| Imperfection meets perfection: the `65` shattering cycle and the `49` Jubilee cycle cross at `735/734 BC`. | Structural inference from the checked `195/196` crossing; theological reading preserved. |
| Prophetic unity: Isaiah’s prophecies connect to Ezekiel’s `390 + 40` pattern. | Now supported locally through the Kings ledger, the schematic Temple block, and the literal post-exilic `967 BC → 537 BC = 430` coreference; broader component grammar remains `File_17` controlled. |
| The shadow as grace: backward shadow becomes forward grace through `14 + 1 + 14`. | Typological reading / structural inference tied to the Dial of Ahaz and Hezekiah reign display. |
| The Sevenfold Jubilee: `1191 BC → 701 BC = 490` magnifies into `4116 BC → 686 BC = 3430 = 70 × 49`. | Arithmetic fact plus Sabbatical-cycle theological note. |

Argument-control result:
The file’s main proof layer remains the checked arithmetic and the textual data. Structural inference is allowed where repeated state-controlled alignments interlock. Theological claims explain why the alignments matter. Providence-language is preserved, but it does not replace arithmetic, dependency control, or source-state precision.

## Audit Notes

Audit note:
No local author-decision or pressure-test blocker remains. Remaining items are cross-file updates that must be applied in their own files.

Audit note:
The detailed Immanuel macro-chiasm is no longer locally developed in `File_19`. It is cross-referenced to `File_17`, where the monarchy / Isaiah endpoint controls belong.

Audit note:
`AD 29515` is retained as the actual Pillar node in this file: `184315 − 29515 = 154800 = 430 × 360`. No BC-side Pillar coordinate carries local proof weight.

State-control note:
The Temple-month clarification is integrated as a state-control note. `File_19` does not attempt a granular month/day conversion. It preserves the authorial judgment that the literal `430.5` ledger, the close `430` Temple-month bridge, the literal `967 BC` second-month → `537 BC` second-month `430` post-exilic coreference, and the `860` Exodus-to-Fall relation belong together within the `215`-year base scheme.

## Unresolved Issues

1. Recommended cross-file updates remain to be applied in their own files. No local source blocker remains after pressure testing.

## Revision and archive note

This public-clean Markdown source removes only archival amendment history, pass logs, pressure-test repetition, pointer-refresh records, and obsolete replacement-workflow notes.

Detailed revision history is preserved in the `Repository_Change_Archive`.

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

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