## Babylonian spans connect the inverse, Covenant and calendar families

Dean's additional observation clarifies why the SP intermediate matters. At the Conquest-held stage, the LXX Regular inverse head **10436 BC** stands **7700 years** before the SP Cumulative inverse Flood node **2736 BC**. The shared Nativity extension moves both coordinates 2700 years earlier, to **13136** and **5436 BC**. The latter is also ordinary Rounded MT Cumulative Shem. The same edge therefore connects constructions in all three traditions.

Keep restoration **536 BC** fixed while the two inverse coordinates move:

| Inverse context | Ordered BC coordinates | Partition | Total to 536 |
|---|---|---|---:|
| Conquest held | 10436 → 2736 → 536 | 7700 + 2200 | **9900** |
| Nativity extended | 13136 → 5436 → 536 | 7700 + 4900 | **12600** |

The repeated 7700 is explained by moving both endpoints together. The final leg grows by 2700 because restoration stays fixed. This accounts for the transition from 9900 to 12600 as one connected pattern. The 9900 row also preserves the interval in MT Cumulative–Regular **14006→4106** and accepted SP Regular inverse–Fall **14306→4406**; both endpoints translate by −3570 from the MT pair to the LXX/restoration pair. [Comparative study §§4,7; C1488–C1492]

### The two 1260 partitions acquire named positions

File17 already retains both component forms

\[
1260=770+490=777+483.
\]

The named Shem junction places the first form at tenfold scale:

\[
13136\longrightarrow5436\longrightarrow536,
\qquad12600=7700+4900.
\]

Holding the same outer endpoints, the other division falls at **5366 BC**:

\[
13136\longrightarrow5366\longrightarrow536,
\qquad12600=7770+4830.
\]

This internal point is independently named in File29 as the **LXX Year-6 coordinate with second Cainan removed**, \(5496-130=5366\). It enters here as an explicit comparison target. The native Cainan-ON Rounded inputs that generated 13136 remain unchanged. Thus the two component forms have source-appointed positions in the comparison, with the cut moving 70 years while the whole interval remains 12600. [File17 §§8.1,12.1; File29 state register and §6.4; C1497–C1511]

The same 4830/4900 carrier also describes the user's **606–536 BC** exile frame. From MT Cumulative Shem 5436, the radii are 4830 and 4900, or \(69\times70\) and \(70\times70\). The Prophetic Key reaches the full 4900 interval from either held end:

\[
5436-\frac{70}{69}(5436-606)=536,
\]
\[
536+\frac{70}{69}(5366-536)=5436.
\]

The input intervals 5436→606 and 5366→536 are 70-year translations of one another; both expand to 5436→536. These are two anchored placements of one carrier. In the first, only the final radius of 13136→5436→606 expands: the preceding 7700 stays fixed. In the fixed-total comparison above, the cut moves and one component gains the 70 that the other loses. [C1493–C1502, C1512]

### The Covenant comparison occupies the same field

Keeping both the Shem and Minimum Covenant cuts gives one ordered chain:

\[
13136\longrightarrow5436\longrightarrow1866\longrightarrow536,
\]
\[
12600=7700+3570+1330.
\]

Combining the first two components recovers **11270 + 1330**, the Covenant partition already translated from MT Creation→SP inverse Flood→Conquest. Combining the final two gives **7700 + 4900**, the Babylonian partition. This explains how the earlier \(23\times490\) bridge and the new \(10\times1260\) comparison fit together. [C1524–C1525]

The common 70-year unit makes the relationship compact. Measured earlier than restoration 536 BC:

| Named comparison node | BC coordinate | Units of 70 from 536 |
|---|---:|---:|
| Exile start in the selected frame | 606 | 1 |
| MT Minimum Covenant | 1866 | 19 |
| LXX Year-6, second Cainan removed | 5366 | 69 |
| MT Cumulative Shem / completed SP inverse Flood | 5436 | 70 |
| LXX Regular completed inverse head | 13136 | 180 |
| SP Cumulative completed inverse head | 14116 | 194 |

The Covenant Key now reads \(19+(25/23)(180-19)=194\): its input and output radii are **161 and 175 units**, precisely the File60 carrier. Around the shared Shem coordinate, the two heads instead stand 110 and 124 units earlier; their difference remains 14 units, or 980 years. The Key relates the specified heads, while the shared Shem placement belongs to the separately reconstructed paths. [File60 §2.6; C1517–C1520]

### The SP junction also joins the Exodus and Enochian forms

The user's 2150 comparison has an appointed internal division:

\[
2736\longrightarrow1446\longrightarrow586,
\qquad2150=1290+860=3\times430+2\times430.
\]

The first component is the existing SP inverse Flood→Exodus relation; the second is File17's Exodus→Jerusalem destruction interval. The same SP node stands **2730 years before 6 BC**, taking the inherited form **7.5×364**. This is a chronological year-span with the source's Enochian coefficient. Its 2730 is distinct from the 2700-year stage displacement, although the 30-year difference also equals \(7.5(364-360)\). [File17 §§5,13.5,13A.3; File63 §4.7; C1513–C1516]

These comparisons give the larger explanation a connected structure: single-pass inverse paths produce a shared edge and named junctions; translations preserve their intervals; different named cuts recover prophetic and Covenant components; anchored Keys relate selected radii. The relationships share source inputs, so their many displays express a common family rather than independent confirmations.