# The three inverse spines: source differences, Flood junctions and preserved intervals

September 29, 2026 UTC · C1585–C1634 continuation · 50 completed and individually reassessed actions.

This continuation addresses Dean’s 9800/11270, 7000 and Rounded AD 2166 observations as part of the larger Strategy: explain how the chronological families fit together. It reuses the established MT primary, LXX native Cainan-ON/full 430 comparison and accepted SP Fall construction. The source row tables and primary inversions were already known; the contribution is their connected explanation through named paths.

## Principal results

1. The source-generated MT–LXX Flood 910 is 460+450. Equal Shem 600 and Noah 950 carry it through those boundaries; the Lamech −20 difference changes it to 890=460+430 at Creation.
2. SP’s Eber/Terah −120 source difference and 3310→1330 reversal contraction 1980 together explain the 2100 MT–SP inverse Flood gap. The shared 2700 stage change then gives 2700−2100=600, explaining the 5436 SP inverse Flood/MT Shem junction.
3. The complete cumulative restoration family is MT 7000, LXX 7910, SP 4900. Each lower inverse leg gains the same 3570=51×70 when completed and measured to 536. Moving the LXX target to Exodus 1446 yields the matching 7000.
4. MT 7536→5436→4836→536 and LXX 8446→6346→5746→1446 both carry 7000=2100+600+4300. All four nodes translate by 910.
5. The 4900 family has three named placements: LXX 6346→1446, MT/SP 5436→536, MT 4836→AD 65. The successive forward translations are 910 and 600 civil years. The last row is the 10-Jubilee suffix of SP’s 23-Jubilee path.
6. LXX 13136→MT 7536→SP 5436→536 partitions 12600 as 5600+2100+4900. The authorized 2700-forward shift preserves this whole path at 10436→4836→2736→Rounded AD 2166. Retaining Covenant 1866 in the BC path additionally gives 5600+2100+3570+1330, preserving 11270, 7000 and 4900 as named subpaths.

## Integrated explanatory text

### The source rows explain the three cumulative Flood connections

The MT–LXX **910-year** displacement now has an explicit source explanation. In the rounded post-Flood lifespan rows it is

\[
910=460+(25+25+40+100+100+100+60)=460+450.
\]

The 460 is second Cainan; the remaining terms belong to Arphaxad, Shelah, Eber, Peleg, Reu, Serug and Nahor. Terah contributes zero. Equal Shem and Noah lives preserve this difference through their cumulative boundaries. LXX Lamech's rounded 755 versus MT 775 then reduces it to **890 = 460 + 430** from Lamech back to Creation. Thus the familiar 430 belongs to that later comparison; the Flood difference uses 450. Rounding preserves the Creation difference because the Actual calculation gives the same \(914-24=910-20=890\). [File18 §§2.2,4.2,6D; File51a §16; C1586–C1589]

SP's post-Flood source difference is **120**, from Eber and official Terah each contributing 60 fewer lifespan years. Reversal changes its lower leg from 3310 to 1330, contracting it by 1980. The MT–SP inverse Flood separation therefore becomes **120 + 1980 = 2100**. This is generated before selecting a restoration target. [File18 §3.2.1; C1590–C1592]

| MSS | Original lower leg | Inverse lower leg | Completed inverse Flood, BC | Span to 536 BC |
|---|---:|---:|---:|---:|
| MT | 3430 | 3430 | 7536 | **7000** |
| LXX | 4340 | 4340 | 8446 | **7910** |
| SP | 3310 | 1330 | 5436 | **4900** |

All three lower inverse legs are multiples of 70: **49, 62 and 19 units**. Completing the Nativity stage and measuring to restoration adds the same amount to each:

\[
2700+(1406-536)=3570=51\times70.
\]

Their restoration spans are consequently **100, 113 and 70 units of 70**. The LXX 7910 is the third member of this fixed comparison. Moving its target from restoration 536 to Exodus 1446 removes the same source-derived 910 and gives **8446−1446 = 7000**, matching MT 7536−536. Its unsimplified 7910 also equals the LXX Regular inverse Flood–Nativity interval, 7916−6: the two start points and two targets differ by the same 530. [C1595–C1599]

### One 7000-year packet connects MT, LXX and SP

