File: File_17 Title: Prophetic Time Span Anatomy Entity: Prophetic Time Span Anatomy Classification: Foundational Axiom / Internal Structure Reference UUID: AXIOM_TIMESPAN_COMPONENTS Status: Final; Priestly 336-day Ledger cross-file update applied; File_14 Biological Fractals cross-file update applied; File_15 Generational Axiom cross-file update applied; File_19 Hezekiah / Temple 430 cross-file update applied; 1876 Cainan macro-vector cross-file update applied; File_26 precessional-season cross-file update applied; Samaria Node cross-file update applied; Ezekiel Date-String cross-file update applied; bounded cross-file updates focused pressure tested under current Register Agreement; Ezekiel endpoint-derivation / siege-frame / SP year-mirror bounded update applied (July 2026); File_59 Judah dual-Key instance pointer applied and focused checked July 16 2026; bounded File_62 dual-490 reciprocal pointer applied (July 2026); bounded Final File_66 common-2580 / 1150→1250 reciprocal update applied August 4 2026; bounded File_67 reciprocal pointer applied August 10 2026; bounded Final File_68 reciprocal pointer applied August 13 2026; bounded Final File_69 reciprocal pointer applied August 17 2026. Pressure-test status: Current; prior full and focused pressure-test results retained; focused verification complete August 4 2026 for the bounded Final File_66 reciprocal update; no new full pressure test is claimed and no publication blocker remains; focused reciprocal-routing verification complete August 10 2026 for the bounded File_67 pointer; no new full pressure test claimed; focused reciprocal-routing verification complete August 13 2026 for the bounded File_68 pointer; no new full pressure test claimed; focused reciprocal-routing verification complete August 17 2026 for the bounded File_69 pointer; no new full pressure test claimed. Reciprocal-routing verification status: File_62 and Final File_66 pointers applied and bounded machine-diff, exact-arithmetic, dependency, Machine-Guard, Markdown-structure, and publication-clean checks completed through August 4 2026; no new full pressure test was performed for either bounded update; bounded Final File_68 pointer applied and focused machine-diff, dependency, guard, and Markdown checks completed August 13 2026; no new full pressure test; bounded Final File_69 pointer applied and focused machine-diff, dependency, guard, Markdown-structure, and publication-clean checks completed August 17 2026; no new full pressure test. Register Agreement status: Checked against State_Vocabulary_Register v1.37 Part D §D.30 and Restart Capsule v11.36; the common-2580, 1150/1250, and Precession-Square dependency guards are registered. File_17 retains control of the ordinary ratio and precessional-day grammar; no File_17 Primary anchor, ratio definition, calendar state, or prior proof spine is changed; File_67 reciprocal guard registered at State_Vocabulary_Register v1.39 §D.31 and routed through Restart Capsule v11.38; no pre-existing proof-bearing state or Primary anchor changed; 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; File_69 reciprocal guard registered at State_Vocabulary_Register v1.41 Part D §D.33 and routed through Restart Capsule v11.40; no pre-existing proof-bearing state or Primary anchor changed. Publication-cleanup status: Public-clean Markdown source; archival amendment history routed to Repository_Change_Archive; bounded File_69 reciprocal replacement incorporated into the Manifest v22 non-archive release package; no live deployment or external archival capture claimed. Primary domain: Prophetic; Calendar; Comparative; Theological Traditions: MT; SP; LXX; Enochian; Jubilee; Second Temple Canonical source: Markdown Primary anchors: 931/930 BC; 736/735 BC; 701 BC; 686 BC; 671/670 BC; 606/605 BC; 541/540 BC; 1878–1871 BC; 1876–1871 BC; 1876 BC; 726–721 BC; late 722 BC ±1; 1846 BC; 1662/1661 BC; 1661 BC; 1446 BC; 1406 BC; 1399 BC; 606 BC; 587/586 BC; 967/966 BC; 537/536 BC; 516 BC; 490 BC; 2166 BC; 2091 BC; 2556 BC; 168–165 BC; 4116 BC; 4114 BC; 4176 BC; 4176n BC; 3901n BC; 3900n BC; 1476 BC; 1366 BC; AD 60; AD 29515; 168; 270; 275; 276; 280; 336; 364; 1260; 1274; 2150; 2160; 25800; 25920; 8600; 8640; 593 BC; 585 BC; 588 BC File_66 dependency-controlled comparison values: 841 BC; 1150; 1250; 184900; 185000; 185150; 2580; 25921; 1296050 Related files: File_00; File_04; File_05; File_07; File_08; File_10; File_12; File_13; File_14; File_15; File_16; File_18; File_19; File_22; File_26; File_30; File_51a; File_59; File_61; File_62; File_66; Restart Capsule v11.36; 490d Repository Style Guide v2.5; Project Procedures v3.5; State Vocabulary Register v1.37; File_67; File_68; File_69 Major operators: same-side BC span; Key of 23; 25/23; 70/69; File_62 half-scale instances 40.25 × 25/23 = 43.75 and 80.5 × 25/23 = 87.5; File_62 dual-490 routes 402.5 + (80.5 × 25/23) = 490 and 483 × 70/69 = 490; File_62 calendar-equivalent closure 483 × 25/23 = 525 and 525 × 336 = 490 × 360 = 176400; prophetic year 360; Enochian year 364; Cainan macro-vector B6 by dependency; audit-controlled 2307 companion; Priestly 336-day Ledger; 24 × 7 = 168; 168 + 168 = 336; 24 × 14 = 336; 4 × 7 = 28; 336 + 28 = 364; leap month 30; purification/testing 40; Jubilee 49; Danielic 490; Sojourn 430; Affliction 400; Canaan/Egypt division 215 + 215; 1260; 1274; 1290; 1335; 1334; 1150; File_66 local application 1150 × 25/23 = 1250; Samaria Node 1876–1871 BC → 726–721 BC; 2300; 2340; 2520; 2700; 2730; 1656; 1800; standard precessional day 72; alternate precessional day 71⅔ years = 215/3; standard precessional month 2160 = 30 × 72; alternate precessional month 2150 = 30 × 71⅔; standard precessional season 8640 = 120 × 72; alternate precessional season 8600 = 120 × 71⅔; common File_19/File_66 count 430² = 2580 × 71⅔ and 430 × 432 = 2580 × 72; File_10-controlled square root 161 × 25/23 = 175; File_15 authorized generational units; call-to-death generational-span register; exact normalized triad 100:70:40 = 10:7:4; Abrahamic-base fractions 10/10, 7/10, 4/10 = 2/5; generational LCM LCM(40, 70, 100) = 1400; File_19 Hezekiah 720; File_19 185000; 2150 = 5 × 430 = 10 × 215; 36 + 394.5 = 430.5; 967 BC second month → 537 BC second month = 430; 1446 BC → 586 BC = 860 = 2 × 430 = 4 × 215; 391 = 17 × 23; Ezekiel day-quartet 5 | 7 | 10 | 12 = 2 + 3 + 2; 2550 = 1260 + 1290; 2730 = 430 + 2300; 1075 = 2.5 × 430; 2580 = 430 + 2150 = 430 × 6; inclusive close 1655 / 1656; leap-month scheme-instance by File_12 §7A dependency Major modal states: prophetic component state; File_62 half-scale / dual-490 dependency state; File_66 common-2580 precessional-day interface state; File_66 1150/1250 Priestly application state; File_10/File_66 Precession-Square dependency state; textually explicit span state; inferred component state; Cainan macro-vector B6 state; audit-controlled 2307 / solar companion state; MT Ezekiel state; LXX Ezekiel state; SP Sojourn state; Sojourn / Affliction offset; Samaria Node 1150 half-cycle state; precessional display state; File_26 precessional month / season dependency state; File_19 Hezekiah prophetic complex state; Immanuel 65/49 crossing state; Temple 430.5 month-state bridge; literal post-exilic 430 coreference state; AD 29515 actual Pillar state by File_10 / File_19 dependency; Priestly 336-day Ledger state; Priestly-Enochian bridge corollary state; Priestly-Enochian half-week straddle state; Enochian half-week state; Jubilee register; Key-of-23 conversion state; purification-extension state; biological-fractal state; variant-gap gestation state; 276 full-year boundary-extension state; Triple-1656 Spine; 587/586 BC adjacent Fall of Jerusalem date-state; File_15 authorized generational-unit state; call-to-death generational-span register; exact normalized generational triad; generational LCM state; ordered endpoint-pair display state; decree-average state; slash-pair / range / envelope state; Creation-week / Year-6 state; typological reading; theological note; exploratory note; dependency-controlled cross-reference state; Ezekiel date-string state; siege-frame derivation state; SP year-mirror display state; leap-month scheme-instance state; File_59 Judah 1380 → 1400 / 1500 dual-Key instance state Revision basis: 490d Repository Style Guide v2.5; Restart Capsule v11.36; State Vocabulary Register v1.37; Project Procedures v3.5; prior finalized source; corrected Final File_61; Final File_62; Final File_66 with author-invoked Finalization August 4 2026; Repository_Change_Archive (non-controlling history); bounded File_59, File_62, and File_66 reciprocal routing; Final post-final pressure-tested File_67; State Vocabulary Register v1.39; Restart Capsule v11.38; Final File_68 after the August 13 2026 Finalization refresh; State Vocabulary Register v1.40; Restart Capsule v11.39; Final File_69; State Vocabulary Register v1.41; Restart Capsule v11.40; Publication Manifest v22 non-archive release package. Current refresh note: The August 4 2026 bounded Final File_66 update adds two downstream applications of existing File_17 grammar: the common 2580 precessional-day count in the File_19 430²/430×432 pair, and the 1150 × 25/23 = 1250 Abrahamic comparison at 841 BC. File_10 remains controlling for 25921; File_66 controls the Hezekiah chronology, 185150, and the celestial capstone. No File_17 Primary anchor, ratio definition, calendar state, or prior proof spine is changed; Bounded File_69 reciprocal routing applied August 17 2026; the registered guard changes no pre-existing arithmetic, anchor, source duration, node-class, operator, sign convention, calendar definition, Mirror protocol, claim-status label, theological claim, or dependency boundary. Source-history status: Version 5.3

