C1622 — Classify what each new relation actually explains
Question
Which numerical agreements depend on source choices, and which follow from an admitted transport?
Sources
[
"Strategy §§5D,F,6",
"current cycle models"
]
Opened utc
2026-09-29T15:04:17.534586+00:00
Results
[
{
"family": "MT–LXX Flood910",
"source_condition": "rounded row differences460+450",
"consequence": "equal Shem/Noah lives and self-reversing lower legs carry910 to selected inverse prefixes"
},
{
"family": "SP–MT inverse gap2100",
"source_condition": "Eber/Terah120 plus SP reversal1980",
"consequence": "common stage shift preserves2100"
},
{
"family": "5436 junction",
"source_condition": "2700−2100 equals independently supplied Shem600",
"consequence": "SP completed inverse Flood shares ordinary MT Shem coordinate"
},
{
"family": "7000 packets",
"source_condition": "MT–LXX910 also equals Exodus–restoration910",
"consequence": "all four nodes and all six pairwise distances translate"
},
{
"family": "4900 toAD65",
"source_condition": "Shem600 also equals civil restoration→AD65",
"consequence": "the4900 interval transports from Shem/restoration to Flood/AD65"
},
{
"family": "12600 refinement",
"source_condition": "LXX inverse sum9030−MT lower3430=5600",
"consequence": "retain MT/SP nodes to recover5600+2100+4900; coarse partitions follow"
},
{
"family": "SP23 Jubilees",
"source_condition": "SP inverse prefix11200 and Conquest displacement1400 give9800",
"consequence": "AD65 adds3 Jubilees; MT leg7 yields13|7|3"
},
{
"family": "RoundedAD2166",
"source_condition": "q(536BC)+2700 equals negative q(Abram2166BC)",
"consequence": "whole translated path preserves its intervals"
}
]
Finding
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.
Checks
{}
Closed utc
2026-09-29T15:04:17.535132+00:00
Record provenance
Exact record hash: 0d2674e7265ef03ddb5c73dac51dee8c08121ff4c0c082263b9c0659b40de1d9
Source journal: Research_Cycles/C1585_C1634/journal.json