File: File_45
Title: Superstructure of the 14000 / 1400 Fractal
Source title: `SUPERSTRUCTURE_14000_1400.md`
Entity: Superstructure of the 14000 / 1400 Fractal (Danielic Harmonics)
Classification: Master Architecture / Deterministic Statistical Proof (Exact Phase Sweep)
UUID: SUPERSTRUCTURE_14000_1400_ENOCH_PIVOT_EXACT
Status: Final; post-final pressure tested; source status `DEFINED` retained
Pressure-test status: Current; publication-clean verification complete; June 9 2026 focused 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.
Source status: DEFINED (v10.1-compatible; no 434-year lock language)
Primary domain: Statistical; NT Genealogical; Danielic; Macro-Harmonic; Comparative; Theological
Traditions: NT / Luke; NT / Matthew; Danielic / prophetic by pattern-template; Exodus / Conquest by target-frame; cumulative MT by target-frame dependency; prime / A-space terminology by dependency
Canonical source: Markdown
Primary anchors: 14006 BC; 1476 BC; 1446 BC; 1406 BC; 1366 BC; 4836 BC; 5326 BC; 5256 BC; 4906 BC; 4486 BC; 4416 BC; 4206 BC; 3856 BC; 3786 BC; 3436 BC; 3366 BC; 2946 BC; 2876 BC; 2806 BC; 1896 BC; 916 BC; 846 BC; 6 BC; AD 30; AD 65; AD 135
Related files: `File_42`; `File_43`; `File_44`; `File_32`; `File_33`; `File_15`; `File_06`; `File_22`; `File_54`; Restart Capsule v11.15; State Vocabulary Register v1.17; 490d Repository Style Guide v2.5; Project Procedures v3.2
Major operators: A-space conversion; no-year-0 civil coordinate mapping; fixed starred-node manifest; Boundary / `+30` / `+40` point-cloud expansion; node weight `w`; distance `d = |t − p|`; cycle hit `d ≡ 0 mod c`; distance-0 perfect-hit rule; cycle family `C = {490, 700, 1400, 4900, 7000}`; exact phase sweep over `49000`; exact phase-space frequency; rarity `1 / p`; Danielic x10 pattern-template `490 + 4340 + 35 + 35 = 4900`; civil cross-axis span `BC + AD − 1` where opened
Major modal states: exact-sweep statistical proof state; A-space phase-sweep state; fixed node-manifest state; target-frame state; target-node coincidence state; point-cloud expansion state; weighted-node state; phase-space frequency state; Joshua packet state; Enoch pivot state; Jared / 2nd Cainan Danielic front-packet state; Christ-generation bisection state; Daniel 9 pattern-template state; non-lock `+460` motif state; File_43 genealogy-node dependency state; File_44 scaling-law dependency state; File_42 700-Year Seal / geometry-first support state; File_32 / File_33 Prime–Civil / Polarity Namespace state
Major claim-status labels: verified arithmetic fact; verified score output; corrected exact phase-space frequency; arithmetic correction by recomputation; structural inference; Danielic pattern-template; display motif; theological note; dependency-controlled; Machine Guard; audit note
Revision basis: 490d Repository Style Guide v2.5; Restart Capsule v11.15; State Vocabulary Register v1.17; Project Procedures v3.2; author-supplied `FILE_45: SUPERSTRUCTURE_14000_1400.md`; File_43 Final Harmonized / post-final pressure-tested source by dependency; File_44 Final Post-Final Pressure Tested scaling-law controls by dependency; File_42 geometry-first support; File_32 / File_33 Prime–Civil / Polarity Namespace controls; prior finalized File_45 source; Repository_Change_Archive (non-controlling history).
Current refresh note: Public-clean trust-status equalization aligns active control pointers to 490d Repository Style Guide v2.5, Restart Capsule v11.15, State_Vocabulary_Register v1.17, and Project Procedures v3.2. Register Agreement status is recorded in the header; no arithmetic, anchors, modal states, node-classes, operators, sign conventions, slash-pairs, ranges, envelopes, Mirror protocols, Machine Guards, claim-status labels, theological claims, or dependency boundaries are changed. Detailed pass logs, pressure-test records where applicable, pointer-refresh history, and replacement-workflow notes are preserved in Repository_Change_Archive.

# File_45 — Superstructure of the 14000 / 1400 Fractal

## 0. File-function

`File_45` defines an exact-sweep statistical test for the `14000 / 1400` superstructure.

Active state:
exact-sweep statistical proof state; A-space phase-sweep state; fixed node-manifest state; File_43 genealogy-node dependency state; File_44 scaling-law dependency state; File_42 700-Year Seal / geometry-first support state; File_32 / File_33 Prime–Civil / Polarity Namespace state.

This file tests a fixed target-frame against a fixed node point cloud extracted from the corrected Matthew / Luke 70-year genealogy lattice.

This file does not claim that Matthew / Luke explicitly mention the Exodus / Conquest. It does not claim that Daniel 9 forces a single historical chronology.

This file does claim the narrower testable statement:

```markdown
Given a fixed node set extracted from the corrected 70-year genealogy table (Matthew + Luke) and a fixed family of Danielic cycle lengths, the target-frame `{14006 BC, 1476 BC, 1446 BC, 1406 BC, 1366 BC, 4836 BC}` is an unusually high-scoring interference peak relative to the same node set under all possible phase shifts in the 49000-year cycle space.
```

All probabilities in this file are phase-space frequencies, not metaphysical certainties.

