manuscript covenant v2.json

{
  "status": "Reader-facing draft modules; no numbered research or source change",
  "scope_note": "C1034 whole-frame +215 is formal covariance only, not the admitted Minimum-to-full-state source operation; the explicit clarification is sealed at C1070.",
  "modules": [
    {
      "id": "source_local_scope",
      "title": "Start with the source relationships",
      "citations": [
        "C1032–C1034",
        "C1057",
        "File60 §§0.4,2–3",
        "File61 §§6–8"
      ],
      "text": "The 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.",
      "word_count": 191
    },
    {
      "id": "rails_147",
      "title": "Three 147 rails require two source conditions",
      "citations": [
        "C1035–C1039",
        "File60 §§2.3–2.7,3.1–3.2"
      ],
      "text": "The 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 an independently retained endpoint. Their explanatory roles are different even when the displayed numbers agree.",
      "word_count": 176
    },
    {
      "id": "common_key_join",
      "title": "The common Key landing is one agreement condition",
      "citations": [
        "C1040–C1043",
        "C1047",
        "File60 §§5.3–5.5,6.1–6.2"
      ],
      "text": "The 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.",
      "word_count": 172
    },
    {
      "id": "clutch_construction",
      "title": "The clutch aligns two source paths",
      "citations": [
        "C1051–C1056",
        "File61 §§6.3–6.6,7.3–7.6,8.2–8.4",
        "File62 §§1.1–1.4,2.4"
      ],
      "text": "The clutch begins with a comparison between maximum lifespan capacity and regular elapsed chronology. 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 whole translated root 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.",
      "word_count": 192
    },
    {
      "id": "source_constraint_vs_consequence",
      "title": "Separate constraints from their consequences",
      "citations": [
        "C1039",
        "C1042–C1047",
        "C1053–C1057",
        "File60 §§2–6",
        "File61 §§6–8"
      ],
      "text": "A 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.",
      "word_count": 203
    },
    {
      "id": "full_42_field_interpretation",
      "title": "Forty-two coordinates form one structured field",
      "citations": [
        "C1048–C1051",
        "C1056–C1057",
        "File61 §§7.3A–7.6",
        "File62 §§1.2–1.4"
      ],
      "text": "The 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.",
      "word_count": 200
    }
  ]
}