File: File_12 Title: Calendrical Physics Legacy source title: CALENDRICAL_PHYSICS.md Entity: TIME PHYSICS Classification: Advanced Mechanics / Solar-Lunar Synchronization UUID: SYS_PHYSICS Status: Verification-complete bounded amendment working copy — September 6 2026; inherited Final source preserved; Sothic additions centrally registered at State Vocabulary Register v1.52 §D.42 / Restart Capsule v11.51 §10.29; new material not separately author-Finalized or full-file pressure tested. Inherited Final status: Final; post-final Solstice Mirror, Tishri Recess, Priestly 336-day Ledger, priestly source-control, and focused pressure-test patches applied; File_34 post-final citation-control update applied and focused pressure tested June 3 2026; File_56-routed bibliography-vector update applied (July 6 2026); 360-day intercalation cycle bounded update applied (July 6 2026); bounded File_61 / File_62 Mosaic-phase and dual-490 reciprocal pointer applied July 23 2026; bounded Final File_68 reciprocal pointer applied August 13 2026; bounded Final File_69 reciprocal pointer applied August 17 2026. Amendment trust scope: New sections, state rows, and guards are amendment-local pending separate author Finalization; central registration is complete at State Vocabulary Register v1.52 §D.42 / Restart Capsule v11.51 §10.29. All inherited Finalization, pressure-test, and publication assertions below refer to the frozen pre-amendment source unless expressly dated September 6 2026. No new full-file pressure test or live deployment is claimed. Pressure-test status: Current; publication-clean verification complete; prior focused patches retained; File_34 post-final citation-control update focused pressure tested June 3 2026. Focused checks complete for the bibliography-vector and intercalation-cycle bounded updates; §7A focused pressure test PASS July 6 2026 (15/15 with File_17 §13A), the §7A.4 exact-closure note added at test; 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: Bounded corrected-File_61 / Final-File_62 calendrical pointers applied and focused machine-diff checked July 23 2026; no new full pressure test was performed for this pointer-only 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: Inherited File_12 controls remain as previously registered; the September 6 Sothic/365-day amendment adds three centrally registered guards and companion states at State Vocabulary Register v1.52 §D.42 / Restart Capsule v11.51 §10.29. No inherited arithmetic, Primary anchor, calendar definition, Mirror protocol, source datum, or prior proof spine changes. 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: Calendar; Prophetic; Comparative; Theological Traditions: biblical calendar; Enochian; New Testament / Christological Canonical source: Markdown September 7 2026 calibration clarification: Author-approved bounded addition at §5.1A keeps S_K / 7.475 dominant and adds S_E / 7.5 as a supportive file-local companion. A bounded follow-up designates the later Simon/FITS expression as the primary epoch comparison, retains Laskar/NASA as an older independent check, and adds the Enoch–Moses midpoint as providential / typological corroboration only. Exact-rational, epoch-computation, dependency, and diff checks complete. The inherited Final and September 6 amendment trust scopes are unchanged; no new full-file pressure test, central registration, or deployment is claimed. Primary anchors: Nisan / Spring = 06:00; Tebeth / Winter = 00:00; Christ's Birth; 0.5-unit offset; 7 / 7.5; rounded Null Zone display 6 BC to AD 6 as 10 under mod-5 / mod-10 chronology; precise cross-axis 6 BC to AD 6 = 11; File_00 related exact Null Zone 6 BC → AD 5 = 10; 6480 / 6450 / 30; legacy 299/300 source label; author-resolved 300/299 Enochian Key-of-23 ratio; 365.2422 true-solar reference; 365.24 display; 364; 91 days; Day 91; 6-month offset; 3.5 years; 336-day Priestly Ledger; 24 priestly courses; 168 + 168; four festival-week / epagomenal-week corollary; 360-day Prophetic Year; 1 Enoch 75:1–2 / source shorthand 75:2; 1 Enoch 82; Enoch 80; Matthew 24:22 Related files: File_00; File_01; File_02; File_04; File_06; File_07; File_08; File_09; File_16; File_17; File_34; File_51a; File_54; File_61; File_62; Restart Capsule v11.30; 490d Repository Style Guide v2.5; Project Procedures v3.5; State Vocabulary Register v1.31; File_68; File_69 Major operators: 24-hour year; Solar/Lunar Straddle; 0.5-unit day-start offset; 7 / 7.5 duality; 10x Null Zone; rounded mod-5 / mod-10 Null Zone display; precise civil cross-axis span; Dual-Precession Drive; 6480 versus 6450; 30-year difference; Enochian Gearbox; legacy 299/300 source label; author-resolved 300/299 Enochian Key-of-23 operator; 91-day seasonal leader; Nisan Rule; Tishri Recess dependency fork; 6-month phase offset; Aaron/Moses L = 3.5; 3.5-year half-week state; Priestly 336-day Ledger; 24 × 7 = 168; 168 + 168 = 336; 24 × 14 = 336; 4 × 7 = 28; 336 + 28 = 364; Priestly-Enochian liturgical half-week projection; Solstice Mirror; File_09 phase-resolved Mirror coordinate-completion; Julian Jan-1 phase-coordinate proof; Mirror suffix inversion; paired-versus-single Mirror distinction; epagomenal exclusion; 360-day Prophetic Year; theological shortening; claim-status control; argument-control rule; 6 × 360 + 30 = 2190 = 6 × 365; 4 × 360 + 30 = 1470 = 3 × 490; 14610 = 40 × 365.25; leap-month counted-or-not option; File_62 proposed Jacob/Aaron/Moses phase pairs, quarter- and half-scale 25/23 expansion, distinct dual-490 routes, and 525 × 336 = 490 × 360 = 176400 day-volume closure by downstream dependency Major modal states: Nisan default; Tishri dual-date state; Creation-side Nisan/Tishri suffix state by File_07; File_09 phase-resolved Mirror suffix-inversion dependency where Mirror coordinate-completion is opened; File_09 Julian Jan-1 phase-coordinate proof state; File_09 paired-versus-single Mirror distinction; Solar / Lunar Straddle; EnvNorm 7; EnvSpread 7.5; 0.5-unit phase state; Tishri/Nisan 6-month phase-offset state; Aaron/Moses terminal L = 3.5 straddle state; Priestly 336-day Ledger state; Priestly half-year 168 state; Priestly two-week shift variant; epagomenal festival-week corollary state; Priestly-Enochian liturgical projection state; File_34-controlled 3 months and 3.5 days dependency state; File_34 post-final citation-control state; Appendix B phase-chain dependency state; 10x scale-state; symbolic Null Zone state; rounded mod-5 / mod-10 Null Zone state; precise 11-year cross-axis state; File_00 exact 10-year dependency state; Enochian year; Solar year; Prophetic Year; precessional standard / alternate display state; legacy relation-label state; author-resolved Enochian Key-of-23 ratio state; arithmetic-control state; argument-control state; source-retained datum state; verified source-text anchor state; arithmetic-fact state; architectural-axiom state; corollary state; structural-inference state; dependency-controlled Solstice Mirror state; theological-note state; punitive Enochian shortening; gracious Christological shortening; 360-day intercalation cycle state; counted-or-not option principle; 1260 / 1290 same-half-week corollary state; year-scale instantiation display; File_61 / File_62 half-clutch, proposed Mosaic phase-pair, quarter-/half-scale Key, dual-490, and Priestly/Prophetic day-equivalence downstream dependency state Major claim-status labels: source-retained calendrical datum; author-resolved source control; verified source-text anchor; arithmetic fact; dependency-controlled arithmetic fact; architectural axiom; corollary; structural inference; dependency-fork clarification; dependency-controlled Mirror coordinate-completion; local Mirror source-label; theological note; source-text anchor; audit note Revision basis: 490d Repository Style Guide v2.5; Restart Capsule v11.30; State Vocabulary Register v1.31; Project Procedures v3.5; prior finalized source; corrected Final File_61; Final File_62 post-final pressure tested; bounded reciprocal-routing update of July 23 2026; Repository_Change_Archive (non-controlling history); 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: Bounded corrected-File_61 / Final-File_62 reciprocal routing aligns active control pointers to 490d Repository Style Guide v2.5, Restart Capsule v11.30, State_Vocabulary_Register v1.31, and Project Procedures v3.5. Register Agreement status is recorded in the header; the downstream Mosaic-phase and dual-490 pointers change no File_12 arithmetic, anchors, source data, modal-state logic, node-classes, operators, sign conventions, slash-pairs, ranges, envelopes, Mirror protocols, pre-existing Machine Guards, claim-status labels, theological claims, or dependency boundaries. Detailed pass logs, pressure-test records where applicable, pointer-refresh history, and replacement-workflow notes are preserved in Repository_Change_Archive; 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.

