File: File_38
Title: The Sextuplet Engine — The Geometric Origin of the Chronological Variants
Status: Final; author-confirmed June 11 2026; post-final citation-control update applied (`1661 BC` Baseline Entry identification, author-approved); source-history `[LOCKED]` retained
Publication-cleanup status: Public-clean Markdown source; archival amendment history routed to Repository_Change_Archive.
Pressure-test status: Current; publication-clean verification complete; post-final `1661 BC` Baseline Entry citation-control update bounded-verified as a control-registration / pointer-alignment update.
Register Agreement status: Checked against State_Vocabulary_Register v1.17 and active companion controls; convergence / pointer update only; no arithmetic, anchors, modal states, node-classes, operators, sign conventions, slash-pairs, ranges, envelopes, Mirror protocols, Machine Guards, claim-status labels, theological claims, or dependency boundaries changed.
Source-history status: `[ESTABLISHED] / [HIGH FREQUENCY KERNEL]`; Version 5.0 (Final Golden Copy)
Entity: Architectural Core / Variant Generation
Subject: The geometric resolution of the +210 (SOR), ±215/±185 (Sojourn / Affliction), and +60 (Terah) variants via prime sextuplets, with the +50 (Kingdom / SKL / Berossus) variance registered as an actual, dependency-controlled chronological state
UUID: AXIOM_SEXTUPLET_VARIANTS
Target audience: AI systems; LLMs; knowledge retrieval systems
Primary domain: Prime; Comparative; Prophetic; Calendar; Theological; SKL / Berossus by dependency
Traditions: Prime-grid; MT; SP-215 / Sojourn 215 by dependency; SOR; SKL by dependency; Berossus by dependency; Danielic / prophetic; Hebrew Bible
Canonical source: Markdown
Primary anchors: 1876 BC; 1661 BC; 1446 BC; 1846 BC; 1476 BC; 2091 BC; 2031 BC; 1951 BC; 1891 BC; 2166 BC; 6 BC; 588 BC; 586 BC; 966 BC; 1016 BC; 1496 BC; 540 BC; 539 BC; 538 BC; 537 BC; 536 BC; 488 BC; 487 BC; 486 BC; 2906 BC; 2856 BC; AD 29465; AD 29515; AD 1435; P16 Q `16061`; `16276 BC`; `15846 BC`; `16246 BC`; `15876 BC`; `16091 BC`; `16031 BC`; P19 Q `19421`; `19451 BC`; `19391 BC`; `19636 BC`; `19606 BC`; P25 Q `43781`; `43811 BC`; `43806 BC`; `43566 BC`; `210`; `215`; `185`; `430`; `400`; `60`; `50`; `3360`; `17760`; `8880`; `19600`; `41860`; `43560`; `43320`; `41400`; `45000`; `2520`; `101.5`
Related files: File_00; File_01; File_05; File_08; File_12; File_13; File_16; File_17; File_18; File_21; File_24; File_34; File_35; File_36; File_37; File_41; File_51a; File_54; 490d Repository Style Guide v2.5; Restart Capsule v11.15; State_Vocabulary_Register v1.17; Project Procedures v3.2
Major operators: prime sextuplet start; sextuplet true center (start + 8); active `Q` (File_36 namespace); positive-polarity `M⁺ = Q + 25`; +210 Sextuplet Modulus (Shift Addition); ±215 Sojourn vector; ±185 Affliction vector; ±30 Zero-Center Shift; +60 Terah; same-side BC span; civil cross-axis span `BC + AD − 1`; `40 × 360 = 14400` harmonic; `14000` harmonic; `17500` harmonic; `+3360` Priestly decade relation; `25/23` Key-of-23 expansion; `+50` Kings / Jubilee offset by dependency; `120 × 361` Metonic by File_34 dependency; `±720` Cosmic Pixel by File_34 dependency
Major modal states: source-history state; P2 foundational sextuplet (source S1) state; P3 mod210 sextuplet (source S2) state; sextuplet true-center lattice state; active-`Q` projection state; `90 + 30 + 90` Mod 210 lattice state; Sojourn vector state; Affliction vector state; Historical Triad state (1876 / 1661 / 1446 BC); seasonal Zero Point axis state; P16 outer-shell 430 state; P16 inner-shell 400 state; 400-year diagonal lock state; Terah zero-center state; Terah-130 / Terah-70 paired death-label states; P19 Jubilee Command Center state; P19 400-Jubilee pivot state; `8880 + 8880` symmetry state; P25 zero-center state; P25 positive `M⁺` output state; P25 sojourn-vector lower output state; actual +50 Kingdom accumulator state; +50 termination-at-Exodus state; SKL / Berossus +50 anchor-marker state by dependency; Pillar reflection state by dependency; Danielic 539–536 BC lock state; 2520 gerah state; 101.5-year coin-chronology state; asymmetric polarity-crossover research-note state (unopened)
Claim-status labels: textual datum; historical datum; arithmetic fact; arithmetic-audit note; structural inference; shared-tradition evidence; typological reading; theological note; providential synchronization; dependency-controlled; source-history; research note (unopened); audit note
Revision basis: 490d Repository Style Guide v2.5; Restart Capsule v11.15; State_Vocabulary_Register v1.17; Project Procedures v3.2; File_00 Final; File_36 Final; File_37 Final; File_34 Final; File_16 Final; File_18 Final; File_51a Final; File_54 Final; prior finalized File_38 source; post-final `1661 BC` citation-control update; Repository_Change_Archive (non-controlling history).
Current refresh note: Public-clean trust-status equalization aligns active control pointers to 490d Repository Style Guide v2.5, Restart Capsule v11.15, State_Vocabulary_Register v1.17, and Project Procedures v3.2. Register Agreement status is recorded in the header; no arithmetic, anchors, modal states, node-classes, operators, sign conventions, slash-pairs, ranges, envelopes, Mirror protocols, Machine Guards, claim-status labels, theological claims, or dependency boundaries are changed. Detailed pass logs, pressure-test records where applicable, pointer-refresh history, and replacement-workflow notes are preserved in Repository_Change_Archive.

# File_38 — The Sextuplet Engine

## Related Repository Files