Publication-cleanup note:
This public-clean source preserves the Final and focused post-final pressure-tested status in the header. Detailed pass ledgers, patch-set cleanup records, pressure-test summaries, cross-file recommendation tables, and Revision Log material are archived rather than repeated in the public body.

Argument-control rule:
The exact-sweep statistics carry the file's base layer. Structural meaning, Danielic segmentation, and theological framing explain why the tested architecture matters, but they do not change the node set, target set, cycle family, scores, or rarity outputs.

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

## 0.1 Related Repository Files

| File | Function for `File_45` |
|---|---|
| `File_42` | Source-named dependency for the `700-Year Seal` and geometry-first support. Where prime / P2 / A-space language appears, terminology is harmonized through File_32 / File_33. |
| `File_43` | Primary genealogy-node source: Matthew / Luke 70-year lattice, LukeSpan / LukeIntervals, MattSpan_BirthHinge / MattSpan_Carrier, the `6 BC` hinge, AD 65, AD 135, and the genealogy-node proof burden. |
| `File_44` | Scaling-law dependency for the cycle family, `10x`, `700`, `1400`, `4900`, `7000`, Seal700 context, display-vs-lock discipline, and non-import of conditional anchor sets. |
| `File_32` | Current Prime–Civil / Polarity Namespace, including A-space, positive-polarity rails-space, negative-polarity / signed A-space, P2 rail-window / A-space bridge distinction, and Coordinate Mirror as secondary agreement. |
| `File_33` | Reinforces File_32 terminology and polarity-before-Mirror hierarchy; File_33 Ordinal Authentication is not opened locally. |
| `File_15` | Controls authorized generational-unit vocabulary: Jacobean `70`, Mosaic `40`, Abrahamic `100`, and `1400 = LCM(40, 70, 100)` where opened. |
| `File_06` | Joshua / Conquest dependency context for `1366 BC` as a Joshua / Conquest-related target. |
| `File_22` | Cumulative MT harmonic context for `14006 BC`, deep-time target framing, and exact-ratio family where opened by dependency. |
| `File_54` | Comparative Luke 70-year lattice context mediated primarily through File_43. |
| Restart Capsule v11.15 | Repository-wide anchors, operators, modal states, and dependency controls. |
| 490d Repository Style Guide v2.5 | Canonical Markdown, no-comma number formatting, claim-status labels, modal-state discipline, and cross-axis span rules. |
| Project Procedures v3.2 | Project workflow controls, audit-note protocol, Context Economy, Novelty Verification Rule, and canonical source / derived publication boundary. |
| State Vocabulary Register v1.17 | Current per-file modal-state vocabulary, convention entries, and Machine Guards. |

## 0.2 File map

| Section | Function | Active state |
|---|---|---|
| §0 | File-function, dependencies, Machine Guards, state controls, arithmetic register, and argument register | exact-sweep statistical proof state |
| §1 | Definitions | A-space coordinate state; point-cloud expansion state; weighted-node state |
| §2 | Starred-node manifest | fixed node-manifest state |
| §3 | Target frames | fixed target-frame state |
| §4 | Cycle family | Danielic wave-set state; File_44 scaling-law dependency |
| §5 | Scoring rule | distance-hit state; distance-0 perfect-hit state |
| §6 | Exact phase-sweep method | A-space phase-sweep state; exact phase-space frequency state |
| §7 | Observed scores | verified score output |
| §8 | Exact rarities | corrected / verified exact phase-space frequency output |
| §9 | Structural meaning | structural inference; Boundary / internal marker distinction |
| §10 | Jared / 2nd Cainan rationale | Daniel 9 pattern-template state; no 434-year lock |
| §11 | Optional `+460` note | non-lock motif state |
| §12 | Machine-readable output summary | corrected exact-sweep assertion register |
| §13 | Audit notes and unresolved issues | corrected exact-rarity notes; dependency-boundary audit notes; unresolved-issue closure |

## 0.3 Machine Guards

Machine Guard [FIXED NODE MANIFEST]:
The only node-rows used in this file are the starred rows listed in §2.1. No target may be added to the node manifest by implication.

Machine Guard [NODE-VS-TARGET FIREWALL]:
A target may coincide with a node-generated point. That coincidence is a scoring event, not target injection.

Machine Guard [POINT-CLOUD LIMIT]:
Each starred row generates exactly three points: Boundary, `+30`, and `+40`. No hidden points are permitted.

Machine Guard [A-SPACE PHASE SWEEP]:
All phase shifts `+k` must be executed on converted A-space integer coordinates. Do not add `k` directly to civil BC / AD labels.

Machine Guard [FILE_43 / FILE_44 PROOF-BURDEN SPLIT]:
`File_43` supplies the genealogy-node lattice. `File_44` supplies scaling-law controls and display-vs-lock discipline. `File_45` must not collapse these proof burdens.

Machine Guard [FILE_44 CREATION-HEAD NON-IMPORT]:
`File_45` does not import File_44's Creation-head `400/700/1000` triad as a proof-bearing target set.

Machine Guard [DANIEL 9 PATTERN-TEMPLATE]:
The Daniel 9 decomposition is used as a pattern-template. This file does not assert Jared / 2nd Cainan as the literal referent of Daniel 9:25 and does not introduce a 434-year lock.

Machine Guard [EXACT PHASE FREQUENCY]:
The rarity outputs are exact phase-space frequencies within the stated `49000`-year sweep, not metaphysical certainties.

Machine Guard [NON-LOCK `+460` MOTIF]:
The 2nd Cainan `+460` motif is excluded from the target set and phase sweep in this file. It may be mentioned only as a non-lock motif.

