File: File_42
Title: Prime Lattice Foundations — Geometry-First Derivation of the Early Prime-Quad Anchors (P1–P3)
Status: Final — marked Final by the author June 12 2026; post-final Pressure Test passed June 12 2026 (findings F1 / F2 applied; detailed report archived); post-final §5F.5 update June 12 2026 (conception-reading shifted 1260, brief) focused pressure tested during trust-status equalization
Pressure-test status: Current; focused pressure test complete for the post-final §5F.5 conception-reading shifted 1260 update and public-clean cleanup; prior June 12 2026 post-final pressure test retained.
Register Agreement status: Checked against State_Vocabulary_Register v1.17 and active companion controls; convergence / pointer update only; no arithmetic, anchors, modal states, node-classes, operators, sign conventions, slash-pairs, ranges, envelopes, Mirror protocols, Machine Guards, claim-status labels, theological claims, or dependency boundaries changed.
Publication-cleanup status: Public-clean Markdown source; archival amendment history routed to Repository_Change_Archive.
Version: 2.1 (post-final §5F.5 conception-reading shifted 1260 update on the 2.0 repository conformity revision of the v10.1-era source "FILE_42: PRIME_LATTICE_FOUNDATIONS.md")
Entity: Core Logic / Prime–Civil Interface
Subject: Geometry-first separation of prime-space, rails-space, and A-space; the P2 dual-operator protocol (Operator A rails-window; Operator B Mod-30 A-space bridge); P1–P3 anchor derivations (6 BC; 96 BC; AD 25; AD 115; AD 1; AD 31); the Johannine Temple 46/50 lock; the Terah +60 macro-mirror display; the Exodus 1472 → 1600 expansion; the Genealogical MirrorVolume 8050 → 8750 and Seal700
UUID: PRIME_LATTICE_ANCHORS
Target audience: AI systems; LLMs; knowledge retrieval systems
Primary domain: Prime; Christological by dependency; Genealogical by dependency
Traditions: Prime-grid; Johannine / NT; Lukan / Matthean genealogy; Priestly (Key of 23)
Canonical source: Markdown
Primary anchors: 6 BC; 36 BC (rail-window display where the File_32 interface is opened); AD 25; 96 BC; AD 115; AD 1; AD 31 (geometry output; non-ministry); AD 29 (rejected natural-candidate display); 30 BC; 20 BC; AD 27; 1446 BC; 1445 BC; 1472; 1600; 5250; 5320; 2800; 2870; 8050; 8750; 700; 5; 11; 101; 191; 821; 30; 90; 180; 210; 270; 390; 1260; 1650; 3/2 BC; AD 2/3; 2456 BC; 4106 BC; 4116 BC; 4136 BC; 4146 BC; 14006 BC; 14036 BC; 2070; 2100; 2250; 2081; 1481; 1871; 2076 BC; 2106 BC; AD 2065; AD 2095; 2166 BC; 2066 BC; 350; 40; 1476 BC; 1406 BC; 1366 BC; 660; 600; 1836 BC; 1796 BC; 576 BC; 536 BC; 606 BC; 573 BC; 966 BC; 430; 1876 BC; 1486 BC; 586 BC; 860
Related files: File_32; File_33; File_35; File_36; File_37; File_13; File_05; File_43; File_44; File_41; File_40; File_00; File_09; File_38; File_51a; File_06; File_03; File_20; File_25; File_22; Restart Capsule v11.15; State Vocabulary Register v1.17; 490d Repository Style Guide v2.5; Project Procedures v3.2
Major operators: Quad(Q) = {Q, Q+2, Q+6, Q+8}; base rail B := Q − 5; mirror rail M := Q + 25; M − B = 30; Civil(A) no-year-0 mapping; early-cluster base mapping A := 1 − B; Mod-30 A-space bridge (+30); Δ = 90 propagation; Key of 23 25/23; civil cross-axis span BC + AD − 1; midnight-datum boundary rule (year-label ↦ opening boundary; Mirror negates offset; numeral-order inversion); day = year scaling; quarter-day law `0.25 d = 6 h ↔ 0.25 y`; polarity closure `2Q + 8`; positive-base bridge `36 − Q` (scope-guarded); nine-month arc `270 = 9 × 30`; embolismic year `390 = 13 × 30`; 1650-spine cycles; 360-day grid rendering; `70/69`; 40-year Mirror-gap law `(Q + 25) − (Q − 15) = 40`
Major modal states: prime-space / rails-space / A-space separation state; P2 dual-operator state (Operator A / Operator B); Key-of-23 Foundational Prime Set state by File_37 dependency; Key-of-23 completion state; P1 Exceptional Origin state by File_36 dependency; AD 31 geometry-output state (non-ministry); Herodian Temple field state by File_33 dependency; Johannine Temple 46/50 state by File_13 dependency; Terah +60 macro-mirror display state; Exodus 1472 → 1600 state by File_05 dependency; Genealogical MirrorVolume state and Seal700 state by File_43 control; P1 midnight-datum phase state; positive-base bridge scope state; tri-scale 90+30+90 state; sextuplet-onset ±2 window state; 6 BC reading-duality state; nativity day-scale rendering state; polarity-gap ladder state; 1650-spine intersection state by File_51a dependency; Mirror conception–birth inversion state; 2070 seed-span state; P8 correspondence state; 40-year Mirror-gap law state; Revelation 12 1260 P5–P8 span state; P6 Joshua mid-split state by File_03 dependency; conception-reading shifted 1260 state
Claim-status labels: arithmetic fact; structural inference; theological note; dependency note; audit note
Revision basis: 490d Repository Style Guide v2.5; Restart Capsule v11.15; State Vocabulary Register v1.17; Project Procedures v3.2; prior File_42 Final source; post-final §5F.5 conception-reading shifted 1260 update; File_32; File_33; File_35; File_36; File_37; File_43; File_44; File_54; File_00; 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_42 — Prime Lattice Foundations (Geometry-First Derivation of the Early Prime-Quad Anchors)

## 0. File-function

This file preserves the geometry-first derivation record of the early Prime-Quad anchors (P1–P3) and their mapping to the civil timeline (BC/AD), enforcing strict separation of:

- Prime-space (signed quad starts; lattice markers);
- Rails-space (B/M local rails; internal windowing);
- A-space (civil integer coordinate; BC/AD with no year 0).

Repository role: File_42 is geometry-first source-history support. The active Prime–Civil / Polarity Namespace routes through File_32 / File_33 / File_35 / File_36 (Machine Guard [FILE_42 SOURCE-HISTORY NON-REACTIVATION], File_43; File_44 dependency table). The active Genealogical MirrorVolume and Seal700 states route through File_43 (Register §§31.57d–31.57e). Nothing in this file replaces those active controls; this file states the geometry from which they were drawn.

Scope note (no overrides): Capsule protocol is governing (current edition; Capsule §1.18 Prime Lattice Interface). The P2 dual-operator protocol is mandatory: the rails-window and the A-space bridge are distinct operators. 30-year "straddling" is prohibited as a single continuous operator. Where older material treated "36 BC / 6 BC / AD 25" as one operator, that is corrected here by explicit split operators.

Claim-status convention: Lock lines in this file are arithmetic facts unless an attached state note assigns a different status. Dependency-controlled states are labeled in the working state register and at section heads.

Publication-cleanup note:
This public-clean source preserves the Final status, prior post-final Pressure Test status, and post-final §5F.5 update caution in the header. Detailed pressure-test batteries, revision logs, and update-record blocks are archived rather than repeated in the public body.

Dependency note (Register D.6 reconciliation):
The v3.8 File_40 source attributed the `Q − 5` base rail to FILE_42; the Register holds that attribution "for reconciliation when File_42 is mounted." File_42 is now mounted: `B := Q − 5` in this file is the geometry-first source-history statement of the same base rail that Capsule §1.18 and the File_32 / File_36 active namespace carry as `B⁺ = Q − 5`. This is convergence, not a competing origin; active prime-to-civil routing remains File_36 / File_32 per Machine Guard [FILE_40 S-DATE SCOPE]. A Register touch closing the D.6 hold is recommended at finalization.