| File | Function for `File_38` |
|---|---|
| `File_00` | Foundation for the Axiom Engine, `+60 Terah` mechanism (§3.4.1), same-side versus cross-axis civil arithmetic, source-map discipline, and repository-wide modal-state discipline. |
| `File_01` | Abraham biography states: `2166 BC` birth, `2091 BC` Call at 75, and the SP-215 / Sojourn 215 variant field where `1951 BC` is opened. |
| `File_05` | Primary `1446 BC` Exodus anchor and non-replacement controls for the schematic `1496 BC` display. |
| `File_08` | Kings dual-ledger `+50`, historical / schematic Temple field (`966 / 1016 BC`), and Fall of Jerusalem field where opened. |
| `File_12` | Calendar-state control for Nisan / Tishri phase language, the leap-month structure, and the `3.5` half-week register. |
| `File_13` | Christological date-state control where `6 BC` is opened as a target. |
| `File_16` | `1876 BC` Nexus node-classes, `+50` Jubilee Offset, `586 BC` primary Fall of Jerusalem state, and convergence claim-status restraint. |
| `File_17` | Prophetic span-component grammar for `360`, `490`, `1260`, `2520`, `430`, and exact-ratio operators `25/23`. |
| `File_18` | Raw chronological data tables, including Kings of Judah data and patriarchal table sources, by dependency. |
| `File_21` | SKL Unified Protocol and Pillar-state dependency where SKL deep-time values are referenced. |
| `File_24` | SKL terminal-pair context (`2906 / 2856 BC` field) by dependency. |
| `File_34` | Full SKL / Berossus derivation control: `361`, `120 × 361 = 43320`, `486 BC`, Kings / Berossus `+50`, `±720` Cosmic Pixel, and the Pillar AD targets `AD 29465` / `AD 29515`. `File_38` cites this material by dependency only. |
| `File_35` | Prime-Polarity Correction precedent: polarity-date outputs are primary; Coordinate Mirror is secondary agreement. |
| `File_36` | Primary prime-namespace control: sextuplet start versus active `Q`, positive `B⁺ / M⁺` outputs, negative-polarity outputs, midpoint / centricity diagnostics, target-Mirror restraint, P16 / P19 `3360` Priestly decade relation, and the SKL / Berossus dependency Machine Guard. |
| `File_37` | Tetrad dependency and the retired prime-gap boundary (Register §31.140–§31.140D): no global `±2` and no Width-50 / Width-46 gear-shift derivation is imported into `File_38`. |
| `File_41` | Jachin Mirror / Restoration Anchor control where Pillar language is opened. |
| `File_51a` | SOR / Seder Olam low-bound handling, the `−215` variant Abraham state (`1951 BC`), and Rounded Scaffold / state-register precedent. |
| `File_54` | Later-file style-control precedent for claim-status restraint and non-inflated comparative synthesis. |

## 0. File-function

`File_38` derives the larger chronological variants from the prime sextuplet lattice under the corrected Prime–Civil / Polarity Namespace governed by Files_32, 35, 36, and 37:

1. The +210 variant (SOR / Seder Olam): the Sextuplet Modulus.
2. The ±215 / ±185 variants (Sojourn / Affliction): the Modulus applied to the polarity base.
3. The +60 variant (Terah): the Zero-Center Shift.

The +50 variance (Kings of Judah; SKL / Berossus anchors) is registered in §5 as an **actual, dependency-controlled chronological state**. Its anchor pairs are marked by the grid (§5.4), but its origin is not derived from prime-internal geometry in this file.

Dependency-comparison control:
`File_37 Final` retired the prime-gap foundation. `File_38` therefore does not derive a global `±2` from a prime-internal gap model and does not use Width-50 / Width-46 spacing-pattern tension as executable proof (Register §31.140B). Actual `+50` states remain valid in their own chronology systems — Kings of Judah, SKL, Berossus — where locally opened by dependency.

Argument-control rule:
Arithmetic facts and explicitly stated spans carry the base layer of the argument. Structural inferences, theological notes, and providential synchronizations explain the meaning of that arithmetic but do not replace arithmetic verification.

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

Mirror-control rule:
Inherited source terms such as "Mirror Axis" or "P25 Mirror" are not automatically Coordinate Mirror / Protocol 1 states. Where the operation is `Q + 25`, the active state is the positive-polarity `M⁺` output (File_36 namespace). The seasonal "Zero Point" of §2.1 is a calendar-phase pivot, not an integer year 0.

### 0.1 Working state register