September 8 2026 bounded Lamech routing: §8 explicitly retains MT 777; §13A.4 labels the 4026 LXX endpoint as a generated, non-operative comparison under File_18 §4A. No span, ratio, calendar, or pre-existing arithmetic changes. Register v1.53 §D.43 / Capsule v11.52 §10.30; focused verification only; no new full pressure test.

File_17 — Prophetic Time Span Anatomy

File_59 Judah dual-Key note: File_59 supplies the local exact instances 496800 × 70/69 = 504000 = 1400 × 360 and 496800 × 25/23 = 540000 = 1500 × 360. The Prophetic and Priestly Keys remain distinct operators; File_59’s Judah interpretation and Christological synthesis do not redefine File_17’s ratio families.

File_62 dual-490 reciprocal note: File_62 supplies the downstream exact instances 40.25 × 25/23 = 43.75, 80.5 × 25/23 = 87.5, 402.5 + (80.5 × 25/23) = 490, 483 × 70/69 = 490, 483 × 25/23 = 525, and 525 × 336 = 490 × 360 = 176400. File_17 remains controlling for the ratio families, prophetic-span grammar, and 336/360 calendar distinction. File_62 controls the proposed phase coordinates and local chronology. The common endpoint 490 does not make 25/23 and 70/69 one operator, and the equal day total does not make the Priestly 336-day year identical to the Prophetic 360-day year.

File_66 Hezekiah / precession reciprocal note: Final File_66 applies File_17 component grammar in two bounded ways:

430 × 430 = 2580 × 71⅔
430 × 432 = 2580 × 72

and:

1991 BC → 841 BC = 1150
2091 BC → 841 BC = 1250
1150 × 25/23 = 1250.

File_17 now registers these as downstream applications. File_19 controls the Hezekiah endpoints; File_10 controls 25921; File_66 controls the A7 chronology, 185150, and the theological synthesis.

File_67 Key-family application reciprocal note

Final File_67 applies File_17's established exact-rational grammar to the flanking-kings field: 161×25/23=175, 483×70/69=490, 828×70/69=840, and appendix-only 33120×70/69=33600. It also uses the established alternate/standard precessional-day pair 71⅔/72 in the 215/216 and 1075/1080 companion displays. File_17 remains controlling for the Key families and precessional components.

Machine Guard [FILE_17 FILE_67 KEY-FAMILY APPLICATION ROUTING]: Final File_67's 161→175, 483→490, 828→840, and appendix-only 33120→33600 executions are downstream instances of File_17's 25/23 and 70/69 operators. The 162/161 palindromic-calendar side ratio is appendix-only and is not a fourth standard Key-of-23 operator. File_17 retains all ratio definitions, component grammar, and precessional-day controls.

File_68 calendar-half and Sanctuary-contraction reciprocal note

Final File_68 applies File_17's prophetic-span grammar to two bounded downstream structures: the generation-resolved 1260/1274 calendar pair and the finite Sanctuary contraction 1290→1260→1150. The latter is executed as 1290=30+110+720+430, 1260=110+720+430, and 1150=720+430, terminating at the controlled 606/586/536 BC field.

Machine Guard [FILE_17 FILE_68 CALENDAR-HALF / SANCTUARY-CONTRACTION ROUTING]: Final File_68 may apply File_17's 1260, 1274, 1290, 1150, 400, and 430 grammar to its declared accordion and Sanctuary/Kings states. File_17 retains all prophetic-span definitions, component statuses, calendar firewalls, and Key-of-23 operators. File_68's mixed central triples, generated full-resolution coordinates, Kings chronology, and Week-6 interpretation do not become File_17 Primary anchors or redefine the prophetic components.

File_69 prophetic-span reciprocal note: Final File_69 executes 1260/1274, 2300±30, and the 25/23 / 70/69 families only as downstream applications. File_17 retains the prophetic-span and exact-ratio definitions.

Machine Guard [FILE_12 FILE_17 FILE_69 CALENDAR-RESOLUTION ROUTING]: Final File_69 may apply 180/182, 600/614, 1260/1274, and 13/13.5/14×360/364 inside its declared genealogical-resolution states. File_12 remains controlling for the Priestly 336, Prophetic 360, Enochian 364, and calendar non-collapse; File_17 remains controlling for prophetic-span grammar and the 25/23 and 70/69 operators. File_69 creates no new calendar-year definition, prophetic component, or parent-file Primary anchor.

0. File-function

File_17 defines the internal component structure of major prophetic time spans used across the 490d Unified Chronology repository.

The file treats prophetic spans as composite structures rather than monolithic integers. Some components are textually explicit, such as 1260 = 360 + 720 + 180 in the “time, times, and half a time” formula. Other components are inferred from repeated chronological, calendrical, and typological usage.

