{"id": "d-c10be95a7f5a5a45", "title": "How the Chronological Families Fit Together", "filename": "490d_How_Chronological_Families_Fit_Together_C1131.md", "role": "History", "step": null, "sha256": "c10be95a7f5a5a4559e6d92beaf0a85b4451d433b6ca8497a8deca0eac368139", "bytes": 63960, "origins": ["C480–C1634/Research_Cycles/C0932_C1131/deliverables/490d_How_Chronological_Families_Fit_Together_C1131.md", "C480–C1634/Research_Cycles/C1132_C1431_Recovered/inherited/490d_How_Chronological_Families_Fit_Together_C1131.md"], "download": "/sources/c10be95a7f5a5a4559e6d92beaf0a85b4451d433b6ca8497a8deca0eac368139.md", "format": "md", "derived": false, "tags": ["Regular", "Cumulative", "Rounded", "Inverse", "Calendar Keys", "Covenant", "Counts & NT"], "excerpt": "How the Chronological Families Fit Together\n\nA continuation of the Research Strategy through C1131 · 28 September 2026\n\nThe families use different measurements of ordered source material. A small set of operations, each tied to its source, connects them. Shared constraints explain their agreements; retained labels and ", "content": "# How the Chronological Families Fit Together\n\nA continuation of the Research Strategy through C1131 · 28 September 2026\n\nThe families use different measurements of ordered source material. A small set of operations, each tied to its source, connects them. Shared constraints explain their agreements; retained labels and the information each operation loses explain their differences.\n\nThe strongest new bridge is local: the SP begetting chain supplies Flood capacities, those capacities generate the shortened lifespans, and their ordered accumulation generates the Cumulative displacement field. Rounded analysis then records how those counts change under its own rules. The inverse and Key families add different, precisely specified comparisons; they do not replace the source genealogy with one universal date formula.\n\nThis draft separates retained source premises, generated consequences, and additional compatibility conditions. Mathematical reconstruction is distinct from a historical sequence of transmission. The Strategy’s providential interpretation remains an interpretive premise, not a parameter adjusted to make the calculations work.\n\n## How to read this draft\n\nFor the main argument, read the family table, the SP cap, the Rounded inverse junction and the final section, “What the shared grammar now explains.” The middle chapters show how Keys, Covenant joins and counted structures extend that explanation. The technical companion gives the equations; the source notes identify the controlling passages.\n\n![Chronological families: the SP construction and companion comparisons](sandbox:/workspace/scratch/1b40da62dcbd/c932_c1131/deliverables/490d_Chronological_Family_Map_C1131_Final.png)\n\n*Figure 1.* Birth intervals generate SP Flood capacities, capacities limit lifespans, and those lifespans feed Cumulative and Rounded measurements. Resolve the count convention before rounding. The companion constructions on the right have their own stated interfaces; the source field supplies their roles and placement. The PNG and editable SVG accompany this draft.\n\n## The families at a glance\n\n| Family | What the source supplies | What the construction does | Main connection |\n|---|---|---|---|\n| Regular | Ordered effective birth intervals and event bindings | Accumulates intervals in their declared state | Gives the birth distances used by the SP cap |\n| Cumulative | Ordered selected lifespans and terminal | Stacks full life measures | Carries cap reductions through every earlier boundary |\n| Rounded | A specified row measure and nearest-five rule | Records rounded values and residuals before accumulation | Keeps a coarse scaffold while explaining internal displacement |\n| Rounded inverse | Original components, anchors and placeholder policy | Reverses each admitted original component once | The fixed register and carry branch explain the 12026 junction |\n| Calendar Keys | Measured spans, units, selected parts and pivots | Applies exact rational conversion | Common volume, retained-part equations and grid conditions connect distinct paths |\n| Covenant/clutch | Local ages, life measures, phase and comparison state | Derives the clutch and aligns complete paths | First joins are forced; the next uses the shared 147 condition |\n| NT and counted lists | Named positions or counts, category/order and metric | Accumulates, measures and coarsens a complete field | The same path grammar works; source roles and count measures remain explicit |\n| Jubilees | Source timestamps and selected reconstructed subdivisions | Contracts or repartitions declared paths | Whole totals can be preserved with different internal cuts |\n| Sothic/SKL comparisons | Separate source fields, calibrations and symmetry rules | Uses its established bounded comparison maps | An inherited extension of the grammar; no remote source-chain expansion in this cycle |\n\nThese are related constructions of source-labelled objects. They are not interchangeable date systems, and one scalar affine map does not carry all traditions from Regular to Cumulative chronology.\n\n## Source rows: Regular, Cumulative and the SP cap\n\n### Two measurements of one ordered genealogy\n\nRegular 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 Noah-to-Abraham birth path of SP-with-Cainan and native LXX still carries different lifespan measurements.\n\n### A shared Flood boundary explains the whole SP family\n\nThe SP Flood cap begins with three 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.\n\n### What the capped lives determine about the ages\n\nThe 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 separately supplied source value of 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. With the begetting chain held, the exact capped lives recover the inclusive contribution of 601; with that contribution held, they recover the late-age combinations described above. 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.\n\n### Why the cap cannot identify the ancestral ledger\n\nA 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.\n\n### The cap connects to Rounded chronology through counts\n\nRounded 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.\n\n### The source controls which constructions belong to a family\n\nA 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.\n\n\nThe separation of source rows, counting conventions and placement now lets the Actual and Rounded fields be compared one operation at a time.\n\n## Rounded chronology and the inverse junction\n\n### Actual and Rounded chronology retain their selected states\n\nThe Actual and Rounded families can be compared precisely when each date retains its source role. For the present Creation bridge, the selected Actual completion endpoints are 14004 BC in cumulative chronology and 4114 BC in regular chronology. Their Rounded companions are 14006 and 4106 BC. The respective gaps are therefore 9890 and 9900 years. These figures describe two related, explicitly selected comparisons.\n\nThe changes have different causes. In the regular calculation, six years arise from the combined row-rounding residuals; the standard-versus-strict Shem convention supplies two further years. Together they explain the movement from Rounded 4106 to selected Actual 4114. In the cumulative calculation, row rounding preserves the 12600-year total and its 14006 BC head. Selecting the lower Actual completion endpoint supplies the separate two-year change to 14004.\n\nThis distinction makes the shared structure more informative. The displacement pair, cumulative −2 and regular +8, preserves the weighted coordinate (4C+R)/5 because 4(−2)+8=0. Here C and R denote cumulative and regular Creation respectively. Both selected pairs therefore yield 12026 BC. That conservation belongs to these stated endpoints and conventions. The source rows, endpoint selections, and individual chronological roles remain part of the explanation.\n\n### The regular total fixes the transformed outer span\n\nThe regular Creation–Flood–Conquest path consists of 1650 and 1050 years. A single placeholder-preserving reversal gives 5610 and 5010, totaling 10620. A broader mathematical fact explains why this outer total is stable within its particular decimal register.\n\nBoth original components have three-digit cores followed by exactly one zero: 165 and 105. For any two components in this same register, let H, T, and U denote the sums of their hundreds, tens, and units digits. Their original total is 10(100H+10T+U), while their reversed total is 10(H+10T+100U). Because both core endings are nonzero, H and U lie between 2 and 18; T lies between 0 and 18.\n\nAn original total of 2700 forces U=10 and 10H+T=26. Those bounds permit only H=2 and T=6. The reversed total must therefore be 10620, placing its endpoint at 12026 BC when 1406 BC is held.\n\nThe theorem determines the outer measurement without recovering the internal split. The source-appointed Flood boundary still supplies that information. Other mathematical allocations within this register illustrate the theorem but receive no chronological admission. Reversing the unsplit 2700 uses a different register and retains its established, different result.\n\n### The cumulative path selects one carry branch\n\nThe cumulative primary path, 9170+3430, shares the regular path’s reversed total of 10620. Its original total of 12600, however, allows two aggregate possibilities within the same two-component decimal register. This identifies a specific source condition behind the convergence.\n\nLet H, T, and U again be the sums of the two core digit columns. The total 12600 forces U=10 and 10H+T=125. The permitted digit bounds leave exactly two solutions: (12,5,10), giving reversed total 10620, and (11,15,10), giving 11610. The literal cores 917 and 343 select the first. Their units generate one carry into the tens column, but the resulting tens sum 6 generates no further carry. The other aggregate branch has a tens-to-hundreds carry and changes the reversed measurement by 990.\n\nThus total and register determine the regular result uniquely, while cumulative convergence additionally requires the source-selected carry branch. Neither branch is a probability estimate or an invitation to replace the source breakpoint.\n\nAppending the already declared 1400 tail, whose one-pass value is 4100, gives completed durations 14720 or 15710. Only the first has an integral 25/23 completion. Within this precise two-branch domain, integral Priestly completion and agreement with the regular primary path select the same condition. Their agreement supplies a useful connection between modules, without becoming two independent observations.\n\n### The weighting and continuation have distinct causes\n\nThe common 12026 BC endpoint connects two different measurements of the Creation paths. The regular component total increases from 2700 to 10620 under its one-pass reversal, a gain of 7920. The cumulative total decreases from 12600 to 10620, a loss of 1980. Their ratio is 4:1. Consequently the common endpoint equals (4C+R)/5, where C and R are the cumulative and regular Creation dates.\n\nThe selected Rounded-to-Actual displacement gives the same weight from another direction: cumulative −2 and regular +8 require a cumulative coefficient 4/5 for conservation. Once the source values and operations are fixed, these matching coefficients express their compatibility. The weight is a derived relation, so repeating it in another formula does not supply an additional independent premise.\n\nThe continuation to 14726 BC requires its own stated source leg. Conquest 1406 and Nativity 6 define an original 1400-year interval; one reversal gives 4100. Changing the held anchor from 1406 to 6 and adding that transformed leg shifts the earlier endpoint by 4100−1400=2700. Thus 12026 becomes 14726.\n\nThe shift happens to equal the regular Creation-to-Conquest total. Its justification nevertheless remains the Conquest-to-Nativity leg and its declared operation. Retaining Nativity 6, the original 1400 interval, and the anchor change makes the continuation reproducible while preserving the distinct roles of the two 2700 quantities.\n\n### An integral completion can retain fractional internal positions\n\nFile_52c’s four admitted completed paths all have one-pass total 14720. The stated Priestly conversion gives 16000, and holding 6 BC places the completed endpoint at 16006 BC. Examining the entire paths reveals which further information that clean endpoint preserves.\n\nThe regular Flood path has transformed components 4100,5010,5610. Its successive prefix sums have residues 6,2,0 modulo 23. The regular Noah path gives 6,4,0; the finer Flood–Noah path gives 6,2,4,0; and the cumulative primary path gives 6,9,0. Consequently every proper prefix remains fractional after multiplication by 25/23, while the final sum becomes integral.\n\nUniform conversion is still additive over exact rational values. Transforming each component and then summing agrees with transforming the whole duration. The extra requirement that every intermediate position remain on an integer grid is a separate condition. A consecutive block has integral transformed length precisely when its original sum is divisible by 23; these four paths permit only the final cut.\n\nThis gives a coherent mathematical comparison without changing any source boundary. A coarse numerical total can display integer closure while the retained internal path carries rational coordinates and its original event roles. The componentwise rational display is a conditional extension of the source’s whole-span conversion, rather than an independently adopted historical chronology.\n\n### 23 and 529 connect operations across whole families\n\nThe importance of 23 becomes clearer when it is attached to operations and complete source families. The three Keys share one calibrated measure: 336(25/23)=360(70/69)=364(300/299)=8400/23. Their different year counts can therefore represent the same modeled day-volume. Integer closure remains an additional condition, controlled by the denominators 23,69, and 299 and by the source-appointed anchors.\n\nThe 529 ladder applies the same Priestly denominator twice; its detailed relation to endpoint placement follows below. Here it supplies the next connection: decimal structure controls the transformed inputs, while calendar structure controls their subsequent completion. The familiar coefficient 20 is computed from the supplied 10580 span, rather than added as another premise.\n\nThis helps explain how the chronological families fit together without merging their source identities. Digit registers explain the primary reversal totals; the selected cumulative branch controls their agreement; calendar calibration relates their declared measures; and anchors locate the resulting spans. Some conditions coincide within a restricted source family, while others require additional placement or subdivision information. The explanatory gain lies in identifying those dependencies and reusable operations across complete fields. Historical intention and the interpretation of the source placements remain further questions.\n\n\n## Calendar Keys, retained parts and placement\n\n### Different calendar counts, one schematic measure\n\nThe three calendar Keys connect different year counts through one declared measure. Write E=25/23 for the Priestly Key, P=70/69 for the Prophetic Key, and J=300/299 for the Enochian Key. Their matching calendar lengths satisfy 336E=360P=364J=8400/23. Multiplying a span by a Key therefore changes its count while preserving the same modeled day-volume when the corresponding unit accompanies the result.\n\nFor the shared span 12558, the outputs are 13650, 12740 and 12600. Multiplying these respectively by 336, 360 and 364 gives 4586400 in every case. This existing calibration explains why different numerical totals can belong to one mathematical family.\n\nUnit labels also matter when separate components receive different Keys. The inherited comparison built from the 299|161 partition gives 300|175 under J on the first part and E on the second. With their matching units, 300×364+175×336=168000. Swapping the units changes that volume to 164500 although the numerical sum remains 475.\n\nThe connection is exact but conditional: it describes a schematic calendar realization, not proof that a chronology literally elapsed in mixed historical calendars. A complete comparison consequently carries both the number and its declared unit. Equal numbers without matching units, and unequal numbers with matching measures, tell different stories.\n\n### Selective expansion and successive Keys\n\nA Key can act on a selected part while the rest remains fixed. This produces a different operation from applying a Key to the whole span. The distinction links two source families. In the 483 carrier, the final 80.5 is one sixth of the total: expanding that part by E produces 402.5+87.5=490, the same total as applying P to all 483. In the 12558 path, the final 483 is one twenty-sixth: expanding that part by E produces 12075+525=12600, the same total as applying J to the whole.\n\nThe general rule is simple. If fraction f receives factor k, the effective total factor is 1+f(k−1). This explains the selected fractions 1/6 and 1/26 without treating their source boundaries as interchangeable. The computed intermediate fraction 3/13 connects P to J, but calculation alone does not appoint a corresponding chronological cut.\n\nNested selection multiplies selection fractions: one sixth followed by three thirteenths selects one twenty-sixth. Successive whole-span conversion instead multiplies the Keys themselves; P followed by J gives 7000/6877, not J.\n\nTogether with calendar calibration, the two inherited completion relations form four equations with three independent constraints. Solving them backward recovers the Keys, but supplies an equivalent description of established relationships, not independent evidence for their historical origin.\n\n### What retained parts let us recover\n\nSeveral apparently separate families follow the same retained-part construction. Let u denote the component that receives a Key and v the component held unchanged. Their native, Prophetic and Priestly totals are T₀=u+v, Tₚ=Pu+v and Tₑ=Eu+v. Because E−1=6(P−1), the gains obey Tₑ−T₀=6(Tₚ−T₀). The three totals therefore contain only two independent numerical measurements.\n\nTwo totals recover the components exactly: u=69(Tₚ−T₀), then v=T₀−u. The third total checks the same relationship rather than adding a third independent fact. This one construction covers all three 690-core brackets: with retained flanks of 0, 30 or 60, the native/P/E totals are respectively 690/700/750, 720/730/780 and 750/760/810.\n\nSupplement A’s cumulative calendar-body family uses the same construction on a larger scale. Its converted upper segment is 9660 and its fixed lower segment is 2940. The resulting totals are 12600, 12740 and 13440. These source-defined components make the family intelligible without treating its three totals as unrelated coincidences.\n\nNumerical recovery still leaves chronological information to the source. It does not identify which named interval occupies each role, their order, their absolute placement, or permission to apply the operation. Recovering two magnitudes is therefore one part of reconstructing a declared chronological object.\n\n### When a total preserves the full comparison\n\nCombining several components into one total can hide exactly the information that distinguishes two chronological paths. There is a precise test for when this simplification is harmless. If every component in a combined block receives the same conversion factor, we may add first and convert afterward, or convert each component and then add. The two procedures agree for every possible set of component values.\n\nIf the factors differ inside a block, this universal agreement fails. A particular source total may still agree because its component weights make the differences cancel. That is a property of the supplied arrangement, not permission to forget its internal boundary.\n\nThe 483 carrier makes the distinction concrete. Keeping 402.5 fixed and expanding the final 80.5 by E gives 402.5|87.5. Applying P uniformly gives 408⅓|81⅔. Both total 490, but their two components differ by −35/6 and +35/6. The total erases a real internal displacement.\n\nThis is why a family comparison should retain intermediate boundaries as well as endpoints. An equal total answers a narrower question than an equal path. The same discipline helps relate regular, cumulative and Rounded objects: first specify the components and measurement, then state which internal distinctions the chosen total preserves and which it loses.\n\n### Pivots place the whole field\n\nA duration ratio does not determine a date transformation until a held pivot is declared. Around pivot a, factor k sends coordinate x to a+k(x−a). Differences between points scale by k, while their absolute placement still depends on a. This separates the shape of a chronological field from where it sits.\n\nFor two successive Keys, integer placement has an exact test. Let their reduced ratios be p₁/q₁ and p₂/q₂, with integer pivots a and b. An integer input can have integer outputs at both stages only when gcd(p₁,q₂) divides b−a. If that condition holds, the admissible inputs form one residue class with spacing q₁q₂/gcd(p₁,q₂). A complete field belongs to that class when one point has the right placement and every internal difference is a multiple of the spacing.\n\nFor the fixed pivots 14006 and 4836, the diagnostic J→P composition has no such integer inputs: gcd(300,69)=3 does not divide their difference. This identifies a domain limit without inventing replacement pivots or authorizing new chronological routes.\n\nFractions themselves remain exact coordinates. The full File46 head pattern, with indices 92,89,46,43,0 on a ten-unit mesh, survives E expansion on mesh 250/23. Preserving that entire rational image explains the family more faithfully than discarding points to retain only integer endpoints.\n\n### The structural role of 529\n\nThe number 529 has a specific role in the Priestly expansion family: it is 23², the denominator needed for two applications of E=25/23 to produce integral duration widths. A width 529n therefore follows the ladder 529n→575n→625n. The inherited examples 1058→1150→1250 and 10580→11500→12500 share that duration grammar, with the second ten times the first. Their agreement follows from the same operation and scale relation.\n\nWidths alone do not determine endpoints. Holding the same integer pivot for both stages requires each starting point’s offset from that pivot to be divisible by 529. With different pivots, the allowed residue changes. Two fields can therefore share a 529-multiple width while only one has integral endpoints under its declared pivots. The successful inherited small example and the fixed-12026 comparison exhibit exactly this distinction.\n\nThe Rounded macro family also supplies a particular endpoint realization: with AD 12026 held, AD 1446→AD 526→476 BC accompanies the widths 10580→11500→12500. Its last crossing uses the declared Rounded coordinate convention; substituting ordinary civil counting changes the final display.\n\nThus 529 connects these families through a reusable two-stage duration structure. It does not license a universal date conversion, supply a missing pivot, or establish independent evidence merely because another multiple follows the same inherited ladder.\n\n\nThe Covenant family supplies a concrete test: local ages and biographies generate the paths, and the declared Keys compare selected measurements of those paths.\n\n## Covenant and cumulative root joins\n\n### Start with the source relationships\n\nThe regular Covenant field can be generated from local source relationships without supplying its conspicuous 161, 299 and 276 spans as starting answers. The packet retains the Covenant coordinate, its offsets to Ishmael and Isaac, Isaac’s interval to Jacob, Jacob’s call age, the household timing of Levi and Joseph, their lifespans, and the terminal. Following these relationships produces the complete labelled field.\n\nThis approach distinguishes three things that can share a number: a source datum, a generated coordinate, and a comparison between generated coordinates. Levi’s lifespan belongs to the source path. His calculated death is an output. Its distance from the Covenant is a further measurement. Keeping these roles separate explains what the model actually requires.\n\nThe packet remains local rather than a claim of ultimate historical independence. Covenant 2081 is author-designated; 1866 is its declared −215 placement. The offering comparison at 2051, with Isaac at proposed age 15, remains proposed. Genesis 22 does not state that age. These choices are retained as premises.\n\nThe Strategy’s larger gain is a reproducible explanation of connected families, with the source choices still visible. The generated agreement does not establish those choices’ historical origin.\n\n### Three 147 rails require two source conditions\n\nThe three 147-year rails measure different relationships: Isaac’s birth to Levi’s birth, Jacob’s own lifespan, and Jacob’s call to Levi’s death. Their agreement can be reduced to two source conditions. The first is 60+77+10=147: Isaac’s interval to Jacob, Jacob’s call age, and the interval from that call to Levi’s birth. The second is 10+137=147: the same household interval followed by Levi’s lifespan.\n\nThe familiar vertical separations of 60 and 77 then follow from these two conditions. Subtracting one condition from the other also gives 60+77=137, explaining the shared diagonal. These further equalities describe the same connected arrangement rather than adding separate source requirements.\n\nIshmael’s and Levi’s equal 137-year lives supply another premise. Equal lives preserve their birth separation at death, producing the corresponding 161 displacement. The further 161 years from Levi’s death to the terminal still depends on the terminal’s placement.\n\nThis distinction helps the families fit together: some agreements come from shared paths, some from equal-valued biographies, and others from a separately retained endpoint. Their explanatory roles are different even when the displayed numbers agree.\n\n### The common Key landing is one agreement condition\n\nThe two routes to the transformed 1566 point use different Keys on different source paths. Let u be the Covenant-to-Levi-death span and w the Covenant-to-Joseph-death span. The regular source packet generates u=299 and w=276. Holding the Covenant coordinate Q, the two points are Q−(300/299)u and Q−(25/23)w.\n\nThey agree precisely when 13w=12u. For the supplied paths, both transformed spans are 300 and both points are 1566. The larger gain on Joseph’s route absorbs the original 23-year separation between the deaths. The agreement does not make the two Keys interchangeable, and 1566 remains a transformed comparison rather than a newly appointed historical death.\n\nIntroducing a common-point variable clarifies the dependency. One equation defines the point from the first route; the second tests whether the other route reaches it. Eliminating the generated point leaves one condition on the source paths.\n\nThat condition adds information beyond the preceding Covenant rails in the declared variable model. Its evidentiary contribution is therefore one source-path agreement, with the two displayed landings and their shared 300 measurement as dependent consequences.\n\n### The clutch aligns two source paths\n\nThe clutch begins with a comparison between maximum lifespan capacity and regular elapsed chronology. For the full-state comparison, let B and D be Levi’s regular birth and death, M Moses’ birth, and e the Exodus. Let L, K and A be the selected Levi, Kohath and Amram lifespans. The source construction subtracts B−e from L+K+A+(M−e). The Exodus cancels, leaving d=M+K+A−D.\n\nThe expression M+K+A is cumulative Kohath’s boundary. Thus d is exactly cumulative Kohath minus regular Levi death. Subtracting d must land there: this first agreement follows from the construction.\n\nThe adjacent Levi-birth agreement follows because both paths use Levi’s same lifespan. The next Jacob-to-Isaac agreement has a different status. It requires Isaac’s regular birth to lie one Jacob lifespan before Levi’s regular birth—the 147 condition already identified in the Covenant family.\n\nThe complete set of translated cumulative boundaries can therefore be described from Levi’s regular death and the selected lifespans. Moses’ original anchor cancels when the clutch is recomputed, while his historical birth remains fixed in its original role.\n\nThe source retains one Nisan-derived clutch across the Aaron phase. Recomputing a separate full clutch to the same landing would erase that phase displacement and would be a different construction.\n\n### Separate constraints from their consequences\n\nA constraint states something additional about the source packet. A consequence follows once the existing constraints and construction rules are supplied. This distinction matters because a compact family can produce many exact equations from relatively few relationships.\n\nFor example, the selected Covenant claim list has nine equations but only eight independent rows when its source quantities are treated as variable. One household-middle equality follows from the second 147 rail, equal lifespans, the twin death arms and Joseph’s double span. It adds no further condition after those are retained.\n\nThe count also depends on which values are already fixed. The centred 147–161–175 progression and the Priestly completion of 161 to 175 are distinct equations while the relevant lifespans vary. Once the source 147 and 175 are supplied, either radius condition implies the other.\n\nEven prominent pattern totals leave some source data unidentified. Formal sensitivity calculations can change local ages while preserving those selected totals. These directions demonstrate a limit of the pattern description; they are not admitted chronological alternatives.\n\nAccordingly, algebraic rank explains information requirements rather than probability or historical independence. The useful result is a dependency map: what is supplied, what is generated automatically, and which further joins require an additional source relationship.\n\n### Forty-two coordinates form one structured field\n\nThe cumulative phase-and-clutch table has seven genealogical rows, two phase states and three clutch positions. Its 42 coordinates follow one expression: X(i,j,k)=b(i)+jp−kh. Here b(i) is a row’s original boundary, p the phase offset, and h the half-clutch. The indices select Nisan or Aaron phase and the original, half-clutch or full-clutch position.\n\nBefore additional source equalities are imposed, seven row positions plus p and h give nine parameters. The 42 displayed coordinates therefore satisfy 33 independent linear relations. Seven original Nisan boundaries, one Aaron boundary and one half-clutch boundary suffice to recover the unrestricted field.\n\nAdditional source relations can reduce that description. The exact link h=2p, represented by 7=2×3.5, removes one freedom. The equality of Levi’s and Amram’s 137 lifespans removes another. These are relational constraints; separately fixing all their numerical values is a stronger specification. The whole-year phase 3 does not satisfy the same phase relation and retains its distinct display policy.\n\nFinally, the row boundaries themselves can be generated from the Moses anchor and lifespan stack, and the clutch from the regular/cumulative comparison. The table then becomes an output of the coupled source model. Its derived interfaces do not relocate the historical people whose source dates anchor the construction.\n\n\nThe same reconstruction question extends to lists and literary sequences: which ordered measurements recover the whole object, and which relations survive grouping?\n\n## Lists, NT metrics and literary counting\n\n### Recovering a complete list from ordered measurements\n\nEsau’s gift shows how a narrative list enters the same grammar as a chronological path. The source supplies nine printed counts, their species and sex labels, and the clean/unclean classification. It also supplies distinct orders: the male-first clean walk, the female register in drove order, and the unclean framing walk. Accumulation turns these labelled counts into cumulative measurements; adjacent differences recover the increments wherever the walk includes them.\n\nThe six clean prefixes are 20, 40, 50, 250, 450 and 490. Together with the five female prefixes, they determine eight of the nine counts. The male-donkey count is absent from both registers, so it remains free. Adding the printed grand total of 550 supplies precisely that missing information and recovers the complete list. A smaller selection of nine measurements already suffices: all six clean prefixes, the third and fifth female prefixes, and the grand total.\n\nThis is a whole-list transfer of the cumulative-path rule. The reconstruction respects the source’s animal categories and the printed camel block; unnumbered young contribute no invented count. It also preserves the distinction between measurements and placements. A cumulative value such as 430 is an exact list result; assigning it a chronological comparison requires the separately declared dates and roles.\n\n### An exact change of coordinates, with its information cost\n\nThe Esau reconstruction identifies two complete ways to encode the same nine source counts. One uses selected clean and female cumulative measurements with the grand total. The other uses the complete clean and unclean walks. Their measurement matrices have determinants +1 and −1, respectively. Consequently, each encoding has an integer inverse: every count is recovered by exact additions and subtractions, without fractional corrections.\n\nThis result explains why a family can look different while retaining all its numerical information. Counts, successive landings and selected cumulative registers can serve as alternative coordinates for one labelled object. The calculation removes redundant reporting, but nine independent measurements still carry nine free numerical coordinates in this reconstruction. It does not derive those source values from fewer free choices. Nor does an arbitrary integer measurement vector automatically describe admissible animal counts: nonnegativity and the source’s category meanings remain additional requirements.\n\nUsing every clean, female and unclean prefix gives fourteen measurements of rank nine. Five dependencies therefore follow from the measurement structure itself. Other equalities have a different status. The clean and unclean walks both reach 20 and 50, but through different animal rows; those agreements depend on the particular printed counts. Distinguishing structural dependencies from count-specific matches keeps the common grammar explanatory without multiplying the evidence supplied by equivalent descriptions.\n\n### Which source conditions recover the Tishri ledger?\n\nThe complete Tishri ledger contains seven ritual categories and four species totals: 75 bulls, 18 rams, 176 lambs and 11 goats. Those margins alone leave the allocation among categories unresolved. A more informative reconstruction retains the source’s row templates and lets their seven amplitudes vary. Daily and Sabbath offerings contain lambs; the other templates retain their printed species ratios, including the complete Sukkot vector 70:14:98:7.\n\nThe four margins then provide four independent equations for seven amplitudes. Three additional source conditions close the system: Trumpets, Atonement and Eighth Day have equal amplitudes, giving two equations, and the daily contribution is 44 lambs. These recover the entire seven-row ledger. Removing daily 44 restores a Daily/Sabbath exchange; removing the festival equalities restores two allocation freedoms. The premises therefore have identifiable jobs rather than appearing as an undifferentiated collection of assumptions.\n\nThe seven-day Sukkot sequence gives a smaller version of the same result. Total 189, seven days and decrement 1 determine the totals 30 through 24. Retaining the uniform nonbull contribution 17 then gives the bulls 13 through 7. Other positive arithmetic bull sequences also sum to 70 if the decrement is free. Both reconstructions are conditional on numerical source templates and stated conditions; neither claims that a few totals independently generate the ritual system.\n\n### Separating the NT slot ratio, duration and placement\n\nThe NT lattice makes three kinds of information visible: a relation among slots, the duration of a slot, and the placement of the field. Let u denote one generation slot and w the Enoch-to-hinge radius. The supplied Key factors P=70/69 and E=25/23 send the Enoch radius to Jared one slot farther out and Adam six slots farther out. Their equations are (P−1)w=u and (E−1)w=6u.\n\nThese two equations contain only one independent condition. Since E−1 is six times P−1, both reduce to w=69u. They explain the relative named positions while leaving the unit’s duration free. The separately supplied Book of Jubilees (BJ) span of 2450 years across 35 slots fixes the slot duration: u=70 and w=4830.\n\nPlacement requires additional source information. In the existing display, BJ Creation at 3856 BC and Conquest at 1406 BC lie 55 and 20 slots from the birth hinge. Together those co-registrations recover the same 70-year unit and the 6 BC hinge. This is conditional identification inside an already constructed schematic field. It supplies neither an independent historical derivation of the dates nor two new independent proofs of the metric. Preserving the source’s birth, event and carrier roles prevents a successful coordinate recovery from silently becoming a claim about a different dated object.\n\n### Keeping occurrence counts when sections are grouped\n\nThe Toledot table supplies eleven formula occurrences distributed across ten major sections. Its only repeated section is Esau: the formulas at Genesis 36:1 and 36:9 occupy positions 9 and 10 but belong to one major section. Terah is occurrence 6. There are therefore five formula occurrences before Terah and five after it, while the section count gives five earlier sections and four later ones.\n\nThe difference arises from the chosen measure. Counting sections assigns one unit to the Esau section; counting occurrences assigns it two. Retaining the ten section labels with multiplicities 1, 1, 1, 1, 1, 1, 1, 1, 2, 1 recovers the eleven-occurrence total and the five-on-each-side balance around Terah. The source need not abandon either grouping to explain why the counts differ.\n\nThis establishes a useful shared rule: an aggregation can preserve a source measure if its multiplicities travel with it. It does not follow that every operation on the original occurrence list survives the aggregation. In particular, the doubled Esau section still prevents index reflection from acting consistently on the ten section labels. The center established here is an occurrence-count center; it is not automatically a midpoint in elapsed years or a proof of semantic equivalence between paired headings. Those would require their own supplied measures and relations.\n\n### When a reflection survives grouping\n\nA reflection survives a grouping only when every pair of items grouped together has reflected images grouped together as well. This gives a direct test across complete source objects. On the eleven Toledot occurrences, index reflection sends position i to 12−i. The two Esau occurrences, 9 and 10, reflect to 3 and 2: Noah and Adam, which remain distinct sections. A single Esau section would therefore have two different reflected section images. Its multiplicity preserves the count but cannot resolve that ambiguity.\n\nA formal repair would also group Adam and Noah, yielding nine classes. That calculation identifies the obstruction; the supplied source does not authorize the extra grouping. It is therefore excluded from the reconstructed literary object.\n\nThe primary NT path provides the positive comparison. Its 77 seventy-year intervals, from 5326 BC to AD 65, divide into eleven complete blocks of seven intervals. Reflection reverses the block order and preserves every selected boundary at indices 0, 7, …, 77. Each block represents 490 years, so the coarsening retains both the measure and the reflection. The separately displayed AD 65–135 extension is outside this primary path. These examples explain why retaining a total is weaker than retaining an action: source grouping, boundary selection and interval coarsening each require their own compatibility check.\n\n\n## What remains supplied\n\nThe compact explanation retains the source rows and their labels, declared manuscript/state selections, interval-counting rules, chosen partitions, and placement anchors. These have different roles from generated endpoints. The accompanying primitive-data register lists the concrete working packets; its label “primitive” means an input to this reconstruction, not a claim that every entry is historically independent.\n\nFor the inverse junction, the original Flood divisions and the 1400 Conquest–Nativity tail remain explicit. For the SP cap, the baseline life ledger, effective begetting intervals and 600-plus-inclusive-one relation remain explicit. For the Covenant field, local source ages replace the conspicuous output gaps. For lists and schematic genealogies, category membership, order and slot identity remain part of the object even when the numerical measurements can be inverted.\n\n\n## A short operation inventory\n\n| Operation | Construction | What must be retained |\n|---|---|---|\n| Select a declared source state | Use the finite source inventory with its row and event bindings. | No unlimited repeated variant addition is inferred. |\n| Choose and accumulate a measure | $X_i=a+\\sum_{j\\ge i}w_j$, where $w_j$ are the selected downstream weights. | A complete ordered field and anchor recover adjacent weights. |\n| Round resolved row counts | $Q(n)=5\\lfloor(n+2)/5\\rfloor$ on the positive integer count domain used here; retain $e=Q(n)-n$. | Order is preserved; additivity and exact invertibility generally fail. |\n| Cap a resolved lifespan ledger | $Y_i=\\min(L_i,B_i-F+1)$, with source-qualified count/death tags. | Monotone, idempotent, many-to-one. |\n| Reverse admitted original components once | Strip and retain trailing-zero placeholders; reverse the remaining decimal core; restore placeholders. | Partition and digit register matter; no general additive law. |\n| Apply an exact Key about a pivot | $D_{k,a}(x)=a+k(x-a)$; selected components may have separate declared roles. | Exact rational differences scale; integer-stage domains require divisibility. |\n| Translate a specified field | Move precisely the source-declared nodes by the stated amount. | Internal differences survive common translation; scope cannot be enlarged. |\n| Group or coarsen with retained measure | Sum declared blocks or identify source classes; carry multiplicities when needed. | Symmetry descends only when the grouping respects the action. |\n\nThese operations have different domains and information effects. Together they form a source-qualified network of constructions. They do not form one group of reversible date transformations.\n\n\n## What the repeated agreements amount to\n\n| Family | Retained premises | Consequences | Additional information or qualification |\n|---|---|---|---|\n| Regular inverse register | 2700 total plus specified two-component register | 10620 outer total forced | Flood split remains source information |\n| Cumulative inverse register | 12600 total plus same register | two carry branches; source chooses 10620 | integral E completion is equivalent selector only in this domain |\n| Actual/Rounded junction | selected shifts −2/+8 and source path totals | same 4:1 weighted coordinate | continued 14726 separately retains original 1400 tail |\n| SP cap | begetting chain, baseline lives, Noah/Flood count relation | all nine outputs; three shortened rows | backward age recovery also holds Enoch 65 |\n| Key calibration/allocation | two calibrations and two retained completion relations | rank 3; one dependent equation | back-solving is equivalent description |\n| Retained-part totals | native and P totals with source component roles | E total follows $5T_0-6T_P+T_E=0$ | magnitudes recovered; roles not inferred |\n| Covenant claims | local parameterization and selected source conditions | nine equations rank 8; rank changes when values held | first join follows by definition; second uses the shared lifespan; third uses the Isaac-to-Levi 147 condition |\n| Esau registers | nine selected labelled measurements | integer inverse; extra registers dependent | nine free numerical coordinates retained |\n| NT fork | one-slot P / six-slot E source returns | rank 1; w=69u | 35-slot 2450 relation supplies metric |\n| Toledot grouping | eleven occurrences mapped to ten sections | multiplicity preserves occurrence measure | reflection is not well-defined on the ten grouped sections |\n\nThis ledger separates a reduction in independent constraints from a change of coordinates. Rank counts the independent equations in the declared variable model. They are not estimates of rarity or counts of historically independent witnesses.\n\n\n## Continuity with the wider repository\n\nThe local grammar also explains inherited families that this cycle has not retested as new evidence. Jubilees’ biological and surface paths both total 575 while their four internal increments differ: 100|60|130|285 becomes 111|59|125|280. The changes +11,−1,−5,−5 preserve the outer span. The source’s unresolved prose tensions remain unresolved; its SP-derived 7+1300 construction is not an independent witness.\n\nThe six previously reconstructed macro heads likewise follow M=R+12(C−R). Their two retained source coordinates determine both body size and placement. A retained terminal biography can preserve an internal 147-year segment even when a uniform conversion of that segment would change it. This is the same distinction between a total and its internal realization that the present Key analysis formalizes.\n\nThe Sothic/SKL work remains a bounded inherited extension. Its shared construction grammar is broader than the original three Keys’ common calibration. This cycle does not expand remote SKL chains, choose new reset epochs or turn explored fields into untouched holdouts.\n\n| Source distinction | Retained execution |\n|---|---|\n| Current controlling Round draft | Latest File52c, frozen with the source packet |\n| Strict and standard MT | Strict 4112 remains distinct from standard 4114; Rounded 4106 has its own row construction |\n| Cumulative completion | Lower Actual 14004 is distinct from the 14006 Moses-line/Rounded head |\n| Main LXX | Lamech 182/753; calculated 571 remains in its role; 777 is appendix-only and 188 nonoperative |\n| SP | Native G2 capacities and local Noah/Shem companion scope; official Terah 145 is distinct from Ideal 205 |\n| Cainan | Regular 130 and Cumulative 460 are different measurements; native LXX retains Cainan |\n| Civil and Rounded crossing | Civil BC+AD−1; the stated Rounded comparison uses BC+AD−2 |\n| Exact and whole-year phase | 1936.5 exact and 1936 whole-year remain different source displays |\n| Covenant interpretation | 2081 author-designated; offering 2051 and Isaac age 15 proposed |\n| NT schematic field | Generated carriers retain their roles; 36 BC comparison does not revise the 6 BC Nativity |\n| Deferred or quarantined work | No second decimal inversion, upstream Gear extension, primer expansion or new statistical target tally |\n\nThese choices are part of the model’s descriptive cost. The common grammar preserves them rather than concealing them in adjustments.\n\n\n## What the shared grammar now explains\n\nAcross these families, local measurements generate complete fields, and their differences reveal what each construction preserves. The SP cap links birth distances to lifespan and Cumulative changes; rounding carries row residuals through those fields; decimal rules and Keys transform declared spans; and grouping retains a measure or symmetry when its internal structure permits it. The families fit together through explicit maps between source structures and their chronological realizations. Their shared grammar is clearest where the same construction explains both an agreement and the precise form of a difference.\n\nThe present result has four parts: a compact input register, an operation inventory, relations among operations, and a reconstruction ledger. It supplies the presentation requested by the Strategy. It also distinguishes genuine reduction from a reversible re-description: nine Esau measurements still carry nine free count coordinates, whereas several displayed Key or Covenant agreements are consequences of fewer retained equations.\n\nThe best next research question is now about source choice rather than another distant numerical landing: **which additional source-controlled constraints explain the remaining begetting values, lifespan excesses, and named partitions that the present maps cannot recover?** The SP family provides a concrete starting point. Its three caps and retained Enoch 65 determine the distinctive late ages, but leave earlier ages and the discarded excess lifespans unresolved. The Covenant system similarly leaves local freedoms until specific source ages are supplied.\n\nA next cycle should declare one such unresolved input family in advance, keep its complete ordered source field fixed, and ask whether a proposed local mechanism reconstructs it without a newly selected endpoint. Already explored families cannot become untouched holdouts. Historical transmission remains a separate investigation, and the Strategy’s providential interpretation remains distinct from the mathematical reconstruction.\n\nThis cycle does not claim a uniquely smallest grammar. It establishes a smaller, more explicit explanation of several previously separate families and identifies exactly where further source information is needed.\n\n\n## Source and verification notes\n\nThe accompanying Source_Claim_Index_C1131.md maps the five main argument blocks to the exact frozen source copies. The complete evidence packet contains the sequential research, source hashes and independent reviews.\n\n**1. Two measurements of one ordered genealogy** — Research Strategy §3.2, §5, Stages B and G; File18 §§2.1.3–2.2, §§3.1–3.2, §4.1, §§6A–6D; File09 §§0.3–0.4.\n\n*Research record:* C733–C748, C787–C788, C954–C956, C972–C973.\n\n**2. A shared Flood boundary explains the whole SP family** — File18 §2.1.3, §3.1, §3.1.3, §6C; Research Strategy §5, Stage B, §8, main unresolved reconstruction task.\n\n*Research record:* C741, C953–C959, C972–C973, C983.\n\n**3. What the capped lives determine about the ages** — File18 §3.1, §3.1.3; Research Strategy §5, Stages D and F, §6.\n\n*Research record:* C747–C748, C960–C967, C971.\n\n**4. Why the cap cannot identify the ancestral ledger** — File18 §2.1.3, §3.1.3, §4.1; Research Strategy §1, §5, Stages D, E and G.\n\n*Research record:* C905–C906, C968–C970, C982.\n\n**5. The cap connects to Rounded chronology through counts** — File51a §3.4, §§16.1–16.2, §17; File18 §3.1, §3.1.3; Research Strategy §5, Stage F.\n\n*Research record:* C749–C770, C978–C981.\n\n**6. The source controls which constructions belong to a family** — File18 §1.3, §3, active state and frame conversion, §3.1, §3.1.3, §4.1, §6C; Research Strategy §§1–2, §5, Stages A, C and H, §6.\n\n*Research record:* C743–C748, C787–C788, C905, C953, C974–C977, C983.\n\n**7. Actual and Rounded chronology retain their selected states** — File52c §3.14.1–3.14.2; File51a §§3,16; C492–C494; C902; C932–C936.\n\n*Research record:* C932–C952, C1058–C1068.\n\n**8. The regular total fixes the transformed outer span** — File52c §§1.2,3.3; C938–C939; C943–C946.\n\n*Research record:* C932–C952, C1058–C1068.\n\n**9. The cumulative path selects one carry branch** — File52c §§3.3–3.4; C940–C942; C947; Interface packet IQ04 and calculations.json:branch_equivalence.\n\n*Research record:* C932–C952, C1058–C1068.\n\n**10. The weighting and continuation have distinct causes** — File52c §§3.3–3.4,3.14.2; C936–C937; C948–C952.\n\n*Research record:* C932–C952, C1058–C1068.\n\n**11. An integral completion can retain fractional internal positions** — File52c §3.4, especially the four-path table; Interface packet IQ01–IQ03 and calculations.json:completed_path_prefix_field; Key-constraints packet §C.\n\n*Research record:* C932–C952, C1058–C1068.\n\n**12. 23 and 529 connect operations across whole families** — Research Strategy §3.3; File52c §§3.9.1,6.1–6.2; C500–C507; C937–C948; Key-constraints packet §§A,H; Interface packet IQ13.\n\n*Research record:* C932–C952, C1058–C1068.\n\n**13. Different calendar counts, one schematic measure** — 490d_Unification_Research_Strategy_v0_2_20260906.md §3.3; File12 Calendrical Physics Active Enochian Key clarification, line 263; File63 Scale-Neutral 480/483/490 Carrier §9.7; File60 Levitical Covenant Spine §5; component 161→175 reconciliation; c532_c631/journal.json C533: assembled 300|175 comparison.\n\n*Research record:* C988, C1004, C1005, C1006, C1007.\n\n**14. Selective expansion and successive Keys** — File63 Scale-Neutral 480/483/490 Carrier §1.3; §§7.3–7.4; §9.7; 490d_Unification_Research_Strategy_v0_2_20260906.md §3.3; §5E.\n\n*Research record:* C984, C985, C986, C987, C989, C990, C991, C992.\n\n**15. What retained parts let us recover** — 14-file_70-supplement-a-key-of-23-fine-resolution-720-30-rail-2-.md §1.2: complete 690/30 bracket table; 14-file_70-supplement-a-key-of-23-fine-resolution-720-30-rail-2-.md §10.3: cumulative calendar-body matrix, lines 2130–2185.\n\n*Research record:* C995, C996, C997, C1007.\n\n**16. When a total preserves the full comparison** — File63 Scale-Neutral 480/483/490 Carrier §1.3; c532_c631/journal.json C609: inherited internal-defect example; 490d_Unification_Research_Strategy_v0_2_20260906.md §§3.1–3.2; §5E.\n\n*Research record:* C993, C994, C997, C1007.\n\n**17. Pivots place the whole field** — File46 Harmonic Expansion Protocols §§2–3: 14006 and 4836 pivots; §6A.5: complete head field; 490d_Unification_Research_Strategy_v0_2_20260906.md §5C: transformations and domains; c482_c531/journal.json C506–C507: inherited placement witnesses.\n\n*Research record:* C998, C999, C1000, C1001, C1002, C1003.\n\n**18. The structural role of 529** — File_52c.Rounded_Whole_Span_Inverse_Detailed_Study_Draft (2)(1).md §§3.8–3.9; coordinate convention in§1 and§6; c482_c531/journal.json C505–C507: duration ladder and placement; C510–C511: Rounded endpoint realization; c932_c1131/journal.json C1001: inherited width/placement distinction.\n\n*Research record:* C505, C506, C507, C510, C511, C998, C1001, C1007.\n\n**19. Start with the source relationships** — C1032–C1034; C1057; File60 §§0.4,2–3; File61 §§6–8.\n\n*Research record:* C1032–C1034, C1057.\n\n**20. Three 147 rails require two source conditions** — C1035–C1039; File60 §§2.3–2.7,3.1–3.2.\n\n*Research record:* C1035–C1039.\n\n**21. The common Key landing is one agreement condition** — C1040–C1043; C1047; File60 §§5.3–5.5,6.1–6.2.\n\n*Research record:* C1040–C1043, C1047.\n\n**22. The clutch aligns two source paths** — C1051–C1056; File61 §§6.3–6.6,7.3–7.6,8.2–8.4; File62 §§1.1–1.4,2.4.\n\n*Research record:* C1051–C1056.\n\n**23. Separate constraints from their consequences** — C1039; C1042–C1047; C1053–C1057; File60 §§2–6; File61 §§6–8.\n\n*Research record:* C1039, C1042–C1047, C1053–C1057.\n\n**24. Forty-two coordinates form one structured field** — C1048–C1051; C1056–C1057; File61 §§7.3A–7.6; File62 §§1.2–1.4.\n\n*Research record:* C1048–C1051, C1056–C1057.\n\n**25. Recovering a complete list from ordered measurements** — File_58 §13.1, §13.2, §13.3, §13.4.\n\n*Research record:* C1008, C1009, C1010, C1011.\n\n**26. An exact change of coordinates, with its information cost** — File_58 §13.1, §13.2, §13.3, §13.4.\n\n*Research record:* C1011, C1012, C1013.\n\n**27. Which source conditions recover the Tishri ledger?** — File_58 §2.2, §2.3, §3.1, §3.2, §7.1.\n\n*Research record:* C1014, C1015, C1016.\n\n**28. Separating the NT slot ratio, duration and placement** — File_43 §§2.1–2.3, §3.4; File_54 §6, §8.6, §13.2.\n\n*Research record:* C1019, C1020, C1021, C1022.\n\n**29. Keeping occurrence counts when sections are grouped** — File_70 Appendix B.1, Appendix B.2.\n\n*Research record:* C1023, C1024, C1025, C1026.\n\n**30. When a reflection survives grouping** — File_70 Appendix B.1; File_43 §3.4; File_54 §8.6, §§10.1–10.3.\n\n*Research record:* C1025, C1026, C1027, C1028, C1029.\n", "evidenceLinks": [{"id": "file52c", "title": "File 52c"}, {"id": "d-be42daca1d82dac9", "title": "File 62"}, {"id": "d-68301ab760bfbe2e", "title": "File 18"}, {"id": "d-9a1eff41920cd0f8", "title": "File 12"}, {"id": "d-18e8c54ff1663fb1", "title": "File 46"}, {"id": "d-45851004c5864229", "title": "File 09"}, {"id": "d-924db415dff003d2", "title": "File 58"}, {"id": "d-d8aa38afb2a2df8f", "title": "File 51a"}, {"id": "d-1ff1914fa180de2a", "title": "File 54"}, {"id": "d-dde4eca7c1f64eae", "title": "File 43"}, {"id": "d-0fa80217c94b3951", "title": "File 70"}, {"id": "d-180803601a2db301", "title": "File 63"}, {"id": "d-d580afd48d6e12d6", "title": "File 61"}, {"id": "d-12a48221b7fdcdcd", "title": "File 60"}]}