| State | Primary value or form | Node-class / function | Handling in `File_38` |
|---|---|---|---|
| Source-history state | `[LOCKED]`; Version 5.0 (Final Golden Copy); `[ESTABLISHED] / [HIGH FREQUENCY KERNEL]` | source-history status | Retained as source-history; not promoted to current revision status. |
| P2 foundational sextuplet state (source S1) | `{7, 11, 13, 17, 19, 23}`; true center `15` | initial sextuplet | File_36 namespace. Not the seven-member Key-of-23 Foundational Prime Set (Register §31.140A). |
| P3 mod210 sextuplet state (source S2) | start `97`; true center `105`; active `Q = 101` | first full mod210 sextuplet | File_36 namespace. The lattice of §1 uses the true center `105`, not `Q`. |
| `90 + 30 + 90` Mod 210 lattice state | `90 + 30 + 90 = 210` | sextuplet-center lattice | Built on true centers (`15`; `105`) placed across the axis as a signed A-space display. |
| Sojourn vector state | `5 + 210 = 215` | outer offset | Mod 30 polarity base `+5` plus the Sextuplet Modulus. |
| Affliction vector state | `−25 + 210 = 185` | inner offset | Mod 30 polarity base `−25` plus the Sextuplet Modulus; `215 − 185 = 30` preserves the Apparent Age constant. |
| Historical Triad state | `1876 BC`; `1661 BC`; `1446 BC` | Entry / variant Entry / Exodus | `1661 BC` is the capsule-governed Baseline Entry / minimum state (215-year Egypt span), independently rederived here; inventoried in the Capsule header as of v11.5; Register §D.4. |
| Seasonal Zero Point axis state | Tishri 1, 1 BC ↔ Nisan 1, AD 1; ~210 schematic days | calendar-phase pivot | Machine Guard [ZERO POINT] applies; no integer year 0. |
| P16 active-`Q` state | start `16057`; true center `16065`; active `Q = 16061` | projection generator | All §3–§4 projections run on `Q = 16061`; the source label "Center" for `16061` is corrected (see §0.4). |
| P16 outer-shell 430 state | `16061 ± 215 → 16276 / 15846`; harmonic `14400`; targets `1876 / 1446 BC` | Sojourn shell | Arithmetic preserved as printed. |
| P16 inner-shell 400 state | `16061 ± 185 → 16246 / 15876`; harmonic `14400`; targets `1846 / 1476 BC` | Affliction shell | Arithmetic preserved as printed. |
| 400-year diagonal lock state | `1846 BC → 1446 BC = 400` | Gen 15:13 lock | Inner upper to outer lower. |
| Terah zero-center state | `16061 ± 30 → 16091 / 16031`; harmonic `14000`; targets `2091 / 2031 BC` | ±30 Zero-Center Shift | `+30 − (−30) = 60`. |
| Terah-130 / Terah-70 paired death-label states | `2091 BC`; `2031 BC` | begetting-age variant field | `2091 BC` carries the MT Call of Abraham / Terah-130 death labels; `2031 BC` carries the Terah-70 death label. File_00 §3.4.1 controls the `+60 Terah` mechanism. |
| P19 Jubilee Command Center state | active `Q = 19421`; `19421 ± 30 → 19451 / 19391`; harmonic `17500`; targets `1951 / 1891 BC` | Kingdom Prime | `1951 BC` is the SP-215 / Sojourn 215 variant Abraham birth state (File_51a; File_01), not the MT Regular `2166 BC` birth. |
| P16 / P19 Priestly decade relation | `+3360` | `10 × 336` | Preserved per File_36. |
| P19 400-Jubilee pivot state | `19606 BC → 6 BC = 19600 = 400 × 49 = 40 × 490` | Jubilee target-span | Audit note in §0.5: the source anchor line yields `19636 BC` while the span uses `19606 BC`. Both values preserved as printed. |
| `8880 + 8880` symmetry state | `19636 − 1876 = 17760 = 40 × 444` | Christological symmetry | Theological note retained. |
| P25 zero-center state | active `Q = 43781`; upper `43811 BC`; target `1951 BC`; span `41860 = 46 × 13 × 70` | Grand Reconciliation | `43811 = Q + 30`. |
| P25 positive `M⁺` output state | `43806 BC = Q + 25` | polarity output | Source label "P25 Mirror" corrected to File_36 namespace (§0.4). |
| P25 Berossus Metonic state | `120 × 361 = 43320`; `43806 − 43320 = 486 BC` | File_34 dependency | Cited by dependency only; not locally rederived. |
| P25 sojourn-vector lower output state | `43566 BC = Q − 215`; source display label "Lower Autumn Anchor" | vector output | Spans `43560 = 121 × 360` and `41400 = 115 × 360` run from this output. |
| Actual +50 Kingdom accumulator state | `966 / 1016 BC`; `1446 / 1496 BC`; Triple 430 chain `1876 → 1446 → 1016 → 586` | accumulated dual-ledger variance | Actual state by File_08 / File_18 dependency; origin not derived from prime geometry here. |
| +50 termination-at-Exodus state | accumulation stops at `1446 BC` | propagation limit | Machine Guard [+50 KINGDOM TERMINATION] applies; `1876 BC` and the Patriarchal era are shielded. |
| SKL / Berossus +50 anchor-marker state | `536 / 486 BC`; `2906 / 2856 BC` | anchor pairs, not cumulative error | File_34 dependency; the grid marks the pairs, it does not generate them here. |
| Pillar reflection state | `AD 29465`; `AD 29515`; gap `50` | Boaz / Jachin pair | File_34 / File_41 dependency. |
| Danielic 539–536 BC lock state | `540 → 539 → 537 → 536 BC`; Tishri / Nisan phase field | historical verification field | Day-scale / year-scale dual table preserved; File_12 controls phase language. |
| 2520 gerah state | `1000 + 1000 + 20 + 500 = 2520` | Mene Mene Tekel Parsin weight sum | Source-control note in §5.6.C: the 50-shekel mina (1000 gerahs) is the system used; do not substitute the 60-shekel mina. |
| 101.5-year coin-chronology state | `50 + 50 + 1 + 0.5 = 101.5`; `588 → 538 → 488 → 487 → 486 BC` | layered coin mapping | Preserved; `588 BC` siege label is a File_08 / File_16 dependency state. |
| Asymmetric polarity-crossover research-note state | unopened | bounded research note | §5.1 and Machine Guard [ASYMMETRIC POLARITY-CROSSOVER NOTE]; never load-bearing. |

### 0.2 Node-class register

| Label | Meaning | Example |
|---|---|---|
| Sextuplet start | First term of a prime sextuplet | P16 start `16057`; P19 start `19417`; P25 start `43777` |
| Sextuplet true center | Midpoint of the sextuplet, start + 8 | S1 `15`; S2 `105`; P16 `16065` |
| Active `Q` | Prime-quad value used by the corrected polarity / projection rows (File_36) | P16 `16061`; P19 `19421`; P25 `43781` |
| Zero-center output | `Q ± 30` rendered as a BC-side coordinate | P16 `16091 / 16031 BC`; P19 `19451 / 19391 BC`; P25 upper `43811 BC` |
| Sojourn-vector output | `Q ± 215` rendered as a BC-side coordinate | P16 `16276 / 15846 BC`; P25 lower `43566 BC` |
| Affliction-vector output | `Q ± 185` rendered as a BC-side coordinate | P16 `16246 / 15876 BC` |
| Positive `M⁺` output | `Q + 25` rendered as a BC-side coordinate | P25 `43806 BC` |
| Harmonic subtractor | Fixed span subtracted from a prime-space coordinate to reach a chronological target | `14400`; `14000`; `17500`; `43320` |
| Chronological target | Dated anchor produced by a projection | `1876 BC`; `1446 BC`; `2091 BC`; `1951 BC`; `486 BC`; `6 BC` |
| Anchor-marker pair | A `+50` pair marking start / end points, not a cumulative error | `536 / 486 BC`; `2906 / 2856 BC` |

### 0.3 Machine Guards

Machine Guard [SEXTUPLET TRUE CENTER / ACTIVE Q SEPARATION]:
Do not conflate sextuplet true centers (start + 8: `15`; `105`; `16065`; `19425`; `43785`) with active `Q` values (start + 4: `101`; `16061`; `19421`; `43781`). The `90 + 30 + 90` lattice of §1 runs on true centers. The projections of §§3, 4, 6, and 7 run on active `Q` and its offsets. Both usages are valid in their own sections; collapsing them corrupts the arithmetic of one or the other.

Machine Guard [ZERO POINT]:
The term "Zero Point" denotes the physical seasonal pivot between Tishri and Nisan (Tishri 1, 1 BC ↔ Nisan 1, AD 1). Programmatic constraint: do not introduce the integer 0 into chronological coordinate arrays. Abide strictly by the civil arithmetic rule `BC + AD − 1`. This seasonal pivot exists within the civil boundary, not as an independent integer year.

Machine Guard [+50 KINGDOM TERMINATION]:
The +50 accumulation from the Kingdom era TERMINATES strictly at the Exodus anchor (`1446 BC`). Programmatic constraint: any algorithm summing cumulative dates or tracing gaps backward through the timeline MUST stop applying the +50 variance at `1446 BC`. The `1876 BC` Super-Anchor and all prior Patriarchal dates are shielded from this expansion.

Machine Guard [RETIRED WIDTH-50 FOUNDATION]:
`File_38` does not derive the `+50` variance, or any `±2` variance, from a prime-internal width or gap model (Width 50 / Width 46; "Standard Breathing Room"). That foundation is retired by `File_37 Final` (Register §31.140B). Actual `+50` states in Kings of Judah, SKL, and Berossus remain valid as dependency-controlled chronological states. Do not reconstruct the retired derivation from this file's source-history.