File_12 — Calendrical Physics

Related Repository Files

Dependency note: File_07 is controlling for the Creation-side Tishri/Nisan dual date. Where File_12 opens Creation-side Nisan/Tishri forms, it must preserve n and t as state labels, preserve Creation-week endpoint slash-pairs, and keep endpoint states distinct from Year-6 / Adam states.

Dependency note: File_09 controls phase-resolved Mirror suffix inversion only where a section explicitly opens Mirror coordinate-completion for a .5 Tishri/Nisan dual date. File_12 may name this dependency, but the local file does not import new Mirror arithmetic unless the section opens that protocol.

Post-final Solstice Mirror dependency note: The source term Solstice Mirror is now dependency-classified. When the term is used for exact Mirror-coordinate work, the governing explanation is in File_09: the Julian Jan-1 phase-coordinate proof with Oct 1 / Jan 1 / Apr 1 mapping, the civil cross-axis span BC + AD − 1, the phase-resolved suffix-inversion rule, the paired-versus-single Mirror distinction, and the phase-polarity caution for standalone exact Mirror nodes.

Post-final Tishri Recess dependency note: The source line 6-month offset (3.5 years) is now classified as compressed dependency-fork language, not as ordinary arithmetic equivalence. The 6-month element belongs to the Tishri/Nisan phase-offset state, controlled by File_06 and File_09 where exact phase-coordinate work is opened. The 3.5 element belongs first to the Aaron/Moses L = 3.5 half-week / priestly-straddle dependency controlled by File_01, File_04, File_06, File_00, and File_17. The Priestly-Enochian liturgical half-week projection is now elevated as a structural theorem inside File_12, while its granular historical execution variables remain source-control dependent.

Post-final Priestly 336-day Ledger dependency note: The 336-day Priestly Ledger is a foundational architectural baseline, not a peripheral approximation. It is generated by the 24 priestly courses as a half-year cycle of 24 × 7 = 168 days and a full schematic year of 168 + 168 = 336 days. The two-week shift variant, 24 × 14 = 336, preserves the same conceptual total. Interstitial solar-alignment weeks and festival-week inserts are firewalled from the baseline count. A corollary bridge to the Enochian year is possible through four epagomenal festival weeks: 4 × 7 = 28; 336 + 28 = 364.

File_34 post-final citation-control note: File_34 Final; post-final pressure tested now controls the full SKL / Berossus month/day function. In File_12, this remains a dependency state for the SKL appended 3 months and 3.5 days datum only. File_34 Appendix B phase-chain arithmetic, the 2370 corridor, the 30 + 20 + 30 restoration corridor, Pillar / AD target spans, and Sanctuary Fractal machinery are not locally opened unless a section explicitly names those states.

File_61 / File_62 reciprocal-routing note: Corrected Final File_61 and Final File_62 apply this file's calendar controls to a downstream Mosaic phase and birth-law investigation. File_62 proposes Jacob 1930t/1929n BC, Aaron 1530t/1529n BC, and Moses 1527t/1526n BC as phase-paired states; develops 40.25 × 25/23 = 43.75, 80.5 × 25/23 = 87.5, the distinct closures 402.5 + (80.5 × 25/23) = 490 and 483 × 70/69 = 490, and the exact total-day identity 525 × 336 = 490 × 360 = 176400. File_12 controls the Tishri/Nisan, 3/3.5, 7/7.5, 336/360, and ratio-family firewalls; Files 61–62 control the proposed dates and chronological applications. No proposed phase coordinate is promoted into File_12's Primary anchors, and equality of total days does not identify the Priestly and Prophetic year states.

File_68 generation-resolved calendar-half reciprocal note

Final File_68 uses File_12's established Prophetic 360 and Enochian 364 calendar registers to interpret the exact downstream identities 70+110=180=360/2, 72+110=182=364/2, 7×180=1260, and 7×182=1274. File_68's generation-resolved accordion is an application of those calendar states, not a redefinition of them.

Machine Guard [FILE_12 FILE_68 GENERATION-RESOLVED CALENDAR-HALF ROUTING]: Final File_68 may derive 180/182 generation-resolved cells and 1260/1274 fully stretched weeks from its fixed 70/72 carriers plus +110. File_12 remains controlling for Prophetic 360, Enochian 364, rounded 365, true-solar 365.2422, 3.5×360/364, and their non-collapse. File_68's generated 8756/8854/8936/9036 BC coordinates and 720/728/730 triptych do not become File_12 Primary anchors or new calendar-year definitions.

File_69 calendar-resolution reciprocal note: Final File_69 applies the established Prophetic 360, Enochian 364, and Priestly 336 registers within declared genealogical resolutions. File_12 remains the calendar-definition controller.

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_12 defines the repository's calendrical-physics control layer. It records the seasonal clock, the Solar/Lunar Straddle, the 10x Null Zone, precessional comparison states, the Enochian Gearbox, the Nisan / Tishri seasonal directive, the epagomenal exclusion principle, and the theological contrast between punitive Enochian shortening and gracious Christological shortening.

Publication-cleanup note: This public-clean source preserves the Final status, prior focused patch status, and File_34 focused pressure-test status in the header. Detailed finalization and focused pressure-test ledgers are archived rather than repeated in the public body.

This file does not replace the Creation matrices in File_07, the span-component dictionary in File_17, the Flood/SKL Enochian rails in File_02, or the foundational Calendrical Engine in File_00. It functions as a compact operator and state-control file for later calendar arguments.

Creation-side dependency note: The Tishri/Nisan dual date at Creation is not inferred from the short source text by itself. It is governed by File_07, which treats Creation-week endpoints such as 4114n/4115t BC as endpoint states and keeps them distinct from Year-6 / Adam states such as 4116 BC. File_12 therefore preserves the Nisan / Tishri dual-date field as a state-control dependency rather than expanding it into new local Creation arithmetic in this source.

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

Argument-control rule: Arithmetic facts and source-retained calendrical data carry the base layer of File_12. Dependency-controlled arithmetic facts may support the local argument only inside their stated dependency. Structural inferences explain how calendar states interlock. Theological notes, verified source-text anchors, local Mirror source-labels, dependency-controlled Mirror coordinate-completion states, and audit notes are preserved, but they do not replace arithmetic, source-control, or dependency control.

Source-control note: The author-resolved controls remain active: 300/299 is the active Enochian Key-of-23 operator, the Null Zone distinguishes rounded mod-5 / mod-10 display from precise cross-axis counting, and verified source-text anchors do not become independent arithmetic operators.

0.1 Working state register

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

0.1a Node-class and display-state register

This register identifies values most likely to be misapplied by future retrieval or arithmetic review.

