# C1618 — Connect LXX Exodus, SP/MT restoration and MT AD65

## Question

Can the new600 relation extend the inherited910 comparison using only already-appointed nodes?

## Sources

```json
[
  "Comparative_Study §4.1",
  "Shem_600_restoration_Jubilee_transport.json"
]
```

## Opened utc

2026-09-29T15:01:40.614954+00:00

## Results

```json
{
  "roles_and_labels": [
    [
      "LXX cumulative Shem / Exodus",
      6346,
      1446
    ],
    [
      "MT cumulative Shem = SP completed inverse Flood / restoration",
      5436,
      536
    ],
    [
      "MT cumulative Flood / civil AD65",
      4836,
      -65
    ]
  ],
  "civil_coordinates": [
    [
      -6345,
      -1445
    ],
    [
      -5435,
      -535
    ],
    [
      -4835,
      65
    ]
  ],
  "successive_forward_translations": [
    910,
    600
  ],
  "direct_first_to_third": 1510,
  "shared_width": 4900,
  "status": "three linked placements of one width; source translation plus named lifespan transport"
}
```

## Finding

The4900 family runs LXX6346→1446, MT/SP5436→536, MT4836→AD65, with whole-interval translations910 then600. It joins Exodus, restoration and the NT endpoint through named source boundaries.

## Reassessment

Specify the source roles at5436 so that the connection is not misread as a universal inverse-Shem identity.

## Checks

```json
{}
```

## Closed utc

2026-09-29T15:01:40.615518+00:00

## Record provenance

Exact record hash: `97bd6ae4c6ab138f1dde3fd60166045671973d24836b8c858a32aef88c62fc25`

Source journal: `Research_Cycles/C1585_C1634/journal.json`