Machine Guard [NODE-CLASS BOUNDARIES]:
Node rows, generated points, targets, cycles, scores, and rarity outputs are different modal objects. A date-label that appears in more than one object-class must be restated by state and function.

Machine Guard [TARGET-FRAME NON-GENERATION]:
`T_5` and `T_6` are fixed target frames. They do not generate node rows, point-cloud rows, cycle values, or extra weights.

Machine Guard [FILE_43 / FILE_44 DEPENDENCY BOUNDARY]:
File_43 supplies the genealogy-node lattice used to form the node manifest. File_44 supplies the scaling-law and display-vs-lock discipline used to frame the cycle family. Neither file supplies File_45's exact-sweep statistical conclusion by itself.

## 0.4 Working state register

| State | Value or expression | Node-class / function | Handling in `File_45` |
|---|---:|---|---|
| Exact-sweep statistical proof state | full `49000`-year sweep | deterministic phase-space test | Primary file function. |
| A-space coordinate state | AD `n → A = n`; BC `n → A = 1 − n` | integer coordinate axis | Required for all scoring and phase shifts. |
| Fixed node-manifest state | §2.1 starred-node rows | source node list | Closed manifest; no hidden nodes. |
| Point-cloud expansion state | Boundary; `+30`; `+40` | deterministic expansion | Each starred row produces exactly three points. |
| Weighted-node state | `Jared_Abraham_Row = 2`; all others `1` | dual-presence weighting | Only `Jared_Abraham_Row` has weight `2`. |
| Target-frame state | `T_5`; `T_6` | tested frames | Fixed target sets; not nodes. |
| Target-node coincidence state | `d = 0` | scoring event | Permitted; not target injection. |
| Danielic wave-set state | `{490, 700, 1400, 4900, 7000}` | cycle family | Tested cycle set. |
| Distance-hit state | `d ≡ 0 mod c` | scoring operator | Core hit definition. |
| Distance-0 perfect-hit state | `0 ≡ 0 mod c` for every `c` | exact coincidence rule | One weighted hit per cycle. |
| Exact rarity state | `N≥ / 49000`; rarity `1 / p` | phase-space frequency | Recomputed; exact rarity rows corrected where required. |
| Joshua packet state | `1476 / 1446 / 1406 / 1366 BC` | Mosaic packet / 110-year target window | Tested in `T_5` and `T_6`. |
| Deep-time target state | `14006 BC` | cumulative deep-time target | Included in `T_5` and `T_6`. |
| Enoch pivot state | `4836 BC` | Enoch / cumulative Flood Week target by dependency | Added in `T_6`. |
| Shealtiel_Luke_Row state | `1476 BC`; weight `1` | Luke-side exile hinge | Generates `1476 BC` Boundary and `1446 BC` internal `+30` point. |
| Jared / 2nd Cainan Danielic front-packet state | `4906 BC → 4416 BC = 490` | front-packet analogue | Rationale for including Jared and 2nd Cainan nodes. |
| Christ-generation bisection state | `6 BC → AD 30 → AD 65` | terminal half-week analogue | x10 Danielic bisection pattern. |
| Daniel 9 pattern-template state | `49 + 434 + 3.5 + 3.5 = 490`; x10 `490 + 4340 + 35 + 35 = 4900` | pattern-template | No 434-year lock. |
| Non-lock `+460` motif state | 2nd Cainan `+460` | excluded motif | Not part of target set or phase sweep. |

## 0.5 Modal-state confirmation register

Active state:
modal-state confirmation state; exact-sweep statistical proof state; A-space phase-sweep state; fixed node-manifest state; target-frame state; File_43 genealogy-node dependency state; File_44 scaling-law dependency state; Daniel 9 pattern-template state; non-lock `+460` motif state.

Modal-state scope:
This register records the modal-state boundaries already present in the source. Scores, rarities, phase-sweep counts, and arithmetic outputs are handled in the arithmetic verification register in §0.6.

