{ "title": "SP manuscript modules for the chronological-family synthesis", "scope": "Reader-facing modules integrating C953–C983 with earlier complete-family results; conditional mathematical reconstruction, without statistical or historical-origin claims.", "overarching_thesis": { "text": "The chronological families fit together as different measurements of ordered source structures, connected by operations whose inputs, counting conventions, and anchors remain explicit. Local changes such as conserved lifespan repartition, inserted rows, rounding, and the SP Flood cap generate entire comparison fields, allowing compatibility to be explained while retaining each family's distinct chronology. A useful unifying account therefore combines a small set of source-qualified constructions with an explanation of what each representation retains or loses, while treating historical origin as a separate question.", "sentences": [ "The chronological families fit together as different measurements of ordered source structures, connected by operations whose inputs, counting conventions, and anchors remain explicit.", "Local changes such as conserved lifespan repartition, inserted rows, rounding, and the SP Flood cap generate entire comparison fields, allowing compatibility to be explained while retaining each family's distinct chronology.", "A useful unifying account therefore combines a small set of source-qualified constructions with an explanation of what each representation retains or loses, while treating historical origin as a separate question." ], "sources": [ { "file": "Research Strategy", "sections": [ "§1", "§3.2", "§5, Stages B–H", "§6" ] } ], "steps": [ "C733–C770", "C905–C906", "C953–C983" ] }, "modules": [ { "id": "regular_cumulative_same_ledger", "title": "Two measurements of one ordered genealogy", "text": "Regular and Cumulative chronology can be read as two measurements of the same ordered genealogical rows. Regular chronology accumulates the effective interval from one birth to the next; Cumulative chronology accumulates the selected lifespan of each person. For a compatible row, begetting age plus remaining years equals lifespan. Moving years between the two parts can therefore change the Regular chain while leaving the Cumulative contribution unchanged. Adam's 130 + 800 and 230 + 700 both preserve 930.\n\nThis local distinction generates a whole comparison field. If G is the difference between corresponding Cumulative and Regular coordinates, each adjacent change in G equals the lifespan minus the effective Regular interval. One terminal placement and the ordered row contributions reconstruct every intermediate comparison. The rule works across the complete MT, LXX, and SP source profiles, provided their inserted rows and counting conventions remain explicit.\n\nThe SP cap adds a mechanism that changes the lifespan itself. Birth distances determine which ancestral lives encounter the Flood boundary, and the resulting reductions pass into the Cumulative field by the same ordered accumulation. This explains why shared births need not imply shared Cumulative dates: the aligned SP-with-Cainan and native LXX birth path retains different lifespan measurements.", "sources": [ { "file": "Research Strategy", "sections": [ "§3.2", "§5, Stages B and G" ] }, { "file": "File18", "sections": [ "§§2.1.3–2.2", "§§3.1–3.2", "§4.1", "§§6A–6D" ] }, { "file": "File09", "sections": [ "§§0.3–0.4" ] } ], "steps": [ "C733–C748", "C787–C788", "C954–C956", "C972–C973" ], "word_count": 200 }, { "id": "sp_cap_forward_full_family", "title": "A shared Flood boundary explains the whole SP family", "text": "The SP Flood cap begins with independently declared kinds of information: ordered begetting intervals, a Noah–Flood relation, and a baseline lifespan ledger. In the native SP G2 frame, primary Noah is placed at 3493 BC and Flood start at 2893 BC. Working backward through the nine completed begetting intervals reconstructs every birth from Adam through Lamech. Lamech's 53rd counted year contributes 52 completed units in this chain.\n\nFor each birth B, the inclusive capacity to Flood start is B − 2893 + 1. The rule selects the smaller of that capacity and the baseline lifespan. Applied to all nine rows, it gives Adam 930, Seth 912, Enosh 905, Kenan 910, Mahalalel 895, Jared 847, Enoch 365, Methuselah 720, and Lamech 653. Six baseline lives remain unchanged; three meet the shared boundary. Their inclusive counts place the selected deaths at Flood start, while the other six deaths retain ordinary subtraction.\n\nThe three reductions, 115, 249, and 124 relative to the MT ledger, generate every pre-Flood Cumulative displacement and sum to 488. Eber and official Terah supply a separate 120, producing the established 608 difference. The shared rule thus explains both the local changes and their accumulated effect; Noah remains outside the cap domain.", "sources": [ { "file": "File18", "sections": [ "§2.1.3", "§3.1", "§3.1.3", "§6C" ] }, { "file": "Research Strategy", "sections": [ "§5, Stage B", "§8, main unresolved reconstruction task" ] } ], "steps": [ "C741", "C953–C959", "C972–C973", "C983" ], "word_count": 202 }, { "id": "conditional_inverse_ages", "title": "What the capped lives determine about the ages", "text": "The Flood-cap relation can also be read backward, but only with its retained premises in view. Fix the Noah–Flood relation at 600 completed units, so that the inclusive contribution is 601. Lamech's capped life of 653 then leaves 52 completed units from his birth to Noah's. Methuselah's 720 exceeds Lamech's capacity by 67, recovering his begetting interval. Jared's 847 exceeds Methuselah's capacity by 127, recovering the combined Jared–Enoch interval.\n\nThese three equations determine three quantities. They do not separate Jared from Enoch. When Enoch's independently supplied 65 is held, Jared's interval is fixed at 62. Without that input, adding one unit to Jared's begetting age and subtracting one from Enoch's changes Enoch's birth while preserving all nine capped lifespan outputs. The earlier five begetting ages are likewise not determined by these three active capacities.\n\nThe distinction matters for the wider unification. A complete ordered boundary field can recover its local intervals by adjacent differences; selected capped outputs retain less information. The source's exact lifespan values fix the inclusive contribution at 601, whereas merely naming the same three clipped rows permits a wider range. Forward and backward readings therefore express one conditional relation, rather than two separate reasons to accept its premises.", "sources": [ { "file": "File18", "sections": [ "§3.1", "§3.1.3" ] }, { "file": "Research Strategy", "sections": [ "§5, Stages D and F", "§6" ] } ], "steps": [ "C747–C748", "C960–C967", "C971" ], "word_count": 201 }, { "id": "clipping_information_loss", "title": "Why the cap cannot identify the ancestral ledger", "text": "A cap preserves a value when it lies below the available capacity and removes any excess above that capacity. Its output therefore carries different information in the two cases. An uncapped lifespan identifies its input exactly. A lifespan equal to the capacity only tells us that the input was at least that large. The amount removed cannot be recovered from the capped result alone.\n\nThis distinction is visible across the full SP family. Both the MT baseline, with Lamech's 777, and the main LXX baseline, with his 753, produce the same nine SP lives under the fixed SP capacities. Their total reductions differ by 24, but the output no longer records that difference. Even supplying the three changed MT lifespans as an unordered set leaves four assignments to Jared, Methuselah, and Lamech that produce the same clipped values. The source's person-by-person placement remains necessary.\n\nThe cap consequently belongs to a different class of operation from a reversible frame translation. Applying the same cap twice changes nothing after the first application, and multiple inputs can share one output. This explains a route to compatibility between traditions while also limiting the historical claim: agreement of the capped fields does not identify which ancestral ledger came first.", "sources": [ { "file": "File18", "sections": [ "§2.1.3", "§3.1.3", "§4.1" ] }, { "file": "Research Strategy", "sections": [ "§1", "§5, Stages D, E and G" ] } ], "steps": [ "C905–C906", "C968–C970", "C982" ], "word_count": 204 }, { "id": "rounded_count_interface", "title": "The cap connects to Rounded chronology through counts", "text": "Rounded chronology acts on declared row quantities before those quantities are accumulated. Regular births use rounded begetting intervals; theoretical Regular deaths combine rounded begetting and remaining years; Cumulative chronology rounds lifespan counts. These procedures can disagree because rounding a sum need not equal the sum of its rounded parts. The complete comparison fields retain each local rounding residual and carry it into earlier boundaries by ordered addition.\n\nThe SP cap fits this account cleanly once its inclusive counts have been resolved. Nearest-five rounding preserves order, so rounding the smaller of a lifespan and its capacity gives the same result as taking the smaller of their rounded values. Across the complete nine-row SP field, the three clipped counts become 845, 720, and 655, and the same three rows remain strictly reduced.\n\nRounding the date labels first performs a different construction. For those same rows, separately rounded births and Flood start yield capacities of 846, 716, and 651. They do not replace the resolved count results. Relative to MT, the changed SP rows contribute rounding residual differences of zero, minus one, and plus four. Their combined plus three explains the established Cumulative comparison changing from minus 608 to minus 605. The connection rests on the source counts and their residuals, not on independently rounding final dates.", "sources": [ { "file": "File51a", "sections": [ "§3.4", "§§16.1–16.2", "§17" ] }, { "file": "File18", "sections": [ "§3.1", "§3.1.3" ] }, { "file": "Research Strategy", "sections": [ "§5, Stage F" ] } ], "steps": [ "C749–C770", "C978–C981" ], "word_count": 214 }, { "id": "source_authority_limits", "title": "The source controls which constructions belong to a family", "text": "A common mathematical rule becomes a chronological explanation when the source also supplies its permitted inputs, order, and scope. The SP cap uses the native G2 birth chain, its selected Flood boundary, and explicitly qualified lifespan counts. The full-430 comparison moves births and Flood together by 215 years, preserving every capacity. Local Noah and Shem counting alternatives preserve the same ancestral Flood distance; they do not create companion birth positions throughout the genealogy.\n\nThese distinctions keep the wider family model interpretable. Cainan's admitted insertion contributes 130 in a Regular chain and 460 in a Cumulative chain because the two constructions measure different parts of his row. Likewise, an inclusive SP cap count does not become an ordinary elapsed lifespan merely because the numbers enter a shared formula. Current source selections also retain main LXX Lamech 182/753 and official SP Terah 145; earlier summaries or comparison overlays do not silently replace them.\n\nFormal sensitivity calculations show how a construction would respond to changed inputs, but they do not authorize those changes as textual variants. The forward cap reconstruction explains consequences of a declared source model. Its conditional inverse identifies recoverable parameters. Neither establishes a sequence of ancient revisions. This separation allows mathematical compatibility, transmission history, and the Strategy's interpretive premise to remain distinct.", "sources": [ { "file": "File18", "sections": [ "§1.3", "§3, active state and frame conversion", "§3.1", "§3.1.3", "§4.1", "§6C" ] }, { "file": "Research Strategy", "sections": [ "§§1–2", "§5, Stages A, C and H", "§6" ] } ], "steps": [ "C743–C748", "C787–C788", "C905", "C953", "C974–C977", "C983" ], "word_count": 212 } ] }