# Selection and source-constraint candidates after C931 Preparation only. No numbered research action, canonical edit, new chronological state or statistical tally has been executed. The accompanying diagnostics are preparatory calculations for root to select and reassess. Self-contained packet: `selection_constraints_inputs.json` carries seven literal tables,65 source rows, five bounded source excerpts, exact line locators and the controlling hash. `prepare_selection_constraints.py` regenerates that packet. `selection_constraints_diagnostics.json` records18 passing independent preparatory checks, generated by `prepare_selection_constraints_diagnostics.py`. These files are now complete and can be frozen by root. ## Strongest new family **The complete nine-row SP Flood-cap family is the best next transfer after the Actual/Rounded junction work.** It changes the kind of explanation: selected lifespan values can be generated from independently supplied begetting rows and a shared Flood boundary, rather than merely accumulating already supplied lifespan differences. Controller: latest local File18 §§3.1 and3.1.3, approximately lines1442–1539, SHA256 `68301ab760bfbe2e874aedc5c8d943ced7a6219d34bc2859332a70713f9630d5`. The source explicitly defines a cap as the minimum of the current lifespan count and its qualified Flood capacity. The source's preferred native SP head4199 supersedes older Adam/Creation repair displays; do not substitute a remembered4414/4415 head. Keep the initial execution **native SP G2**, with Noah primary3493, Flood start2893, close2892. The later+215 whole-frame comparison is allowed separately. Do not introduce upstream Gear transport. The Noah/Shem companion belongs only to its local person stations; it does not move the nine ancestral births. ### Compact exact packet The nine rows are Adam, Seth, Enosh, Kenan, Mahalalel, Jared, Enoch, Methuselah, Lamech. Effective begetting intervals to primary Noah are `b = [130,105,90,70,65,62,65,67,52]`. The final52 is completed duration in the53rd counted year. It is fixed before calculating births. Let `U` be suffix accumulation. Then `u=Ub=[706,576,471,381,311,246,184,119,52]`, `B=3493+u=[4199,4069,3964,3874,3804,3739,3677,3612,3545]`, `C=B−2893+1=u+601=[1307,1177,1072,982,912,847,785,720,653]`. Capacities are not nine asserted lifespans. Against the MT supplied lifespan ledger `L=[930,912,905,910,895,962,365,969,777]`, the source rule `L_SP=min(L,C)` gives `[930,912,905,910,895,847,365,720,653]`. Every row matches the SP source. Only Jared, Methuselah and Lamech are clipped. Their ledger reductions are115,249,124, totaling488. The six unchanged rows retain ordinary lifespan subtraction. The clipped output counts are inclusive and place death at Flood **start**2893; subtracting to close2892 is an equivalent capacity calculation, not a second physical-death assignment. The numerical minimum must retain those branch-specific count tags. ### Why this serves the larger question This is a local coupling between the regular begetting measure and selected cumulative lifespan inputs. The regular chain supplies each remaining distance to the Flood; the cap determines the three shortened lifespans; cumulative accumulation then carries those source-local changes through its own field. The same family can be read in reverse as a conditional constraint on the changed begetting ages. That is more informative than a match between distant endpoints. With `k=601`, the three capped lives require `L_Jared = b_Jared+b_Enoch+b_Methuselah+b_Lamech+k`, `L_Methuselah = b_Methuselah+b_Lamech+k`, `L_Lamech = b_Lamech+k`. Consequently, their observed847,720,653 give completed Lamech52, Methuselah67, and Jared+Enoch127. Holding the independently supplied Enoch65 then forces Jared62. Without that held65, the late begetting matrix has rank3 on four unknowns and kernel `(1,−1,0,0)`: the cap values alone do not determine the Jared/Enoch split. The construction is conditional on source premises. It does not establish a historical MT→SP revision. In particular, using the main LXX Lamech753 in the otherwise identical nine-lifespan baseline gives exactly the same SP capped output; the cap erases the777/753 difference. Current sources themselves warn against inferring historical direction from numerical compatibility. ## Prior-work audit `prep/completed_family_index_C482_C931.tsv` contains all450 locally available completed actions, with one-line titles and findings. Explicit searches across the five journals find no prior Flood-cap/capacity/minimum-lifespan reconstruction or File47 column-walk family. The earlier work does already cover: - C485–487: MT/LXX/SP local row differences and aggregate projections. - C733–748: complete ordered regular/cumulative fields and their recoverability from adjacent differences. - C749–770: full rounding defects/residuals and the SP residual+3. - C772–788: finite variant support and the official SP Terah145 distinction. - C901–913: endpoint basis, recoverability, operational registers and finite necessity qualifications. Therefore the new result is **the source-controlled minimum/cap mechanism and its conditional inverse constraints**, not another discovery of−608, residual+3 or the same native coordinate tables. No exhaustive audit of C01–C479 is claimed. File47 is a secondary candidate only. Its MT S0 and SP S0 alternating pair projections could be useful later, but §6.2 displays3707−3207=500 while printing a501 bracket, and §5.2 intentionally combines a cross-state502 bracket with102 within-pair gap. Those latter displays cannot be read as one continuous unqualified path. Do not divert the present cycle into harmonizing those source tensions. ## Thirty ranked bounded questions These are candidate questions, not a fixed instruction to spend thirty numbered steps. Combine adjacent questions if their answers follow in one calculation. A completed scalar result should be cited rather than counted again. ### Construct the whole source family 1. **Can all nine SP births be regenerated from the begetting rows and primary Noah alone?** Hold3493 and the effective nine-edge vector, with no lifespan inputs. Compare every generated birth with the literal source table. This establishes which later cap inputs are independently generated from regular data. 2. **Can the complete capacity field be generated without an absolute BC anchor?** Remove3493 and2893 together. Show `C=Ub+601`; the600 Noah-to-Flood duration and inclusive+1, rather than absolute placement, generate all nine capacities. 3. **Does one source-qualified minimum rule reconstruct every SP pre-Noah lifespan?** Use the full nine-row source baseline, rather than first selecting the three successful shortened rows. Keep ordinary versus inclusive output tags. 4. **Which rows are clipped, which merely lie below the cap, and how much slack remains?** The complete slack field is377,265,167,72,17,0,420,0,0. Distinguish a strictly reduced lifespan from merely equaling a capacity; this matters in later parameter diagnostics. 5. **Is the predicted lifespan vector the unique greatest feasible vector?** Under `x_i≤L_i` and `x_i≤C_i`, prove `min(L,C)` is coordinatewise greatest, hence uniquely minimizes total reduction when no lifespan may increase. This explains the source's “shorten only as required” mechanism conditional on those assumptions. 6. **Do all selected deaths retain their correct boundary meanings?** Recover six ordinary deaths by subtraction and three Flood-start deaths by the inclusive rule. Demonstrate once that the equivalent close-based capacity formula does not assign those deaths to Flood close. ### Identify exactly what the cap constraints determine 7. **Can each capped source row separately recover the same held Flood boundary?** With its absolute birth held, `F=B−L_SP+1` gives2893 for Jared, Methuselah and Lamech. Treat this as an inverse identification problem, not three new independent predictions afterF has already been supplied. 8. **Which two nonredundant synchronization constraints remain after one cap is used to fix the common parameter?** The three cap values identify `k=L_SP−u=601`. Fixk from one row; compare the remaining two. The third pairwise difference is dependent on the first two. 9. **How weak is knowing only the clipped-row support?** For the fixed begetting and MT lifespan rows, exactly the Jared/Methuselah/Lamech strict-clipping support is compatible with `584≤k<716`. The support alone permits132 integerk values; the particular cap lifespans select601. Derive this interval algebraically, without an endpoint scan or probability interpretation. 10. **Can a supplied aggregate identifyk without the individual cap values?** Within that fixed support region, the total output is `5334+3k`. The total7137 fixes601; identify which information the aggregate still fails to supply—especially order and the input support assumptions. This is an alternative conditional identification, not additional evidence beyond its component sum. 11. **What is the exact rank of the late begetting/cap equations?** On `(b_Jared,b_Enoch,b_Methuselah,b_Lamech)` withk fixed, the three-cap map has rank3 and kernel `(1,−1,0,0)`. Recover the individual and combined quantities it does determine. 12. **Does holding Enoch's independent65 recover all three distinctive SP begetting inputs?** The equations yield Jared62, Methuselah67, completed Lamech52. The last corresponds to the printed53rd counted year. This is the most useful reverse source-row explanation in the family. 13. **Can a bounded non-admitted kernel diagnostic preserve all cap outputs while changing an internal birth?** Change Jared/Enoch begettings by+1/−1 with the rest fixed. The three clipped capacities and all nine resulting lifespans remain unchanged, but Enoch's birth changes. This proves why source placement is not recovered from the cap outputs alone. Label the diagnostic explicitly unadmitted. 14. **Which earlier begetting inputs remain unconstrained by the three late cap values?** The upper five begetting intervals lie outside their suffix support. Show that the source's early genealogy remains a premise; the new local mechanism does not derive every ancestral age. 15. **What can the SP cap outputs recover about the uncapped ancestral lifespans?** An output strictly below capacity fixes its input lifespan; an output at capacity gives only a lower bound. The three larger MT lifespan values cannot be recovered numerically from their capped SP values. 16. **Does the known three-value ancestral multiset recover their placement?** Among the six assignments of962,969,777 to Jared/Methuselah/Lamech, four yield the same cap outputs847/720/653. This finite diagnostic establishes non-identifiability even when the multiset and total are held. It is not a proposed source variant or an alternative historical genealogy. 17. **Does the main LXX lifespan baseline project to the same SP family?** Replace only the baseline Lamech777 with main LXX753 and apply the same fixed SP capacity field. The output is unchanged, while the ledger reduction is464 instead of488. The lost24 shows why the forward numerical mechanism cannot establish MT-versus-LXX historical priority. 18. **What is the smallest source-supported equation packet for the late rows?** The four late begetting ages, three capped lives andk are eight variables with three independent equalities. Holdingk andEnoch65 leaves a three-dimensional relation between the remaining three begettings and three lives. Separate choice of coordinate basis from discovery of independent source facts. ### Connect the mechanism to the chronological families 19. **Can the complete pre-Noah cumulative displacement field be regenerated from the three cap reductions?** Accumulate the sparse115/249/124 support through every named boundary. Its total488 is inherited arithmetic; the new result is its derivation from the minimum mechanism rather than a supplied difference list. 20. **Does the cap module explain its share of the existing total SP−MT discrepancy?** Add only the already established post-Flood Eber−60 and Terah−60 source changes, giving−488−120=−608. Preserve official SP Terah145. The aggregate is a dependent synthesis, not another independent discovery. 21. **How does a change in a begetting input propagate into both regular and cumulative measures under the fixed active cap support?** With suffix matrixU and active-row maskA, the local derivatives are `dB=U db`, `dL_cap=A U db`, and `dC_cumulative=U A U db`. Derive the complete finite support matrices. This formal sensitivity model explains how a regular-row change can induce a cumulative change through the cap; it does not authorize new chronological variants. 22. **Does changing from native SP to the admitted+215 comparison frame preserve the whole cap family?** Move every relevant birth and Flood boundary together by215. All capacities, clipped counts and source-life reductions remain fixed, while absolute births/deaths translate. Do not confuse this frame change with changing a lifespan or moving only the Flood. 23. **Do the three admitted local Noah/Shem counting paths preserve the same ancestral capacities?** The source's52+500+100,53+499+100 and53+500+99 all give652 from Lamech to Flood start. Keep the ancestral births fixed and the companion local. This explains the counting equivalence without extending a−1 rail upstream. ### Join the cap to Rounded chronology and the operation grammar 24. **Does nearest-five rounding commute with the count cap over the complete nine-row family?** BecauseQ is monotone, `Q(min(L,C))=min(Q(L),Q(C))`. Evaluate every row with the same count conventions, giving930,910,905,910,895,845,365,720,655. This is a count operation; it is not yet a Rounded chronological date construction. 25. **Is the strict clipped-row support preserved by this particular rounding?** CompareQ(L) andQ(C) for all nine rows, checking for new ties or clipped rows. The source field retains the same three clipped identities; this need not hold for arbitrary near-threshold inputs. 26. **Why is rounding the capacity different from rounding its two date labels first?** A bounded formal diagnostic gives count-rounded845/720/655, versus846/716/651 from `Q(B)−Q(F)+1`. This illustrates the inherited rule to resolve the count convention before rounding. Neither diagnostic date-grid formula is promoted to a canonical Rounded Flood table. 27. **Can the known SP rounding residual+3 now be traced through the cap mechanism?** Relative to MT residuals, Jared contributes0, Methuselah−1, Lamech+4, yielding+3. Connect this derived support to the previously established−608→−605 cumulative difference. Do not count those totals again as new findings. 28. **What algebraic kind of operation is a cap?** On its fixed count domain it is monotone and idempotent, `cap_C(cap_C(L))=cap_C(L)`, and many-to-one. It is not invertible like a frame translation. This supplies a concrete new reason the entire chronology grammar is not one transformation group; its irreversible information loss is exhibited by the actual source family. 29. **Which claims survive deleting all generated outputs from the input packet?** Build one compact forward packet usingbegetting rows, a heldNoah/Flood relation, the baseline life ledger and the cap rule. Generate births, capacities, selected lives and death labels, then compare the complete literal SP family. Exact cap outputs must not also be inputs to this forward validation. 30. **What is newly justified about source choices, and what remains unproved?** Produce one dependency diagram or compact constraint table distinguishing independent transmitted/project-selected rows, conditional cap equations, generated cumulative differences, parameter identification, source-value non-identifiability and historical origin. The new success is a mechanism linking local age and lifespan data; no remote endpoint agreement or inferred probability is needed. ## Mathematical versus historical conclusions **Parametric identifiability:** fixed independent inputs can determine a parameter or row values uniquely within a declared model. The three cap equations can identifyk and, withEnoch65 held, the changed SP begettings. AbsoluteF additionally requires the placement frame. **Explanatory compression:** one rule reconstructs all nine SP outputs and the location of changes, with shared source inputs. It reduces duplicated description; it does not remove the cost of the rule, the source begetting vector or the ancestral baseline. **Historical origin:** the calculations do not determine which text preceded another, which quantities a scribe held fixed first, or whether an ancient editor consciously applied the exact minimum rule. The many-to-one projection and the identical output from MT/LXX baselines give positive mathematical reasons to keep that question separate. The strongest final sentence this family could earn is: > In the supplied SP model, the regular begetting chain sets each ancestor's remaining capacity to the Flood. Applying that capacity to the inherited lifespan ledger generates exactly the three shortened lives; the same equations, read conditionally in reverse, recover the distinctive later begetting ages once the unchanged Enoch row is held. That sentence explains a mechanism among chronological families while stating its source premises. It is a more useful advance than multiplying the number of endpoint checks.