| Modal-state field | Modal-state resolution | Boundary preserved |
|---|---|---|
| File identity | `File_45` exact-sweep statistical proof state | This file tests a fixed node cloud against fixed target frames; it does not revise File_43 or File_44. |
| File_43 genealogy-node dependency | Primary source for the Matthew / Luke 70-year genealogy-node lattice | File_43 supplies the node-lattice background; File_45 owns the statistical test built from the selected starred-node manifest. |
| File_44 scaling-law dependency | Source for scaling-law controls, cycle-family vocabulary, and display-vs-lock discipline | File_44 does not supply File_45's target frames, node weights, exact scores, rarities, or phase-sweep conclusions. |
| File_42 support state | 700-Year Seal / geometry-first source-history support by source naming | Terminology remains harmonized through File_32 / File_33 where A-space or prime-language boundaries are active. |
| Fixed node-manifest state | §2.1 starred rows only | No unstarred genealogy row, target, cycle, or patch-note datum becomes a node. |
| Node row state | Civil start label plus weight | A node row is not itself a target and not itself the three-point cloud until expanded by §2.2. |
| Generated point state | Boundary, `+30`, and `+40` A-space points | Generated points are derived from node rows; they are not additional node rows and do not change the fixed manifest. |
| Weighted-node state | `Jared_Abraham_Row = 2`; all other rows `1` | The weight-2 state is local to that one supplied row. No target coincidence creates extra row weight. |
| Target-frame state | `T_5` and `T_6` | Targets are tested against the point cloud; they do not generate the point cloud. |
| Target-node coincidence state | `d = 0` where a target equals a generated point | A coincidence is a scoring event only. It is not target injection and does not authorize a new node. |
| Joshua packet state | `1476 / 1446 / 1406 / 1366 BC` | The packet is a target-frame cluster. It remains distinct from the Shealtiel_Luke_Row node source. |
| Shealtiel_Luke_Row state | `1476 BC` starred node row, weight `1` | This row may generate Boundary `1476 BC` and internal `+30` point `1446 BC`; the row is not added because those are targets. |
| Deep-time target state | `14006 BC` | Deep-time target remains a target-frame member; it is not a node row in §2.1. |
| Enoch pivot state | `4836 BC` | In `T_6`, `4836 BC` is a target. In §2.1, Enoch_1 is also a node row. This shared date-label is permitted only with node-class restatement. |
| Danielic wave-set state | `C = {490, 700, 1400, 4900, 7000}` | Cycle values are scoring operators; they are not targets and not node rows. |
| A-space phase-sweep state | `k ∈ {0, …, 48999}` over converted A-space coordinates | Phase shifts must not be applied directly to civil BC / AD labels. |
| Exact phase-space frequency state | `N≥ / 49000`; rarity `1 / p` | Statistical-output state; arithmetic verification and corrections are recorded in §0.6. These are not theological certainties. |
| Daniel 9 pattern-template state | `49 + 434 + 3.5 + 3.5 = 490`; x10 `490 + 4340 + 35 + 35 = 4900` | Pattern-template only. No 434-year lock and no literal Jared / 2nd Cainan referent claim. |
| Jared / 2nd Cainan front-packet state | `4906 BC → 4416 BC = 490` | Included as Danielic front-packet rationale; not a separate 434-year operator. |
| Christ-generation bisection state | `6 BC → AD 30 → AD 65` | Terminal bisection state; arithmetic verified in §0.6 and recorded in §0.6. |
| Non-lock `+460` motif state | 2nd Cainan `+460` motif | Excluded from targets and phase sweep. It remains non-lock commentary only. |
| Patch-set source-history state | Patch 45-A integrated into §3.3 and Machine Guards | Patch-set residue is not a second source body and supplies no additional nodes, targets, cycles, or weights. |

Modal-state result:
No modal-state correction is required. The arithmetic/statistical verification is recorded in §0.6.


## 0.6 Arithmetic verification register

Active state:
arithmetic verification state; A-space coordinate state; point-cloud expansion state; weighted-node state; target-frame scoring state; cycle-hit logic state; exact phase-space frequency state; civil cross-axis span state where opened.

Arithmetic-verification scope:
This register verifies the arithmetic stated in the source and in the modal-state base. It does not revise the node manifest, target frames, node weights, cycle family, Daniel 9 pattern-template state, File_43 / File_44 dependency boundaries, or theological claims.

### 0.6.1 A-space and point-cloud checks

| Arithmetic field | Formula / computation | Verification result |
|---|---|---|
| BC conversion | `A = 1 − n` | Verified. `6 BC → -5`; `1406 BC → -1405`; `14006 BC → -14005`. |
| AD conversion | `A = n` | Verified. AD 30 → `30`; AD 65 → `65`; AD 135 → `135`. |
| Node-row count | §2.1 starred rows | Verified: `21` node rows. |
| Row-weight mass | `20 × 1 + 1 × 2` | Verified: total row-weight mass `22`. |
| Point-cloud entries | `21 × 3` | Verified: `63` generated point entries. |
| Weighted point mass | `22 × 3` | Verified: `66` weighted point-mass units. |
| Point generation | `(S,w)`, `(S+30,w)`, `(S+40,w)` | Verified from every node row. |

### 0.6.2 Cycle-family and phase-space checks

| Arithmetic field | Formula / computation | Verification result |
|---|---|---|
| Cycle set | `C = {490, 700, 1400, 4900, 7000}` | Verified as stated. |
| LCM | `LCM(490, 700, 1400, 4900, 7000)` | Verified: `49000`. |
| Phase domain | `k ∈ {0, …, 48999}` | Verified as the complete residue class under the cycle LCM. |
| Hit rule | `d = |t − p|`; hit when `d ≡ 0 mod c` | Verified. |
| Distance-0 rule | `0 ≡ 0 mod c` for every `c ∈ C` | Verified. A distance-0 coincidence produces five cycle hits before weight multiplication. |

### 0.6.3 Observed score checks

| Target | Recomputed score | Verification result |
|---:|---:|---|
| `14006 BC` | `10` | Verified. |
| `1476 BC` | `12` | Verified. |
| `1446 BC` | `12` | Verified. |
| `1406 BC` | `16` | Verified. |
| `1366 BC` | `16` | Verified. |
| `4836 BC` | `17` | Verified. |

| Target frame | Recomputed total | Verification result |
|---|---:|---|
| `{14006 BC, 1446 BC, 1406 BC}` | `38` | Verified. |
| `T_5 = {14006 BC, 1476 BC, 1446 BC, 1406 BC, 1366 BC}` | `66` | Verified. |
| `T_6 = T_5 ∪ {4836 BC}` | `83` | Verified. |

### 0.6.4 Exact phase-sweep checks

Using the stated node manifest, generated point cloud, weights, cycle family, A-space conversion, score rule, and inclusive phase domain `k ∈ {0, …, 48999}`, the recomputed exact phase-space counts are:

| Target frame | Observed score `S_0` | Source `N≥` before arithmetic verification | Recomputed `N≥` | Recomputed exact rarity | Verification result |
|---|---:|---:|---:|---:|---|
| `{14006 BC, 1446 BC, 1406 BC}` | `38` | `27` | `28` | `1 in 1750` | Source count corrected. |
| `T_5` | `66` | `9` | `9` | `1 in 5444.4` | Verified unchanged. |
| `T_6` | `83` | `2` | `3` | `1 in 16333.3` | Source count corrected. |