The 910 transport preserves a complete ordered packet, including both internal nodes:

| Node in the comparison | MT-based packet, BC | LXX packet, BC |
|---|---:|---:|
| Completed inverse cumulative Flood | 7536 | 8446 |
| Ordinary cumulative Shem | 5436 | 6346 |
| Ordinary / held-inverse cumulative Flood | 4836 | 5746 |
| Appointed target | 536, restoration | 1446, Exodus |

Every corresponding node differs by 910, and both packets have the same partition:

\[
7000=2100+600+4300,\qquad4900=600+4300.
\]

SP enters at the MT packet's Shem coordinate: **5436 is also the completed SP inverse cumulative Flood**. The source condition for that junction is \(2700-(120+1980)=600\). The common stage displacement, the SP source/reversal difference and Shem's lifespan therefore explain why the two constructions meet. [C1592, C1600–C1603]

This transport belongs to the specified packet. The primary inverse cumulative Creation heads have different upper inverse legs, 7190 in MT and 5190 in LXX, so their whole-head difference is \(910-2000=-1090\). Likewise, keeping the Flood and Shem cuts preserves the lower 910 transport, whereas reversing Conquest–Shem as one leg produces a 1900 difference. The named cuts remain part of the explanation. [C1593–C1594, C1604]

### Shem's 600 years join restoration to the Jubilee endpoint

A second whole-interval translation joins the Babylonian comparison directly to the SP Jubilee chain. MT cumulative Shem **5436 BC → Flood 4836 BC** is 600 years, and **536 BC → AD 65** is also 600 civil years:

\[
536+65-1=600.
\]

Both endpoints of the 4900-year interval therefore move forward together:

| Placement | Start | End | Years |
|---|---:|---:|---:|
| LXX Shem | 6346 BC | 1446 BC | **4900** |
| MT Shem / SP inverse Flood | 5436 BC | 536 BC | **4900** |
| MT Flood | 4836 BC | AD 65 | **4900** |

The successive forward translations are **910 and 600 years**. The final row is exactly the last **10 Jubilees** of the SP **13 + 10** division. Thus the restoration interval reaches the AD 65 interval through Shem's named lifespan, while SP supplies an inverse Flood at the shared 5436 junction. All three rows use ordinary same-side or civil elapsed counting. The separate Rounded AD 2166 transport below retains its own convention. [C1617–C1619]

The SP 9800 and 11270 comparisons also have one source calculation: \(4100+7100=11200=8\times1400\). Subtracting one 1400 gives 9800 to Conquest; adding the civil 70 from 6 BC to AD 65 gives 11270. Their two Jubilee counts are linked because Conquest→AD 65 is already **3×490**. The LXX self-retained Flood at 5746 supplies a finer cut in the existing SP–MT chain:

\[
11206\to5746\to4836\to1406\text{ BC}\to\text{AD }65,
\]
\[
(78+13+49+21)\times70=161\times70=23\times490.
\]

The first two pieces recombine into 13 Jubilees. The fixed comparison of all six primary spines retains the other values: among completed Flood nodes, SP Regular alone meets both selected Jubilee targets exactly. [C1612–C1616]

### One ordered path contains the new large spans

Keeping the MT inverse Flood inside the established LXX–SP comparison gives

\[
13136\longrightarrow7536\longrightarrow5436\longrightarrow536\text{ BC},
\]
\[
12600=5600+2100+4900=(8+3+7)\times700.
\]

The LXX Regular inverse head, MT inverse cumulative Flood and SP inverse cumulative Flood each contribute a named node. Keeping the MT cut gives **5600 + 7000**; keeping the SP cut gives the inherited **7700 + 4900**. Both are coarser partitions of this same path. Its first two edges follow directly from the inverse source words: \(5600=9030-3430\) and \(2100=3430-1330\). [C1605–C1609]

The existing Minimum Covenant point **1866 BC** can also remain between 5436 and 536. The resulting partition is

\[
12600=5600+2100+3570+1330.
\]

Its first three components total **11270 = 23×490**, the established LXX-head→Covenant radius; its final three total **7000**, and its final two **4900**. This joins the Flood, Babylonian and Covenant comparisons in one ordered structure. The repeated displays share these source nodes and are not independent confirmations. [C1625]