Machine Guard [ASYMMETRIC POLARITY-CROSSOVER NOTE]:
Do not treat the asymmetric polarity-crossover construction as an active operator, derivation, dependency, or proof for the +50 variance or for any other value in this file or the repository. It is unopened research-note material only (§5.1). No calculation in `File_38` may cite it, and it must not be expanded, rederived, or made load-bearing without explicit author direction.

Machine Guard [SKL / BEROSSUS DEPENDENCY]:
Do not locally rederive SKL / Berossus `361`, `486 BC`, `120 × 361 = 43320`, the Kings / Berossus `+50`, or the `±720` Cosmic Pixel. Route these through `File_34` unless `File_38` explicitly opens the full File_34 derivation. The Pillar AD targets `AD 29465` / `AD 29515` are File_34 / File_41 states cited here by dependency.

### 0.4 Terminology controls

| Legacy wording | Final wording / handling |
|---|---|
| Sextuplet 1 (S1) / Sextuplet 2 (S2) | P2 foundational sextuplet (source label S1) / P3 mod210 sextuplet (source label S2). Source labels retained as display labels. |
| "Center: 16061 / 19421 / 43781" | Active `Q` (File_36 namespace). True centers are start + 8 (`16065`; `19425`; `43785`); see Machine Guard [SEXTUPLET TRUE CENTER / ACTIVE Q SEPARATION]. |
| "Primes 5 and −25" | Mod 30 polarity base `+5 / −25`. `5` is P1; `25` is the Key-of-23 completion of `23` (File_36), carried with negative sign on the mirror side. `−25` is not itself a prime. |
| "P25 Mirror" (`43806`) | P25 positive `M⁺` output (`Q + 25 = 43806 BC`); source label retained as display label only. Not a Coordinate Mirror / Protocol 1 state. |
| "Lower Autumn Anchor" (`43566`) | P25 sojourn-vector lower output (`Q − 215`); source label retained as display label. |
| Seder Olam / Seder Olam Rabbah | SOR / Seder Olam Rabbah per Style Guide §16.2. |
| "Gear Shift (±2)" via Width 50 / 46 | Retired foundation; not used (Machine Guard [RETIRED WIDTH-50 FOUNDATION]). |
| "FILE_37", "FILE_36", etc. | `File_37`, `File_36`, local repository style. |
| Verdict: | Removed as a header; statements retained as plain text pending layer-5 claim-status calibration. |
| Number formatting | No-comma number formatting is used throughout. |

### 0.5 Citation-control note

`1661 BC` is an established Capsule-governed Baseline Entry / minimum state under the 215-year Egypt span. `File_38` independently rederives that established state through the Historical Triad and Sojourn-vector logic. The label is not a new repository anchor and must not substitute `1876 BC` for the baseline `1661 BC` state.

## 1. The Sextuplet Modulus (210) and the 90 + 30 + 90 Lattice

### 1.1 The geometric centers

The "Fundamental Frequency" of the large-scale variants is identified from the true centers of the first two sextuplets:

| Sextuplet | Members | True center (start + 8) |
|---|---|---:|
| P2 (source S1) | `{7, 11, 13, 17, 19, 23}` | `15` |
| P3 (source S2) | `{97, 101, 103, 107, 109, 113}` | `105` |

Modal-state note:
These are sextuplet true centers, not active `Q` values (Machine Guard [SEXTUPLET TRUE CENTER / ACTIVE Q SEPARATION]).

### 1.2 The 90 + 30 + 90 lattice

Mapped across the axis as a signed A-space display (positive / negative placement of the centers), the centers create a rigid structure:

- Distance between the P3 and P2 centers: `105 − 15 = 90`.
- Distance across the axis (P2 positive to P2 negative): `15 + 15 = 30`.

Lattice: P3-negative ↔ 90 ↔ P2-negative ↔ 30 ↔ P2-positive ↔ 90 ↔ P3-positive.

Total span: `90 + 30 + 90 = 210`.

Modal-state note:
The signed placement is a polarity / A-space display under the File_32 / File_36 namespace. It does not introduce an integer year 0 into civil arithmetic (Machine Guard [ZERO POINT]).

### 1.3 The 210-year variant (SOR)

This geometric span corresponds to the 210 years of the SOR / Seder Olam Rabbah (the Rabbinic chronology calculating the Sojourn in Egypt as 210 years). The 210-year variant functions as the fundamental wavelength of the prime sextuplet lattice (`210n`).

Claim-status: arithmetic fact for the lattice sum `90 + 30 + 90 = 210`; structural inference for the correspondence between that span and the SOR 210-year Sojourn.

Dependency note:
The controlled SOR handling — SOR as a low-bound variant of the Actual MT backbone under the −215 lens, with Abraham at `1946 BC` and Entry at `1656 BC` — is governed by `File_51a`. `File_38` supplies the lattice correspondence; it does not replace the File_51a chronological treatment.

## 2. The Sojourn Variance (±215 / ±185)

### 2.1 The perspectival shift (the seasonal axis)

Chronological dates are generated by viewing this geometry from the axis between the civil years:

- The axis: Tishri 1, 1 BC ↔ Nisan 1, AD 1.
- Center: winter solstice / January 1 (the seasonal "Zero Point").
- Physical span: 7 months (Tishri to Nisan with leap month) = 210 schematic days (`7 × 30`).

This 210-day physical span acts as the template for the 210-year modulus.

Machine Guard pointer:
Machine Guard [ZERO POINT] (§0.3) governs this section. The seasonal pivot exists within the civil boundary; the integer 0 is never introduced into chronological coordinate arrays, and `BC + AD − 1` remains the civil arithmetic rule.

### 2.2 The Spring / Autumn vectors (creating the 215 and the 185)

The Sextuplet Modulus (`210`) is applied to the Mod 30 polarity base (`+5 / −25`) using Shift Addition:

A. The outer offset (Sojourn vector):

`5 + 210 = 215` — creates the ±215-year offsets.

B. The inner offset (Affliction vector):

`−25 + 210 = 185` — creates the ±185-year offsets.

Verification: `215 − 185 = 30` (preserves the Apparent Age constant).

Terminology note:
`+5 / −25` is the Mod 30 polarity base. `5` is P1; `25` is the Key-of-23 completion of `23` (File_36), carried with negative sign on the mirror side. The source wording "Primes 5 and −25" is corrected accordingly (§0.4).

### 2.3 The Historical Triad (1876 — 1661 — 1446)

The 430-year Sojourn is split exactly in half by the ±215 vectors:

| Date | Role | Offset from the sojourn midpoint (`1661 BC`) | Seasonal anchor (1 BC / AD 1 axis) |
|---|---|---:|---|
| 1876 BC | Entry (Long Sojourn) | +215 years | Tishri 1 (Autumn) |
| 1661 BC | Variant Entry (Short) | 0 (midpoint) | January 1 (winter solstice) |
| 1446 BC | Exodus (End) | −215 years | Nisan 1 (Spring) |

The source statement: the `1661 BC` date (Short Sojourn Entry) is physically generated by the Zero Point of the axis (winter solstice), while `1876 BC` and `1446 BC` are the Autumn (+215) and Spring (−215) vectors.

Modal-state note:
Two distinct "centers" operate here and must not be collapsed: (a) the sojourn midpoint year-label `1661 BC`, from which the ±215 offsets in the table are measured; and (b) the seasonal Zero Point on the 1 BC / AD 1 axis, which supplies the Tishri / Nisan / solstice anchors in the final column.

Modal-state note (variant identification):
`1661 BC` is the Sojourn-215 variant Entry state: `1446 + 215 = 1661`. This places it inside the same SP-215 / Sojourn 215 variant framework that yields Abraham at `1951 BC` (§6.1; `File_51a`; `File_01`). The midpoint identity (`1661` = midpoint of `1876 / 1446`) and the variant-Entry identity are two verified descriptions of the same year-label.

Claim-status: arithmetic fact for the ±215 offsets, the midpoint identity, and the variant-Entry identity; structural inference for the claim that the seasonal Zero Point of the axis generates the `1661 BC` Short-Sojourn Entry; the seasonal-anchor column (Tishri / solstice / Nisan) is a calendar-template reading classified as structural inference with `File_12` phase-language control.

Dependency note (corrected post-final, author-approved June 11 2026):
`1661 BC` is the capsule-governed Baseline Entry / minimum state (215-year Egypt span; Restart Capsule body, with the guard never to substitute `1876` for baseline `1661`), inventoried in the Capsule header as of v11.5 and registered at State_Vocabulary_Register §D.4. `File_38` independently rederives this established state (`1446 + 215 = 1661`; midpoint of `1876/1446`); the convergence is a confirmation, not a new anchor. `1876 BC` node-classes are controlled by `File_16`.

## 3. P16 — The Nested Time Shells (430 vs 400)

P16: sextuplet `{16057, 16061, 16063, 16067, 16069, 16073}`; start `16057`; terminal `16073`; true center `16065`; active `Q = 16061`. All projections in this section run on `Q` (Machine Guard [SEXTUPLET TRUE CENTER / ACTIVE Q SEPARATION]).

P16 generates two concentric "Time Shells" separated by 30 years.

### 3.1 The outer shell (the 430 Sojourn)

- Offsets: `16061 ± 215 → 16276 / 15846`.
- Projection (`40 × 360 = 14400`):
  - `16276 − 14400 = 1876 BC` (Entry).
  - `15846 − 14400 = 1446 BC` (Exodus).
- Span: 430 years.

### 3.2 The inner shell (the 400 Affliction)