Arithmetic correction note:
The original source-counts for `{14006 BC, 1446 BC, 1406 BC}` and `T_6` match a non-zero-phase convention only if `k = 0` is excluded. However, the file's stated definition uses `k ∈ [0, 48999]`, which includes `k = 0`. The non-zero-phase convention also does not explain `T_5`, because `T_5` has `9` phases only when `k = 0` is included. Therefore the arithmetic verification corrects the exact rarity table to the inclusive phase-domain definition already stated in the file.

High-score phase check:

| Target frame | Recomputed high-scoring phases `k:score` |
|---|---|
| `{14006 BC, 1446 BC, 1406 BC}` | `0:38`; `40:42`; `1440:45`; `6410:38`; `7390:41`; `9840:42`; `11240:46`; `16140:38`; `16210:39`; `17190:45`; `18590:40`; `19600:38`; `19640:43`; `21040:44`; `26010:40`; `26990:41`; `29440:43`; `30840:44`; `35810:38`; `36790:42`; `38190:40`; `39200:38`; `39240:44`; `40640:45`; `45540:39`; `45570:38`; `45610:41`; `46590:45` |
| `T_5` | `0:66`; `1470:69`; `11270:67`; `19600:67`; `21070:66`; `25970:66`; `39200:66`; `40670:67`; `45570:69` |
| `T_6` | `0:83`; `1470:83`; `19600:83` |

### 0.6.5 AD 30 midpoint and Danielic template checks

| Arithmetic field | Formula / computation | Verification result |
|---|---|---|
| `6 BC → AD 30` | `6 + 30 − 1 = 35` | Verified. |
| AD 30 → AD 65 | `65 − 30 = 35` | Verified. |
| `6 BC → AD 65` | `6 + 65 − 1 = 70` | Verified. |
| Jared → 2nd Cainan | `4906 − 4416 = 490 = 7 × 70` | Verified. |
| Danielic x1 template | `49 + 434 + 3.5 + 3.5 = 490` | Verified as pattern-template arithmetic. |
| Danielic x10 template | `490 + 4340 + 35 + 35 = 4900` | Verified as pattern-template arithmetic. |

Arithmetic-verification result:
Observed target scores and frame scores are verified. The exact rarity table required two corrections under the file's stated inclusive phase-sweep definition.

## 0.7 Argument-control register

Active state:
argument-control state; verified arithmetic fact; verified score output; corrected exact phase-space frequency; structural inference; Danielic pattern-template; display motif; dependency-controlled claim; theological note.

Argument-control scope:
This register calibrates the claim-status of the already verified arithmetic. It does not change A-space conversion, point-cloud generation, node weights, target frames, cycle family, observed scores, corrected exact rarity rows, File_43 / File_44 dependency boundaries, or Daniel 9 pattern-template arithmetic.

| Argument field | Claim-status | Argument-control handling |
|---|---|---|
| A-space conversion | verified arithmetic fact | Carries the coordinate mechanics of the proof. |
| Point-cloud generation | verified arithmetic fact | `21` node rows generate `63` point entries and `66` weighted point-mass units. |
| Observed individual scores | verified score output | Scores remain verified; no interpretive claim changes them. |
| Target-frame scores | verified score output | `{14006 BC, 1446 BC, 1406 BC} = 38`; `T_5 = 66`; `T_6 = 83`. |
| Exact rarity rows | corrected exact phase-space frequency | Rarity rows follow the inclusive domain `k ∈ {0, …, 48999}`. |
| High-score phase list | arithmetic-audit support | Supports the corrected `N≥` counts; it is not a second scoring method. |
| Statistical meaning | structural inference from verified arithmetic | The rarity results support the claim of an unusually high-scoring interference peak. |
| Phase-space frequency | statistical claim, not metaphysical certainty | The file does not assert inevitability, divine proof, or historical necessity from the probability alone. |
| File_43 dependency | dependency-controlled source state | Supplies genealogy-node lattice background; does not supply File_45's statistical conclusion. |
| File_44 dependency | dependency-controlled scaling-law state | Supplies scaling-law controls and display-vs-lock discipline; does not supply File_45's scores or rarities. |
| Daniel 9 segmentation | pattern-template | Used for structural analogy; no 434-year lock and no literal Jared / 2nd Cainan referent claim. |
| Jared / 2nd Cainan inclusion | structural inference | Justified by the `490`-year front-packet role; not by genealogical ornamentation alone. |
| Christ-generation bisection | arithmetic fact plus structural inference | `6 BC → AD 30 → AD 65` verifies the terminal `35 + 35` pattern and supports the Danielic template. |
| `+460` motif | display motif / non-lock commentary | Explicitly excluded from the target set and phase sweep. |
| Theological reading | theological note only | The statistical architecture may be theologically meaningful, but the arithmetic proof is carried by the exact sweep. |

Argument result:
No claim-status correction requires arithmetic or modal-state revision. The argument-control register preserves the corrected rarity values and classifies the file's main conclusion as a structural inference from verified exact phase-space arithmetic.

## 1. Definitions

### 1.1 Civil year coordinate: A-space

Use civil BC / AD with no year 0, converted into an integer axis:

```markdown
AD n → A = n
BC n → A = 1 − n
```

Examples:

| Civil label | A-space coordinate |
|---:|---:|
| `6 BC` | `A = -5` |
| `1406 BC` | `A = -1405` |
| `14006 BC` | `A = -14005` |