0.2 File map

0.3 Terminology controls

0.4 Machine Guards for File_12

Machine Guard [FILE_12 CREATION-SIDE TISHRI / NISAN]:

Where File_12 touches Creation-side Tishri/Nisan dual dates, File_07 controls the display state. Preserve n and t as Nisan-state and Tishri-state labels. Preserve Creation-week endpoint slash-pairs such as 4114n/4115t BC as endpoint states, and do not collapse them into Year-6 / Adam states such as 4116 BC.

Machine Guard [FILE_12 FILE_07 / FILE_09 DISPLAY ORDER]:

File_07 source endpoint display and File_09 phase-resolved Mirror display are related but distinct. 4114n/4115t BC is a File_07 Creation-week endpoint slash-pair display. 4115t/4114n BC → AD 1406t/1407n is a File_09 Mirror coordinate-completion display where that Mirror state is explicitly opened. Do not reorder, unsuffix, average, or convert one display into the other without naming the active dependency and operator.

Machine Guard [FILE_12 SOLAR / LUNAR STRADDLE]:

The 0.5-unit Solar/Lunar Straddle, EnvNorm 7, and EnvSpread 7.5 are coordinated states, not corrections of one another. Do not collapse 7 into 7.5, or 7.5 into 7, without a local operator that explicitly resolves the state.

Machine Guard [FILE_12 NULL ZONE ROUNDING / PRECISION]:

The source phrase “Year Zero” is symbolic Null Zone language in this file. Do not infer a civil year 0. The source display 6 BC to AD 6 checks exactly as 6 + 6 − 1 = 11. In rounded mod-5 or mod-10 chronology, this 11-year crossing may be displayed as a 10-year Null Zone. In precise actual-date or exact Mirror work, the full 11-year cross-axis amount must be preserved.

Machine Guard [FILE_12 NULL ZONE / FILE_00 DEPENDENCY]:

File_00 supplies a related exact 10-year Null Zone display as 6 BC → AD 5, checking as 6 + 5 − 1 = 10. File_12 preserves the separate rounded 6 BC to AD 6 display by author decision. Do not replace either state with the other.

Machine Guard [FILE_12 ENOCHIAN RATIO DIRECTION]:

The active Enochian Key-of-23 operator is 300/299, the third allowable ratio after 25/23 and 70/69. It means that 300 × 364 Enochian days nearly equals 299 × 365.2422 true-solar days. The legacy 299/300 label is retained only as source-history / inverse wording where it appears. Do not make 299/300 the operative conversion ratio.

Machine Guard [FILE_12 SOLAR / ENOCHIAN / PROPHETIC YEAR FIREWALL]:

The Solar Year display 365.24, the Enochian Year 364, and the 360-day Prophetic Year are distinct calendar states. The epagomenal exclusion principle explains a harmonic reckoning state; it does not erase Solar or Enochian states unless a local section explicitly opens that conversion.

Machine Guard [FILE_12 TISHRI RECESS]:

The source preserves both a 6-month offset and a 3.5-year statement under the Tishri Recess. Treat this as compressed dependency-fork language, not as ordinary arithmetic equivalence. The 6-month state is the Tishri/Nisan phase-offset state. The 3.5-year state is the half-week / priestly-straddle state, controlled by the Aaron/Moses L = 3.5 dependency where the terminal Aaron/Moses register is active. The Priestly-Enochian liturgical half-week projection may explain the 3.5 state outside the terminal Aaron/Moses register, but it must remain distinguished from the ordinary 6-month phase-offset and from the File_34 3 months and 3.5 days datum.

Machine Guard [FILE_12 PRIESTLY 336-DAY LEDGER]:

The 336-day Priestly Ledger is a foundational architectural baseline. It is generated by 24 × 7 = 168 and 168 + 168 = 336, with the two-week variant 24 × 14 = 336 preserving the same conceptual total. Interstitial solar-alignment weeks and festival-week inserts are firewalled from this baseline. Do not demote the 336-day ledger to peripheral context, and do not use it to erase the 360-day Prophetic Year, the 364-day Enochian Year, or the Solar Year display.

Machine Guard [FILE_12 PRIESTLY / ENOCHIAN HALF-WEEK]:

The Priestly-Enochian phase-offset is a structural half-week state: the Priestly vector begins from Saturday evening / Sunday onset, while the Enochian solar vector is anchored to Wednesday morning at sunrise. The resulting 3.5-day straddle may project by the day-year principle to the 3.5-year / 1260-day prophetic half-week. Historical execution variants, including Qumran-adjacent Tuesday-evening boundary questions and festival-week roster mechanics, remain corollary / source-control material unless a later file promotes them with source-control.

Machine Guard [FILE_12 PRECESSIONAL DISPLAY]:

The 6480 and 6450 values are paired precessional display states in the Dual-Precession Drive. Do not use either value to correct the other. The 30-year difference is retained as source terminology under “The Lubricant.” Its visible difference checks; its interpretive role remains dependency- and argument-controlled.

Machine Guard [FILE_12 SOLSTICE MIRROR / FILE_09 CONTROL]:

Solstice Mirror is a source-retained seasonal Mirror label in File_12. When it is used for exact .5 Tishri/Nisan Mirror coordinate work, File_09 governs the explanation: the Julian Jan-1 phase-coordinate proof, Oct 1 / Jan 1 / Apr 1 mapping, phase-resolved suffix inversion, paired-versus-single Mirror distinction, and civil cross-axis component checks using BC + AD − 1. It is not automatically File_00 foundational Mirror protocol, Protocol 1 rounded target generation, 10x Mirror scaling, or inverse-number reversal.

Machine Guard [FILE_12 FILE_09 PAIRED / SINGLE MIRROR FIREWALL]:

File_09 distinguishes paired phase-resolved Mirror dates from standalone exact Mirror dates. Paired .5 Tishri/Nisan slash-pairs use suffix inversion, such as Yt/(Y−1)n BC → AD (Y−1)t/Y n, to preserve the half-year relation. Standalone exact Tishri or Nisan Mirror nodes may be valid, but they use their own numeric-year counterpart and can flip phase polarity at the midpoint. Do not use standalone polarity behavior to overwrite paired t/n Mirror coordinate-completion.

Machine Guard [FILE_12 SOURCE-TEXT ANCHORS]:

The references to 1 Enoch 75:1–2 / source shorthand 75:2, 1 Enoch 82, Enoch 80, and Matthew 24:22 are preserved as verified source-text anchors or source-supported source-control notes. Citation-control is now complete for these anchors. They remain theological and textual references and must not carry arithmetic burden unless a later section explicitly promotes them with source and operator control.

Machine Guard [FILE_12 ARGUMENT BURDEN]:

Arithmetic facts may support calendrical mechanics. Dependency-controlled arithmetic facts may support the local argument only inside their stated dependency. Structural inferences require explicit state, node-class, tradition, and operator control. Theological notes, verified source-text anchors, local Mirror source-labels, dependency-controlled Mirror coordinate-completion states, and audit notes remain preserved but do not carry the main argument.

Machine Guard [FILE_12 FILE_62 PHASE / DUAL-490 DEPENDENCY]:

Final File_62's proposed Jacob, Aaron, and Moses phase pairs; 40.25/80.5 quarter- and half-scale calculations; distinct Priestly 25/23 and Prophetic 70/69 routes to 490; and 525 × 336 = 490 × 360 = 176400 day-volume closure are downstream dependency states. Do not promote the proposed phase labels into File_12's Primary anchors, do not exchange 25/23 with 70/69, do not identify a 336-day Priestly year with a 360-day Prophetic year, and do not convert exact rational equalities into exact physical solar-calendar identities.

