C746 — Verify composition on the full shared genealogy

Question

Do MT→SP→LXX comparisons compose node-by-node in both modes and the modebridge?

Inputs

{
  "shared_nodes": [
    "Adam",
    "Seth",
    "Enosh",
    "Kenan",
    "Mahalalel",
    "Jared",
    "Enoch",
    "Methuselah",
    "Lamech",
    "Noah",
    "Shem",
    "Arphaxad",
    "Shelah",
    "Eber",
    "Peleg",
    "Reu",
    "Serug",
    "Nahor",
    "Terah",
    "Abraham"
  ],
  "modes": [
    "R",
    "C_lower",
    "G"
  ],
  "excluded_from_shared_grid": "nativeLXX-onlyCainan retained in itsownpath"
}

Sources

[
  "C738–C745; Research Strategy §5D"
]

Opened utc

2026-09-28T01:46:35.742370+00:00

Results

{
  "composition_residuals": {
    "R": [
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0
    ],
    "C_lower": [
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0
    ],
    "G": [
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0,
      0
    ]
  },
  "typed_comparisons": 60
}

Finding

All60 typed shared-node comparisons compose exactly. This is consistency of a common source-coordinate representation, not independent confirmation from60matches. The native inserted row remains visible rather than being invented in the othertraditions.

Reassessment

Test why matchingCreation totals alone cannot recover the ordered source structure.

Checks

{
  "all_zero": true,
  "coverage": true
}

Closed utc

2026-09-28T01:46:35.742596+00:00

Record provenance

Exact record hash: 6891f5aed69ba0035ea5911d4bd9075def94b214e1622ab960f61620c273baa6

Source journal: Research_Cycles/C0732_C0831/journal.json