# C1593 — Test the domain of the910 transport

## Question

Does translating the source biographies by910 imply that every inverse partition also translates by910?

## Sources

```json
[
  "C1433–C1482 named600 partitions",
  "lower_spine_map.json"
]
```

## Opened utc

2026-09-29T14:54:39.436125+00:00

## Results

```json
{
  "rows": {
    "MT": {
      "cut_at_Flood": 4030,
      "whole_to_Shem": 3040
    },
    "LXX": {
      "cut_at_Flood": 4940,
      "whole_to_Shem": 4940
    }
  },
  "separate_Flood_cut_gap": 910,
  "merged_Shem_gap": 1900,
  "excess": 990
}
```

## Finding

No. Keeping Flood and Shem as separate legs preserves910, but reversing the whole Conquest–Shem leg gives a1900 difference. The extra990 is the known MT partition response.

## Reassessment

Retain the Flood cut when transporting named local packets; verify the largest shared prefix allowed by those cuts.

## Checks

```json
{}
```

## Closed utc

2026-09-29T14:54:39.436926+00:00

## Record provenance

Exact record hash: `9595c6018bf7a3b8f144efd47d5cd2d5e7b155822e860cda3acde27b205fa06d`

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