Terminology note:
A-space here follows the File_32 / File_33 Prime–Civil / Polarity Namespace where relevant. In `File_45`, A-space functions as the integer coordinate axis for phase-sweep scoring, not as a new prime-grid operator.

### 1.2 Node model: a 70-year generation produces three points

Each starred 70-year row is represented by three points:

| Point type | A-space expression |
|---|---:|
| Boundary | `A = S` |
| Internal `+30` | `A = S + 30` |
| Internal `+40` | `A = S + 40` |

`S` is the A-space start coordinate of the 70-year generation.

### 1.3 Double-asterisk weighting rule

If a node-row is marked `**`, it is counted twice:

```markdown
w = 2
```

This reflects dual presence, Matthew + Luke, at that row in the supplied input constraints.

## 2. Nodes included

Active state:
fixed node-manifest state; no-hidden-input state; File_43 genealogy-node dependency state.

### 2.1 Starred-node rows

These are the only node-rows used to generate the point cloud. All start years are BC unless explicitly marked AD.

| Node label | Start year | Weight |
|---|---:|---:|
| LukeHead_God | 5326 BC | 1 |
| Adam_Creation_Luke | 5256 BC | 1 |
| Jared_1 | 4906 BC | 1 |
| Enoch_1 | 4836 BC | 1 |
| Flood_Arphaxad_1 | 4486 BC | 1 |
| Cainan2_1 | 4416 BC | 1 |
| Adam_Creation_Matt (Shadow) | 4206 BC | 1 |
| Jared_Abraham_Row | 3856 BC | 2 |
| Enoch_Isaac_Row | 3786 BC | 1 |
| Flood_Arphaxad_2 | 3436 BC | 1 |
| Cainan2_2 | 3366 BC | 1 |
| David_Luke_Row | 2946 BC | 1 |
| Nathan_Row | 2876 BC | 1 |
| Abraham_BirthHinge | 2806 BC | 1 |
| David_Matt_Row | 1896 BC | 1 |
| Jeconiah_Row | 916 BC | 1 |
| Shealtiel_Row | 846 BC | 1 |
| Shealtiel_Luke_Row (Exile entry generation) | 1476 BC | 1 |
| Christ_Generation_Start | 6 BC | 1 |
| Final_Generation_Start | AD 65 | 1 |
| Final_Generation_Next | AD 135 | 1 |

Node-class note:
Each row in this table is a node-row state. It becomes a point-cloud source only through §2.2. It does not become a target unless the same date-label is separately listed in `T_5` or `T_6`.

Non-optional note:
`Shealtiel_Luke_Row` at `1476 BC` is part of the starred-node manifest. It is included because it is the Luke-side exile hinge that also yields the Mosaic packet markers by lattice geometry:

```markdown
Boundary at 1476 BC = distance 0 to target 1476 BC.
Internal +30 at 1446 BC = distance 0 to target 1446 BC when that internal point is tested.
```

This is an explicit input-row effect, not hidden-target injection.

Weight note:
`Jared_Abraham_Row` at `3856 BC` is the only weight-2 row in the supplied constraints.

### 2.2 Point cloud expansion

For each row above with start `S` and weight `w`, the point cloud contains:

```markdown
(S, w)
(S + 30, w)
(S + 40, w)
```

Generated-point modal note:
Boundary, `+30`, and `+40` are point states derived from a node row. They do not create new node rows and do not alter target-frame membership.

No other points are permitted in this file.

## 3. Targets

Active state:
fixed target-frame state; target-node coincidence state; node-vs-target firewall; target-frame non-generation state.

### 3.1 Joshua packet + deep time: five targets

```markdown
T_5 = {14006 BC, 1476 BC, 1446 BC, 1406 BC, 1366 BC}
```

### 3.2 Joshua packet + deep time + Enoch pivot: six targets

```markdown
T_6 = T_5 ∪ {4836 BC}
```

Expanded display:

```markdown
T_6 = {14006 BC, 1476 BC, 1446 BC, 1406 BC, 1366 BC, 4836 BC}
```

Target-frame modal note:
`T_5` and `T_6` are rigid frames tested by phase shifting. They are not node manifests, not point-cloud definitions, and not cycle families.

### 3.3 Targets may coincide with node-generated points

This file uses a single 70-year lattice to generate the node point cloud: Boundary, `+30`, and `+40`. It then tests fixed targets against that cloud.

Therefore, some targets may coincide exactly with points in the cloud:

```markdown
distance = 0
```

This is permitted and expected because certain historically meaningful years also occur as lattice boundary or internal markers in the genealogical construction.

Important:
This does not mean targets are added as nodes. The node list remains only the starred rows in §2.1. Coincidence occurs only when a target equals one of the derived points from those rows.

Consequence:
If a target equals a point, then `distance = 0`, and it is divisible by every cycle tested:

```markdown
490 / 700 / 1400 / 4900 / 7000
```

This yields a perfect self-hit for that point under §5.

## 4. Cycles tested

Active state:
Danielic wave-set state; File_44 scaling-law dependency state.

This file uses the agreed cycle list:

```markdown
C = {490, 700, 1400, 4900, 7000}
```

| Cycle | Interpretation | Claim-status in `File_45` |
|---:|---|---|
| `490` | Danielic week of weeks; `70 × 7` years | cycle-family input |
| `700` | Danielic `70 × 10` scale carrier; `70` generations × 10-year unitization | cycle-family input by File_44 scaling-law dependency |
| `1400` | structural harmonic; `2 × 700` | cycle-family input |
| `4900` | `10 × 490`; scaled Danielic carrier | cycle-family input |
| `7000` | `10 × 700`; scaled generation carrier | cycle-family input |