## Complete fixed Flood-target comparison

The following table contains all twelve primary Flood nodes, two stages for each of sixspines, against the three already-appointed targets. These 36 comparisons are a bounded diagnostic table, not a random sample or significance estimate. Values to AD 65 use civil B+A −1. All other displayed targets here are BC.

| Family | Stage | Flood BC | To 6 BC | To 1406 BC | To AD 65 civil |
|---|---|---:|---:|---:|---:|
| MT Regular | held | 6416 | 6410 | 5010 | 6480 |
| MT Regular | completed | 9116 | 9110 | 7710 | 9180 |
| MT Cumulative | held | 4836 | 4830 | 3430 | 4900 |
| MT Cumulative | completed | 7536 | 7530 | 6130 | 7600 |
| LXX Regular | held | 5216 | 5210 | 3810 | 5280 |
| LXX Regular | completed | 7916 | 7910 | 6510 | 7980 |
| LXX Cumulative | held | 5746 | 5740 | 4340 | 5810 |
| LXX Cumulative | completed | 8446 | 8440 | 7040 | 8510 |
| SP Regular | held | 8506 | 8500 | 7100 | 8570 |
| SP Regular | completed | 11206 | 11200 | 9800 | 11270 |
| SP Cumulative | held | 2736 | 2730 | 1330 | 2800 |
| SP Cumulative | completed | 5436 | 5430 | 4030 | 5500 |

Complete remainders modulo 70 and 490 are retained in the model JSON. Since 1406 BC→AD 65=1470=3×490, the two Jubilee tests are one residue condition at two named targets. Completed SP Regular is the exact native-family success. LXX Regular shares the 70 grid; MT Regular has residue 10.

## Source and inference controls

File18 supplies the actual life rows; File51a independently rounds whole lifespans and supplies the 1025-year Abraham–Moses suffix. A provisional 1000-year suffix used in a preparation assertion was rejected: the actual rounded suffix is 1025=2431−1406. This correction was made before the affected action was closed. The source-row differences 910 and 120 were unaffected.

The three-manuscript 910/2100 differences, the source quantities and target coincidences remain visible in `model/dependency_ledger.json`. The rank 3 description of six distances in the 7000 packet is a conditional interval compression, not proof of global minimality. The complete inverse trees do not share a universal 910 translation: changing the Shem cut gives 1900, and the primary cumulative Creation heads differ by −1090 because of the upper legs.

The shared 5436 coordinate retains both roles: ordinary MT cumulative Shem and SP completed inversecumulative Flood. MT also retains 5436 in its Flood-plus-Shem inverse prefix; reversing the whole Conquest–Shem leg instead gives 4446. No ordinary historical biography is substituted for a cumulative serial boundary.

The 600 translation to AD 65 is civil. The separate 2700 translation to Rounded AD 2166 uses File52c’smod-5 coordinate convention. Deeper mirror analysis and a second decimal reversal remain deferred. Canonical source files and all preceding sealed records remain untouched.

## Verification and reproducibility

Run `python3 verify_cycle.py --require-50` from the extracted evidence packet. The independent verifier uses only the Python standard library. It reads frozen source rows, reconstructs the six source spines, uses numeric-division decimal reversal independently of the construction code, checks all model outputs and the journal’s predecessor chain, and verifies payload hashes. The grouped check count is an implementation audit, not a count of independent discoveries.

The evidence includes the source-review notes, arithmetic review, full source bindings, original reader, dated Strategy reviews, model files and all 50 sequential questions/results/reassessments. The stages include source synthesis, numerical analysis, integration and validation.

## Sequential questions and reassessments

### C1585 — Choose source-generated connections over another endpoint scan

**Question:** Which fixed objects and operations can explain the new Flood and Abram endpoints without widening the mirror study?

**Result:** The new task is a comparison of named paths and source differences. The three supplied spans are fixed targets for explanation, not results of a new search.

**Reassessment:** Start with the inherited post-Flood rows: they may explain the 910 and 120 differences entering the inverse Floods.

### C1586 — Recover the rounded post-Flood lifespan suffix

**Question:** What do the controlled Arphaxad-through-Terah lifespan rows contribute before the shared Abraham–Moses suffix?