This file functions as a span-component reference. It does not replace the anchor-specific arguments in File_00, File_04, File_14, File_15, File_16, File_18, File_19, or the later Rounded Scaffold files. When a span is tied to an anchor such as 1876 BC, 1846 BC, 1446 BC, 587/586 BC, 1406 BC, 701 BC, 686 BC, 967/966 BC, 537/536 BC, or 4176 BC, the local state and node-class must be preserved.

Publication-cleanup note: This public-clean source preserves the Final status and the later cross-file-update caution label in the header. Detailed pass logs, pressure-test records, bounded update ledgers, and replacement-workflow notes are archived rather than repeated in the public body.

0.1 Working state register

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

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

0.2 File map

0.3 Modal-state processing rules

1. A span-family entry is not a universal operator. It becomes executable only when the local section states the active state, tradition, node-class, and arithmetic operator.
2. Slash-pairs such as 931/930 BC, 736/735 BC, and 1662/1661 BC are paired state labels, not averages and not ranges. Preserve order and evaluate component-wise if later arithmetic requires it.
3. En-dash ranges such as 1878–1871 BC, 728–721 BC, and 168–165 BC are windows or historical ranges. Do not collapse them into a single anchor.
4. 1876 BC is a shared year-label. In this file it may function as Entry, famine-window target, Sojourn start, or component endpoint depending on active state. Follow File_16 and File_04 where 1876 BC is more than a component example.
5. 1846 BC is the Affliction-start state in the 400/1260 register. It is related to 1876 BC by the 30-year offset but does not replace it.
6. 400, 430, 1260, and 1290 may appear in the same Egypt-bookend field, but each value must retain its distinct node-class: Affliction, Sojourn, half-week, or extended half-week.
7. Prophetic-year, Enochian-year, Jubilee, and precessional readings are parallel component states. Do not use one calendar register to correct another unless a local operator explicitly does so.
8. Typological and theological notes may explain why a component matters, but arithmetic facts and stated textual data carry the computational burden.
9. Rounded Scaffold or Year-6 values are clarity-only unless a section explicitly opens the Rounded or Year-6 state. 4176 BC in §13 is an MT +275 / Year-6 comparison state, not a replacement Creation anchor.
10. Dependency-controlled cross-references such as File_30 remain dependency-controlled. Do not infer missing derivations from a span-family resemblance.
11. The Priestly 336-day Ledger, Prophetic 360-day Year, and Enochian 364-day Year are distinct calendar registers. 336 + 28 = 364 may function as a bridge corollary, but it does not erase the 336-day baseline or the 364-day Enochian state.
12. The Priestly-Enochian 3.5-day straddle may project into the prophetic half-week under the day-year principle, but this projection is a File_12 dependency and must not be generalized to every local 3.5 use.
13. File_14 biological-fractal values such as 270, 275, 276, and 280 are dependency-controlled when used as gestation / purification states. In File_17, they may clarify span-component families but do not become universal component operators unless a local section opens File_14's argument.
14. File_15 generational-unit values such as 100, 70, and 40 are dependency-controlled when used as Abrahamic, Jacobean, or Mosaic authorized units. In File_17, they may clarify span-component families but do not become universal component operators unless a local section opens File_15's argument.
15. The common count 2580 in 430² = 2580 × 71⅔ and 430 × 432 = 2580 × 72 coordinates two precessional-day states. It does not make 71⅔ and 72 equal, and it must not be merged with the Ezekiel 2580 day-string or another chronology unless the active node-class is restated.
16. Final File_66’s 1150 × 25/23 = 1250 is a downstream application at the 841 BC coordinate. It does not redefine the 1150 family, make 1250 a universal prophetic span, or promote 841 BC into File_17’s Primary anchors.
17. 25921 = 161² is controlled by File_10. File_17 may supply the root conversion 161 × 25/23 = 175, but it must not treat 25921 as a fourth ordinary ratio or import File_66’s 185150 capstone as local proof.

0.4 Machine Guards for File_17

Machine Guard [FILE_17 COMPONENT STATUS]:

File_17 is a component reference file. A span decomposition listed here does not by itself prove that every context using the same number has the same node-class, tradition, state, or operator. When a component is applied to a date or anchor, the active file must restate the governing state.

Machine Guard [FILE_17 SOJOURN / AFFLICTION OFFSET]:

The 1876 BC Sojourn state, the 1846 BC Affliction state, and their 430/400 and 1290/1260 offsets must remain distinct. 1876 BC and 1846 BC are related by the 30-year leap-month / apparent-age unit, but one does not replace the other.

Machine Guard [FILE_17 PROPHETIC / ENOCHIAN FIREWALL]:

The prophetic half-week 1260 = 3.5 × 360 and the Enochian half-week 1274 = 3.5 × 364 are parallel state expressions. Do not collapse 1274 into 1260, and do not treat the 14-year difference as a correction unless the local section explicitly states that it is an adjustment.

Machine Guard [FILE_17 PRIESTLY 336-DAY LEDGER]:

The 336-day Priestly Ledger is component grammar: 24 × 7 = 168; 168 + 168 = 336; 48 × 7 = 336; and 24 × 14 = 336. It is the Priestly service-cycle baseline, not a correction of the 360-day Prophetic Year and not a correction of the 364-day Enochian Year.

Machine Guard [FILE_17 PRIESTLY / ENOCHIAN BRIDGE COROLLARY]:

The bridge 4 × 7 = 28 and 336 + 28 = 364 is a corollary state. It may interface the Priestly ledger with the Enochian year, but it must not be used to delete the 336-day baseline or to require one exact historical festival-week mechanism unless the local file supplies source-control.

Machine Guard [FILE_17 KEY-OF-23 EXACT RATIOS]:

The Key-of-23 ratios 25/23, 70/69, and 300/299 are exact rational operators. Do not replace them with rounded decimals. Do not invoke the Residue Protocol unless the local file explicitly shifts from whole-year conversion to physical residue or residual-display arithmetic.

Machine Guard [FILE_17 FILE_62 DUAL-490 NON-COLLAPSE]:

Final File_62 may apply 25/23 locally to 40.25/80.5, apply 70/69 to the whole 483, and compare 525 × 336 with 490 × 360. These are downstream applications of File_17 component grammar. Do not promote File_62’s proposed phase dates into File_17 Primary anchors; do not exchange 25/23 with 70/69; do not identify the Priestly 336-day year with the Prophetic 360-day year; and do not treat exact rational day-volume equality as exact physical solar-calendar identity.

Machine Guard [FILE_17 CAINAN MACRO-VECTOR DEPENDENCY]:

File_17 may index 2300, 2520, 2730, and 1260 → 1290 → 1260 as component families, but the Cainan macro-vector B6 classification belongs to File_16 and the table-source values belong to File_18. Do not use span-component vocabulary to create new event-node witnesses or to alter the File_16 Bullseye inventory.

Machine Guard [FILE_17 2307 / SOLAR AUDIT]:

The 2307 inclusive companion and solar comparison remain audit-controlled. They are not active File_17 span families unless a later sanctuary / Hanukkah / phase-resolved solar dependency opens them explicitly.

Machine Guard [FILE_17 FILE_14 BIOLOGICAL-FRACTAL DEPENDENCY]:

File_14 controls biological-fractal terminology for 270, 275, 276, and 280, the 40 + 40 purification structure, typological mirroring, variant-gap gestation, and the Triple-1656 Spine. In File_17, these are dependency-controlled component states. They must not replace ordinary prophetic span-component states, and File_14 typological mirroring must not be treated as formal repository Mirror protocol.

Machine Guard [FILE_17 PRECESSIONAL DISPLAY]:

The standard precessional-day state is 72 years = 1 Precessional Day, derived from 25920 ÷ 360 = 72. The alternate precessional-day state is 71⅔ years = 1 Precessional Day = 215/3 years, derived from 25800 ÷ 360 = 215/3. Use 71⅔ as the display form and 215/3 as the exact arithmetic state.

Machine Guard [FILE_17 COMMON 2580 NON-COLLAPSE]: 430 × 430 = 2580 × 71⅔ and 430 × 432 = 2580 × 72 preserve one common count under alternate and standard precessional-day lengths. Do not identify 71⅔ with 72, and do not collapse this interface with the Ezekiel 2580 day-string or another 2580 chronology state.

Machine Guard [FILE_17 FILE_66 1150 / 1250 APPLICATION]: Final File_66 may apply 25/23 to 1150 at the dependency-controlled 841 BC coordinate, yielding 1250. This does not redefine the 1150 family, create a universal 1250 span, or promote File_66’s dates into File_17 Primary anchors.

Machine Guard [FILE_17 PRECESSION-SQUARE DEPENDENCY]: File_10 controls 25921 = 161². File_17 controls the ordinary Priestly ratio and may state 161 × 25/23 = 175. Do not treat 25921 as a fourth Key-of-23 fraction, and do not import File_66’s 185150 × 7 = 50 × 25921 as local File_17 proof.

Machine Guard [FILE_17 SLASH-PAIR / WINDOW SAFETY]:

Slash-pairs and windows in this file are state labels. 931/930 BC, 736/735 BC, 1662/1661 BC, and similar forms must not be averaged, reversed, or collapsed. Ranges such as 1878–1871 BC, 728–721 BC, and 168–165 BC remain windows or historical ranges unless a local section identifies a specific internal event-year.

Machine Guard [FILE_17 DECREE AVERAGE]:

The 490 BC average is a calculated composite center of four decree dates. It is not a fifth decree and not a replacement for any individual decree date. Treat the decree list as a source-retained historical datum until a controlling dependency supplies the source-critical framing.

Machine Guard [FILE_17 TYPOLOGY / ARITHMETIC BURDEN]:

Typological and theological notes may explain why a span component matters. They must not carry arithmetic burden. Arithmetic facts remain direct calculations from stated anchors or operators, and textual data remain distinct from structural inference.

Machine Guard [FILE_17 FILE_15 GENERATIONAL-UNIT DEPENDENCY]:

The Abrahamic 100, Jacobean 70, and Mosaic 40 are File_15 authorized generational units. They may intersect existing File_17 component families, especially 40, 70, 400, and 1400, but shared numbers do not create identity. Restate the active File_15 state before using the triad as a generational axiom.

0.5 Arithmetic-control summary

Arithmetic-control scope: This control checks visible arithmetic statements, same-side BC spans, component sums, factorization claims, Key-of-23 conversions, and exact precessional-day displays. It does not revise argument force except where arithmetic status must be clarified.

0.6 Argument-control summary

Argument-control scope: This control clarifies evidential role and claim-status without changing arithmetic, anchors, modal states, node-classes, sign conventions, operators, or theological claims.

Argument-control result: The file now presents span families as a component dictionary. The strongest claims are textual datum plus arithmetic fact. Typological, theological, aesthetic, and dependency-controlled observations are retained but do not carry the arithmetic burden.

1. Preamble: the molecular structure of time

Biblical prophetic time spans are not monolithic integers but composite structures with internal components. Just as 1260 is explicitly divided into “a time, times, and half a time” (360 + 720 + 180), other spans have native component breakdowns. Some are stated; others are inferred.

Understanding these components explains:

• why certain numbers appear in related contexts;
• how different spans interlock without “jostling”;
• the calendrical logic underlying prophetic arithmetic;
• how the chronology flows “like the wheels of Ezekiel’s chariot” — orderly, but multi-faced.

The components function as the internal gearing that allows multiple prophetic systems to mesh smoothly. Understanding these parts also enables one, including AI, to spot where other patterns may exist by extending a component part to its larger whole.

Typological note: The source compares divided prophetic spans with covenant-cutting imagery. The analogy explains why divisions such as 2300 → 1150 + 1150 and 2520 → 1260 + 1260 matter symbolically. The arithmetic burden remains the stated division of the span, not the typological analogy itself.

2. The 65 family: shattered numbers

Active state: Isaiah shattered-number register. The 65, 130, 195, and 390 values are treated here as a related curse / judgment family. This does not make every use of 130 or 390 identical in node-class.

2.1 The 65: half of curse / Isaiah’s shattering

Source: Isaiah 7:8 — “Within sixty-five years Ephraim will be shattered, no longer a people.”

The repetition in Isaiah 8:9, “Prepare for battle, and be shattered! Prepare for battle, and be shattered!”, signals the doubling of 65 to make 130. Isaiah 40:2 confirms: “she has received from the LORD’s hand double for all her sins.”

The 35/70 versus 65/130 Kingdom parallel:

2.2 The 65/130/195/390 escalation

2.3 Historical anchors

Modal-state note: The paired labels 931/930 BC, 736/735 BC, 671/670 BC, 606/605 BC, and 541/540 BC are retained as slash-pair year labels. They are not averaged or collapsed in this file.

Arithmetic retained from source:

931 − 736 = 195 = 65 × 3 = half of 390

2.4 File_19 Immanuel 65/49 crossing

Active state: Immanuel 65/49 crossing state by File_19 dependency.

File_19 transfers the detailed Immanuel macro-chiasm to File_17 because the endpoints belong to the monarchy-to-return field rather than to the local Hezekiah proof burden.

State-control note: 735/734 BC is a conception/birth slash-pair and must not be collapsed. The 391 = 17 × 23 macro-chiasm may support the Immanuel 65/49 crossing field, but 930 BC and 539 BC remain monarchy / return endpoints and must be supplied by the active Kings / Exile dependency when the argument becomes proof-bearing.

3. The 190 family: LXX Ezekiel / Metonic interface

Active state: LXX Ezekiel / Metonic comparison state. The textual LXX burden structure and the astronomical Metonic cycle are parallel component witnesses, not the same node-class.

3.1 The 190: LXX variant / lunar cycles

The 190 interfaces the LXX textual tradition with the Metonic lunar cycle of 19 years, allowing prophetic spans to mesh with astronomical observations.

4. The 390 family: prophetic year + leap month

Active state: closing-cycle / leap-month component state. The 390 value may be generated by several component structures; each row must retain its derivation.

4.1 The 390: closing-cycle function

4.2 The closing-cycle function

390 represents the final year of an era: the 360-day year plus the intercalary month of 30 days that closes the old cycle before a new one begins.

The Adam / Creation application:

The 30 days before Adam equal the full leap month, converting to 30 years for Adam’s apparent age.

4.3 Levitical confirmation

This grounds Adam’s +30 Apparent Age in calendrical logic. It represents the leap month that closes the pre-Adamic Creation cycle.

5. The 430/432 family: six days of precession

Active state: Sojourn / precessional comparison state. The 430 Sojourn value, the 432 precessional value, and the 215/216 half-cycle values are parallel component states. Do not use one to correct the other.

5.1 Precession basis

Precessional arithmetic note: The file preserves two precessional-day states. The standard state uses 72 years = 1 Precessional Day from a 25920-year Great Year. The alternate state uses 71⅔ years = 1 Precessional Day = 215/3 years from a 25800-year Great Year.

Structural inference: Both readings function as six cosmic days, a Creation-week parallel minus the Sabbath. The Abrahamic star-field supplies the typological setting; the arithmetic basis remains the paired precessional-day states.

5.1A File_26 precessional month and season extension

Active state: File_26 precessional month / season dependency state.