Interpretive guard:
These cycles are tested as a fixed Danielic wave set. This section does not assert that every cycle is a lock in every tradition.

## 5. Scoring rule

Active state:
distance-hit state; distance-0 perfect-hit state; weighted-node state.

### 5.1 Hit definition

For a target `t` in A-space and a point `p` with weight `w`:

```markdown
d = |t − p|
```

A cycle hit occurs for cycle `c ∈ C` when:

```markdown
d ≡ 0 mod c
```

Distance-0 rule:
If `d = 0`, then:

```markdown
0 ≡ 0 mod c
```

for every `c ∈ C`.

Therefore, a distance-0 coincidence contributes one weighted hit per cycle at that point. Under the current cycle set, this is five cycle-hits before any other points are considered.

### 5.2 Score accumulation

For each target `t`, score is:

```markdown
Score(t) = Σp Σc [d ≡ 0 mod c] × w(p)
```

Total score for a rigid target-frame `T` is:

```markdown
Score(T) = Σt Score(t)
```

No normalization is applied. The test is comparative under phase shifts.

## 6. Exact phase-sweep method

Active state:
A-space phase-sweep state; exact phase-space frequency state.

### 6.1 Why `49000` is the full phase space

The phase behavior of divisibility waves in `C` repeats with period equal to:

```markdown
LCM(490, 700, 1400, 4900, 7000) = 49000.
```

Therefore, shifting every target by `k` years for:

```markdown
k ∈ {0, …, 48999}
```

exhausts the entire equivalence class of relative alignments between targets and the point cloud.

Machine Guard:
All `+k` shifts during the phase sweep must be executed strictly on the converted A-space integer coordinates. Do not add `k` directly to civil year labels before A-space conversion, because this can introduce boundary errors if the shift crosses the 0 threshold.

### 6.2 Exact rarity definition

For a target-frame `T` with observed score `S_0`, define:

```markdown
N≥ = #{k ∈ [0, 48999] : Score(T + k) ≥ S_0}.
```

Then the exact phase-space frequency is:

```markdown
p = N≥ / 49000
Rarity = 1 / p
```

## 7. Observed scores

Active state:
verified arithmetic fact; score recomputation state.

Scores are computed over the full point cloud `P` from §2.2 and the full cycle set `C` from §4, using §5.2.

### 7.1 Individual target scores

| Target | Observed score |
|---:|---:|
| 14006 BC | 10 |
| 1476 BC | 12 |
| 1446 BC | 12 |
| 1406 BC | 16 |
| 1366 BC | 16 |
| 4836 BC | 17 |

### 7.2 Rigid-frame totals

| Target frame | Observed total score |
|---|---:|
| `T_5 = {14006 BC, 1476 BC, 1446 BC, 1406 BC, 1366 BC}` | 66 |
| `T_6 = T_5 ∪ {4836 BC}` | 83 |

Audit clarification:
A common misread is to assume that the extra `+10` in the Joshua packet scores means that `1476 BC` and `1446 BC` were added as nodes. That is false. The `+10` is explained entirely by the explicit starred input row `Shealtiel_Luke_Row` at `1476 BC`, which generates:

```markdown
a distance-0 coincidence at target 1476 BC;
a distance-0 coincidence at target 1446 BC through the row's +30 internal marker.
```

## 8. Exact rarities

Active state:
exact phase-space frequency state; exact-sweep recomputation state; arithmetic correction by recomputation.

These are exact phase-space results, not estimates, under the stated inclusive sweep domain:

```markdown
k ∈ {0, …, 48999}
```

| Target frame | Observed total | Exact rarity over `49000`-year sweep | `N≥` | Verification status |
|---|---:|---:|---:|---|
| `{14006 BC, 1446 BC, 1406 BC}` | `38` | `1 in 1750` | `28` | Corrected from source value `1 in 1814.8`; `N≥ = 27`. |
| `T_5` Joshua packet + deep time | `66` | `1 in 5444.4` | `9` | Verified unchanged. |
| `T_6` = `T_5 + {4836 BC}` | `83` | `1 in 16333.3` | `3` | Corrected from source value `1 in 24500`; `N≥ = 2`. |

Interpretation:
The Joshua packet strengthens the alignment: rarity improves from `1 in 1750` to about `1 in 5444.4`.

Adding `4836 BC` strengthens the alignment further to `1 in 16333.3` within the complete inclusive phase space.

Arithmetic correction note:
The source values `N≥ = 27` for `{14006 BC, 1446 BC, 1406 BC}` and `N≥ = 2` for `T_6` are exactly what would result if the original phase `k = 0` were excluded. However, §6.2 defines `N≥` over `k ∈ [0, 48999]`, which includes `k = 0`. Since `T_5` already uses the inclusive count `N≥ = 9`, this public-clean source normalizes all exact rarity counts to the inclusive definition.

## 9. Structural meaning of the result

Active state:
structural inference; Boundary / internal marker distinction.

This framework naturally separates the Mosaic anchors:

| Anchor | Primary role in this file |
|---:|---|
| `1406 BC` | Boundary attractor; end / start marker. |
| `1446 BC` | Internal `+30` attractor; generation-internal ministry marker. |
| `1476 BC / 1366 BC` | Reinforces that the packet is a coherent 110-year window, not only one date. |

This is the point of including the internal `30 / 40` structure. `1446 BC` is not automatically guaranteed once `1406 BC` is aligned; it requires the internal marker geometry to participate.

## 10. Why Jared and 2nd Cainan are included