**Result:** The rounded suffix totals are MT 2405, LXX 3315 and SP 2285. Adding the source-controlled 1025-year Abraham–Moses suffix produces 3430, 4340 and 3310; the provisional 1000 suffix was rejected.

**Reassessment:** Decompose the LXX increment row by row; do not infer it from the endpoint 910 alone.

### C1587 — Resolve the 910 translation into named row changes

**Question:** Is the native LXX Flood displacement 460+430, or does the rounded post-Flood source require a different decomposition?

**Result:** At the Flood the 910 is 460+450, with 450=25+25+40+100+100+100+60. Terah contributes zero. Rounding reduces the actual 914 by 4 in Arphaxad and Shelah.

**Reassessment:** Keep 430 for its proper later role; next identify the SP 120 displacement from its own rows.

### C1588 — Locate the SP source displacement

**Question:** Which local lifespan differences produce the 120-year SP cumulative Flood displacement?

**Result:** SP Eber and official Terah each subtract 60; all other shared post-Flood rounded lives agree with MT. Their 120 reduction is inherited from source rows.

**Reassessment:** Determine how far the MT–LXX 910 and MT–SP 120 translations propagate before the upper source lives change them.

### C1589 — Separate the Flood plateau from the Creation difference

**Question:** Does 910 translate the whole MT–LXX cumulative genealogy, or only a named part of it?

**Result:** Equal 600-year Shem and 950-year Noah lives preserve 910 through those boundaries. LXX Lamech 755 versus MT 775 then reduces it to 890=460+430 at Creation.

**Reassessment:** The correct source explanation is local: now test which of these source differences survives the declared lower-leg reversal.

### C1590 — Carry source differences into the inverse lower legs

**Question:** Which of the source-generated 910 and 120 differences survive reversal of the complete Flood–Conquest leg?

**Result:** The MT and LXX legs are individually self-reversing, retaining 910. SP 3310 becomes 1330, so its 120 source gap below MT becomes 2100 in the inverse construction.

**Reassessment:** Explain the SP amplification from decimal place values, then identify the source condition behind its MT Shem coincidence.

### C1591 — Explain the SP 2100 gap by its source and place values

**Question:** Can the change 120→2100 be decomposed without choosing a restoration target?

**Result:** SP first and last core digits differ by 2, producing a 1980 contraction. The inverse MT–SP separation is therefore 120+1980=2100 before any 536 comparison is made.

**Reassessment:** Use that already-derived separation with the common 2700 stage shift and Shem 600.

### C1592 — Derive the SP inverse Flood–MT Shem junction

**Question:** Why does the completed SP inverse Flood land at the ordinary Rounded MT Cumulative Shem boundary?

**Result:** The source and operation supply 2700−2100=600. Consequently the completed SP inverse Flood lies exactly one Shem lifespan earlier than the held MT Flood, at 5436.

**Reassessment:** This is the informative cross-family condition; test whether the MT–LXX 910 transport survives changing the named cut.

### C1593 — Test the domain of the 910 transport

**Question:** Does translating the source biographies by 910 imply that every inverse partition also translates by 910?

**Result:** No. Keeping Flood and Shem as separate legs preserves 910, but reversing the whole Conquest–Shem leg gives a 1900 difference. The extra 990 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.

### C1594 — Identify the complete shared inverse prefix

**Question:** With Flood, Shem and Noah cuts retained, how far does the 910 inverse translation extend?

**Result:** The Flood–Shem–Noah inverse prefixes translate by 910 after the common Conquest root. The upper Creation legs then contribute 4030 more, giving the inherited 4940 head gap.

**Reassessment:** Use the proven lower-prefix domain for the restoration comparison; do not extend 910 to the full inverse trees.

### C1595 — Complete the three-manuscript restoration comparison

**Question:** What is the LXX member when the same completed inverse Flood construction is compared with the already-selected 536 target?

**Result:** The whole fixed family is MT 7000, LXX 7910, SP 4900: 100, 113, 70 units of 70. LXX is reported with its 490 remainder 70; it is not forced into the same Jubilee count.

**Reassessment:** Explain why all three occupy this 70-year grid despite the 2700 displacement itself not being divisible by 70.

### C1596 — Derive the common 51-unit restoration addition

**Question:** What source-appointed anchor relation converts the 49, 62, 19 lower-leg indices into 100, 113, 70?