Machine Guard [CANONICAL MARKDOWN / DERIVED AI FORMATS]:

Markdown remains the canonical repository source. This file is not reshaped into JSON, JSONL, prompt/response format, dialogue format, or generic AI-summary format during ordinary revision.

0.5 Arithmetic-control summary

Arithmetic-control scope: This arithmetic-control layer records visible arithmetic statements and arithmetic-adjacent operator claims in File_12. It preserves the author-resolved Null Zone and Enochian ratio decisions without adding new chronological rows.

Arithmetic-control result: The visible arithmetic checks are stable. The Null Zone is resolved by separating rounded mod-5 / mod-10 display from precise 11-year cross-axis counting. The Enochian ratio direction is resolved: 300/299 is the active Enochian Key-of-23 operator. The Solstice Mirror role is dependency-classified under File_09 where exact Mirror coordinate work is opened. The compressed Tishri Recess expression is resolved as a non-equivalence / dependency-fork clarification: 6 months remains the Tishri/Nisan phase-offset state, while 3.5 years remains the half-week / priestly-straddle state. The 336-day Priestly Ledger is elevated as a foundational architectural baseline, and the Priestly-Enochian 3.5-day phase-offset is now a structural theorem for the prophetic half-week; historical execution variants remain corollary / source-control material.

Argument-control result: The checked arithmetic supports File_12 as a calendrical-physics control file. The strongest local claims are arithmetic fact or dependency-controlled arithmetic fact. Claims about Christ's Birth, Enochian decay, gracious shortening, and the Angelic Prince are preserved as theological or verified source-text states and do not carry the arithmetic burden. Solstice Mirror is preserved as a source label whose exact phase-resolved Mirror mechanics are dependency-controlled by File_09 when opened.

0.6 Claim-status and argument-control register

Claim-status scope: File_12 is a control file rather than a full proof file. Its argument is strongest where it records checked arithmetic, repository-defined calendar states, and dependency-controlled operators. Theological and symbolic language is retained because it explains why the calendrical physics matters, but it must be labeled rather than allowed to carry arithmetic burden.

Argument-control rule: Arithmetic facts may support the local argument directly. Dependency-controlled arithmetic facts may support the argument only inside their stated dependency. Structural inferences may support the argument when state, node-class, tradition, and operator are explicit. Local Mirror label-states, theological notes, and verified source-text anchors explain significance but do not replace arithmetic or source-control.

Section-level argument ladder:

0.7 Author-resolved controls

Author decision — Enochian ratio: The active Enochian Key-of-23 ratio is 300/299. It is the third allowable Key-of-23 ratio after 25/23 and 70/69. It means that 300 × 364 Enochian days nearly equals 299 × 365.2422 true-solar days. Any 299/300 source wording is retained only as legacy inverse / relation-label language and is not the operative conversion ratio.

Author decision — Null Zone rounding and precision: The File_12 source display 6 BC to AD 6 checks exactly as 6 + 6 − 1 = 11. In chronologies rounded to mod-5 or mod-10, this 11-year crossing may be displayed as a 10-year Null Zone. Precise actual dates and exact Mirror amounts that are not rounded to mod-5 or mod-10 must preserve the full 11-year cross-axis count. The related File_00 form 6 BC → AD 5 remains the exact 10-year civil-span dependency.

Post-final author clarification — Solstice Mirror: The explanation of Solstice Mirror is governed by File_09 where exact Mirror coordinate work is opened. File_09 supplies the Julian Jan-1 phase-coordinate proof with Oct 1 / Jan 1 / Apr 1 mapping, the civil cross-axis span BC + AD − 1, the phase-resolved suffix-inversion rule, and the phase-polarity distinction between paired .5 Tishri/Nisan Mirror states and standalone exact Mirror nodes. This resolves the prior File_12 Solstice Mirror role issue without turning File_12 into a full Mirror proof file.

Post-final author clarification — Priestly 336-day Ledger: The 336-day Priestly Ledger is elevated as a foundational architectural baseline. It is generated by 24 × 7 = 168 and 168 + 168 = 336. The two-week shift variant, 24 × 14 = 336, preserves the same conceptual total. Interstitial weeks required for actual solar alignment are firewalled outside the mathematical ideal. The four festival-week / epagomenal-week bridge, 4 × 7 = 28 and 336 + 28 = 364, is retained as a corollary linking the Priestly and Enochian registers without altering the baseline.

Post-final author clarification — Priestly-Enochian half-week: The 3.5 state may be explained as the macro-projection of a liturgical 3.5-day Creation straddle. The Priestly vector begins from Saturday evening / Sunday onset. The Enochian solar vector anchors primacy to Wednesday morning at sunrise. The intervening half-week divides the seven-day week and scales under the day-year principle into the 3.5-year / 1260-day prophetic half-week. Qumran-adjacent boundary questions and exact roster mechanics remain source-control / corollary material.

Author-decision result: The Null Zone exactness audit, the Enochian ratio audit, the Solstice Mirror role classification, the Tishri Recess compression, and the status of the 336-day Priestly Ledger are resolved. The source-control queue for 1 Enoch 75:1-2 / source shorthand 75:2, 1 Enoch 82 leader / 91-day material, Enoch 80, and Matthew 24:22 is now complete. The legacy File_00 section mapping remains dependency-controlled. The mathematical Priestly-Enochian half-week theorem is active; granular historical execution details remain source-control / corollary material if promoted later.

0.8 Source-control verification record

Finalization source-control scope: This section verifies the source-text anchors that were previously held in the source-control queue. The verification resolves source-control status; it does not promote theological or source-text material into arithmetic proof.

Source-control result: The source-text queue for 1 Enoch 75:1-2 / source shorthand 75:2, 1 Enoch 82 leader / 91-day material, Enoch 80, and Matthew 24:22 is resolved for Finalization. Their role remains claim-status controlled: verified source-text anchor / theological note, not arithmetic fact unless a later file explicitly supplies an operator.

1. The 24-hour year: seasonal mapping

Active state: seasonal-clock mapping.

Spring / Nisan = 06:00.

Winter / Tebeth = 00:00.

Theological note: The source identifies the Winter / Tebeth 00:00 anchor with Christ's Birth. This claim is preserved as a calendrical / theological anchor and does not carry civil-date proof burden in this file.

Display-state note: The 06:00 and 00:00 labels are seasonal-clock display states inside the 24-hour year. They are not treated here as ordinary civil clock times, date stamps, or proofs of a civil-year hinge.

Arithmetic note: The visible seasonal-clock relation checks as 06:00 − 00:00 = 6 hours. On an evenly quartered 24-hour year, 24 ÷ 4 = 6, so Spring / Nisan at 06:00 stands one quarter-clock from Winter / Tebeth at 00:00. This check does not infer the unsupplied summer or autumn clock positions.

Claim-status note: The Nisan / Spring and Tebeth / Winter labels are source-retained calendrical data. The quarter-clock check is an arithmetic fact. The identification of the Winter / Tebeth 00:00 anchor with Christ's Birth is a theological / calendrical anchor and should not carry civil-date proof burden.

Dependency note: This section records the seasonal clock supplied by the source. It does not infer the unsupplied summer or autumn clock positions.

2. The Solar/Lunar Straddle

Active state: Solar/Lunar Straddle; day-start duality; EnvNorm / EnvSpread distinction.

Definition: The biblical day has two start points, creating a permanent 0.5-unit offset.

Source expression: This offset is represented as the 7 versus 7.5 year duality.

Node-class note: The 0.5 value is a phase-offset / day-start unit. EnvNorm 7 is the normalized week label. EnvSpread 7.5 is the physical or phase-spread envelope. These are distinct node-classes inside the same Solar/Lunar Straddle field.