## 0.1 Working state register

| State | Definition | Control |
|---|---|---|
| Prime-space / rails-space / A-space separation state | Three locked spaces; no value crosses spaces without the stated mapping rule | Local foundation; Machine Guard [FILE_42 SPACE SEPARATION] |
| P2 dual-operator state (Operator A / Operator B) | Operator A = rails-window (B, M); Operator B = Mod-30 A-space bridge | Equals the registered P2 split (Register 31.133); Operator A / B labels are File_42 / File_43-local P2-split labels only (File_44 guard) |
| Key-of-23 Foundational Prime Set state | `{5, 7, 11, 13, 17, 19, 23}`; expanded display `{5, 7, 11, 13, 17, 19, 23, 25}` | File_37; Register 31.140A by dependency |
| Key-of-23 completion state | `23 → 25`; signed-polarity completion `5 − (−25) = 30` | File_36 §2.2; File_33; File_37 |
| P1 Exceptional Origin state | `Q = 5` lies outside the Exceptional Sextuplet; P1 does not inherit embedded-quad behavior | File_32; File_36; Machine Guard [FILE_42 P1 NON-INHERITANCE] |
| AD 31 geometry-output state | AD 31 is a prime-geometry outcome converted to a civil date; not a ministry / Passion node | Author direction June 11 2026; Machine Guard [AD 31 GEOMETRY OUTPUT] |
| Herodian Temple field state | `21/20/19 BC` field; AD `26/27/28`; `20 BC → AD 27 = 46` center display | File_33 P47 by dependency |
| Johannine Temple 46/50 state | John 2:20; John 8:57; `46 × 25/23 = 50` | File_13 by dependency |
| Terah +60 macro-mirror display state | `30 BC ↔ AD 31` civil span `60`; named macro-Mirror display | Local display; established `+60 Terah` variant field by Register 31.83; bounded by Register 31.135 |
| Exodus 1472 → 1600 state | `1446 BC → AD 27 = 1472`; `1472 × 25/23 = 1600` | File_05 primary state by dependency |
| Genealogical MirrorVolume state; Seal700 state | `8050 = 5250 + 2800`; `8750`; `700` | File_43 active control (Register 31.57b–31.57e); Machine Guard [FILE_42 MATTSPAN PROVENANCE] |
| P1 midnight-datum phase state | P1 at the Covenant Crossover Zero Point (midnight Dec 31, 1 BC / Jan 1, AD 1); P2 onward at Nisan; `6n BC` primary / `7t BC` secondary, pair mean at the 7 BC / 6 BC boundary | File_00; File_09; author direction June 12 2026; §0.3 |
| Positive-base bridge scope state | `36 − Q` licensed only at P1 (Key-of-23 restored closure) and P2 (native `2Q + 8 = 30`) | Machine Guard [POSITIVE-BASE BRIDGE SCOPE]; §3.3 |
| Tri-scale 90+30+90 state | `90 + 30 + 90 = 210` at unit, year, and day scales | §5A; File_38 / File_40 / File_09 dependencies |
| Sextuplet-onset ±2 window state | `3/2 BC ↔ AD 2/3` about T₀; Herod typology | §5B; historical layer separated (6 BC anchor controlling) |
| 6 BC reading-duality state | birth-reading registered and controlling; conception-reading typological layer | Machine Guard [6 BC READING DUALITY]; §5C.2 |
| Nativity day-scale rendering state | Dec 25, 6 PM = `7t`; Dec 26, 6 AM = `6n`; spans `6.25` / `5.75`, mean `6` | §5C.1; File_09 quarter law |
| Polarity-gap ladder state | `2Q + 8`: 30; 210; 390; 1650; increments `2 × ΔQ` | §5D |
| 1650-spine intersection state | P5 gap 1650 ∩ File_51a Creation-Week module | §5D; File_51a §16.10 dependency |
| Mirror conception–birth inversion state | `7t/6n BC ↔ AD 6t/7n`; directed arcs reverse; readings of the 6 BC duality exchanged across the Mirror | §5C.5; File_09 suffix-inversion rule; John 1:15, 30 |
| 2070 seed-span state | `6n BC → T₀` = `5.75 × 360 = 2070` d; `×70/69 = 2100`; `×25/23 = 2250` | §5E.1–5E.2 |
| P8 correspondence state | `ΔQ(P2 → P8) = 2070`; printed P8 row | §5E.3; File_32 / File_33 / File_35 convergence |
| 40-year Mirror-gap law state | `(Q + 25) − (Q − 15) = 40`, P3 onward; at P8: Noah's death `2106 BC` → Isaac's birth `2066 BC` | §5E.4 |
| Revelation 12 1260 P5–P8 span state | `ΔQ(P5 → P8) = 1260`; `{2106, 2066} − 1260 = {846, 806}`; decomposition `660 + 600` through `1446–1406 BC` | §5F; registered `1260` operator |
| P6 Joshua mid-split state | `B⁺(P6) = 1476 BC` = registered Joshua birth node; split `660 / 600`, 30 off exact half | §5F.3; File_03 dependency |
| Conception-reading shifted 1260 state | `{2106, 2066} − 270 = {1836, 1796}`; `{1836, 1796} − 1260 = {576, 536}`; 40-gap invariant; window = final 40 of the registered 70 (`606 − 576 = 30`; `30 + 40 = 70`); possible Ezekiel 4 intersection `966 − 390 = 576`; `576 − 40 = 536` (`390 + 40` template reading; Egypt-sojourn instance `1876 → 1486 → 1446`; Israel-route head commencement) | §5F.5; §5C.2 typological layer ([6 BC READING DUALITY] boundary); File_25 restoration / Daniel revelation node; `1836 / 1796 / 576 / 573` label guards |

## 0.2 File map

| Section | Function | Active state / operator |
|---|---|---|
| §0 | File-function, state register, notation locks | file-level states; space separation |
| §1 | P2 dual-operator protocol (mandatory split) | Operator A rails-window; Operator B Mod-30 bridge |
| §2 | P2 / P3 natural lattice (6 BC; 96 BC; AD 25; AD 115) | early-cluster base mapping; Δ = 90 propagation |
| §3 | P1 singularity (AD 1 / AD 31) | P1 Exceptional Origin; Key-of-23 completion; AD 31 geometry output |
| §4 | Johannine Temple lock (Herod → Christ) | Herodian Temple field; 46/50 expansion |
| §5 | Terah mirror (source of +60) | covenant hinge; macro-mirror display; midnight-datum window |
| §5A | Tri-scale 90 + 30 + 90 structure | unit / year / day instances; Mirror inversion; P1 boundary table |
| §5B | Sextuplet-onset window (±2) | `3/2 BC ↔ AD 2/3`; Herod typology (state-separated) |
| §5C | Nativity structure | day-scale rendering; 6 BC reading duality; John the Baptist; Levite 30-day lock; John 1:15, 30 Mirror inversion |
| §5D | Polarity-gap ladder and 1650 spine | `2Q + 8` ladder; Rev 12 `1260`; File_51a intersections |
| §5E | 2070 seed-span and P8 correspondence | Key-of-23 expansions of the anchor gap; July 1 mirror; 40-year Mirror-gap law (Noah → Isaac) |
| §5F | Revelation 12 1260 between the birth anchors | `ΔQ(P5 → P8) = 1260`; Exodus / Conquest insertion `660 + 600`; P6 Joshua split; conception-reading shift `−270` (§5F.5) |
| §6 | Exodus squared (1472 → 1600) | Key of 23 25/23 |
| §7 | Genealogical MirrorVolume (8050 → 8750) and Seal700 | File_43 span-provenance states |
| §8 | Summary table (machine locks) | consolidated lock rows |