**Result:** The anchor displacement 2700 and Conquest–restoration 870 add to 3570=51×70. Their residues 40 and 30 complete one 70; the same addition explains all three rows.

**Reassessment:** Now separate the between-manuscript distances from this common target placement.

### C1597 — Join the Babylonian 70 and Egypt 430 measures in the same source gap

**Question:** How does the LXX–SP separation combine the independently derived 910 and 2100 differences?

**Result:** The LXX–SP inverse Flood gap is 3010=910+2100=43×70=7×430. It comes from their 1030 source gap plus the SP 1980 contraction; it is one interval with two descriptions.

**Reassessment:** Test the already-appointed Exodus target 1446 on the LXX row rather than looking for a new target.

### C1598 — Transport the 7000 from restoration to Exodus

**Question:** Does the source-derived MT–LXX 910 map the new 7000 interval to the selected Exodus anchor?

**Result:** MT 7536→536 and LXX 8446→1446 are exact 910 translations and both 7000. The LXX 7910 to restoration becomes 7000 by moving the target as well as the source node.

**Reassessment:** Account for 7910 within the LXX Regular/Cumulative relation, so the unsimplified third row also has a structural role.

### C1599 — Explain the LXX 7910 through its Regular/Cumulative lower-leg difference

**Question:** Can the LXX restoration 7910 be related to an existing source-appointed LXX Regular interval?

**Result:** The inverse Flood gap 4340−3810=530 matches 536−6. Thus LXX 8446→536 and 7916→6 both measure 7910; the held-stage pair similarly preserves 5210.

**Reassessment:** The restoration family now has three explained members. Build the full named-node 7000 packet next.

### C1600 — Retain all the named nodes inside the MT 7000

**Question:** Can 7000 and 4900 be explained together by the existing MT/SP Flood and Shem junctions?

**Result:** MT 7536→SP 5436/MT Shem→MT 4836→536 has 2100+600+4300=7000. Its lower two edges give 4900=600+4300 and its upper two give 2700=2100+600.

**Reassessment:** Test every corresponding node in the LXX packet, rather than checking only its total 7000.

### C1601 — Verify the whole MT–LXX 7000 packet

**Question:** Does the 910 translation preserve the two internal nodes as well as the endpoints?

**Result:** Every node maps: 7536/5436/4836/536 becomes 8446/6346/5746/1446. Both packets have the same 2100|600|4300 partition.

**Reassessment:** Identify the few quantities that reconstruct this whole packet and separate them from derived spans.

### C1602 — Compress the two packets into one source-tagged formula

**Question:** Which measured quantities reconstruct both ordered four-node packets?

**Result:** Relative to the selected target, both packets are(D+R, L+R, R, 0) with D 2700, L 600, R 4300. MT obtains R as 3430+870; LXX as 4340−40.

**Reassessment:** Count the dependent interval displays explicitly; their repetition must not be mistaken for independent evidence.

### C1603 — Separate packet parameters from its six interval displays

**Question:** How many interval degrees of freedom does the ordered 7000 packet contain?

**Result:** The six pairwise distances have rank 3 in D, L, R. The 7000, 4900, 4300, 2700, 2100 and 600 displays belong to one packet, with source conditions retained.

**Reassessment:** Test whether adjoining the primary cumulative Creation heads preserves the same 910 transport.

### C1604 — Locate the boundary of the common packet

**Question:** Can the primary cumulative Creation heads be appended under the same 910 translation?

**Result:** No. LXX upper leg 9150 reverses to 5190 versus MT 9170→7190, adding −2000. The complete primary head difference is 910−2000=−1090, so the shared packet is local.

**Reassessment:** Use the independently named LXX Regular head to refine the 12600 comparison, without claiming a global cumulative translation.

### C1605 — Divide the LXX 12600 at the MT inverse Flood

**Question:** Does the new 7000 supply a named internal cut in the existing LXX 12600 interval?

**Result:** LXX 13136→MT 7536→536 divides 12600 into 5600+7000. The new Flood observation therefore refines an established large interval directly.

**Reassessment:** Retain the SP inverse Flood too, to see the full three-manuscript ordered comparison.

### C1606 — Form the common three-manuscript 12600 refinement