State-control note: The 0.5-unit offset belongs to the Solar/Lunar Straddle. The 7 and 7.5 forms must be preserved as dual states unless a later section explicitly narrows the active state.

Claim-status note: The day-start duality is a source-retained technical definition and repository structural inference by dependency. The calculation 7.5 − 7 = 0.5 is an arithmetic fact. The argument does not require 7 and 7.5 to compete as corrected values.

Arithmetic note: The internal offset checks as 7.5 − 7 = 0.5. Where the 10x scale-state is active, the same phase offset checks as 0.5 × 10 = 5.0. These are scale-state checks, not ordinary date corrections.

3. The 10-Year Null Zone

Active state: symbolic Null Zone / 10x scale-state; rounded mod-5 / mod-10 display; precise cross-axis firewall.

Definition: The source states that the “Year Zero” expands to a 10-Year Span, approximately 6 BC to AD 6, on the 10x scale.

Author-decision note: The File_12 source display 6 BC to AD 6 is retained. It is not an exact 10-year civil-span claim. It is a rounded Null Zone display where chronologies operating in mod-5 or mod-10 may round the exact 11-year cross-axis amount as 10.

Arithmetic note: If the File_12 source display is treated as an exact civil cross-axis span, the repository formula gives:

$6+6-1=11.$

The related File_00 exact 10-year Null Zone form checks separately as:

$6+5-1=10.$

Node-class note: “Year Zero” is source-retained symbolic language. It does not create a civil year 0.

Precision rule: Use 6 BC to AD 6 = 11 where precise actual dates or exact Mirror amounts are active and the chronology is not rounded to mod-5 or mod-10. Use the rounded 10-year display only where the active state is rounded, mod-5, mod-10, or symbolic Null Zone display.

Dependency note: File_00 supplies a related exact 10-year Null Zone form as 6 BC → AD 5. File_12 preserves the separate rounded 6 BC to AD 6 display by author decision. The two forms are related but non-identical states.

Claim-status note: The 6 + 6 − 1 = 11 and 6 + 5 − 1 = 10 checks are arithmetic facts. The mod-5 / mod-10 rounding of the 11-year crossing to a 10-year Null Zone is author-resolved source control and structural display logic.

4. The Dual-Precession Drive

Active state: precessional comparison.

The Lubricant: The 30-year difference between 6480 and 6450 aligns the Cosmic Seasons.

Arithmetic note: The visible difference checks: 6480 − 6450 = 30. By File_17 dependency, the standard precessional display also checks as 90 × 72 = 6480, while the alternate precessional display checks as 90 × 215/3 = 6450, equivalently 30 × 215 = 6450.

Modal-state note: 6480 is preserved as a standard precessional display candidate. 6450 is preserved as an alternate precessional display candidate. The 30-year difference is preserved as the source's alignment / lubricant state.

Dependency note: The values 6480, 6450, and 30 are preserved from the source. The derivation of 6450 is now identified through File_17's alternate precessional-day state, while the source's interpretive claim that the 30-year difference aligns the Cosmic Seasons remains argument-controlled.

Claim-status note: The difference 6480 − 6450 = 30 is an arithmetic fact. The statement that the 30-year difference aligns the Cosmic Seasons is structural inference / source-retained interpretive language. It should not carry derivational burden for 6450 unless the alternate precessional-day dependency is explicitly opened.

5. The Enochian Gearbox

5.1 The 300/299 Enochian Key-of-23 ratio

Active state: author-resolved Enochian Key-of-23 operator.

Legacy source statement: The source labels the gearbox as the 299/300 Ratio and says it converts Solar Years (365.24) into Enochian Years (364).

Author-decision handling: The active File_12 operator is 300/299, not 299/300. The 300/299 ratio is the third allowable Key-of-23 ratio after 25/23 and 70/69. Any 299/300 wording is retained only as legacy inverse / relation-label language.

Meaning of the operator: The active Enochian ratio means that 300 Enochian years of 364 days nearly equal 299 true-solar years of about 365.2422 days:

$300 \times 364 = 109200\text{ days}.$

$299 \times 365.2422 = 109207.4178\text{ days}.$

The difference is:

$109207.4178 - 109200 = 7.4178\text{ days}.$

Count-expansion check: The count expansion from 299 to 300 checks exactly under the ratio:

$299 \times \frac{300}{299} = 300.$

Year-length display check: Applying the ratio to the Enochian year gives the near-solar display:

$364 \times \frac{300}{299} = 365.217391\ldots$

Display-state note: 365.2422 is the true-solar reference used in the author decision. 365.24 remains the shorter source display. Neither display activates the Residue Protocol in this file. Exact calibrated references are separately declared in §5.1A.

Claim-status note: The active 300/299 operator is author-resolved source control and exact-ratio arithmetic. The statement that the Enochian Gearbox converts Solar and Enochian registers is structural inference under the active operator. The legacy 299/300 label no longer remains an unresolved audit issue.

5.1A Dominant solar calibration and supportive Enoch-epoch companion

Active state: File_00 §3.24 calibrated solar year S_K remains dominant. The author-approved S_E is a supportive rational companion only; it does not replace the Residue Protocol or any ordinary Key-of-23 operator.

Exact rational remainders. With the unchanged common schematic year K=8400/23, the two standards are:

Both therefore retain a rational remainder beyond 365 days. Their respective 299-year direct day-volume residues are exactly:

The established conceptual residual-display already gives 7.475 × 300/299 = 7.5. The supportive companion supplies that same number as a direct residue under a different reference year; these are related but non-identical operations:

State-control note: S_K (7.475) dominant; S_E (7.5) supportive. Keep the File_00 physical-residue formula R_K(N)=N/40 and the existing 0.575, 1.725, and 7.475 direct residues unchanged. Do not apply the conceptual-display expansion again to S_E's direct 7.5, or use S_E to recalculate existing residue applications silently. The approximate 365.2422 display in §5.1, the 294/293 side ratio, and the Sothic/Julian comparisons in §5A remain distinct.

Quarter-month interpretation. The §2 evening/morning half-day straddle supplies the repository's 7/7.5 envelope distinction. The §7 Enochian reckoning supplies the ideal thirty-day-month body with four annual seasonal service days:

The four service days occur every 364-day year; they are not occasional leap days. For an integer block count n, the supportive identity is 299nS_E−300n(364)=7.5n days. Under dominant S_K, the direct residue is 7.475n days and its Enochian conceptual display is 7.5n days. Thus 15/30/45 days fit the half-/whole-/one-and-a-half-month grid without conflating the two calibrations. File_22 §7.11's existing Watcher's Month remains a conceptual residual-display under the dominant protocol, not a silently revised physical-drift calculation.

Model-dependent epoch comparison. Solving the cited mean-tropical-year polynomials for the exact fractions above gives the following approximate ancient epochs, rounded to decades rather than presented as precise event dates:

For repository comparison, the later Simon/FITS expression is primary; the Laskar/NASA expression is retained as an older independent check rather than a coequal calibration rule. The dominant standard consequently has a modeled locus near the repository's Mosaic/Exodus era, while the supportive quarter-month companion has a modeled locus near 3300 BC. These are computed comparisons, not dates stated by the astronomical sources. The models use Julian centuries from J2000 and uniform 86400-second days; they do not directly count ancient Earth-rotation days. Their agreement is not a statistical confidence interval, and neither fixed rational standard replaces the epoch-varying astronomical year across Genesis. [TY1; TY2]