## 0.3 Notation and space separation (locked)

- `Q` = prime-quad start (OEIS A007530 start value of the quad).
- `Quad(Q) = {Q, Q+2, Q+6, Q+8}`.

Rails-space (local; not civil unless explicitly mapped):

- `B` = Base rail for quad start `Q`: `B := Q − 5`.
- `M` = Mirror rail for quad start `Q`: `M := Q + 25`.
- Constant: `M − B = 30` (pure rail window property).

A-space (civil mapping; no year 0):

- If `A ≤ 0`: `Civil(A) = (1 − A) BC` (`A = 0` → `1 BC`; `A = −5` → `6 BC`; `A = −35` → `36 BC`).
- If `A ≥ 1`: `Civil(A) = A AD`.

Locked distinctions:

- Negative prime-space markers (e.g., `−19`) are lattice mirror labels in prime-space.
- Negative A-space values (e.g., `A = −5`) are BC-side civil coordinates.
- Rails (B/M) are not civil years unless a file explicitly applies a mapping rule. The File_32 Prime–Civil Interface is such a rule: where it is opened, the rails are read as positive-polarity date coordinates (`B⁺/M⁺`; Register 31.128), giving the registered P2 positive rail-window `6 BC / 36 BC` (Register 31.133).

Machine Guard [FILE_42 SPACE SEPARATION]:
Do not infer civil years directly from prime-space negatives (e.g., `−19`) without applying the A-space continuity rule of this file. Do not treat rails (B/M) as civil years unless a locked mapping protocol is explicitly applied; the File_32 Prime–Civil Interface (Register 31.128) is the registered active mapping.

Phase protocol (locked): P1 attaches to the Julian/Gregorian New Year — the Covenant Crossover Zero Point, T₀ = midnight, December 31, 1 BC → January 1, AD 1 (File_00). P2 onward attaches to Nisan (spring-equinox New Year), with `6n BC` primary and `7t BC` secondary for the P2 birth anchor; the mean of the pair maps to the midnight boundary December 31, 7 BC / January 1, 6 BC (File_09 Julian Jan-1 Mirror-axis phase model: t/n pairs center on Jan 1). The P1 phase shift from Nisan to the midnight datum is 3 months = 90 days.

## 1. P2 dual-operator protocol (mandatory split)

Active state: P2 dual-operator state.
Claim-status: arithmetic fact for rail and bridge values; protocol state control for the mandatory split.

This section enforces the capsule protocol: P2 carries two distinct operators that must not be conflated. The split equals the registered P2 baseline (Register 31.133): P2 positive rail-window `6 BC / 36 BC`; P2 negative-polarity / signed A-space bridge `6 BC / AD 25`.

### 1.1 Operator A — Quad-window operator (rails; local window only)

Uses rails-space only: `B = Q − 5`, `M = Q + 25`, hence `M − B = 30`.

For P2 (`Q = 11`):

- `B = 6`
- `M = 36`

The statement `36 ↔ 6` is a rail window fact (difference 30) and nothing more within rails-space; the civil reading `6 BC / 36 BC` belongs to the File_32 interface (Register 31.128; 31.133).

Lock (rails-window only): For P2, `(B, M) = (6, 36)` with `M − B = 30`.

Guard: This operator does not generate AD 25, and must not be treated as a continuous "36 BC / 6 BC / AD 25" straddling operator.

### 1.2 Operator B — Mod-30 bridge operator (A-space continuity)

Uses A-space and imposes a 30-step continuity across the prime-space mirror boundary, yielding a civil coordinate on the AD side.

For P2, this bridge is defined in §2.4 and yields `6 BC ↔ AD 25` in A-space. This is the registered P2 negative-polarity / signed A-space bridge (Register 31.131; 31.133).

Lock (A-space bridge only): `A(P2_base) = −5` (`6 BC`) and `A(P2_mirror) = +25` (AD 25) are related by `+30` in A-space.

Guard: Operator B does not imply `36 BC`, and must not be merged with Operator A.

### 1.3 Hard separation rule

Machine Guard [FILE_42 P2 NON-STRADDLING]:
The quad-window (rails) and the Mod-30 bridge (A-space) are distinct; they must not be merged into a single "30-year straddling" operator. This is the same boundary carried by Machine Guard [FILE_43 P2 NON-STRADDLING].

Terminology note: the labels Operator A and Operator B are File_42 / File_43-local labels reserved for this P2 split only. They must not be reused for unrelated ratio expansions such as `300/299` or `70/69` (File_44 guard).

## 2. The P2/P3 natural lattice (6 BC anchor)

Claim-status: arithmetic fact for all §2 derivations; structural inference for the seed / anchor significance language; convergence notes are dependency-controlled.

### 2.1 Sextuplet contains quad (embedded seed)

Active state: Key-of-23 Foundational Prime Set state by dependency; active-`Q` convention.

A prime sextuplet has the form `{p, p+4, p+6, p+10, p+12, p+16}`; the embedded quad begins at `p + 4` (the active `Q = S + 4` convention; File_36 namespace).

The first prime sextuplet (`p = 7`) is the Exceptional Sextuplet `{7, 11, 13, 17, 19, 23}` (File_32 §2.1). Its embedded quad begins at `Q = 11`. Therefore `Q = 11` (P2) is the first natural quad seed.

With P1 `5` joined to the Exceptional Sextuplet, the seven-member set `{5, 7, 11, 13, 17, 19, 23}` is the Key-of-23 Foundational Prime Set (File_37; Register 31.140A); its mod-30 completion appears in §3.3.

### 2.2 P2 base (Q = 11) → 6 BC (A-space mapping for early cluster)

Active state: early-cluster base mapping.

- P2: `Q = 11`; `Quad(11) = {11, 13, 17, 19}`.
- Base rail: `B = Q − 5 = 6`.
- Early-cluster A-space mapping rule (explicitly invoked here): `A := 1 − B`.
- `A = 1 − 6 = −5` → Civil = `6 BC`.

Lock: P2(base) ≡ `6 BC` (`A = −5`).

### 2.3 P3 alignment (Q = 101) → 96 BC via Δ = 90

- P3: `Q = 101`; `Quad(101) = {101, 103, 107, 109}`.
- `ΔQ = 101 − 11 = 90`.
- Under the same early-cluster A-space mapping: `A(P3) = A(P2) − 90 = −5 − 90 = −95` → Civil = `96 BC`.

Lock: P3(base) ≡ `96 BC` (`A = −95`).

Convergence note: `96 BC` is the established P3 base date of the active namespace (File_32; File_36 printed P3 row).

Engine equivalence (arithmetic fact): `A := 1 − B = 1 − (Q − 5) = 6 − Q`, so `Civil = 1 − A = (Q − 5) BC`; the early-cluster base mapping renders the base rail BC-side, which is the File_32 positive-polarity reading (`B⁺ = Q − 5`; Register 31.128). For P3: `101 − 5 = 96` → `96 BC`.

Machine Guard [FILE_42 EARLY-CLUSTER BASE ENGINE]:
For programmatic generation of A-space coordinates for early-cluster bases, always use the definitive formula `A := 1 − B`. The recursive differencing demonstration (`A(P2) − 90`) is an illustrative proof of geometric continuity, but the absolute formula `A = 1 − (Q − 5)` is the required computational engine to prevent propagation drift in loops.

### 2.4 P2 mirror in prime-space mapped by Operator B (A-space Mod-30 bridge) → AD 25

Active state: raw prime-space cross-polarity (Register 31.130) feeding the A-space bridge.

- Prime-space mirror of `Quad(11)` is `{−19, −17, −13, −11}`; mirror start is `−19`.
- Bridge law (prime-space): `11 − (−19) = 30`.
- Impose Operator B (A-space continuity): `A(P2_mirror) = A(P2_base) + 30 = −5 + 30 = +25` → Civil = AD 25.

Lock: P2 mirror node ≡ AD 25 (`A = +25`).