File_26 extends the same paired precessional-day states into month and season displays:

2160 = 30 × 72
2150 = 30 × 71⅔
8640 = 120 × 72
8600 = 120 × 71⅔
25920 = 360 × 72
25800 = 360 × 71⅔

Exact arithmetic note:

71⅔ = 215/3
30 × 215/3 = 2150
120 × 215/3 = 8600
360 × 215/3 = 25800

Dependency note: These values are registered as span-component vocabulary for later citation. File_26 controls the local 18726 BC, Balih, Nexus, and Pillar applications; File_17 only records the component grammar.

5.1B File_19 / File_66 common 2580-day interface

Active state: File_66 common-2580 precessional-day interface by File_19 dependency.

File_19 supplies the paired products:

430 × 430 = 184900
430 × 432 = 185760.

Under the two File_17 precessional-day states, both carry one common count:

184900
= 2580 × 71⅔
= 2580 × 215/3

185760
= 2580 × 72.

Their difference is:

185760 − 184900
= 860
= 2580 × (72 − 71⅔)
= 2580 × 1/3
= 2 × 430.

Component-control result: The common 2580 demonstrates that 430 × 430 and 430 × 432 are alternate/standard measurements of the same count of precessional days. It does not identify the day lengths and does not replace File_19’s anchor-specific Hezekiah argument. Final File_66 controls the later 185150/25921 synthesis.

5.2 The Sojourn as new Creation

State note: 1878 BC is the famine-beginning state; 1876 BC is the Entry / Sojourn state in this table. They are adjacent related labels inside the Egypt field, not the same node.

Typological note: Israel’s multiplication into a mighty nation is read here as a new-Creation pattern over six cosmic days. This note explains the theological fit; the arithmetic basis remains the 432/430 comparison.

5.3 The 215/216 half-cycle: three days of precession

Slash-pair note: 1662/1661 BC is preserved as a paired state label. The table does not resolve the pair into one date.

The Forming + Filling pattern of Genesis 1 is replicated:

5.4 Additional 430 components

State note: This table intentionally preserves MT Ezekiel, LXX Ezekiel, SP Sojourn, and inferred prophetic-generation decompositions as distinct states.

5.5 File_19 Temple 430 and post-exilic coreference

Active state: Temple 430.5 month-state bridge and literal post-exilic 430 coreference state by File_19 dependency.

File_19 adds a monarchy-ledger baseline for the Temple-derived 430 field. This material belongs in File_17 as span-component grammar and does not replace the anchor-specific handling in File_08 or File_19.

Arithmetic checks:

36 + 394.5 = 430.5
967 − 537 = 430
966 − 536 = 430
1446 − 586 = 860 = 2 × 430 = 4 × 215
1016 − 967 = 49
1016 − 966 = 50

State-control note: The literal 967 BC second-month → 537 BC second-month line demonstrates a foundation-to-foundation 430 alongside the schematic 1016 BC → 586 BC route. It does not correct the ordinary 966 BC → 536 BC display and does not collapse the historical ledger into the schematic Kings ledger.

6. The 400 family: affliction

Active state: Sojourn / Affliction offset. 1876 BC and 1846 BC are related by the 30-year offset, but the Sojourn state and Affliction state remain distinct.

6.1 The 400: four generations

6.2 The 400/430 leap-month relationship

The 400-year affliction (Gen 15:13) and the 430-year Sojourn (Exod 12:40) differ by exactly 30 years, the same leap-month unit.

7. The 490 family: Daniel’s seventy weeks

7.1 The 490: core components

7.2 The 483: sixty-nine weeks

Conversions:

File_62 downstream application note: Final File_62 instantiates the same component grammar in a proposed Jacob–Moses phase carrier. It uses the local Priestly route 402.5 + (80.5 × 25/23) = 490 and the whole-carrier Prophetic route 483 × 70/69 = 490, while the full Priestly conversion yields 483 × 25/23 = 525 and the calendar-equivalent total 525 × 336 = 490 × 360 = 176400. These are downstream applications. The common endpoint and equal day volume do not merge the two ratios or the two calendar registers.

7.3 The 70/49/21 Temple triangle

Arithmetic retained from source:

49 + 21 = 70

7.4 The Daniel 10 connection

The “three weeks” (21 days) delay in Daniel 10 builds directly upon Daniel 9’s seventy weeks.

The Providence Protocol demonstrated:

The 49 + 21 = 70 division shows prayer and human will operating alongside Divine sovereignty: “the one not impeding the other.”

7.5 The 490 BC average: four-decree harmonic

Active state: decree-average composite state. The four dates remain individual historical decree labels; 490 BC is the arithmetic average / center, not a replacement decree.

Claim-status note: The sum and average are arithmetic facts. The choice to treat the four decree dates as a composite harmonic is a structural inference retained from the source. The historical framing of the decree list remains source-retained and dependency-controlled unless a future file supplies fuller source-critical support.

The source reads the “going forth of the command to restore and build Jerusalem” (Daniel 9:25) as a composite decree field rather than as only one isolated date. On that reading, the mathematical average of the four decree dates produces 490 BC, creating a date-span equivalence with the 490-year prophecy.

Given:

Calculation retained from source:

$538 + 519 + 458 + 445 = 1960$

$1960 \div 4 = 490\text{ BC}$

Structural result:

The source treats this as the base layer for the 4900-year fractal. The restrained claim is that the duration, 490, and the composite date, 490 BC, form a date-span equivalence inside the Danielic register.

Dependency note: File_30, the Alpha-Omega Link, controls the downstream claim that this 490-year seed expands into the 4900-year cycle from Shem, connecting the Decree Era, 490 BC, to the Messianic Era, AD 33, via the Key of 23. File_17 retains the cross-reference but does not locally re-prove the File_30 expansion.

8. The 777 bridge: Daniel to Revelation

Active state: Daniel-Revelation bridge state. 777 is MT Lamech’s lifespan and functions here as a component bridge into 1260; it does not become a universal half-week operator.

8.1 The 777: Lamech’s lifespan

This explains why 1260 accommodates multiple patterns without conflict. It has multiple valid decompositions.

9. The 1150 family: evening or morning

Active state: Daniel 8 half-cycle state. The 1150 may be read as half of 2300, as 23 × 50, or as a 720 + 430 composite; each derivation retains its node-class.

9.1 The 1150: half of 2300

9.1A Final File_66 decadal Priestly expansion at 841 BC

Active state: File_66 1150/1250 Priestly application state.

Final File_66 supplies a fixed historical-comparison endpoint at 841 BC:

1991 BC → 841 BC = 1150 = 50 × 23
2091 BC → 841 BC = 1250 = 50 × 25.

Therefore:

1150 × 25/23 = 1250.

The gain is exactly:

1250 − 1150 = 100.

Dependency boundary: 1991 BC and 2091 BC remain Abrahamic dependency anchors; 841 BC and the historical interpretation belong to Final File_66. File_17 records only the exact 1150 → 1250 Key instance. The related factorizations 185150 = 161 × 1150 and 201250 = 161 × 1250 remain downstream corroboration rather than new File_17 span families.

9.2 The 720 + 430 historical application

Window note: 1878–1871 BC and 728–721 BC are seven-year windows. They are not converted into single-year anchors in this file.

The seven-year famine, 1878–1871 BC, projects to the broader seven-year Samaria fall window, 728–721 BC, via the 1150 components. File_00 now refines the schematic Samaria Node to 726–721 BC, generated from 1876–1871 BC → 726–721 BC, while preserving the actual late-722 BC ±1 fall-state separately.