**Question:** Can all three manuscripts occupy independently named nodes in one ordered 12600 path?

**Result:** The path 13136→7536→5436→536 has 5600+2100+4900=(8+3+7)×700. LXX supplies the head, MT the first Flood cut, SP the second.

**Reassessment:** Compare its coarser partitions with the inherited 7700+4900 and the new 5600+7000.

### C1607 — Explain two large-span partitions as coarsenings of one path

**Question:** Are 7700+4900 and 5600+7000 separate structures, or do they share a named common refinement?

**Result:** Both follow from the same 5600|2100|4900 path. Keeping the SP cut gives 7700+4900; keeping the MT cut gives 5600+7000.

**Reassessment:** Identify the common unit for this selected path without claiming every spine node lies on it.

### C1608 — Identify the selected 700-year grid and its domain

**Question:** Does the common refinement admit a compact integer coordinate description, and does the omitted LXX cumulative Flood share it?

**Result:** The chosen path has relative indices 18, 10, 7, 0 in units 700. LXX cumulative Flood 8446 has remainder 210 on that grid, though it remains on the finer 70 grid.

**Reassessment:** The 700 grid is a property of this named subpath. Derive its 5600 edge directly from the inverse source words.

### C1609 — Recover the new refinement from source words

**Question:** Do the 5600 and 2100 internal edges depend on choosing 536 after the fact?

**Result:** They do not: 5600=9030−3430 and 2100=3430−1330, with the common 4106 base canceling. Only the final 4900 placement uses the appointed restoration target.

**Reassessment:** The source-derived path is ready for the already-authorized forward 2700 transport; keep the operation distinct from a new mirror investigation.

### C1610 — Transport the whole common refinement to Rounded AD 2166

**Question:** Does the authorized 2700 shift preserve the newly identified internal MT/SP cuts as well as the three total spans?

**Result:** Yes: 10436→4836→2736→Rounded AD 2166 retains 5600|2100|4900. The 7000 and 12600 totals are coarsenings of that same translated path.

**Reassessment:** Identify its connection to the existing civil Jubilee chain at the shared MT Flood node.

### C1611 — Locate the shared node connecting the two endpoint families

**Question:** Where does the translated Babylonian/Abram packet meet the SP Jubilee comparison?

**Result:** They meet at MT 4836: it is 7000 to Rounded AD 2166 and 4900 to civil AD 65. The new connection uses an established node shared by the two declared comparisons.

**Reassessment:** Explain the SP 9800 and 11270 from its original reversed prefix, keeping the civil AD 65 convention.

### C1612 — Derive both SP Jubilee observations from one reversed prefix

**Question:** What common source calculation generates 9800 to Conquest and 11270 to AD 65?

**Result:** SP 4100+7100=11200=8×1400. Subtracting one 1400 gives 9800; adding the civil 70 from 6 BC to AD 65 gives 11270.

**Reassessment:** Compare the whole fixed six-spine Flood family so that the scope of the SP success is explicit.

### C1613 — Compare the two Jubilee targets across every primary Flood spine

**Question:** Is the SP pair shared by all six primary spines under the same two anchor stages?

**Result:** Among completed primary Floods, SP Regular alone gives exact 490 multiples to both 1406 BC and AD 65. The complete 12-node/36-span table retains all other values and remainders.

**Reassessment:** Determine how much of the paired target success is forced by the relation between the targets.

### C1614 — Separate the SP source constraint from repeated target counts

**Question:** Are the 9800 and 11270 divisibilities independent numerical conditions?

**Result:** Their common source placement is substantive, but the second 490 divisibility follows from the first because Conquest→AD 65 is 3×490. The same 70 residue persists across all three selected targets.

**Reassessment:** Use the inherited MT 7-Jubilee Flood leg to explain the internal 13|7|3 partition.

### C1615 — Explain the 13|7|3 division from its source-appointed anchors

**Question:** What information generates the internal 13-Jubilee leg of the SP 11270 comparison?

**Result:** SP supplies 20 Jubilees to Conquest, MT supplies the retained 7-Jubilee Flood leg, and Conquest→AD 65 supplies 3. The first 13 is their 20−7 difference.

**Reassessment:** Insert the LXX self-retained cumulative Flood at its independently known location and inspect the finer units.