### 2.5 P3 mirror yields AD 115 (Δ = 90 propagation in A-space)

- Mirror start for P3 is `−109` (quad mirror `{−109, −107, −103, −101}`).
- A-space continuation: `A(P3_mirror) = A(P2_mirror) + 90 = 25 + 90 = 115` → Civil = AD 115.

Lock: P3 mirror node ≡ AD 115 (`A = +115`).

Engine equivalence (arithmetic fact): `A(P_mirror) = A(P2_mirror) + ΔQ = 25 + (Q − 11) = Q + 14`, the File_32 negative-polarity operator `N⁻₂` (Register 31.131). For P3: `101 + 14 = 115` → AD 115.

Convergence note: AD 115 routes through the printed File_36 P3 civil row (`101 / 96 BC / 126 BC / AD 85 / AD 115`), per the author-confirmed File_40 resolution. The File_41 `AD 115` Prophetic Expansion target is a separate restrained local label and is not opened here (Machine Guard [FILE_41 AD 115 TARGET RESTRAINT] respected by boundary).

## 3. P1 singularity (AD 1 / AD 31)

Claim-status: arithmetic fact for the gap, span, and step values; P1 displays dependency-controlled by File_32 / File_36; AD 31 status per Machine Guard [AD 31 GEOMETRY OUTPUT].

### 3.1 P1 lies outside the Exceptional Sextuplet (non-embedded pivot)

Active state: P1 Exceptional Origin state (File_32; File_36).

P1 has `Q = 5`, which precedes the first sextuplet start (`p = 7`). Therefore P1 is a singular pivot and is not constrained to behave like the embedded P2/P3 quads.

Machine Guard [FILE_42 P1 NON-INHERITANCE]:
P1 must not be treated as if it inherits P2/P3 embedded-quad behavior.

### 3.2 P1 pivot (Q = 5) → AD 1 via P2 gap

- P1: `Q = 5`; `Quad(5) = {5, 7, 11, 13}`.
- Gap to P2 start: `11 − 5 = 6`.
- Civil span check (no year 0; cross-axis `BC + AD − 1`): `6 BC → AD 1`: `6 + 1 − 1 = 6` years.

Lock: P1 ≡ AD 1 (`A = +1`).

Convergence note: this is the established P1 display (`5 − 5 = 0` displayed as AD 1 by author direction; File_32) and the registered P1 / P2 Christological six-year boundary state (File_36 §2.2A: `6 BC → AD 1 = 6`).

### 3.3 Key-of-23 completion at the singularity → AD 31 (geometry restoration)

Active state: Key-of-23 completion state (File_36 §2.2; File_37; File_33; Register 31.140A).

- Natural mirror candidate for `5` is `−23` (prime), but `5 − (−23) = 28` (breaks Mod-30 geometry).
- Key-of-23 completion (`23 → 25`): shift `−23 → −25` to restore 30 spacing: `5 − (−25) = 30`.
- Translate into A-space continuity from the P1 pivot: `A(P1) = +1`; `A_ext = 1 + 30 = 31` → Civil = AD 31.

Lock: P1 extension: natural candidate (`−23`) → AD 29 (28-step); restored geometry (`−25`) → AD 31 (30-step).

Note: `−25` is a geometry node used to restore spacing; it is not asserted as prime. This is the same completion that renders `{5, 7, 11, 13, 17, 19, 23, 25}` mod-30 complete (`5 + 25 = 30`; `7 + 23 = 30`; `11 + 19 = 30`; `13 + 17 = 30`) and the raw / expanded pair `5 + 23 = 28` → `5 + 25 = 30` (File_33).

Machine Guard [AD 31 GEOMETRY OUTPUT]:
AD 31 in this file is a prime-geometry outcome converted to a civil date: the restored Mod-30 spacing at the P1 singularity rendered from the AD member of the `1 BC / AD 1` covenant hinge (`A = +1`; `+1 + 30 = +31`), met again by the Johannine `+50` display from the `20 BC` field center (§4.2). It is not a new consequential node for the ministry or the death of Christ. The Christological ministry / Passion field remains AD 26t, AD 27n, AD 29t, AD 30n, AD 33n (and AD 35n to complete a generation), depending on an AD 30 or especially an AD 33 Friday crucifixion, under File_13 / File_31 display-state controls (Register 31.55). The phase-resolved members pair as ministry-start fields: AD 26t / AD 27n stand `3.5` / `3` years before an AD 30n crucifixion (`26t → 30n = 3.5`; `27n → 30n = 3`), in parallel to AD 29t / AD 30n standing `3.5` / `3` years before the optionally preferred AD 33n crucifixion (`29t → 33n = 3.5`; `30n → 33n = 3`). Do not export AD 31 into that field. (Author direction June 11 2026; phase-resolved members confirmed by author June 11 2026.)

