C736 — Transfer the full bridge to native LXX

Question

Does the MT row-to-boundary rule reconstruct the nativeLXX profile without removingCainan?

Inputs

{
  "source_names": [
    "Adam",
    "Seth",
    "Enosh",
    "Kenan",
    "Mahalalel",
    "Jared",
    "Enoch",
    "Methuselah",
    "Lamech",
    "Noah",
    "Shem",
    "Arphaxad",
    "Cainan2",
    "Shelah",
    "Eber",
    "Peleg",
    "Reu",
    "Serug",
    "Nahor",
    "Terah"
  ],
  "Cainan": "nativeON",
  "terminal_lower_pair": [
    2433,
    2166
  ],
  "Lamech": "182/753"
}

Sources

[
  "File18 §§4.1,6D; C733–C735"
]

Opened utc

2026-09-28T01:42:35.634013+00:00

Results

{
  "names": [
    "Adam",
    "Seth",
    "Enosh",
    "Kenan",
    "Mahalalel",
    "Jared",
    "Enoch",
    "Methuselah",
    "Lamech",
    "Noah",
    "Shem",
    "Arphaxad",
    "Cainan2",
    "Shelah",
    "Eber",
    "Peleg",
    "Reu",
    "Serug",
    "Nahor",
    "Terah",
    "Abraham"
  ],
  "lower_mode_bridge": [
    9400,
    8700,
    7993,
    7278,
    6538,
    5808,
    5008,
    4808,
    4026,
    3455,
    3007,
    2507,
    2177,
    1847,
    1517,
    1147,
    938,
    731,
    531,
    402,
    267
  ],
  "row_generators": [
    700,
    707,
    715,
    740,
    730,
    800,
    200,
    782,
    571,
    448,
    500,
    330,
    330,
    330,
    370,
    209,
    207,
    200,
    129,
    135
  ],
  "source_center_checks": {
    "Adam": 14896,
    "Lamech": 8048,
    "Cainan2": 5280,
    "Peleg": 3856
  }
}

Finding

The identical rule generates all21 nativeLXX comparisons, including theCainan330 remainder contribution. Four separately printed cumulative nodes confirm the reconstructed chain. The resulting Creation bridge9400 belongs to the nativeLXX state, rather than being forced toMT9890.

Reassessment

Transfer the same rule toSP while keeping its inclusive and primaryNoah correction explicit.

Checks

{
  "regular_edges": true,
  "source_nodes": true,
  "bridge": true
}

Closed utc

2026-09-28T01:43:06.664019+00:00

Record provenance

Exact record hash: 52fc55509c5cef77c869a153aa691d131fe256f32409125f1ee471472081c247

Source journal: Research_Cycles/C0732_C0831/journal.json