Within the selected MT chronology, the standard Creation endpoint gives 4114−622=3492 BC, followed by 3492−365=3127 BC; the Enoch lifetime midpoint is 3309.5 on the same-side BC numerical scale. The equally weighted eight-state 60/130/215 variant spectrum spans 4304–3899 BC, with 60+70+60+25+60+70+60=405. Its mean is 4101.5, or 4102t BC under the declared Nisan endpoint convention, and:

giving the phase-resolved Enoch center 3297n BC. These are derived comparison centers, not new Primary anchors; File_18 controls the chronological inputs. The retained structural convergence is Enoch's 365 years, the supportive rational year S_E, and an MT Enoch-centered epoch near 3300 BC, while S_K remains dominant.

Enoch–Moses midpoint corollary. By File_06 dependency, Moses' 120-year life runs from approximately 1526 BC to 1406 BC, placing its midpoint at 1466 BC. Under the primary Simon/FITS comparison, exact S_K is reached at approximately 1456 BC, about 10 years from that Mosaic midpoint. The standard-MT Enoch midpoint 3309.5 BC lies about 18 years from the corresponding S_E equality at approximately 3291.5 BC; the full-variant center 3297n BC lies about 5.5 years from it. Evaluated at the biblical midpoints themselves, the same Simon expression differs from S_K at Moses' midpoint by only about 0.045 second per year, from S_E at the standard Enoch midpoint by about 0.060 second per year, and from S_E at the variant-spectrum Enoch center by about 0.018 second per year. These subsecond figures describe polynomial comparison only and are not historical accuracy claims.

Claim-status note: Enoch and Moses may be paired as revelatory / intercessory ascent figures—Enoch as taken by God and, in Enochic tradition, a heavenly revelator/intercessor; Moses as the Sinai revelator who ascends the mountain and intercedes for Israel. The near-coincidence of their lifespan centers with the supportive S_E and dominant S_K astronomical loci is therefore retained only as providential / typological corroboration. It does not carry arithmetic proof burden, establish ancient knowledge of the fractions, independently date either life, or determine an event's exact month and day.

Source-control references: [TY1] FITS Standard 4.0, §9.3, mean-tropical-year expression: https://fits.gsfc.nasa.gov/standard40/fits_standard40aa-le.pdf. The Simon et al. (1994) attribution is given in Rots et al. (2015), Representations of time coordinates in FITS, §4.2, DOI 10.1051/0004-6361/201424653. [TY2] L. E. Doggett, Calendars, §1.1, Laskar (1986)-based polynomial and uniform-day convention, reproduced by NASA: https://eclipse.gsfc.nasa.gov/SEhelp/calendars.html.

5.2 The Leader Principle

Active state: Enochian seasonal-governance state.

Source statement: Each 91-day season is led by an Angelic Prince on Day 91, keeping the calendar aligned.

Node-class note: The 91-day season and Day 91 leader are Enochian seasonal states. They are not collapsed into a 90-day prophetic quarter or into an epagomenal-day exclusion unless the local argument explicitly opens that relation.

Arithmetic note: The Enochian season total checks as 4 × 91 = 364, matching the 364-day Enochian Year state.

Claim-status note: The 91-day seasonal structure is an arithmetic fact when tied to 4 × 91 = 364. The Day 91 leader statement is source-supported as Enochian calendrical language. The exact Angelic Prince terminology remains source-retained theological / calendrical wording and is not proof-bearing in this file.

Source-control note: This Enochian seasonal-leader claim is preserved. The 91-day seasonal dominion is source-controlled through 1 Enoch 82. Treat “Angelic Prince on Day 91” as repository compression rather than a direct quotation.

5A. The 365-day civil-year and Sothic companions

Amendment state: Bounded September 6 2026 working addition; arithmetic verified, centrally registered at State Vocabulary Register v1.52 §D.42; not separately author-Finalized. The original three Keys remain the default inventory. The two 365-day ratios below are locally opened comparison operators with different preserved quantities.

5A.1 One-extra-year completion and the half-23 grammar

For a shorter year d, a chosen longer reference year Y, and a reference-year count q, exact one-extra-year alignment has:

The ideal mean-year Sothic relation is:

Censorinus, De die natali ch. 18, attests the Egyptian 365-day civil-year drift and canicular synchronism. This supplies a historical analogue for the calculation, not evidence that any repository anchor was an observed heliacal reset. Source: https://topostext.org/work/741 .

With the half-23 unit u=23/2=11.5, a general completion form is:

This is a common mathematical form, not proof of one historical source or a uniquely forced coefficient sequence. The first half-block gives 12.5×336=4200 days, compared with 11.5S_K=4200.2875 days under the File_00 calibrated reference.

5A.2 Three reference standards and two different extensions

The File_00 §3.24 definitions remain unchanged:

The original three Keys share K exactly:

The separate ideal Julian mean is J=365.25. Define the Sothic-adjacent companion:

Its calibration is:

H therefore shadows the ideal Sothic/Julian relation closely; it does not preserve K. It is a Sothic-adjacent Key-of-23 companion, not an automatic replacement for any original Key.

The distinct exact common-K continuation to 365 days is forced by the preservation requirement:

H and G must not be conflated simply because both concern 365 days and denominators divisible by 23. A chronological use must declare which property it preserves.

5A.3 Enochian side ratio and calibration sensitivity

The already admitted 294/293 Enochian comparison and the default 300/299 Key preserve complementary features:

Against the unchanged S_K:

File_53 controls the existing Enochian application. A printed finite decimal is an approximation; exact equivalence uses 107016/293, not equality to a truncated decimal.

For 365 days against S_K, the exact one-extra-year count is 335800/223≈1505.83, whose nearest half-23 member is 1506.5=131u, not 1460.5=127u. Its sensitivity ratio 3015/3013 gives a block discrepancy of −13/80 day. This is an explicit negative control only, not an additional adopted chronological operator. The selection of 127 expresses Sothic/Julian adjacency, not optimum tropical-year alignment.

File_00 retains the same S_K calibration. Section 5.1A now supplies the separately sourced, model-dependent epoch comparison and the supportive S_E companion; it does not substitute an era-dependent astronomical curve for the dominant Residue Protocol.

5A.4 Chronological interfaces and scope

The ordinary 1460→1461 comparison and the half-step 1460.5→1461.5 comparison may be applied to explicitly anchored schematic year-spans. A mean-year day-volume relation and a generated civil-coordinate span are distinct operations; the latter is not automatically a reconstruction of an ancient calendar epoch.

The established Mosaic half-scale gives:

80.5 requires the phase-resolved comparison; same-phase 1526n→1446n BC remains 80 years. Different Keys are alternative declared operations, not gains to accumulate silently.

File_22 §§5A and 9B in the coordinated working amendment carry the matched-Cainan Creation and Pillar applications. File_70 Supplement A §13 carries the SKL paired-Mirror and Mosaic–Joshua selection application. File_09 remains the phase-coordinate controller; File_51a remains the Rounded Scaffold controller. These routed applications do not change the original calendar definitions, raw source rows, or Primary anchors.

Machine Guard [SOTHIC CALIBRATION NON-COLLAPSE]: Keep K=8400/23, S_K=336023/920, and the ideal Julian mean 365.25 distinct. H=2923/2921 is a Sothic-adjacent comparison and satisfies 365H≠K; G=1680/1679 is the distinct exact common-K 365-day extension. Neither silently replaces the default 25/23, 70/69, or 300/299 operator.

Machine Guard [SOTHIC DRIFT AND PROJECTION]: A physical mean-year day-volume comparison is not a civil-coordinate chronology. Declare the anchor, direction, node class, phase, and ratio before a Sothic year-span projection. The File_00 Residue Protocol N/40 follows from the common K calibration and must not be generalized to H. No Egyptian heliacal-reset epoch is inferred from an arithmetic landing.