9.2A Samaria Node refinement by File_00 dependency

Active state: Samaria Node 1150 half-cycle state.

File_00 refines the Samaria application of the 1150 family by distinguishing the actual historical fall from the schematic node. The actual Fall of Samaria remains late 722 BC ±1, after a siege beginning about 725 BC. The schematic Samaria Node is 726–721 BC.

The refined File_00 node is generated from Jacob's Entry / famine-remainder field:

1876 BC → 726 BC = 1150
1871 BC → 721 BC = 1150

The broader seven-year display retained in this file remains useful orientation:

1878–1871 BC → 728–721 BC

State-control note: The broader 728–721 BC window is a source-retained full famine / fall-window display. The refined File_00 Samaria Node is 726–721 BC, with 726 BC as schematic onset / collapse label and 721 BC as terminal / latest-fall label. Neither endpoint replaces the actual late-722 BC fall state.

Machine Guard [FILE_17 SAMARIA NODE 1150 CONTROL]: Do not collapse the broader 728–721 BC source-retained window with the refined File_00 726–721 BC Samaria Node. Use the refined node when citing the File_00 schematic Samaria argument. Preserve the actual late-722 BC ±1 fall as a separate historical state.

9.3 Hanukkah fulfillment: 168–165 BC

Range note: 168–165 BC is retained as a historical fulfillment range. The day-count table functions inside that range and does not resolve it to one civil year.

Tradition allows 1150 + 7 ending.

9.4 Shem → Conquest example: 1150 + 7

Active state: MT +215 Shem-to-Conquest comparison. 1406 BC is Conquest begins / Moses dies; 1399 BC is first Sabbath rest. The seven-year Conquest-rest relation is preserved as a local span state.

Arithmetic retained from source:

2556 − 1150 = 1406
1406 − 7 = 1399

This demonstrates the 1150 + 7 pattern at the macro-chronological level: from Shem, the blessed son through whom Messiah comes, to the completion of the Conquest and first rest in the Promised Land.

10. The 2300 family: evening-morning cycle and purification extensions

Active state: Daniel 8 evening-morning cycle with purification-extension overlays. The base 2300 state and the 2340, 1300, and 2600 extensions must remain distinct.

10.1 The 2300: Key-of-23 signature

The 2300 is the signature number for the Key of 23 because:

2300 × 25/23 = 2500 = 50 × 50

10.2 The 2340 extension: male-child pattern

The 2340 breakdown:

Structural comparison:

Structural inference: The 2340 functions as the curse-associated counterpart to 2520, just as 65 is paired against 70, and 130 against 140, in the source’s component grammar.

10.3 Purification extensions: male and female

State note: This subsection opens a typological purification-extension state. The Leviticus 12 male/female purification values explain the extension, but they do not replace the prophetic half-week or full-week values.

The 40-day male purification period and the 80-day female purification period in Leviticus 12 extend the base prophetic spans.

The sacrificial pattern:

Theological note: The source reads the male, 1260, as a half-week “cut off” for the sake of the female, 2520, the full week. This theological reading echoes:

• the Creation pattern: 40 + 40 from 4186 → 4146 → 4106 BC (File_14, §4);
• Adam alone, male, 40 years → Eve within, female, +40 years → birth / purification complete;
• Christ, the Last Adam, cut off in the midst of the week (Dan 9:27) to make His Bride, the Church, whole.

Claim-status note: The arithmetic facts are 1260 + 40 = 1300, 2520 + 80 = 2600, and 1300 × 2 = 2600. The redemptive-sacrifice reading is theological / typological support and must not replace the arithmetic basis.

10.4 Chronological examples of 1300/2600

State note: This subsection shifts between SP Creation-to-Noah state, MT Priestly-expansion state, and typological Nephilim-cleansing language. The traditions and operators are not collapsed.

The 1300 and 2600 take shape in various ways throughout the chronology as extensions of 1260 and 2520.

SP example: Creation → Flood → Noah’s death.

MT example: the 1800 Priestly Expansion.

1656 × 25/23 = 1800

The 1656 decomposes via the Key of 23:

The 1800 breakdown, 7 + 6 pattern × 100:

The 7 + 6 = 13 template:

Creation: 7 days to Adam + 6 years to Fall = 13
13 × 100 = 1300

The pattern replicates at scale:

500 + 700 + 600 = 1800

Note:

2340 = 65 × 36 = 65 × 6 × 6

This connects to the shattered number, 65, from Isaiah 7–8.

Cross-reference: Biological validation: File_14, 40 + 40 purification structure. Adamic parallel: File_07, §10, 270 + 40 birth pattern.

11. The 2520 family: full prophetic week

Active state: full prophetic-week state. 2520 is treated as the complete seven-year prophetic week; internal decompositions remain component forms of the same full-week state.

11.1 The 2520: seven prophetic years

Chiastic internal structure:

360 + 720 + 180 | 180 + 720 + 360
1260 + 1260 = 2520

Arithmetic note: The full-week chiastic display preserves the stated structure by mirroring the explicit half-week formula on both sides of the midpoint.

The week divides symmetrically around its midpoint, reflecting the “midst of the week” in Daniel 9:27.

12. The 1260 family: half-week variants

Active state: half-week variant register. The prophetic, Enochian, extended, and blessing endpoint forms are parallel states within the half-week family.

12.1 The 1260: prophetic half-week

The explicit biblical breakdown, “time, times, and half a time,” establishes the template for all other spans.

12.2 The 1274: Enochian half-week / double-13 Jubilees

State note: 1274 is the Enochian / Jubilee interface state. It is not a correction of 1260; it is the half-week expressed in a different calendar register.

The Enochian 364-day year produces 1274 as the equivalent of 1260, targeting the exile of Daniel and Ezekiel, 604–597 BC from 1878–1871 BC.

Dual-system interface:

This allows 1274 to run simultaneously with both the Enochian calendar and the Levitical Jubilee system.

12.3 The 1290: half-week + leap month

State note: The Egypt-bookend table uses two related but distinct tracks: 1876 BC as Entry / Sojourn state and 1846 BC as Affliction-start state. The 30-year offset links them without collapsing them.

The Egypt bookends:

Typological note: The same 30-year leap-month offset, 1876 → 1846 and 1290 → 1260, operates at both ends of Israel’s Egypt story: going out and returning. The arithmetic is the offset; the poetic-justice reading is interpretive support.

12.4 The 1335/1334: blessing endpoint with Key of 23

Ordinal-state note: 1335 is the stated blessing endpoint, while 1334 is the hidden complete-day component in the source argument. These are related ordinal states, not competing endpoint claims.

The 1334 hidden component: The phrasing “waits for and reaches the 1335th day” carefully includes the entirety of day 1335, thereby touching the end of day 1334.

Historical verification, Creation → Exodus:

Arithmetic retained from source:

4116 − 1446 = 2670 = 1335 × 2
4114 − 1446 = 2668 = 1334 × 2

12.5 The 1260 family summary table

13. The 2700/2730 family: full Creation-week span

Active state: Creation-week / Year-6 comparison state. 2700 and 2730 are related by the 30-year Sojourn / Affliction offset, but the 2700 Affliction form and 2730 Sojourn form remain distinct.

13.1 The 2700: 7.5 prophetic years

The 2700 represents the complete Creation-week, seven days plus the 0.5-day solar/lunar straddle, scaled to prophetic years. The 2730 variant adds the full 430-year Sojourn instead of the 400-year Affliction.

Structural note: This section was source-located as subsection F under the 1260 family. It is retained here as its own major section because it governs a distinct Creation-week / sanctuary-affliction span family.