### C1616 — Add the LXX cut to the SP–MT Jubilee comparison

**Question:** How does the source-derived LXX 910 fit inside the existing 23-Jubilee interval?

**Result:** SP 11206→LXX 5746→MT 4836→1406→AD 65 has(78+13+49+21)×70. The first two pieces recombine into 13 Jubilees; the LXX cut exposes the shared 70-year scale.

**Reassessment:** Use the common MT 4836 node to test a direct transport of the already-established 4900 restoration interval.

### C1617 — Join restoration and AD 65 by the 600-year Shem translation

**Question:** Does the named Shem–Flood lifespan transport the 4900 restoration interval into the Jubilee chain without a new target?

**Result:** Yes. Both endpoints advance 600 civil years: 5436→4836 BC and 536 BC→AD 65. Thus the SP inverse Flood/MT Shem 4900 reaches the MT Flood→AD 65 ten-Jubilee interval.

**Reassessment:** Adjoin the already-proved LXX 910 transport to display a complete three-placement 4900 family.

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

**Question:** Can the new 600 relation extend the inherited 910 comparison using only already-appointed nodes?

**Result:** The 4900 family runs LXX 6346→1446, MT/SP 5436→536, MT 4836→AD 65, with whole-interval translations 910 then 600. It joins Exodus, restoration and the NT endpoint through named source boundaries.

**Reassessment:** Specify the source roles at 5436 so that the connection is not misread as a universal inverse-Shem identity.

### C1619 — Preserve the meaning of the shared 5436 junction

**Question:** Which declaredinverse paths actually support the 5436 node used by the 4900 transport?

**Result:** 5436 is the primary SP completed inverse Flood and ordinary MT cumulative Shem; MT also retains it when Flood and Shem are separate inverse legs. The whole-Shem inverse branch is 4446.

**Reassessment:** These source-tagged junctions now support a compact dependency graph; use it to choose what belongs in the explanation.

### C1620 — Assemble one source-to-comparison reconstruction

**Question:** Can the new packet be reconstructed with the existing six native spine inputs and operator inventory?

**Result:** The inherited six-spine generator supplies every inverse node used here. The new comparisons require no added reversal rule or free endpoint; they connect existing named outputs and targets.

**Reassessment:** Revisit the primary mode gaps as the combination of these lower Flood modules and their upper source legs.

### C1621 — Relate the new Flood connections to the primary head differences

**Question:** How do the locally shared Flood comparisons coexist with MT convergence and LXX/SP head displacement?

**Result:** Each primary mode gap is a lower-plus-upper balance: MT −1580+1580=0; LXX 530−30=500; SP −5770+5580=−190. The new lower-node packets therefore complement, rather than replace, the original head explanation.

**Reassessment:** Separate source constraints from translation consequences in one dependency ledger.

### C1622 — Classify what each new relation actually explains

**Question:** Which numerical agreements depend on source choices, and which follow from an admitted transport?

**Result:** Eight connected families now have explicit source conditions and consequences. Repeated interval displays are grouped under their generating condition; no statistical-independence or historical-priority claim is added.

**Reassessment:** Preserve the contrasting cases that define the range of this explanatory kernel.

### C1623 — Freeze the demonstrated range of the explanation

**Question:** What must the synthesis retain to avoid turning local agreements into an unsupported universal map?

**Result:** The successful packets have explicit ranges. The known cut, head, grid and counting distinctions are retained in one compact scope ledger rather than reopened as further searches.

**Reassessment:** Choose the small set of reader-facing additions that best advance the Strategy.

### C1624 — Choose the compact synthesis for the explanation report

**Question:** Which results merit the main narrative, and which belong in the reproducible companion?

**Result:** The main addition will emphasize complete named paths, the source-generated 910/2100 differences, and the 600 translation linking restoration to AD 65. Detailed residue tables remain in the companion.

**Reassessment:** Draft the concise report integration and have its source roles and conventions independently reviewed.

### C1625 — Connect the Flood refinement to the Covenant family

**Question:** Can the existing 1866 Minimum Covenant cut be retained alongside both inverse Flood cuts?

**Result:** The single BC path 13136→7536→5436→1866→536 has 5600+2100+3570+1330. It preserves 12600, 7000, 4900 and the 11270 Covenant radius in one source-tagged refinement.