Machine Guard [SOTHIC SENSITIVITY SCOPE]: The 3015/3013 comparison is a calibration sensitivity control only. It is not an active alternative introduced to improve a chronological fit. The 294/293 Enochian side ratio, Sothic 1461/1460, companion H, and extension G remain separately named operations with separately declared calibration and scope.

6. The Seasonal Directive: the Nisan Rule

6.1 The Nisan Rule

Active state: Nisan default / Spring state.

Rule: Regular / Cumulative dates default to Nisan / Spring.

State-control note: Nisan is the default state for Regular / Cumulative dates unless a local section explicitly opens a Tishri state, suffix, phase-pair, or Mirror-coordinate rule.

Suffix rule: An unsuffixed date should not be retroactively assigned a Tishri state. A suffixed date must preserve its suffix unless the active section explicitly converts it into a phase-resolved state.

Claim-status note: The Nisan Rule is a source-retained operating rule and repository calendar-state control. It is not an arithmetic proof, and it does not delete explicit Tishri states.

6.2 Creation-side Tishri/Nisan dependency from File_07

Active dependency: File_07 controls Creation-side Tishri/Nisan dual-date forms.

Dependency note: This table imports only the state-control precedent needed for File_12. It does not add a new Creation matrix to File_12 and does not perform new Creation arithmetic.

Mirror dependency note: Where a later section opens phase-resolved Mirror coordinate-completion, File_09 controls the suffix-inversion form. That dependency may use displays such as 4115t/4114n BC → AD 1406t/1407n. This is a Mirror-state dependency and does not replace the File_07 source endpoint display inside ordinary Creation-side state control.

Claim-status note: This subsection is dependency note / state-control material. It imports no new Creation arithmetic and makes no new local claim beyond preserving File_07 and File_09 roles.

6.3 The Tishri Recess and the Priestly-Enochian Half-Week

Active state: Tishri/Nisan phase-offset state; 336-day Priestly Ledger; Priestly-Enochian liturgical half-week; Aaron/Moses L = 3.5 priestly-straddle dependency; File_09-controlled Solstice Mirror dependency where exact phase-resolved Mirror coordinate work is opened.

Source statement: The 6-month offset (3.5 years) creates the Solstice Mirror.

Post-final clarification: The source line should not be read as ordinary equivalence between 6 months and 3.5 years. It compresses a dependency fork:

6.3.1 Axiom: the 336-day Priestly Ledger

Active state: Priestly architectural baseline.

The 336-day register is not a peripheral approximation. It is the mathematical ideal of the Priestly paradigm.

The Priestly rotation operates on 24 defined courses. At one week per course, the course cycle completes a schematic half-year:

24 × 7 = 168

The full schematic Priestly year is bifurcated as:

168 + 168 = 336

The same conceptual total is preserved if the courses are modeled as a two-week shift variant:

24 × 14 = 336

Architectural note: Interstitial weeks required for actual solar alignment are firewalled outside this mathematical ideal. The 336-day ledger preserves the unbroken geometry of the Priestly course-cycle engine.

Calendar firewall: The Priestly Ledger is distinct from the other year states:

6.3.1a Source-control map: the 24-course Priestly architecture

Active state: source-controlled Priestly roster and weekly-rotation baseline.

Source-control result: The historical / textual source-control status for the 24-course architecture and weekly / Sabbath transition vector is resolved. The exact granular execution of every festival-week or Qumran-adjacent roster variant remains bounded as corollary material unless a later file supplies a page-level source-critical argument.

Primary-source note: The source-control map establishes the 24-course / seven-day / Sabbath-transition architecture. It does not prove that the four epagomenal or festival weeks were always executed by one historical administrative mechanism. That bridge remains a corollary: 4 × 7 = 28; 336 + 28 = 364.

6.3.2 Corollary: the invariance of the 336-day Priestly ideal

Active state: corollary / operational-variant control.

The 336-day registry remains structurally absolute regardless of the specific historical mechanics used to execute the 24 courses. The objective of this framework is not to reconstruct the granular administrative schedule of the temple roster inside File_12, but to identify the mathematical ideal that generates the 336-day Priestly concept.

The conceptual baseline remains unchanged across two operational variables:

Corollary note: The base course architecture is source-controlled by 1 Chronicles 24, 1 Chronicles 9:25, the Sabbath-transition passages, Luke 1:5, Josephus, Mishnah mishmarot witnesses, and the Qumran Mishmarot field. The four festival-week bridge remains a corollary because its exact historical execution may vary: festival sharing, uncounted gaps, epagomenal inserts, or another roster mechanism may account for the bridge without altering the Priestly baseline. The File_12 baseline remains the same: the 336-day conceptual year stands as the mathematical metric of the Priestly paradigm.

6.3.3 Axiom: the 3.5-day Creation straddle

Active state: Priestly-Enochian liturgical half-week.

The Priestly matrix operates in rigid phase-offset against the 364-day Enochian solar calendar.

Because both vectors are treated as rigid calendrical systems, they permanently bisect one another. The span from the Priestly weekly onset to the Enochian solar onset creates a structural half-week:

Saturday evening / Sunday onset → Wednesday morning = 3.5 days

Source-control note: Qumran-adjacent calendrical practice may mark related boundaries differently, including Tuesday-evening boundary possibilities. File_12 uses the strictly solar Wednesday-morning motif as the structural Enochian coordinate, tied to the luminary-creation motif. Qumran Mishmarot texts source-control the use of priestly courses inside 364-day calendrical systems, but they do not by themselves require every File_12 phase-theorem detail. Qumran-specific execution details remain bounded corollary material unless a later file opens them with source-critical controls.

6.3.4 Theorem: the origin of the prophetic half-week

Active state: prophetic day-year projection.

The 3.5-day Priestly-Enochian calendrical schism divides the seven-day week in half. Under the day-year principle, the liturgical phase-offset projects into the prophetic half-week:

3.5 days → 3.5 years
3.5 × 360 = 1260

Where the Enochian Year is active, the parallel half-week state remains distinct:

3.5 × 364 = 1274

Theorem note: The Danielic half-week and the 1260-day motif may therefore be read within File_12 as macro-projections of the Priestly-Enochian Saturday-evening / Sunday-onset to Wednesday-morning split. This is a structural calendrical theorem. It does not erase the Aaron/Moses terminal L = 3.5 state, the 6-month Tishri/Nisan phase-offset state, or the Enochian 1274 state.

6.3.5 File_09 Solstice Mirror control

When the Solstice Mirror is opened as exact Mirror coordinate work, File_09 controls the proof mechanics. Its governing model maps Tishri to Oct 1, Nisan to Apr 1, and the Mirror axis to Jan 1. Phase-resolved .5 Tishri/Nisan dual dates use suffix inversion across the Mirror so that:

Yt/(Y−1)n BC → AD (Y−1)t/Y n

The civil skeleton remains:

BC + AD − 1

The phase proof does not create a second cross-axis span operator.

Resolution note: The former Tishri Recess audit is resolved as a non-equivalence / dependency-fork clarification. The source wording is preserved, but the 6-month phase-offset state, the 3.5-year half-week state, and the 336-day Priestly Ledger are now distinguished. The 336-day Priestly Ledger is elevated as foundational. The base 24-course / seven-day / Sabbath-transition architecture is source-controlled. The Priestly-Enochian half-week is elevated as structural theorem. Festival-week execution and Qumran-specific phase details remain bounded corollary material unless later source-critical controls promote them.

Claim-status note: The 6-month / 0.5-year value is an arithmetic fact. The 336-day Priestly Ledger is an architectural axiom with source-controlled roster and weekly-rotation basis. The festival-week bridge is a corollary. The Aaron/Moses L = 3.5 value is an exact phase-state by dependency. The Priestly-Enochian 3.5-day to 3.5-year projection is a structural theorem. Solstice Mirror is dependency-controlled by File_09 where exact phase-resolved Mirror coordinate work is opened.