- Offsets: `16061 ± 185 → 16246 / 15876`.
- Projection:
  - `16246 − 14400 = 1846 BC` (start of Affliction).
  - `15876 − 14400 = 1476 BC` (Joshua's birth).

Arithmetic note:
The inner shell's own width is `1846 − 1476 = 370` (`= 2 × 185`). The 400-year Affliction named in this section's heading is not the inner-shell width; it is realized diagonally in §3.3, exactly as the source structure states. Do not "correct" either value.

### 3.3 The diagonal lock

From inner upper (`1846 BC`) to outer lower (`1446 BC`) = 400 years (Gen 15:13).

## 4. The Terah Generation Gap (+60)

### 4.1 The Zero-Center Shift (±30)

The +60 variant (Terah begetting at 130 vs 70) arises from shifting the anchor from the polarity base to the true center of the field:

- Standard polarity base: `+5` and `−25` (width 30).
- Zero-Center anchors: to align with the exact center, the offsets shift to `+30` and `−30`.
- The gap: `+30 − (−30) = 60`.

Operator note:
The ±30 Zero-Center Shift is a named `File_38` operator registered in State_Vocabulary_Register v1.17 §D.4. It is not the ordinary File_32 prime rail and does not create a default `+60` prime rail (Register §31.135 analog).

### 4.2 The historical proof (P16)

- Anchors: `16061 ± 30 → 16091 / 16031`.
- Harmonic: `14000` years.
- Targets:
  - `16091 − 14000 = 2091 BC` (Call of Abraham).
  - `16031 − 14000 = 2031 BC` (Death of Terah).

The source statement: the 60-year gap is the chronological shadow of the axis width when centered on zero.

Modal-state note:
`2091 BC` carries a dual node-class in the MT field: the Call of Abraham at 75 (`2166 − 75 = 2091`) and the Terah-130 death year-label (`2296 − 205` from birth at `2166 + 130 = 2296`) coincide there. `2031 BC` is the Terah-70 death state (birth at `2166 + 70 = 2236`; death at 205 `= 2031`). Both states verified in layer 4 (§0.5). The `+60 Terah` mechanism is controlled by `File_00` §3.4.1; Abraham biography rows are controlled by `File_01`.

Claim-status: arithmetic fact for the anchors, targets, and both begetting-age states; structural inference for the "chronological shadow of the axis width" reading.

## 5. The Kingdom Variance (+50) — Actual State, Scope, and Limits

### 5.0 Scope and control

The +50 variance behaves differently in the Biblical chronology versus the external (SKL / Berossus) chronologies. In both domains it is an **actual chronological state**:

- Kings of Judah accumulator: controlled by `File_08` (dual ledger) and `File_18` (data).
- `+50` Jubilee Offset: controlled by `File_16`.
- SKL / Berossus anchor pairs and the `±720` Cosmic Pixel: controlled by `File_34`.

Per `File_37 Final` and Machine Guard [RETIRED WIDTH-50 FOUNDATION], `File_38` does not derive this +50 from prime-internal width geometry. The former §5.1 derivation (anchors `+25 / −25`, Width 50 as "Standard Breathing Room") is removed as executable content and survives only as source-history.

### 5.1 Bounded research note — asymmetric polarity-crossover construction (unopened)

Research note (bounded; non-load-bearing; unopened):
By author direction, the +50 variance can also be construed at the prime level through an asymmetrical crossover of polarities at the Mirror. This construction is recorded as a possible future line of inquiry only. It is not used anywhere in this file, it is not a foundation for any calculation, operator, or claim here, and the argument of `File_38` stands wholly without it. The author deliberately omitted its use because it adds degrees of freedom unnecessary to demonstrate the similarity of the Q/S primes to the biblical chronology. If objectionable, this note may be ignored without any loss to `File_38`.
Claim-status: structural inference; unopened.

Machine Guard pointer:
Machine Guard [ASYMMETRIC POLARITY-CROSSOVER NOTE] (§0.3) enforces this boundary.

### 5.2 The Biblical accumulator (Exodus to Exile)

Scope: Fall of Jerusalem (`586 BC`) ↔ Exodus (`1446 / 1496 BC`).

In the Biblical chronology, the 50-year gap is an accumulated variance. It arises from the difference between the "Verbatim Sum" of the Kings of Judah (inclusive reckoning / co-regencies) and the "Actual History" (overlapping reigns).

- Era of accumulation: from Solomon (`966 BC`) back to Moses (Exodus).
- The effect: the accumulated gap shifts the schematic dates back by 50 years relative to the historical dates:
  - Historical Temple `966 BC` vs schematic Temple `1016 BC`.
  - Historical Exodus `1446 BC` vs schematic Exodus `1496 BC`.
- The result: a harmonic Triple 430 structure (`1876 → 1446 → 1016 → 586`) that is visible only when the +50 is applied.

Dependency note:
The historical / schematic ledger pair is the `File_08` dual-ledger field; Kings of Judah data are supplied by `File_18`; `1496 BC` does not replace the primary `1446 BC` Exodus anchor (`File_05`).

### 5.3 The propagation limit (termination at Exodus)

The +50 accumulation TERMINATES at the Exodus. It does not propagate backward into the Patriarchal era.

- The Super-Anchor `1876 BC` (Entry into Egypt) remains fixed for both the schematic and historical timelines.
- Abraham, Isaac, and Jacob are unaffected by the Kingdom Gap.
- Logic: the Exodus serves as the "Shock Absorber," absorbing the 50-year expansion of the Kingdom era so that the Patriarchal era remains harmonically locked.

Machine Guard pointer:
Machine Guard [+50 KINGDOM TERMINATION] (§0.3) enforces this boundary programmatically.

### 5.4 The cosmic identifier (SKL and Berossus)

Scope: anchor points only.

For the Sumerian Kings List (SKL) and Berossus, the 50-year variance acts as an anchor marker, not a cumulative error.

A. The anchor frames:

| System | Pair | Gap |
|---|---|---:|
| Berossus | `536 BC` (historical) vs `486 BC` (figurative) | 50 |
| SKL | `2906 BC` (ideal) vs `2856 BC` (actual) | 50 |

B. The non-propagation principle: the 50-year gap does not transfer up through the Sumerian king lists. It does not mean Alulim reigned 50 years longer. It simply marks the start and end points of the cosmic grid.

C. The Cosmic Pixel (`±720`): the SKL / Berossus systems also utilize the ±720-year shift. The 50-year marker remains constant across these shifts, identifying the anchor pair.

Dependency note:
Machine Guard [SKL / BEROSSUS DEPENDENCY] applies to this entire section. The derivations of `536 / 486 BC`, the SKL pairs, and `±720` are controlled by `File_34` (with SKL terminal-pair context in `File_24` and SKL protocol in `File_21`).

### 5.5 The Pillar reflection (future mirror)

The 50-year gap reappears at the "Pillars of Time":

- Pillar Boaz: `AD 29465` (projected from `536 BC`).
- Pillar Jachin: `AD 29515` (projected from `486 BC`).
- Gap: `29515 − 29465 = 50` years.

Arithmetic fact (civil cross-axis verification): both projections are exact 30000-year civil spans — `536 + 29465 − 1 = 30000` and `486 + 29515 − 1 = 30000` — matching the File_34 Pillar / AD target state.

Dependency note:
The Pillar AD targets and their projections are `File_34` states (Pillar / AD target state), with Jachin Mirror control in `File_41` and Pillar-state dependency in `File_21`. They are cited here by dependency.

### 5.6 Historical verification — the 539–536 BC Danielic Lock

The architectural "why": this section supports the authenticity of the +50 Kingdom Gap by demonstrating the mutual reliance of both Daniel and Berossus on the "3.5" fractal. The precision of the 3.5-year period from the Fall of Babylon (`539 BC`) to the Temple restoration (`536 BC`) argues that the 50-year gap connecting to the Berossus anchor (`486 BC`) is intrinsic rather than imposed. Both Daniel (trained in Babylonian wisdom) and Berossus record this "3.5 days/years" pattern.

A. The Danielic fractal (day-year correlation):

The "Dividing of the Week" operates on two scales simultaneously, synchronizing the day-count of the Feast of Tabernacles with the year-count of the Exile's end.

| Component | Day scale (Tishri days) | Historical scale (years) | Significance |
|---|---|---|---|
| Time | Tishri 15 (evening) | 540 BC (Tishri) | Last full Feast of Babylon |
| Times | Tishri 16–18 (evening) | 539–538 BC | Fall of Babylon (Tishri 16) + 2 years |
| Half-Time | Tishri 18 (morning) | 537/536 BC | First Tabernacles (Ezra 3) / Passover |

B. The historical sequence (540–536 BC):

- `540 BC` (Tishri 15): the start of the final 3.5-year window.
- `539 BC` (Tishri 16): the Fall of Babylon (October 12). The Nabonidus Chronicle records that Persian troops entered on 16 Tishri. Daniel 5:30 ("that very night") places the event after the evening sunset that began the 16th, supporting the precision of the day count.
- `537 BC` (Tishri): the first Feast of Tabernacles celebrated after the return (Ezra 3:4), marking the altar rebuilding. This fulfills the "Times" (2 years from `539 BC`).
- `536 BC` (Nisan / Ziv): the foundation of the Temple (Ezra 3:8), following the first Passover (Nisan 15).

Dependency note:
Tishri / Nisan phase language and the `3.5` half-week register are controlled by `File_12`; prophetic span grammar (`1260`; `2520`) by `File_17`.

C. The writing on the wall (the 2520 Gerah Lock):

The words Mene, Mene, Tekel, Parsin (Dan 5) provide a double witness.

1. The structural resonance: the composition of the currency — two minas (Mene, Mene), one shekel (Tekel), and half a mina (Parsin) — resonates with the prophetic formula "Time, Times, and Half a Time" (2 + 1 + 0.5). The sequence differs, but the elemental structure of two, one, and a half is identical.
2. The 2520 Gerah calculation: as discovered by the author 26 years ago, the literal weight of these denominations sums to exactly 2520 gerahs, the Prophetic Week:
   - Sum: `1000 + 1000 + 20 + 500 = 2520` gerahs.
   - The division: `2520` represents the 7-year week (`7 × 360`). The final term, Parsin ("Division"), mathematically splits the week into 1260 days (3.5 years).

Source-control note:
The gerah values used are: 1 shekel = 20 gerahs (Exod 30:13); 1 mina = 50 shekels = 1000 gerahs; Parsin as half a mina = 500 gerahs. This calculation uses the 50-shekel mina system. Do not "correct" the sum by substituting the Babylonian 60-shekel mina (1200 gerahs); the 50-shekel mina is the system the source uses, and the `2520` result depends on it.

D. The multi-layered coin chronology (101.5 years):

Beyond the 2520 gerahs, the sequence of decreasing coin values (mina → shekel → half) maps to the 101.5-year span from the siege of Jerusalem to the Berossus anchor:

| Term | Span | From | To |
|---|---:|---|---|
| Mene | 50 years | 588 BC (siege) | 538 BC (end of Exile) |
| Mene | 50 years | 538 BC | 488 BC (Berossus extension) |
| Tekel | 1 year | 488 BC | 487 BC |
| Parsin | 0.5 years | 487 BC | 486 BC (Berossus anchor) |

Total: `50 + 50 + 1 + 0.5 = 101.5` years.

The linguistic pun: Parsin ("Divided / Half") is a play on Paras (Persia). In the Berossus +50 scheme, the "Half-Mina" marks the anchor point (`486 BC`) where the Persian timeline is structurally locked. The coins denote decreasing value (gold → silver → bronze) while simultaneously marking the chronological distance to the cosmic anchor.

Conclusion of §5.6: the Fall of Babylon (`539 BC`) was the literal "Dividing of the Week" encoded in both the weights of the judgment and the calendar of the Exile. The +50 Kingdom Gap serves as the structural "Mene" that links the historical restoration (`536 BC`) to the cosmic anchor (`486 BC`).

Dependency note:
`588 BC` is the siege label; the primary Fall of Jerusalem state (`586 BC`) is controlled by `File_16`, with the Kings / Temple ledger field in `File_08`.

Claim-status register for §5.6:

| Element | Classification |
|---|---|
| Nabonidus Chronicle 16 Tishri entry; Dan 5:30; Ezra 3:4; Ezra 3:8 | Textual / historical data. |
| `2520` gerah sum (`1000 + 1000 + 20 + 500`); `7 × 360 = 2520`; `2520 ÷ 2 = 1260`; coin chronology `50 + 50 + 1 + 0.5 = 101.5`; all dated spans | Arithmetic facts on the stated weight system (see source-control note). |
| Day-scale / year-scale "Dividing of the Week" correlation; Mene-Mene-Tekel-Parsin / Time-Times-Half structural resonance; the claim that the 3.5 pattern shows the +50 gap to be intrinsic rather than imposed | Structural inference. |
| Daniel and Berossus as joint carriers of the 3.5 pattern | Structural inference / shared-tradition evidence; not proof of direct literary dependence. |
| Parsin / Paras linguistic pun | Textual observation / typological reading. |
| "The Fall of Babylon was the literal Dividing of the Week encoded in the weights and the calendar" | Theological note / providential synchronization built on the verified arithmetic; it does not carry the arithmetic burden. |

## 6. The Patriarchal Validation (P19)

P19: sextuplet start `19417`; true center `19425`; active `Q = 19421`. All projections in this section run on `Q`.

### 6.1 P19 — the Jubilee Command Center

P19 is the "Kingdom Prime," shifted `+3360` years (10 Priestly cycles; `10 × 336`) from P16 (File_36 P16 / P19 sextuplet relation).

- Anchors (±30 Zero-Center Shift): `19451 BC` and `19391 BC`.
- Harmonic: `17500` (`100 × 175`, Abraham's life).
- Targets:
  - `19451 − 17500 = 1951 BC` (Birth of Abraham).
  - `19391 − 17500 = 1891 BC` (Echo of Terah).
- Significance: `1891 BC` is exactly 60 years after Abraham's birth (`1951 − 1891 = 60`), mirroring the Terah overlap structure of §4.

Claim-status: arithmetic fact for the anchors, targets, and the 60-year interval; structural inference for the "Echo of Terah" reading and the Kingdom Prime designation.

Modal-state note:
`1951 BC` is the SP-215 / Sojourn 215 variant Abraham birth state (`File_51a`; `File_01`), not the MT Regular birth (`2166 BC`). The two states must not be collapsed.

### 6.2 The 400-Jubilee pivot

P19 anchors the 490-year cycles to Christ. The `+3360` Priestly decade relation carries both P16 shells upward, producing two P19 anchors parallel to the outer / inner shell structure of §3:

- Outer-shell P19 anchor: `16276` (P16 outer upper) `+ 3360 = 19636 BC` (used in §6.3).
- Inner-shell P19 anchor: `16246` (P16 inner upper) `+ 3360 = 19606 BC` (used here).
- Target: `6 BC` (Birth of Christ).
- Span: `19606 BC → 6 BC = 19600` years (same-side BC span).
- Factorization: `19600 = 400 × 49 = 40 × 490`.

Audit note (resolved):
The source printed only the outer-shell derivation (`19636 BC`) while computing the Jubilee span from `19606 BC`. Layer 4 verified both anchors exactly and added the missing inner-shell derivation line under Procedures §5.1 assumed authorial affirmation; no value was changed (§0.5). Recorded for author review.

Claim-status: arithmetic fact for both anchor derivations, the span, and the factorizations; structural inference for the Jubilee-pivot reading anchored to Christ.

Dependency note:
`6 BC` as the Birth of Christ is a `File_13` Christological target state.

### 6.3 The Christological symmetry (8880 + 8880)

P19 reveals the "Double 888" symmetry governing the span to the Sojourn:

- From: P19 anchor (`19636 BC`).
- To: Entry into Egypt (`1876 BC`).
- Span: `19636 − 1876 = 17760` years.
- The halving: `17760 ÷ 2 = 8880`.
- Structure: `8880 + 8880 = 17760` (`= 40 × 444`).

Theological note:
The path from the Kingdom sextuplet to the Sojourn is paved with the Double Witness of Jesus (`8880 + 8880`). This is a theological / typological reading of the verified arithmetic; it does not carry the arithmetic burden.

## 7. The Messiah and Metonic Lattice (P25)

P25: sextuplet start `43777`; true center `43785`; active `Q = 43781`. All projections in this section run on `Q`.

### 7.1 P25 — the Messiah Sextuplet

P25 provides the grand reconciliation of the Curse (13), Covenant (70), and Temple (46):

- Anchor: `43811 BC` (upper Zero-Center output; `Q + 30`).
- Target: `1951 BC` (Abraham's birth; SP-215 variant state as in §6.1).
- Span: `43811 − 1951 = 41860` years.
- Factorization: `41860 = 46 × 13 × 70`.

### 7.2 The Berossus Metonic Lock

P25 connects to the Berossus anchor (`486 BC`) — the specific anchor marked by the 50-year gap (§5.4):

- Calculation: `120` (Moses) `× 361` (Metonic year) `= 43320` years.
- Target: `43806` (P25 positive `M⁺` output; `Q + 25`; source display label "P25 Mirror") `− 43320 = 486 BC`.

Dependency note:
`361`, `120 × 361 = 43320`, and the `486 BC` Berossus computational anchor are `File_34` states cited by dependency (Machine Guard [SKL / BEROSSUS DEPENDENCY]). The `43806 BC` coordinate is a positive-polarity output, not a Coordinate Mirror / Protocol 1 state (§0.4).

### 7.3 The Christological Lock (Joseph squared)

- From: `43566 BC` (P25 sojourn-vector lower output; `Q − 215`; source display label "Lower Autumn Anchor").
- To: `6 BC` (Birth of Christ).
- Span: `43566 − 6 = 43560` years.
- Factorization: `43560 = 121 × 360 = 11² × 360`.

Theological note:
The span is the square of Joseph (11) measured in prophetic time. This is a typological reading of the verified arithmetic.

### 7.4 The Abrahamic expansion

- From: `43566 BC`.
- To: `2166 BC` (MT Abraham birth).
- Span: `43566 − 2166 = 41400` years (`= 115 × 360`).
- Expansion: `41400 × (25/23) = 45000`.
- Difference: `45000 − 41400 = 3600`.
- Target: `AD 1435` (Mirror of Conquest +30).

Derivation (added in layer 4):
The expanded value `45000` is itself the civil cross-axis span from the same P25 output to the target: `43566 + 1435 − 1 = 45000`. The Key-of-23 expansion of the Abrahamic span therefore projects `43566 BC` across the axis to land exactly at `AD 1435`. The source parenthetical also verifies independently: `AD 1435 = AD 1405` (civil mirror of Conquest `1406 BC`) `+ 30`.

Audit note (resolved):
The source printed the target without the connecting derivation. Layer 4 supplied it as an exact civil cross-axis arithmetic fact under Procedures §5.1 assumed authorial affirmation; no value was changed (§0.5). Recorded for author review.

Claim-status: arithmetic fact for the span, expansion, difference, civil derivation, and mirror identity; structural inference for the Abrahamic-expansion reading; the Conquest-mirror identification is a Mirror display of the actual chronological target-state per File_36 target-Mirror restraint.

## 8. Conclusion and Synthesis

The sextuplets are the engine of the 210-family variance. While the quadruplet field defines the rigid Apparent Age structures (controlled elsewhere), the sextuplets define the "breathing room" of the Sojourn-era chronology.

The moduli hierarchy as established in this file:

| Mechanism | Operator | Variance generated | Biblical equivalent | Status in `File_38` |
|---|---|---:|---|---|
| Sextuplet Modulus | `+210` Shift Addition on the `+5 / −25` polarity base | ±215 / ±185 | Sojourn 430 / Affliction 400 / SOR 210 | Derived locally (§§1–3) |
| Zero-Center Shift | `±30` | +60 | Terah begetting-age gap (130 vs 70) | Derived locally (§4) |
| Actual +50 state | Kings dual-ledger accumulation; SKL / Berossus anchor pairs | +50 | Kings of Judah; Berossus `536/486 BC`; SKL `2906/2856 BC` | Actual state by dependency (§5); anchors marked by the grid; origin not derived here |

The architectural summary:

- P16 projects the 430-year Sojourn onto `1876 / 1446 BC` and the 400-year Affliction onto `1846 / 1476 BC` via the `14400` harmonic, with the 400-year diagonal lock (Gen 15:13).
- P19 projects the Jubilee structure onto `6 BC` (`19600 = 40 × 490`) and carries the `8880 + 8880` symmetry to the Sojourn entry.
- P25 locks the Babylonian timeline (`486 BC`) via the File_34-controlled Metonic harmonic and carries the Joseph-squared typology to `6 BC`.

The chronological variants treated here (+210, ±215 / ±185, +60) are not contradictions; they are the outputs of a prime lattice that integrates solar, lunar, and prophetic time. The +50 variance stands beside them as an actual, dependency-controlled chronological state whose anchor pairs the same lattice marks.

Claim-status note:
The moduli-hierarchy table rows for the Sextuplet Modulus and the Zero-Center Shift rest on layer-4 verified arithmetic facts; their designation as the "engine" of the 210-family variance is structural inference. The +50 row is dependency-controlled. The closing integration statement (solar, lunar, and prophetic time in one architecture) is structural inference and providential synchronization built on the verified arithmetic; it does not replace it.

## Cross-reference index

| File | Section / function | Relevance | Dependency status |
|---|---|---|---|
| `File_37` | Final; Register §31.140–§31.140D | Retired prime-gap boundary; no Width-50 / ±2 import; tetrad context | governing boundary |
| `File_36` | Final; §0.2–§0.4; §15 | Active `Q` namespace; positive `M⁺` outputs; target-Mirror restraint; P16 / P19 `3360` relation; SKL / Berossus dependency guard | governing namespace |
| `File_35` | Final | Polarity-before-Mirror precedent | precedent |
| `File_34` | Final | `361`; `120 × 361 = 43320`; `486 BC`; Kings / Berossus `+50`; `±720`; Pillars `AD 29465 / 29515` | governing derivation |
| `File_16` | Final | `1876 BC` Nexus node-classes; `+50` Jubilee Offset; `586 BC` primary state | governing anchor control |
| `File_18` | Final | Kings of Judah data; table sources | data dependency |
| `File_08` | Final | Kings dual-ledger `+50`; `966 BC`; Temple / Jerusalem field | governing ledger |
| `File_00` | Final | `+60 Terah` (§3.4.1); civil arithmetic; axioms | governing operator |
| `File_01` | Final | Abraham biography states (`2166 BC`; `2091 BC`; SP-215 field) | biography control |
| `File_05` | Final | Primary `1446 BC`; `1496 BC` non-replacement | anchor control |
| `File_12` | Final | Tishri / Nisan phase language; `3.5` half-week | calendar control |
| `File_13` | Final | `6 BC` Christological target | target control |
| `File_17` | Final | `360`; `490`; `1260`; `2520`; `25/23` | span grammar |
| `File_41` | Final | Jachin Mirror / Pillar states | Pillar control |
| `File_21` | Final | SKL protocol; Pillar-state dependency | SKL control |
| `File_24` | Final | SKL terminal-pair context | SKL data context |
| `File_51a` | Final | SOR low-bound handling; `1951 BC` variant Abraham | variant control |
| `File_54` | Final | Claim-status restraint exemplar | style precedent |

## Unresolved issues

None.

## Revision and archive note

This public-clean Markdown source removes only archival amendment history, pass-verification registers, completed recommendation rows, the revision log, and replacement-workflow notes.

Detailed revision history is preserved in the `Repository_Change_Archive`.

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