Hinge-member offset note (arithmetic fact): the same `+30` structure reads from the two members of the `1 BC / AD 1` covenant hinge. From the BC member: `A(1 BC) = 0`; `0 + 30 = +30` → AD 30 (the established about-age-30 display, `1 + 30 − 1 = 30`; File_36 §2.2A.2). From the AD member: `A(AD 1) = +1`; `1 + 30 = +31` → AD 31 (this file's geometry output). AD 30 and AD 31 are hinge-member renderings of one structure, not competing values; the ministry / Passion field keeps AD 30n, and the lattice keeps AD 31 under the guard above.

P1 row compatibility note (arithmetic fact): AD 31 is the A-space reflection of the established P1 `M⁺` slot through the established pivot: `+1 − 30 = −29` → `30 BC`; `+1 + 30 = +31` → AD 31; the full window is 60 (§5). At the midnight datum (§0.3) the forward window boundary is one instant carrying two year-labels: end of AD 30 (the bounded covenant Mirror display) / start of AD 31 (this geometry output).

Machine Guard [POSITIVE-BASE BRIDGE SCOPE]:
The `+30` positive-base bridge (`A(base) + 30 = 36 − Q`) exists only where a prime-space 30-closure exists: natively at P2 (`2Q + 8 = 30` only at `Q = 11`; output AD 25, coinciding with `N⁻₂ = Q + 14`) and by Key-of-23 restoration at P1 (`5 − (−25) = 30`; output AD 31). The polarity closure for `Q > 11` is `2Q + 8` (210; 390; 1650; …), never 30. Do not apply the positive-base bridge to P3 onward; values such as `66 BC`, `156 BC`, `786 BC` are unlicensed and must not be generated.

## 4. The Johannine Temple lock (Herod → Christ)

### 4.1 46-year build datum (schematic anchor)

Active state: Herodian Temple field state by File_33 dependency; Johannine Temple 46/50 state by File_13 dependency.
Claim-status: arithmetic fact for the spans; historical source-control field by File_33 for `21/20/19 BC` and AD `26/27/28`; dependency-controlled Johannine 46/50 state by File_13; structural inference for the §4.2 match to the P1 extension target.

- Anchor: Herod's temple foundation = `20 BC` (schematic anchor; center / average of the File_33 `21/20/19 BC` Herodian Temple start field).
- John 2:20 gives "46 years."
- Civil arithmetic (no year 0; cross-axis `BC + AD − 1`): `20 BC + 46 = AD 27` because `20 + 27 − 1 = 46`.

Lock: AD 27 is the 46-year temple-build node.

Convergence note: `20 BC → AD 27 = 46` is the registered center display of the File_33 field, whose John 2 ministry field is AD `26/27/28` (File_36 §2.2A.3).

### 4.2 50-year perfection by the 25/23 operator

- John 8:57 gives "not yet 50."
- Apply priestly expansion: `46 × (25/23) = 50`.
- Therefore: `20 BC + 50 = AD 31` (since `20 + 31 − 1 = 50`).

Lock: Johannine 50-year node matches the P1 extension target (AD 31).

State note: this AD 31 is the same geometry-output value as §3.3 and stands under Machine Guard [AD 31 GEOMETRY OUTPUT]: it is not a ministry or Passion node. The File_33 P47 grid target reads the same `+50` from the field's leading edge: `21 BC + 50 = AD 30` (`21 + 30 − 1 = 50`). The two displays are field-member renderings of one `+50` structure, not competing chronologies.

## 5. The Terah mirror (source of +60)

Active state: covenant hinge by File_36 §2.2A.1 / File_13; Terah +60 macro-mirror display state; P1 midnight-datum phase state (§0.3).

- Christological hinge: `1 BC / AD 1` — the Covenant Crossover Zero Point: T₀ = midnight, December 31, 1 BC → January 1, AD 1 (File_00).
- Forward harmonic node: AD 31 (geometry output; §3.3).
- Mirror counterpart: `30 BC` (the established P1 `M⁺` slot; File_36 §2.2A).
- Civil span (no year 0; cross-axis): `30 BC → AD 31`: `30 + 31 − 1 = 60`.

Lock: Terah +60 macro-mirror: `30 BC ↔ AD 31` is 60 years.

Midnight-datum restatement (arithmetic fact): at T₀ the window is exact. Backward 30 years: midnight December 31, 31 BC / January 1, 30 BC — the opening boundary of 30 BC. Forward 30 years: midnight December 31, AD 30 / January 1, AD 31 — one instant carrying two year-labels: end of AD 30 (the bounded P1 covenant numeric-year Mirror display; File_36) and start of AD 31 (the geometry output; §3.3). The window spans exactly 60 years and contains exactly the 60 year-cells `30 BC … AD 30`. The covenant-Mirror display `30 BC ↔ AD 30` is the same window: start-to-start cell reading `30 + 30 − 1 = 59`; boundary-to-boundary span 60.

Claim-status: arithmetic fact for `30 + 31 − 1 = 60` and the window statement. The `+60` Terah chronological variant itself is established repository chronology (Register 31.83 `70/130 state-dependent` begetting field; Capsule MT `+60` states) and a widely held reading of the Terah begetting data (reception-history note); it is not in question here. The structural inference is only the specific identification of this macro-mirror window as the source of that established `+60`. The identification is the file's preserved thesis.

State note: the `+60` here is a named macro-Mirror display, not an ordinary prime rail (Register 31.135 boundary).

Audit note: the sourcehood identification stands on the macro-mirror geometry rather than on Terah chronology written out locally; the established `+60 Terah` variant field remains controlled by Register 31.83 / File_18. If the author wants the local Terah derivation written out here, that is an addendum task, not a correction.

## 5A. The tri-scale 90 + 30 + 90 structure (midnight datum)

Active state: tri-scale 90+30+90 state; P1 midnight-datum phase state.
Claim-status: arithmetic fact for every chain sum and closure; dependencies as cited; the cross-scale identification (units ↔ years ↔ days) is a structural inference licensed by the registered day-year display states (File_13 day-year displays; precessional-day component-display convention).

One pattern — `90 + 30 + 90 = 210` with a central 30-unit polarity bridge — instantiates at three scales.

### 5A.1 Prime-space scale (units)

Sextuplet true centers (`S + 8`): S1 (`p = 7`) center `15`; S2 (`p = 97`) center `105`. Chain: `−105 →90→ −15 →30→ +15 →90→ +105`; total `210`. The central 30 (`−15 … +15`) is the polarity bridge containing the origin and P1 (`Q = 5`).

Dependency note: File_38 90 + 30 + 90 true-center lattice; File_32 Modulo 210 corridor. True centers (`S + 8`) and active quads (`Q = S + 4`) remain separate namespaces; the [SEXTUPLET TRUE CENTER / ACTIVE Q SEPARATION] boundary is respected.

### 5A.2 Year scale (P2/P3 row; Nisan phase)

`96 BC →90→ 6 BC →30→ AD 25 →90→ AD 115`; closure `96 + 115 − 1 = 210` — the registered File_40 Day 1 rails-separation. The central 30 is the P2 A-space bridge (`6 + 25 − 1 = 30`).

### 5A.3 Day scale (P1; midnight phase)

The plain Tishri → Nisan straddle is 6 schematic months: `Oct 1 →90→ Jan 1 →90→ Apr 1` = 180 days, centered exactly on the datum (File_09 Oct 1 / Jan 1 / Apr 1 mapping). The leap-extended (intercalated) straddle is 7 months = `180 + 30 = 210` days: `Sep 1 →90→ Dec 1 →30→ Jan 1 →90→ Apr 1`. The central month — the 4th of 7 — is December of 1 BC, the Birth month (December 25 inside it; File_00's 8-day Birth → Naming gap), closing exactly at T₀.

Qualification (locked): the 210-day chain requires the intercalary month. Bare half-year = 180 days; the 210 form is the leap-half-year (`7/12` of the schematic year). The actual Julian check: January 1 → April 1 = 90 days exactly in a common year.

### 5A.4 Mirror inversion

The 210-day chain splits about T₀ as `(90 + 30) | 90 = 120 | 90`; reflection through T₀ gives `90 | 120`. Therefore `(90 + 30) + M + 90` inverts to `90 + M + (30 + 90)`: the central month flips from December (1 BC side) to January (AD 1 side). This is the File_09 suffix-inversion rule at month resolution; the year-scale trigger is the Mirror activation `30 BC → AD 30`.

### 5A.5 The P1 row at midnight phase

Rule (locked): at midnight phase a year-label denotes its opening boundary; Mirror activation negates the offset from T₀; boundary labels invert numeral order across the Mirror.

Coordinate relation (locked): for any year-label, opening-boundary offset = `A − 1` (e.g., `30 BC`: `A = −29`, opening boundary `−30`; `AD 31`: `A = +31`, opening boundary `+30`). Boundary offsets are instants; A-space cell coordinates remain the computational engine (§0.3).

| P1 coordinate | Offset from T₀ | Boundary |
|---|---:|---|
| AD 1 | 0 | `1 BC / AD 1` = T₀ |
| 30 BC (activated) | −30 → +30 | `AD 30/31` |
| 12 BC (activated) | −12 → +12 | `AD 12/13` |
| AD 19 (native) | +18 | `AD 18/19` |

Convention note: AD 19 is listed native; its activated form (the File_36 display AD 19 → `19 BC`) reads `19/18 BC` — numeral order inverted, confirming the rule.

Phase-correction note (arithmetic fact): the P1 phase shift from Nisan (April 1) to the midnight datum (January 1) is 3 months = 90 days = one arm of the structure.

## 5B. The sextuplet-onset window (±2)

Active state: sextuplet-onset ±2 window state.
Claim-status: arithmetic fact for the offsets and boundaries; typological note for the Herod reading; the historical layer is state-separated.

S1 begins at `7` = P1's `5` + 2. Under the base mapping that sends `11 → 6 BC` and `101 → 96 BC`, the onset `7` maps to the boundary `3/2 BC` (T₀ − 2); Mirror-activated, `AD 2/3` (T₀ + 2). The pair obeys numeral inversion (`AD 2/3 ↔ 3/2 BC`). The full run `{5, 7, 11, 13, 17, 19, 23 → 25}` (Key-of-23 Foundational Prime Set with completion; §2.1; §3.3) keeps the mod-30 view across polarity; the ±2 onset window is the S1-versus-P1 offset rendered at the datum.

Typological note (Herod window): Matthew 2:16's "two years old and under, according to the time … of the wise men" is bidirectionally ambiguous; a datum-anchored Mirror produces exactly such a ±2 window, readable forward or backward — the structural counterpart of the textual ambiguity.

State note (separation; hard): this is the typological datum-window layer. The historical Herod chronology remains anchored at the registered `6 BC` birth anchor; the `AD 2/3` boundary is not a birth-date claim and must not be exported as one.

## 5C. The nativity structure (day-scale rendering; reading duality; six-month and 30-day locks)

Active state: nativity day-scale rendering state; 6 BC reading-duality state; P1 midnight-datum phase state.
Claim-status: arithmetic fact for all spans and timestamps within the schematic model (30-day months; quarter-day law); reception-history note for the traditional dates; structural inference / typological note for the correspondences; the registered `6 BC` birth-anchor label is controlling.

### 5C.1 Day-scale rendering of the birth pair

At day = year scaling, `0.25 year` (one quarter; Tishri ≈ October 1 at −0.25 from the January 1 mean, Nisan ≈ April 1 at +0.25; File_09) = `0.25 day = 6 hours`. Therefore:

- symbolic `7t BC` = −6.25 years → 6.25 days before T₀ = **December 25, 6 PM** (1 BC);
- symbolic `6n BC` = −5.75 years → 5.75 days before T₀ = **December 26, 6 AM** (1 BC);
- mean −6.00 = the P1–P2 gap; exact member-spans `6.25` / `5.75`, mean `6`.

Reception-history note: December 25, 1 BC is the tradition-anchored birth date on which the modern datum is based; the structure makes no claim about the true birth date. The Tishri-secondary member renders to the traditional nativity evening; the 8th day (inclusive) from December 25 is January 1, AD 1 — the Naming at the Zero Point (File_00).

### 5C.2 Reading duality at 6 BC

Machine Guard [6 BC READING DUALITY]:
The registered and controlling label for `6 BC` is the P2 birth anchor (Capsule §1.18; File_36; §2.2 above). A conception-reading exists as a File_42 typological layer and does not replace the registered label. Under it: `6n BC + 270 days` (`9 × 30`) lands at the close of 6 BC, exactly 5 years (`6n → 1n` same-side: `6 − 1 = 5`) before the tradition-anchored chain at `1n BC` (Annunciation; March 25 + 9 calendar months = December 25 exact; schematic April 1 + 270 = January 1, the ~6-day slack absorbed by the 8-day Birth → Naming window). Whether `6n BC` denotes birth or conception is left open — the ambiguity may be by design; only the December 25, 1 BC tradition is certain, as tradition. Do not export the conception-reading as a replacement of the birth-anchor label. (Author direction, June 12 2026.)

### 5C.3 John the Baptist from the same pair

`7t BC → 6n BC` = 6 months — the Lukan "sixth month" (Luke 1:26). Under the conception-reading, `7t BC + 270 days` = July 1, 6 BC, against the traditional Nativity of John (June 24), six months before December 25 — the same ~6-day schematic slack, the same window logic. One pair, two nativity traditions. Typological note.

### 5C.4 The 30-day lock (Levites)

Numbers 1:1; 3:15; 4:3: the census on the first day of the second month of the second year — Iyar 1, 1445 BC — counted Levites "a month old and upward"; Iyar 1 is the first day after 30 completed days of the year, the 390th schematic day from the Nisan 1, 1446 BC datum (`360 + 30 = 390`). Priestly service began at 30 years: the 30-days ↔ 30-years day-year lock, joining the leap month (30 days; §5A.3; §5D) to the about-age-30 ministry display (AD 30; File_36 §2.2A.2). Structural inference / typological note; arithmetic exact.

### 5C.5 The Mirror inversion of conception and birth (John 1:15, 30)

Claim-status: arithmetic fact for the reflection mechanics; the suffix inversion is the registered File_09 rule; typological / theological note for the Johannine reading.

Reflection through T₀ negates offsets and swaps the t/n phases (the File_09 suffix-inversion rule): the BC pair `7t/6n BC` (−6.25 / −5.75) images to `AD 6t/7n` (+5.75 / +6.25). The order inverts with it: the image of Christ's member (`6n BC → AD 6t`, +5.75) comes first in Mirror chronology; the image of John's member (`7t BC → AD 7n`, +6.25) comes after. In forward time Christ's member follows John's; in the Mirror it precedes.

The same reflection reverses every directed arc: the conception → birth arc (`270 = 9 × 30` days; alternate `280 = 40 × 7`) runs birth-first in the Mirror — birth-image January 1, AD 6 (the AD 5/6 midnight boundary, mirroring the close-of-6 BC boundary) preceding conception-image October 1, AD 6 (`6t`). The two readings of Machine Guard [6 BC READING DUALITY] are therefore exchanged across the Mirror: whichever reading holds on the BC side, the Mirror presents the other ordering. The duality is not merely left open; the structure itself exchanges the readings.

Typological / theological note: John 1:15, 30 — "He who comes after me … was before me" — carries the chronological sense (John conceived and born first, ministering first), the rank sense, and the pre-existence sense; the Mirror renders the statement additionally true as an arithmetic identity of the reflection. Reception-history note; no claim beyond the structure is made.

## 5D. The polarity-gap ladder and the 1650 spine

Active state: polarity-gap ladder state; 1650-spine intersection state by File_51a dependency.
Claim-status: arithmetic fact for every gap, increment, and intersection; the `1260` identification is the registered prophetic operator (File_13 / File_16 / File_17; Revelation 12 Messianic template; `1260 + 1260 → 1 BC` cumulative bridge); the 1650 backbone is File_51a §16.10 (Creation-Week module); typological note for the synthesis.

The polarity closure (positive base to `N⁻₂` mirror, cross-axis) is `2Q + 8` (Machine Guard [POSITIVE-BASE BRIDGE SCOPE], §3.3). The ladder:

| Step | Q | Gap `2Q + 8` | Increment | = 2 × ΔQ |
|---|---:|---:|---:|---|
| P2 | 11 | 30 | — | — |
| P3 | 101 | 210 | +180 | 2 × 90 |
| P4 | 191 | 390 | +180 | 2 × 90 |
| P5 | 821 | 1650 | +1260 | 2 × 630 |

Readings (arithmetic facts): `390 = 360 + 30 = 13 × 30` — the embolismic year (a year with a leap month); `180` = the plain half-year straddle; `1260` = the Revelation 12 Messianic template. The ladder reads: bridge-month (`30`) → leap-half-year added twice (`+180`, `+180`) → Messianic `1260` → `1650`.

1650-spine intersections (File_51a §16.10; exact). With the midnight-inverted counterparts `806 / 836` of the P5 AD values (AD 805 / AD 835; BC/AD counterpart display-label state) alongside the rails `816 / 846`:

- `806 + 1650 = 2456` — the Flood (Gear 1; File_51a cumulative `1650`);
- `816 / 846 / 806 / 836 + 3300 = 4116 / 4146 / 4106 / 4136` — the creation field;
- `806 / 836 + 13200 = 14006 / 14036` — deep-time anchors;
- `14006 − 4106 = 9900 = 6 × 1650` — the File_51a 9900-year bridge.

Synthesis (typological note): the ingredients for expansion along the Chronology of Christ are present in the P1 row and the ladder — the age-12 display (`AD 12/13`), the about-age-30 ministry display (AD 30), and the ±2 window — built upon the initial leap month of 30 days corresponding to the 30 years at which priestly service began (§5C.4): the ministry of the true priest.

Dependency note: registration of the File_42 ↔ File_51a `1650` intersection in File_51a is a recommended cross-file update, to be executed in a bounded File_51a chat after this file finalizes (Procedures §17).

## 5E. The 2070 seed-span and the P8 correspondence

Active state: 2070 seed-span state; P8 correspondence state; 40-year Mirror-gap law state.
Claim-status: arithmetic fact for every identity; the P8 row values converge with the printed active namespace (File_32; File_33; File_35); structural inference for the cross-scale correspondences; typological note for the Noah → Isaac reading.

### 5E.1 The 2070-day anchor gap and its Key-of-23 expansions

On the 360-day grid, the gap from the `6n BC` anchor to the close of December 1 BC (T₀) is `5 × 360 + 270 = 2070` days — exactly `5.75 × 360` (the registered member-span; §5C.1). Expansions (exact; `2070 = 2 × 3² × 5 × 23 = 69 × 30 = 23 × 90`):

- `2070 × 70/69 = 2100`: adds 30 days — the intercalary month (§5A.3).
- `2070 × 25/23 = 2250 = 6.25 × 360`: adds 180 days — anchored at the datum, the start pushes back from `6n BC` to `7t BC`, John's member: Christ's expanded span occupies John's position (§5C.5).
- The two increments compose the ladder step: `30 + 180 = 210` — the P2 gap plus the half-year equals the P3 gap (§5D).

Architectural note (structural inference): the 2070 base is divisible without residue under both Key-of-23-family operators (`23` and `69 = 3 × 23` both divide it); the anchor gap is thereby the seed that expands properly under both.

### 5E.2 The July 1 mirror

Pushed forward from T₀, the 180 lands at July 1, AD 1 — the Mirror image of July 1, 1 BC, the tradition-anchored birth of John (June 24, rounded to the 360-grid month), six months before December 25. Layer consistency: the conception-reading birth of John (July 1, 6 BC; §5C.3) plus the same 5-year displacement of §5C.2 equals July 1, 1 BC. The 30 pushed forward lands at February 1, AD 1 — the close of the inverted central month (§5A.4).

### 5E.3 The P8 correspondence

P8: `Q = 2081` — the eighth quad start (5, 11, 101, 191, 821, 1481, 1871, 2081); `Quad(2081) = {2081, 2083, 2087, 2089}`.

| P# | Q | Positive `Q − 5` | Positive `Q + 25` | Negative `Q − 16` | Negative `Q + 14` |
|---|---:|---|---|---|---|
| P8 | 2081 | 2076 BC | 2106 BC | AD 2065 | AD 2095 |

`ΔQ(P2 → P8) = 2081 − 11 = 2070` — the seed-span of §5E.1 in prime units: P2 to P8 contain, in units, the gap between the `6 BC` and `1 BC / AD 1` anchors in days. Convergence note: the P8 row is printed in the active namespace (File_32; File_33; File_35).

### 5E.4 Noah → Isaac: the 40-year Mirror gap

- `2106 BC` = the P8 `M⁺` rail = Gear 1 death of Noah: Flood `2456 BC` (Gear 1) − 350 post-Flood years (Genesis 9:28) = `2106 BC`.
- The midnight counterpart of the P8 `N⁻₁` value AD 2065 is `2066 BC` = the birth of Isaac (`2166 − 100`; the registered standard Abrahamic row; File_00 / File_07).
- Gap: `2106 − 2066 = 40` years.

40-year Mirror-gap law (arithmetic fact): for every quad with `N⁻₁` on the AD side (P3 onward), `M⁺ − counterpart(N⁻₁) = (Q + 25) − (Q − 15) = 40` — verified at P3 (`126 − 86`), P4 (`216 − 176`), P5 (`846 − 806`), P8 (`2106 − 2066`). P1 and P2 lie outside the law's regime (their `N⁻₁` is BC-side).

Typological note: at P8 the constant 40 spans the death of Noah — the close of the old order — and the birth of Isaac, the promised son — the opening of the new: the transition number generated by the prime Mirror itself. Structural identification; the underlying years are registered chronology.

## 5F. The Revelation 12 1260 between the birth anchors (P5 → P6 → P8)

Active state: Revelation 12 1260 P5–P8 span state; P6 Joshua mid-split state by File_03 dependency.
Claim-status: arithmetic fact for every gap and decomposition; the `1260` is the registered prophetic operator (File_13 / File_16 / File_17); Joshua nodes by File_03 dependency; structural inference for the symbolic-birth correspondence; typological / theological note for the Revelation 12 reading.

### 5F.1 The direct 1260

`ΔQ(P5 → P8) = 2081 − 821 = 1260` — the Revelation 12 operator as a direct Q-gap (distinct from the §5D gap-increment `+1260`, which is `2 × ΔQ(P4 → P5) = 2 × 630`). Pairwise, exactly: `2106 − 1260 = 846` (rail) and `2066 − 1260 = 806` (counterpart): the P8 pair (Noah's death / Isaac's birth; §5E.4) descends to the P5 pair (§5D) by 1260 on both lines.

Symbolic-birth note (structural inference): by §5E.3 (`ΔQ(P2 → P8) = 2070` = the `6n BC → T₀` day-gap), P8 stands to the P2 birth anchor as the datum stands to the `6n BC` anchor; the P8 pair thereby functions as a unit-scale image of the birth at the datum, viewed from `6n BC` looking forward to the Mirror main anchor.

### 5F.2 The Exodus / Conquest insertion

The wilderness pair `1446–1406 BC` (40 years; Cross-Mirror AD counterparts registered, File_20) sits between the pairs and decomposes the 1260 identically on both lines:

| Line | P8 member | step | wilderness member | step | P5 member |
|---|---|---:|---|---:|---|
| Rail | 2106 BC | −660 | 1446 BC | −600 | 846 BC |
| Counterpart | 2066 BC | −660 | 1406 BC | −600 | 806 BC |

`660 + 600 = 1260`. The 40-year law gap at P8 and P5 (§5E.4) aligns with the 40 wilderness years (`1446 − 1406 = 40`); Moses stands 600 years before the P5 pair.

### 5F.3 The P6 split (Joshua)

P6: `Q = 1481`; `B⁺ = 1476 BC` — the registered derived Joshua birth node (`1406 + 70 = 1476`; File_03 Joshua / Conquest state). `ΔQ(P5 → P6) = 660`; `ΔQ(P6 → P8) = 600`. P6 divides the 1260 as `660 + 600` — 30 off the exact half (`630`), the bridge-month constant once more — placing Joshua's birth and the Exodus / Conquest field effectively at the center of the span.

Joshua chain (arithmetic fact; File_03 convergence): Exodus 1446 at age 30; Conquest 1406 at age 70; death `1476 − 110 = 1366 BC` (Joshua 24:29), 40 years after the Conquest.

### 5F.4 Typological reading

Revelation 12: the woman travailing in birth, nourished `1260` days in the wilderness, pursued by the flood from the dragon's mouth (Revelation 12:6, 15) — read against the flood of Noah (the P8 head of the span) and the Jordan crossing (the Conquest member); the Revelation 11–12 templates resonate on the Exodus / Conquest field. The 1260 of Revelation 12 thus fits between the two birth-anchor poles of the span: the P8 symbolic-birth pair and the P5 pair beneath it. Typological / theological note; the gaps themselves are arithmetic facts.

Audit note (author-message corrections under Procedures §5.1): the source direction wrote `1866 BC` for Isaac and a "40-day" gap at `846/806 BC`; both are arithmetic-forced to `2066 BC` and 40 years, applied under assumed authorial affirmation and recorded here.

### 5F.5 The conception-reading shift (brief)

Claim-status: arithmetic fact for the rows; structural inference for carrying the §5F.1 symbolic-birth correspondence to the shifted pair; typological / theological note for the readings.

Revelation 12 commences the `1260` after the birth (Revelation 12:5–6: the child is born and caught up; the woman is then nourished `1260` days). Under the registered birth-reading, the span runs from the P8 pair directly (§5F.1). Under the §5C.2 conception-reading (typological layer; Machine Guard [6 BC READING DUALITY] — the birth-anchor label is not replaced), carried to the symbolic scale by the §5F.1 correspondence, the P8 pair stands as conception; the nine-month arc `270 = 9 × 30` at year-scale gives the shifted birth pair, and the `1260` runs from there:

- `2106 − 270 = 1836`; `1836 − 1260 = 576`
- `2066 − 270 = 1796`; `1796 − 1260 = 536`

The §5E.4 40-year constant is invariant under both uniform shifts (`1836 − 1796 = 40`; `576 − 536 = 40`), and the landing window `576–536 BC` nests as the final 40 of the registered 70-year captivity generation (`606 − 536 = 70`, File_25; `606 − 576 = 30`; `30 + 40 = 70`). The emphasized line is the counterpart: Isaac's birth `2066 BC` (§5E.4) less `270` less `1260` = `536 BC`, the registered restoration / Daniel revelation node (File_25). Ezekiel's temple vision (Ezekiel 40:1; `573 BC`, Nisan 10) falls within the window. Both readings of the `6 BC` duality therefore commence a working Revelation 12 `1260` at the symbolic scale. Typological / theological note; the rows are arithmetic facts.

Possible intersecting node (structural inference; typological note): Ezekiel 4's `390 + 40 = 430` (Ezekiel 4:5–6), commenced at the temple-construction start `966 BC` (1 Kings 6:1; the registered Temple node, File_00 `967/966 BC`), gives `966 − 390 = 576` and `576 − 40 = 536` (`966 − 430 = 536`): Ezekiel 4's final 40 — Judah's portion — coincides with the landing window `576–536 BC`, the last 40 of the exile, suggesting the window as part of the exile schematic in a general sense. Ezekiel 4's `390 + 40` functions here as a repeating template, like Revelation 12's `1260` — the figure recurs with similar meaning rather than marking a single fulfillment. Registered-node instance: the Egypt sojourn runs `1876 − 390 = 1486` (Moses flees to Midian, age 40; registered File_07 node) and `1486 − 40 = 1446` (Exodus; `390 + 40 = 430`, Exodus 12:40), with the further registered `430 + 430 = 860` carrying `1446 − 860 = 586` (File_00). The `966 BC` commencement is therefore one template instance, not the template's sole anchor — and `966 BC` is the registered Northern Kingdom / Kings of Israel schematic route head (File_00 Divided Kingdom route triad), so Israel's `390` (Ezekiel 4:5, the house of Israel) runs from the registered start of the Northern Kingdom route. Ezekiel 4's `390` at `1836 → 1446 BC` (File_20) is another template instance under a distinct application; shared operator, not shared node.

Label discipline: `1836 BC` here is the shifted symbolic-birth rail only, not File_20's Isaac's-sacrifice node; `1796 BC` here is the shifted symbolic-birth counterpart only, not the File_22 / File_18 Levi-death / Kohath-birth node; `576 BC` and `573 BC` are repository-new — `576 BC` carried by this construction and the possible Ezekiel 4 intersection; `573 BC` by Ezekiel 40:1. Shared year-label does not create identity.

## 6. The Exodus squared (1472 → 1600)

Active state: Exodus 1472 → 1600 state by File_05 dependency.
Claim-status: arithmetic fact for the spans and the `25/23` expansion; the Exodus ↔ ministry deliverance pairing is a typological / theological reading carried by File_05.

### 6.1 Solar interval

- Exodus anchor: `1446 BC`.
- Temple 46-year node: AD 27.
- Civil arithmetic (cross-axis): `1446 BC → AD 27`: `1446 + 27 − 1 = 1472`.

Lock: Exodus → AD 27 = 1472 years.

### 6.2 Priestly expansion to the wilderness square

- `1472 = 23 × 64`.
- Apply `25/23`: `1472 × (25/23) = 64 × 25 = 1600 = 40²`.

Lock: 1472 expands to 1600 under `25/23`.

Convergence note: `1446 + 27 − 1 = 1472` and `1472 × 25/23 = 1600` are the established File_05 primary state; File_13 carries the companion factor display `1600 = 4 × 400`.

## 7. Genealogical MirrorVolume (8050 → 8750) and Seal700

Active state: Genealogical MirrorVolume state and Seal700 state — active control is File_43 (Register 31.57b–31.57e); this section preserves the geometry-first source-history statement.
Claim-status: arithmetic fact for all values; span-provenance and state definitions controlled by File_43.

### 7.1 Luke and Matthew spans (no ambiguous labels)

- `LukeIntervals = 5250 = 75 × 70` (intervals).
- `LukeSpan = 5320 = 76 × 70` (names span; not used in MirrorVolume).
- `MattSpan_BirthHinge = 2800 = 40 × 70` (Abraham → `6 BC` bracket).
- `MattSpan_Carrier = 2870 = 41 × 70` (Abraham → AD 65 bracket).

Guard: Bare "Matthew span" is disallowed; any reference must specify MattSpan_BirthHinge or MattSpan_Carrier (Register 31.57c).

### 7.2 MirrorVolume definition (hard; span provenance)

MirrorVolume uses `LukeIntervals = 5250` and `MattSpan_BirthHinge = 2800` only:

- `8050 := 5250 + 2800`.

Machine Guard [FILE_42 MATTSPAN PROVENANCE]:
`MattSpan_Carrier = 2870` MUST NOT be substituted into `8050`, `8750`, or Seal700. This is the same span-provenance boundary carried by Machine Guard [FILE_43 SPAN SPLIT] and Register 31.57d.

### 7.3 Key-of-23 expansion (8050 → 8750)

- `8050 / 23 = 350`.
- `8050 × (25/23) = 350 × 25 = 8750`.

Lock: 8050 expands to 8750 under `25/23` (exact integer; no residue).
Lock: `8750 / 70 = 125` generations `= 5³`.

### 7.4 Seal700 definition (derived difference)

- `8750 − 8050 = 700 = 10 × 70`.

Lock: Seal700 = 700 years is generated (not imposed).

## 8. Summary table (machine locks)

All rows are arithmetic-fact locks with state labels as shown; the P1 extension row carries the AD 31 geometry-output status (Machine Guard [AD 31 GEOMETRY OUTPUT]).

| Node | Domain | Definition | A-space | Civil | Function |
|---|---|---|---:|---|---|
| P2 base | A-space | `A = 1 − (Q − 5)` with `Q = 11` | −5 | 6 BC | Birth anchor |
| P2 rails | rails-space | `(B, M) = (6, 36)`; `M − B = 30` | — | — | Quad-window only (civil reading `6 BC / 36 BC` by File_32 interface) |
| P2 mirror | A-space bridge | `A = −5 + 30` | +25 | AD 25 | Mod-30 bridge only |
| P3 base | A-space | `A(P2) − 90` | −95 | 96 BC | Δ = 90 propagation |
| P3 mirror | A-space | `25 + 90` | +115 | AD 115 | Δ = 90 propagation |
| P1 pivot | A-space | `A = +1` | +1 | AD 1 | Pivot outside sextuplet |
| P1 extension | geometry-restored | `A = 1 + 30` | +31 | AD 31 | Restored Mod-30 at pivot; geometry output, non-ministry |
| MirrorVolume | genealogy | `8050 := 5250 + 2800` | — | — | LukeIntervals + MattSpan_BirthHinge only |
| Cube lock | operator | `8050 × 25/23 = 8750` | — | — | `125 × 70 = 5³ × 70` |
| Seal700 | derived | `8750 − 8050` | — | — | `700 = 10 × 70` |
| Tri-scale 210 | structure | `90 + 30 + 90 = 210` at units / years / days | — | — | §5A; File_38 / File_40 / File_09 dependencies |
| Onset window | datum window | S1 onset `7 = 5 + 2` | ±2 | `3/2 BC ↔ AD 2/3` | §5B typological window |
| Nativity rendering | day-scale | `7t / 6n` at ±6 h about Dec 26, 00:00 | — | Dec 25, 6 PM / Dec 26, 6 AM | §5C.1; quarter-day law |
| Gap ladder | polarity closure | `2Q + 8` | — | 30; 210; 390; 1650 | §5D; increments `2 × ΔQ` |
| 1650 spine | dependency | P5 gap ∩ File_51a module | — | 2456 BC; 4106–4146 BC; 14006 / 14036 BC | §5D; File_51a §16.10 |
| Shifted 1260 | typological layer | `{2106, 2066} − 270 − 1260` | — | 576 BC; 536 BC | §5F.5; landing window = final 40 of the 70-year captivity; possible Ezekiel 4 `390 + 40` from `966 BC` |

## Revision and archive note

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

Detailed revision history is preserved in the `Repository_Change_Archive`.

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

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