7. The Epagomenal Exclusion Principle

Active state: Enochian calendar-reckoning state; Prophetic Year harmonic state.

Rule: Intercalary days “render service” but are “not reckoned in the reckoning of the year” according to the source's citation of 1 Enoch 75:2. Source-control verification shows that the exact wording appears in R. H. Charles, 1 Enoch 75:1, with 75:1–2 recommended for proof-bearing citation if the source's legacy 75:2 label is retained.

Result: A Solar Year is reckoned harmonically as a 360-day Prophetic Year.

Arithmetic note: The Enochian / Prophetic transition checks if one service or leader day is excluded from each 91-day season: 4 × 91 = 364; 364 − 4 = 360; equivalently 4 × 90 = 360. This arithmetic supports the harmonic 360-day Prophetic Year state without erasing the 364-day Enochian Year state.

Node-class note: The epagomenal exclusion state is an Enochian reckoning rule. The 360-day Prophetic Year is a harmonic grid state. The Solar Year, Enochian Year, and Prophetic Year remain distinct.

Source-control note: The epagomenal wording is verified against R. H. Charles, Chapter LXXV. The quoted wording appears in Charles §1 rather than §2. The source's 1 Enoch 75:2 label is preserved as legacy source-caption wording, but proof-bearing citation should use 1 Enoch 75:1–2, or 75:1 if using Charles-only numbering.

State-control note: The 360-day Prophetic Year is a harmonic reckoning state. It does not erase the Solar Year state or the Enochian Year state.

Claim-status note: The 1 Enoch 75:1–2 / source shorthand 75:2 wording is a verified source-text anchor. The calculations 4 × 91 = 364, 364 − 4 = 360, and 4 × 90 = 360 are arithmetic facts. The result that a Solar Year is reckoned harmonically as a 360-day Prophetic Year is structural inference / calendar-harmonization language.

7A. The 360-day intercalation cycle (bounded addition)

Active states: 360-day intercalation cycle state; counted-or-not option principle (360-calendar counterpart of the §7 epagomenal exclusion); 1260 / 1290 same-half-week corollary state; year-scale instantiation display.

7A.1 The 40-year cycle

6 × (6 × 360 + 30) + (4 × 360 + 30) = 6 × 2190 + 1470 = 13140 + 1470 = 14610 = 40 × 365.25

Six cycles of six years, each closed by a leap month, and a seventh cycle of four years with the seventh leap month: forty years, seven intercalations (210 = 7 × 30 days), landing exactly on the Julian mean year. Internal identities: 2190 = 6 × 365 (each closed cycle equals six common years to the day); 1470 = 3 × 490 = 30 × 49; 13140 = 36 × 365. Structure note: seven 30-day months in forty years is the unique solution to 40 × 365.25; the scheme is forced by its own target. Claim-status: arithmetic fact (the cycle and identities); author-declared system / structural inference (the scheme itself — it is reconstructed, not text-stated).

7A.2 The option principle and the calibration pair

As the Enochian intercalary days "render service but are not reckoned" (§7), so the 360-calendar's leap months may be counted or not — an option, not a necessity. The two schematic calendars thereby each carry a real year-length in secret: the 364-day reckoning yields the tropical year (294 × 364 = 293 × 365.2423; File_53 §14A.2), and the intercalated 360 yields the Julian (365.25). Guard: this Julian-mean equivalence is not the File_09 Julian Jan-1 phase-coordinate proof; distinct objects sharing a word; do not collapse. Claim-status: structural inference; the calibration observations are arithmetic facts.

7A.3 The 1260 / 1290 corollary

Any 3.5-year window contains zero or one cycle-end: the same half-week is 1260 days without its leap month and 1290 with it (1260 + 30 = 1290). The 1260 of Revelation 11–12 and the 1290 of Daniel 12 are thereby readable as the without- and with-intercalation expressions of one half-week. Placement rule: a longer window may cross one or two cycle-ends; any instance must declare its placement. Claim-status: textual datum (the two values); arithmetic fact (the corollary); typological / structural reading (the identification).

7A.4 Year-scale instantiation

Both +30 members close on AD 25n, the conception-count "about 30" (File_13 §7.4) — and exactly: 2166 + 25 − 1 = 2190 and 1446 + 25 − 1 = 1470, the ministry node standing the precise cycle-value from each covenant head (exact-closure note, pressure test July 6 2026). The 1876 / 1846 → 586 pair was registered in File_17 before this scheme existed; the scheme retrodicts it. Claim-status: arithmetic fact (all spans); structural inference (the instantiation reading); dependency-controlled (File_13; File_16; File_17; File_22 §9A.5).

8. Enochian Shortening: the physics of sin versus grace

8.1 The Enochian view: punitive shortening

Active state: Enochian theological interpretation.

The Enochian view treats the drift as evidence of cosmic decay, associated in the source with Enoch 80.

Source-text note: Enoch 80 is verified against R. H. Charles, Chapter LXXX. It preserves the punitive / cosmic-decay shortening state by associating shortened years with sinner-days and altered cosmic / seasonal order. This source-text anchor does not add a local arithmetic operator.

Claim-status note: The punitive shortening view is a theological note / source-text anchor. It explains the significance of drift but does not add a local arithmetic operator.

8.2 The Christological view: gracious shortening

Active state: Christological theological interpretation.

The Christological view invokes Matthew 24: unless those days were shortened, no flesh would be saved.

Theological note: Both shortening views are preserved. They do not carry arithmetic burden unless a later section explicitly promotes them with source and operator control.

Arithmetic note: No new shortening arithmetic is executed in this section. By dependency, the prophetic half-week checks as 3.5 × 360 = 1260, and the Enochian half-week checks as 3.5 × 364 = 1274; these remain parallel calendar states where a later section opens them.

Source-text note: Matthew 24:22 is verified against the KJV shortened-days wording. It preserves the Christological gracious-shortening state. This source-text anchor does not add a local arithmetic operator.

Claim-status note: The gracious shortening view is a theological note / source-text anchor. It remains parallel to the Enochian punitive view and should not be collapsed into a single arithmetic claim.

9. Cross-reference index

Cross-reference addition (§7A): File_53 §14A.2 (tropical calibration); File_13 §7.4 (AD 25n); File_16 (1876 / 1846 heads); File_17 §13A (day-scale instances); File_22 §9A.5.

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, source data, modal-state logic, node-classes, sign conventions, operators, slash-pairs, ranges, envelopes, Mirror protocols, pre-existing Machine Guards, claim-status labels, theological claims, or dependency boundaries are changed. The new File_62 guard is a bounded non-collapse control for the reciprocal-routing state.

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

September 6 2026 bounded Sothic amendment record

Prepared under the author's explicit consolidation/update instruction and delegated implementation choice. Intake, additive structure/state preparation, arithmetic/argument review, and bounded verification were performed within the current response. The complete earlier Final parent is preserved, and all pre-existing proof equations, node classes, and guard bodies remain unchanged. The new additions are verification-complete bounded working text, centrally registered but not separately author-Finalized or full-file pressure tested. Active controls are Capsule v11.51 / Register v1.52 / Style Guide v2.5 / Procedures v3.5.

Open scope and adoption: explicit Finalization; registration of the new local states/guards; remote SKL source-chain test; the absent fixed-field 4383; the actual-Apparent-Adam 4.5 residual. Source/control review proposals and complete diffs are supplied in the consolidation package. No publication manifest, archive replacement, deployment, or external preservation capture is claimed.