13.2 Historical application: MT +275 position

State note: 4176 BC is used here as a Year-6 / MT +275 comparison state. It does not replace the base Creation endpoint in other files. 1876 BC remains the Entry / Sojourn state in this table.

Alternate endpoint: Exodus.

13.3 Joshua connection

Joshua, Hebrew Yehoshua, “YHWH saves,” is born exactly 2700 years from Creation Year 6:

4176 BC − 2700 = 1476 BC

Joshua lives 110 years, the same as Joseph, and dies in 1366 BC:

1476 − 110 = 1366

The 400-year Affliction (Gen 15:13) spans from Entry, 1876 BC, to Joshua’s birth, 1476 BC.

Typological note: The source reads Joshua’s birth at this point as the deliverer born at the completion of the Affliction prophecy. The arithmetic basis is the 1876 − 1476 = 400 span.

13.4 Component relationship

The 30-year difference:

2730 − 2700 = 30

This is the same apparent-age / leap-month offset that appears throughout the system: Adam +30, 430 versus 400, and related structures.

Cross-reference: Pattern Mirror: File_07, §11, 2300/2700 Inverted Mirror. Event anchor: File_05, Exodus entity. Axiom definition: File_00, Adam +30.

13.5 Cainan macro-vector dependency note

Active state: Cainan macro-vector B6 by File_16 / File_18 dependency.

The focused-pressure-tested Cainan macro-vector uses several span-component families already controlled in File_17:

Audit note: The companion 2307 checks are retained as audit-controlled material, not as an active span family in File_17.

13A. The Ezekiel date-string: the 2 + 3 + 2 signature

Active state: Ezekiel date-string state (day-level display).

This section registers a bounded day-level date-string. It does not modify the year-scale 2700/2730 family of §13, does not open a granular month/day conversion operator, and does not extend the File_19 Temple 430.5 month-state bridge, whose non-granularity guard stands.

13A.1 Textual data

13A.2 The day-quartet

The four attested day-numbers divide one seven-day scheme:

5 | 7 | 10 | 12  →  2 + 3 + 2 = 7

The traditional 9th-night falls at the scheme's mid-point. The call-week supplies the outer members (5th and 12th; fourth month, 593 BC) and the fall supplies the inner members (7th and 10th; fifth month, 586 BC).

Claim-status: structural inference over textual data. The mapping of both date-sets onto one week-scheme is a declared display, not a calendrical claim.

13A.3 Day-counts on the declared 360 mapping

Declared mapping: months of 30, years of 360, same-side inclusive month arithmetic; day-level display only.

The 2700 / 2730 pair in this table is day-scale. The §13 2700 / 2730 family is year-scale. Same integers, distinct states; do not collapse. The 2730 itself carries two readings — leap-month form (2700 + 30) and Enochian-register form (7.5 × 364) — arithmetically identical, conceptually distinct; dual-reading note, no collapse. The +30 throughout is scheme-licensed by the File_12 §7A intercalation cycle, not a bare device.

13A.3a The siege-frame derivation

Siege (9/10/10) → refugee (12/10/5) = 1080 − 5 = 1075 = 2.5 × 430
Call (5/4/5) → refugee = 2700 (2730 with the leap month)
Call → siege = 2730 − 1075 = 1655; 1656 inclusive
Siege → city (11th yr, 4/9) ≈ 899;   city → refugee ≈ 176 ≈ six months;   899 + 176 = 1075

The siege-to-refugee span is the sides' 430 at the 2.5 scale; the call stands 1656 inclusive before the siege — and the glory of the call-vision appears "like a rainbow in the clouds on a rainy day" (Ezek. 1:28), the Flood's own sign, as Creation stood 1656 from the Flood (typological reading). The city-to-refugee six months carries the Ezra 7:9 journey warrant. The siege duration is read at 2.5 years — an author ruling on the 1.5 / 2.5 question, on the ground that the pattern belongs to Ezekiel's frame (historical-critical inference). The week-window recurs: the city's 9th day sits within a 5–12 window as the temple's days sit within the fifth month's, and the night-divider slot recurs three times — the call-week's mid-night, the city taken by night on the 9th, the temple fired on the 9th toward evening. Claim-status: textual data (all dates); arithmetic fact (all spans under the declared mapping); author ruling / historical-critical inference (the siege duration); typological reading (the rainbow and night-divider lines).

13A.4 The 2730 = 430 + 2300 decomposition

2730 − 430 = 2300

The siege-posture 430 (§13A.1) plus the Daniel 8 component (§10) exactly compose the Enochian-register total, the call-week carried forward within the span. Sibling decomposition: 2580 = 430 + 2150 = 430 × 6 — the sides' 430 in days, "a day for every year" (Ezek. 4:6, the day-for-year license stated in the text itself), plus five more. Cross-scale display: 2580 days = 430 × 6 equals the year-span of the generated, non-operative LXX Lamech comparison 4026 → 1446 = 2580 (File_18 §4A.5–§4A.6). This is a cross-scale structural comparison, not a main LXX birth date or proof of the proposed 182/188 transmission mechanism. The actual main Lamech birth in that frame remains 4020 BC.

Claim-status: arithmetic fact (the identities); textual datum (the day-for-year license); structural inference (the carried-week reading); cross-scale display (the twin).

13A.5 The thirtieth-year signal

Ezekiel's opening "In the thirtieth year" is read as a double signal: the priest's thirtieth year (Num. 4:3) and the +30 apparent-age register of the cumulative Adam (File_00 Adam +30; File_22).

Claim-status: typological reading.

13A.6 Year-scale lock (dependency)

586 BC → 1876 BC = 1290 remains classified by File_16. File_17 registers the span component only.

13A.7 Calibration note (method)

The independently dated Ezekiel string exhibits the same 2 + 3 + 2 = 7 signature as the cumulative chronology's Aaron/Moses 3 with Shem's ±2 (File_18; File_22). Independently dated biblical texts thereby calibrate the inferred cumulative width.

Claim-status: structural inference; method note.

13A.8 The 1290 + 1290 endpoint — derived; open item closed

The endpoint is the fall of the temple, intercalated form: call → temple = 2580 = 1290 + 1290 with the leap month (§13A.3). The former open item is discharged (July 2026); the four-form family 2520 / 2550 / 2550 / 2580 stands complete in both orders — the day-scale sibling of the File_20 §7A.3 three-combination completion.

13A.9 The SP year-mirror

The SP regular chronology carries the same values in years, over the same terminal nodes:

Ezekiel's day-counts are thus mirrored in SP years intersecting at the 1876 / 1846 heads, distilling to the week overwhelmed seven years before the fall. Member selections author-declared (gear labels by File_11; SP values by File_18 §3; heads by File_16). Claim-status: arithmetic fact (the chains); structural inference / providential synchronization (the mirror reading).

14. The 1656/1800 family: Creation-to-Flood

Active state: Creation-to-Flood cross-manuscript state. 1656 is a shared span-form, but its target differs by tradition.

14.1 The 1656: Adam to Flood

The 1800 expansion:

1656 × 25/23 = 1800 = 50 × 36

14.2 The 1656 cross-manuscript anchoring

Modal-state note: The same 1656 span points to different Noah-centered node-classes in LXX, MT, and SP. Do not treat the three rows as one event.

The same span has three anchors, all centered on Noah.

14.3 The Priestly 336-day Ledger and 364-day bridge

Active state: Priestly service-cycle component state; Priestly-Enochian bridge corollary.

The Priestly 336-day Ledger is a foundational service-cycle component. It is generated by the 24 priestly courses and should be treated as a calendar-state baseline rather than as a failed solar year.

