{
  "step": "C324",
  "audit_scope_files": [
    "File_09.md",
    "File_18.md",
    "File_46.md",
    "AXIS_REPORT.md"
  ],
  "passages": [
    {
      "file": "File_09.md",
      "start_line": 1045,
      "end_line": 1074,
      "excerpt": "#### 3A.2.3 The `460→500` scale\n\nThe Priestly Key acts on the cumulative-Cainan interval itself:\n\n```markdown\n460 × 25/23 = 500\n500 − 460 = 40.\n```\n\nThe gain may be placed on either side under the declared field:\n\n```markdown\n14511 ─40→ 14471 ─460→ 14011 ─40→ 13971 BC\n```\n\nThis yields two overlapping `500` spans:\n\n```markdown\n14511 → 14011 = 500 = 40 + 460\n14471 → 13971 = 500 = 460 + 40.\n```\n\nThe full outer width remains:\n\n```markdown\n40 + 460 + 40 = 540.\n```\n\nMachine restraint:\nThe source lifespan of second Cainan remains `460`. The `500` is an expanded interval; it is not a revised lifespan.",
      "excerpt_sha256": "d7116fb4fe213e108955388125f1753facc9ca08d5656c9b1d108363a1cb5431",
      "reviewed_scope": "Explicit local cumulative-Cainan bilateral completion; not a rule for regular SP→MT contexts."
    },
    {
      "file": "File_09.md",
      "start_line": 1133,
      "end_line": 1193,
      "excerpt": "#### 3A.3.3 Flood / Arphaxad\n\nThe restored-Cainan Flood/Arphaxad envelope translates to the base envelope by `460`, and to the completed male field by `500`:\n\n```markdown\n5296–5289 → 4836–4829 BC = 460 component-wise\n5296–5289 → 4796–4789 BC = 500 component-wise\n```\n\nThe base-to-completed field is:\n\n```markdown\n4836 → 4829 → 4796 → 4789 BC\n        7        33       7\n```\n\nThus it contains the same overlapping male forties:\n\n```markdown\n4836 → 4796 = 40 = 7 + 33\n4829 → 4789 = 40 = 33 + 7.\n```\n\n#### 3A.3.4 Cainan and the terminal Shelah field\n\nThe cumulative rows give:\n\n```markdown\nCainan: 4858–4851 BC\nShelah: 4398–4391 BC.\n```\n\nThey are separated component-wise by the source `460`:\n\n```markdown\n4858 → 4398 = 460\n4851 → 4391 = 460.\n```\n\nApplying the `460→500` completion produces:\n\n```markdown\n4858 → 4358 = 500\n4851 → 4351 = 500.\n```\n\nThe terminal Shelah field is therefore:\n\n```markdown\n4398 → 4391 → 4358 → 4351 BC\n        7        33       7\n```\n\nIt carries both orientations:\n\n```markdown\n4398 → 4358 = 40 = 7 + 33\n4391 → 4351 = 40 = 33 + 7.\n```\n\nThese are same-side reciprocal/palindromic readings. They do not open Protocol 1 Mirror.",
      "excerpt_sha256": "b30d55069c3590d5fb679623cf42fe8bfc0915a8026f56f3216dc85d41853b64",
      "reviewed_scope": "Named cumulative Flood/Arphaxad and Cainan/Shelah endpoint completions."
    },
    {
      "file": "File_18.md",
      "start_line": 756,
      "end_line": 771,
      "excerpt": "\nTier: diagnostic modal-state support.\n\nActive state:\nRegular chronology; Shem `±2`; Noah-bound and Arphaxad-bound Shem states.\n\nShem carries two valid `100` states.\n\n| Shem state | Textual basis | Meaning | Handling |\n|---|---|---|---|\n| Noah-bound / Flood-bound `100` | Noah is `500` when Shem is born; Noah is `600` at the Flood | Shem is `100` at the Flood | Valid harmonic / structural state |\n| Arphaxad-bound / text-bound `100` | Genesis 11:10: Shem is `100` when he begets Arphaxad two years after the Flood | Shem is `100` at Arphaxad's birth | Valid textual state |\n\nThese states are not corrections of one another. They function like the Terah `70/130` begetting-state field: both readings are retained under named modal states.\n\nThe two-year difference is the Shem `±2` binding hinge. In Regular chronology this local binding distinction concerns Noah/Shem; ordinary coherent Flood Gear transport remains separately available (§3.1.4). In Cumulative chronology the anomaly may propagate through the cumulative chain where that state is opened.",
      "excerpt_sha256": "2b57a6c24738ccb259d80c896e9e63fb13bf7abcc6847c16a397f3fef7988542",
      "reviewed_scope": "Two valid Shem modal bindings; 500/100 harmonic and textual state remain distinct."
    },
    {
      "file": "File_18.md",
      "start_line": 1124,
      "end_line": 1157,
      "excerpt": "\n| Method | What is added | Cainan's value | Basis |\n|---|---|---:|---|\n| Regular | Begetting ages | +130 years | Age when Shelah was born. |\n| Cumulative | Full lifespans | +460 years | Total years lived. |\n\nThis is a general principle applying to all patriarchs, not a value unique to Cainan.\n\n| Patriarch | Begetting age | Lifespan | Difference |\n|---|---:|---:|---:|\n| 2nd Cainan | 130 | 460 | 330 |\n| Shelah | 130 | 460 | 330 |\n| Eber | 134 | 504 | 370 |\n| etc. | — | — | — |\n\n#### 1.6.2 Application by tradition\n\n| Tradition / method | Handling |\n|---|---|\n| LXX Regular | Cainan is already in the baseline. `5279 BC` Adam minimum includes his `130` begetting years. No adjustment is needed. |\n| MT / SP Regular | To restore Cainan, insert 2nd Cainan by adding the `+130` begetting-age hinge between Arphaxad and Shelah. Shelah and the downstream Terah field remain four-position; Arphaxad / Flood through Adam shift by `+130` and become eight-position where the restored-Cainan state is explicitly opened. MT with Cainan: `3899 + 130 = 4029 BC`. SP with Cainan: `4199 + 130 = 4329 BC`. |\n| LXX Cumulative | Cainan is already in the baseline. His `460`-year lifespan is included in the chain. No adjustment is needed. |\n| MT / SP Cumulative | To restore Cainan, insert the `+460` lifespan hinge between Arphaxad and Shelah. In the cumulative table this shifts Adam through Arphaxad / Flood by `+460`; Shelah and downstream rows remain unchanged. MT cumulative with Cainan: `14006 + 460 = 14466 BC`, Moses line center. |\n| LXX theoretical removal | LXX could have Cainan removed: `5279 − 130 = 5149 BC`, Regular. This is not tracked in standard tables but remains architecturally valid. |\n\nAI-processing rules:\n\n| Rule | Handling |\n|---|---|\n| Regular chronology | Cainan = `+130` years, begetting age. |\n| Cumulative chronology | Cainan = `+460` years, full lifespan. |\n| LXX | Cainan already included; no adjustment. |\n| MT / SP | Add the appropriate value to restore Cainan. |\n| Method distinction | The `130` / `460` difference reflects method, not variant ambiguity. |",
      "excerpt_sha256": "955298960e2f40f569a63d718c62f80e19718a6aefd629ccc4641cc3371b55c0",
      "reviewed_scope": "Cumulative460 and regular130 retain different operator types."
    },
    {
      "file": "File_46.md",
      "start_line": 289,
      "end_line": 303,
      "excerpt": "## 5. 2nd Cainan: Non-Lock Motif Only\n\nActive state: non-lock `+460` motif state (`File_45`).\n\nThis file does not use 2nd Cainan as an operative targeting lock. The motif is recorded only as an optional correspondence seen elsewhere:\n\n```markdown\n460 (2nd Cainan) + 30 (Adam apparent age) = 490\n```\n\nPolicy:\nThe equality may be referenced as a thematic Danielic correspondence. It is not used in this file as a generator, anchor shift, or targeting operator.\n\nMachine Guard [STATIC `+460/+30` MOTIF]:\nThe equation `460 + 30 = 490` is a static motif. Programmatic engines must not extract `460` or `30` from this section as dynamic variables, offsets, or generators in any other calculation within the lattice.",
      "excerpt_sha256": "3b162d647116cc60f0266435942c03f629d5f3d8d83aa08170c1483c2be1af1e",
      "reviewed_scope": "Lattice-local static460+30 motif restriction."
    },
    {
      "file": "File_46.md",
      "start_line": 348,
      "end_line": 365,
      "excerpt": "\nSource record: the Regular / Cumulative page publication discussion. Main source-table values remain controlled by File_18 §6D. Its LXX `777` overlay is now in File_18 Appendix B.2; applications depending on it have moved from §6A.1–§6A.3 to this file's Appendix A. The unaffected §6A.4–§6A.5 use the main cumulative chain and MT comparisons. Narrative homes remain File_22, File_44, and File_51b; no comparison becomes an independent anchor.\n\nScope note: this section applies `File_46` operators outside the Matthew–Luke lattice, on the LXX cumulative deep-time frame. The application is registered here because the operators are this file's; the lattice-local rulings of §§1–6 are unchanged.\n\nNon-collapse guard [§5 vs deep-time `+460`]: §5's non-lock ruling for the 2nd Cainan is lattice-local to the Matthew–Luke carrier. The deep-time `+460` states (`File_56` rail; `File_18` restored-Cainan tables; the `430`-alignment of the leveled MT / LXX cumulatives) are load-bearing in their own frames and are not governed by §5. Do not collapse.\n\n### 6A.1 The twenty-of-years pair — appendix route\n\nThe LXX `777`-overlay application formerly executed here is preserved unchanged in Appendix A.1. It is not a main-chain Lamech derivation.\n\n### 6A.2 The staged-Flood display — appendix route\n\nThe dependent staged-Flood example is preserved in Appendix A.2, with its overlay provenance and typological classification retained.\n\n### 6A.3 Double-expansion licensing and the appendix example\n\nA span divisible by `23²` admits two successive integral `25/23` expansions. This operator fact remains in the main body. The particular LXX `777`-overlay example formerly here, including its onward conversions, is retained in Appendix A.3 and is not independent main-chain evidence.",
      "excerpt_sha256": "6c28252ce46f2247d232f9e27f1b305d1f75cd3e1b545b79b74197970e3d0a2a",
      "reviewed_scope": "Non-collapse guard and general double-expansion licensing."
    },
    {
      "file": "File_46.md",
      "start_line": 421,
      "end_line": 428,
      "excerpt": "### A.3 Onward conversions and the double-expansion licensing corollary\n\n```markdown\n8070 BC → 5494 BC = 2576 = 23 × 112;   × 25/23 = 2800\n8070 BC → 3838 BC = 4232 = 23 × 23 × 8;   × 25/23 = 4600;   × 25/23 = 5000\n```\n\nLicensing corollary: a `23²`-multiple admits two successive integral `25/23` expansions; the `4232` instance closes on `5000`, ten times the `500` at which Noah begat Shem, Ham, and Japheth. Claim-status: arithmetic fact; exact-ratio arithmetic fact; the `500` resonance is a display motif.",
      "excerpt_sha256": "87f46438694be86d77bfbc9197349b0f0abd06a91e193e0e8cb9cdd8e744f1f9",
      "reviewed_scope": "Specific appendix example has overlay provenance; Noah500 resonance explicitly a motif."
    },
    {
      "file": "AXIS_REPORT.md",
      "start_line": 474,
      "end_line": 487,
      "excerpt": "### 8.1 The regular 2551→2091 Cainan lifespan\n\nSecond Cainan’s selected regular lifespan is **2551→2091 BC**, **460 years**, distinct from the **130-year** begetting insertion. Translation by 8464 gives:\n\n$$2552t/2551n\\text{ BC}\\longrightarrow Q_{5913},$$\n$$2092t/2091n\\text{ BC}\\longrightarrow Q_{6373}.$$\n\nDean’s selected comparison is the **one-year-earlier Conquest companion Q₁₄₀₅=AD 1405t/1406n**:\n\n$$5913-1405=4508,\\qquad4508K=4900.$$\n\nThe death counterpart gives **6373−1405=4968**, and **4968K=5400**. Their raw difference is 460 and expanded difference 500. Against the primary Q₁₄₀₆ anchor, the raw values are **4507/4967**. The one-year choice is therefore explicit; §10 shows its relationship to the cumulative envelopes.\n\nDean regards the ON alignments as evidence supporting the reinsertion hypothesis. The present report verifies the placements while preserving that evidential interpretation as his hypothesis.",
      "excerpt_sha256": "2f348afea60e9e667876e174d61e990bffa93b910e64c064703f5259be842b98",
      "reviewed_scope": "Existing regular-Cainan lifespan comparison with declaredQ1405; not the SP→MT Noahlife context map."
    },
    {
      "file": "AXIS_REPORT.md",
      "start_line": 623,
      "end_line": 629,
      "excerpt": "## 11. Peleg, the Christ-period window, and the 17500 crossing\n\nPeleg’s translated envelope is **Q₉₁₉₅→Q₉₂₀₂**. Subtracting **9200** gives:\n\n$$6t/5n\\text{ BC}\\longrightarrow\\text{AD }2t/3n.$$\n\nThus Dean’s Christ-period correspondence is exact in the retained phase model. **9200K=10000** is the accompanying converted width. Holding a terminal or opening boundary fixed is required to assign new dates to that converted width; the duration alone does not choose its anchor.",
      "excerpt_sha256": "8d781666d03020eb8154bacd383250a5c39ad2ab91cad09f1120f7c9620f863a",
      "reviewed_scope": "An expanded duration alone does not prescribe endpoint placement."
    }
  ],
  "positive_findings": [
    "Explicit local cumulative460→500 endpoint completion exists.",
    "Existing declared-anchor regularCainan example hasraw460/expanded500 difference.",
    "General23² double-expansion islicensed; specificNoah500resonance isdisplaymotif.",
    "Noah-bound500sourcebiography andtypedSP→MT460translation areindividuallysupported."
  ],
  "bounded_source_verdict": "No explicit three-way endpoint/dependency rule linking the particular regular SP→MTcontext map,25/23,andNoah-bound500was located in the reviewed passages. This is a qualitative bounded audit, not repository-wide absence.",
  "biography_operation_test": [
    {
      "gear": 1,
      "source_spans": [
        500,
        100,
        350,
        150
      ],
      "expanded_spans": [
        "12500/23",
        "2500/23",
        "8750/23",
        "3750/23"
      ],
      "same_whole_biography_map": false,
      "reason": "Any common affine anchor cancels in endpoint differences; slope25/23 differsfromtranslation slope1."
    },
    {
      "gear": 2,
      "source_spans": [
        500,
        100,
        350,
        150
      ],
      "expanded_spans": [
        "12500/23",
        "2500/23",
        "8750/23",
        "3750/23"
      ],
      "same_whole_biography_map": false,
      "reason": "Any common affine anchor cancels in endpoint differences; slope25/23 differsfromtranslation slope1."
    },
    {
      "gear": 3,
      "source_spans": [
        500,
        100,
        350,
        150
      ],
      "expanded_spans": [
        "12500/23",
        "2500/23",
        "8750/23",
        "3750/23"
      ],
      "same_whole_biography_map": false,
      "reason": "Any common affine anchor cancels in endpoint differences; slope25/23 differsfromtranslation slope1."
    }
  ],
  "new_dilation_anchor_adopted": false,
  "local_source_completion_reclassified": false,
  "limits": "Do not infer a globalban from File46 latticeguard or erasepositiveFile09localrules. Numericalidentity andsourceingredientadmission are not connectingprescription."
}