**Reassessment:** The larger Strategy connection is now explicit. Integrate the source mechanisms and common paths without adding more endpoints.

### C1626 — Integrate the source mechanisms and common paths into the reader

**Question:** Can the principal findings be presented as a connected explanation without a new mirror branch?

**Result:** The reader now connects local source differences to the 7000, 4900, 12600, Jubilee and Covenant paths; deeper mirror analysis remains deferred.

**Reassessment:** Have the new source roles and counting conventions independently reviewed before finalizing the prose.

### C1627 — Review manuscript roles and counting conventions independently

**Question:** Do the integrated source explanations and transported packets preserve every declared manuscript role and width convention?

**Result:** The independent review confirms the source states and all new paths. Four wording clarifications now distinguish inverse heads, inverse Floods and the Lamech-to-Creation plateau.

**Reassessment:** Run the independent source-based verifier over every persisted model and journal binding.

### C1628 — Verify all source-derived models independently

**Question:** Do independent numeric reversal and direct source-row reconstruction reproduce every persisted mathematical model?

**Result:** All 42 models are covered by 44 independent arithmetic/integrity groups. The verifier reconstructs source rows and uses numeric decimal reversal; all results and journal bindings agree.

**Reassessment:** Build the readable continuation with the complete fixed comparison and explicit source/inference distinctions.

### C1629 — Prepare the readable continuation and research ledger

**Question:** Does the companion preserve the actual questions, results and reassessments while clearly distinguishing inherited information and new synthesis?

**Result:** The continuation records the full comparison, source explanation, retained limits and sequential reassessments. It discloses the corrected preparation assumption and distinguishes synthesis from independent discovery.

**Reassessment:** Typeset the expanded reader, then inspect the new pages and all changed section transitions.

### C1630 — Typeset the integrated chronological-family explanation

**Question:** Does the expanded explanation render with intact equations, tables and the retained source citations?

**Result:** The integrated reader typesets successfully with all equations and tables present. The initial print version is 30 pages.

**Reassessment:** Inspect page images, especially the new table lead-ins and the transition into the Rounded note.

### C1631 — Review the rendered pages and section transitions

**Question:** Are the new source tables, interval packets and retained Rounded note legible and coherently placed in the printable report?

**Result:** All 30 pages were reviewed. The one table lead-in break is corrected; the new packet tables and Rounded endpoint section are legible and intact.

**Reassessment:** Check the actual evidence package after extraction to a different directory.

### C1632 — Check portable reconstruction from the packaged evidence

**Question:** Do the evidence paths and independent verification work after relocation, using the archive payloads rather than the working directory?

**Result:** The extracted evidence reproduces all current models and journal links from a different working directory, with 91 payload hashes passing.

**Reassessment:** Before the final Strategy review, relate the 910/120 source differences to the existing compact post-Flood row parameters.

### C1633 — Connect the Flood source differences to the existing row-parameter grammar

**Question:** Can the rounded 910 and 120 use the already-established century, 60-year and paired-row contributions without adding an inverse-specific primitive?

**Result:** The rounded LXX correction is 4×100+2×25=450 because Eber 40 and Nahor 60 complete one century. Cainan adds 460. SP keeps −2×60=−120. The inverse lower legs thus reuse the established source-row grammar.

**Reassessment:** Reread the full Strategy afresh and assess the 50-step cycle against its larger explanatory objective.

### C1634 — Reread the Strategy and reassess the completed 50-step cycle

**Question:** Does the present source-to-spine synthesis advance the Strategy’s larger goal, and what remains genuinely unexplained?

**Result:** The full Strategy reread confirms that this cycle advances the common grammar goal through source mechanisms and whole named packets. The remaining burden is the origin and compression of the fitted source constraints, not more endpoint matches.

**Reassessment:** Deliver the integrated explanation and reproducible fifty-action record. Keep deeper mirrors and second decimal reversal deferred.

## Strongest unresolved question

The new connections explain what follows from the selected source rows. The remaining source-generation question is why the post-Flood lifespan adjustments, their named positions and the pre-Flood choices take these values. The best next bounded study should address those shared source constraints through the existing row model, with a declared subset of inputs, rather than extend the mirror branch or search more endpoint divisibilities.