State-control note: The 336, 360, and 364 registers remain distinct. The 336 + 28 = 364 bridge does not erase the 336-day Priestly baseline and does not turn the 364-day Enochian Year into the Priestly Ledger.

Half-week projection: The Priestly-Enochian liturgical straddle is preserved by File_12 as a structural source of the prophetic half-week. In File_17, it is retained as component grammar:

3.5 × 360 = 1260
3.5 × 364 = 1274

Dependency note: File_12 controls the 24-course source map and the Priestly-Enochian liturgical projection. File_17 records the component grammar only. Do not infer one exact historical execution mechanism for festival weeks, Qumran phase practice, or temple-roster administration from this component section alone.

Source-control vector: The Priestly 336-day Ledger source-control vector includes 1 Chronicles 24:1–19, 1 Chronicles 9:25, 2 Kings 11:5–7, 2 Chronicles 23:4–8, Luke 1:5, Josephus Antiquities 7.365–366, Mishnah Taanit 4:2, Mishnah Sukkah 5:7–8, Qumran Mishmarot texts 4Q320–4Q330, Talmon, VanderKam, Elior, Ben-Dov, and Ratzon / Johnson. In File_17, this vector supports component-state classification only and does not replace File_12 as the source-control file.

14A. File_14 biological-fractal dependency controls

Active state: File_14 biological-fractal dependency.

File_14 Final post-final pressure-tested supplies the biological-fractal and purification controls used when span-component values are read as gestation, purification, or biological validation rather than as ordinary prophetic components.

Claim-status note: These values may be cited as File_14-controlled biological-fractal or typological states. They do not become universal operators merely because the same number appears in another span family.

15. Intercalary constants

Active state: intercalary constant register. These constants explain recurring adjustments; they are not universal add-ons to be applied automatically.

These are the recurring adjustment values that allow different calendrical systems to mesh.

15.1 The 30-day / year unit: leap month

15.2 The 14-day / year unit: Enochian adjustment

15.3 The 45-day / year unit: extended adjustment

15.4 The 75-day / year unit: full extension

16. Component interaction examples

Active state: component-interaction register. The following examples show how components cascade or nest. They do not authorize uncontrolled substitution between span families.

16.1 The 1260 → 1290 → 1335 cascade

1260  base half-week
+ 30  leap month
= 1290 abomination endpoint
+ 45  extended wait
= 1335 blessing endpoint

16.2 The 390 → 430 → 490 escalation

390  Israel’s sin-years = 360 + 30
+ 40 Judah’s sin-years
= 430 total burden / Sojourn
+ 60 Terah variable
= 490 Daniel’s seventy weeks

16.3 The 65 → 130 → 195 → 390 curse escalation

65   shattered
× 2
= 130 double for all her sins

65 + 130 = 195 half of 390
195 × 2 = 390 Ezekiel’s full Israel burden

16.4 The 2300 → 2520 relationship

Arithmetic note: The controlled arithmetic in this subsection is the gap between the Daniel 8 evening-morning span and the full prophetic week.

2520 − 2300 = 220

Therefore:

2300 evening-morning
+ 220 adjustment
= 2520 full prophetic week

No Key-of-23 operator is active for the 220 gap in the final source. Do not introduce a Key-of-23 claim for this gap unless a future dependency supplies the missing derivation.

17. The flow principle: Ezekiel’s wheels

Active state: non-collision principle. This section explains how multiple component readings can coexist when their states are explicit. It does not merge those states.

17.1 Multi-faced harmony

Just as Ezekiel’s chariot wheels move in multiple directions simultaneously without collision (Ezek 1:15–21), prophetic time spans interlock through shared components.

17.2 Non-collision principle

The components allow the chronology to express multiple patterns simultaneously.

All four are valid within their stated states. None contradicts the others. The components provide the degrees of freedom.

17.3 Saturation principle

Argument-state note: This paragraph preserves the source’s aesthetic / theological evaluation while reducing rhetorical force. The claim is interpretive and synthetic; it does not add a new arithmetic operator.

The chronology displays high pattern density in agreement with the narrative without requiring every correspondence to be stated in the same way or at the same level. The component parts explain why many biblical numbers can nest within one another: high information density with limited redundancy, provided each component remains tied to its active state, operator, and node-class.

18. Cross-reference index

Dependency-state note: The following files are cross-reference dependencies. A file reference does not import the full operator into File_17 unless the local section explicitly opens that dependency.

Audit notes

Audit note [FILE_17 2307 / SOLAR COMPANIONS]: The 2307 and solar companion lines remain audit-controlled by dependency. They are not blockers in File_17 and do not become active operators unless a later file opens the required sanctuary / Hanukkah / phase-resolved calendar state.

Dependency note [FILE_17 FILE_19]: File_19 remains an applied Hezekiah prophetic complex and Temple 430 dependency for the Immanuel 391 = 17 × 23 macro-chiasm, the Temple 36 + 394.5 = 430.5 ledger, the literal 967 BC second-month → 537 BC second-month 430 coreference, and the Hezekiah 720 / 185000 span field.

Dependency note [FILE_17 FILE_26]: File_26 supplies the bounded precessional month / season dependency: standard 2160/8640/25920 under 72, and alternate 2150/8600/25800 under 71⅔ = 215/3. File_17 registers component grammar only.

Dependency note [FILE_17 EZEKIEL DATE-STRING]: The §13A date-string is a bounded day-level display. It does not extend the File_19 Temple 430.5 month-state bridge, does not create a granular month/day conversion operator, and leaves the §13 year-scale 2700/2730 family unchanged. File_16 retains classification of the 1876 → 586 = 1290 lock. The +30 leap-month members are scheme-instances of the File_12 §7A intercalation cycle with placement declared; the SP year-mirror (§13A.9) is display-only here, its values controlled by File_18, File_11, and File_16.

Dependency note [FILE_17 CAINAN MACRO-VECTOR]: File_16 and File_18 supply the Cainan macro-vector dependency. File_17 registers the span-component grammar for 2300, 2520, 2730, and 1260 → 1290 → 1260, while preserving File_16 as the Nexus-classification file and File_18 as the table-source file.

Dependency note [FILE_17 FILE_62 DUAL-490]: Final File_62 supplies the local phase chronology and the exact downstream instances 40.25 × 25/23 = 43.75, 80.5 × 25/23 = 87.5, 402.5 + 87.5 = 490, 483 × 70/69 = 490, and 525 × 336 = 490 × 360 = 176400. File_17 remains the component and operator controller. File_61 supplies the separate local 216 = 3 × 72 Joshua application. Neither downstream file alters File_17’s Primary anchors or ratio-family definitions.

Dependency note [FILE_17 FILE_66]: Final File_66 supplies the Hezekiah/Judah dates, the 185150 companion, and the theological/statistical synthesis. File_17 registers only the component interfaces 430² = 2580 × 71⅔, 430 × 432 = 2580 × 72, and 1150 × 25/23 = 1250. File_10 remains controlling for 25921 = 161².

Unresolved issues

None. The former §13A.8 open item is closed (endpoint derived, July 2026). Later local pressure testing may still be requested by the author, but no current source blocker remains.

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 pre-existing arithmetic, anchors, modal states, node-classes, sign conventions, operator definitions, slash-pairs, ranges, envelopes, Mirror protocols, claim-status labels, theological claims, or dependency boundaries are changed. The bounded Final File_66 update adds two downstream component applications, three non-collapse Machine Guards, reciprocal routing, and focused arithmetic clarification without redefining the parent span families.

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