Active state:
Jared / 2nd Cainan Danielic front-packet state; Daniel 9 pattern-template state; no 434-year lock; no literal Daniel 9 referent claim.

The other nodes, Adam, Flood / Arphaxad, Abraham, David, Christ, and related hinges, are self-evident as genealogical hinges. Jared and the 2nd Cainan require explicit rationale because they are included for Danielic structure, not merely for genealogical completeness.

### 10.1 Jared → 2nd Cainan = 490 years

From the 70-year lattice:

```markdown
Jared row begins: 4906 BC
2nd Cainan row begins: 4416 BC
```

Difference:

```markdown
4906 − 4416 = 490 = 7 × 70.
```

This places the Watcher-crisis interval, Jared / Enoch horizon, into a full Danielic week of weeks at the x1 scale of the lattice.

### 10.2 Daniel 9 decomposition and the x10 echo

Daniel 9 is often articulated schematically as:

```markdown
49 + 434 + 3.5 + 3.5 = 490.
```

This file treats that breakdown as a pattern-template, not a calendar lock.

Under x10 scaling, it becomes:

```markdown
490 + 4340 + 35 + 35 = 4900.
```

The interpretive move in the present lattice is that the Jared → 2nd Cainan `490`-year block corresponds structurally to the role played by the `49`-year opening segment at x1: a distinguished first packet. This does not assert that Jared / 2nd Cainan is the literal referent of Daniel 9:25.

This corresponds to the Danielic clause commonly paraphrased as “it will be built again, with plaza and moat, but in troubled times,” where the first segment is marked as structurally distinct.

This file does not claim Jared / 2nd Cainan is the literal referent of Daniel 9:25. It claims the lattice uses a Danielic-style segmentation where a first packet is distinguished.

### 10.3 Why the x10 terminal halves matter: `6 BC → AD 30 → AD 65`

On the Christ side, the lattice supplies a terminal `35 + 35` structure on the x10 scale:

| Node | Function |
|---:|---|
| `6 BC` | Christ generation start in the 70-year framework. |
| AD 30 | Midpoint, 35 years after `6 BC` under no-year-0 civil arithmetic. |
| AD 65 | End of the 70-year Christ generation. |

The scaled week is bisected, yielding the cut-short motif:

```markdown
6 BC → AD 30 = first half
AD 30 → AD 65 = second half
```

This is the reason Jared and 2nd Cainan are not optional ornaments in this file. They supply the front-end Danielic packet:

```markdown
490 years = 7 generations
```

while the Christ generation supplies the back-end bisection:

```markdown
35 + 35
```

Together, these allow the lattice to exhibit a Daniel 9-style first segment in trouble plus final week bisected behavior without importing unrelated 434-year locks.

### 10.4 Jared / 2nd Cainan summary

Jared and 2nd Cainan are included because:

| Reason | Function |
|---|---|
| They define a clean `490`-year / 7-generation block in the lattice. | Jared → 2nd Cainan. |
| That block serves as the structurally distinct front-packet analogue in the Daniel 9 segmentation template. | Pattern-template, not literal referent claim. |
| The terminal half-and-half at Christ supplies the matching end-of-week bisection on the x10 scale. | `6 BC / AD 30 / AD 65`. |

## 11. Optional non-lock motif

Active state:
non-lock `+460` motif state; excluded-target state; excluded-phase-sweep state.

If the 2nd Cainan `+460`-year motif is discussed elsewhere, it must be framed as a non-lock motif only.

In this file, the `+460` motif is not needed to obtain the statistical result and is intentionally excluded from the target set and the phase sweep.

## 12. Output summary

Active state:
machine-readable assertion register; verified score output; corrected exact phase-space frequency; structural inference from verified arithmetic.

```markdown
Node set = exactly §2.1.
Point-cloud expansion = Boundary / +30 / +40 with weights.
Cycles tested = exactly C = {490, 700, 1400, 4900, 7000}.
Exact phase space = 49000 years.
Three-target frame `{14006 BC, 1446 BC, 1406 BC}` score = 38 → exact rarity 1 in 1750.
T_5 score = 66 → exact rarity 1 in 5444.4.
T_6 score = 83 → exact rarity 1 in 16333.3.
Jared → 2nd Cainan = 490 years.
Jared / 2nd Cainan supplies the Danielic front-packet analogue.
Christ-generation bisection = 6 BC / AD 30 / AD 65.
No 434-year lock is opened.
```

Argument-status note:
The output summary records verified arithmetic facts and corrected exact phase-space frequencies. The conclusion that the target-frame is an unusually high-scoring interference peak is a structural inference from those verified results, not a metaphysical-certainty claim.

## 13. Audit notes and unresolved issues

Audit note:
No modal-state blocker was identified.

Audit note:
The observed individual scores and frame scores were verified. No score correction is required.

Audit note:
Two exact rarity rows were corrected under the stated inclusive phase-sweep definition: the three-target frame is `1 in 1750`, and `T_6` is `1 in 16333.3`. These remain corrected exact phase-space frequencies.

Audit note:
`File_45` uses File_43 as the genealogy-node source and File_44 as the scaling-law source. Their proof burdens remain distinct.

Audit note:
`File_45` does not import File_44's Creation-head `400/700/1000` triad as a proof-bearing target set.

Audit note:
Daniel 9 language remains a pattern-template and does not assert Jared / 2nd Cainan as the literal referent of Daniel 9:25. No `434`-year lock is opened.

Audit note:
The `+460` motif remains excluded from the target set and phase sweep.

## 13.1 Unresolved issues

None.

## 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.