File: File_58 Title: The Numbers 28–29 Tishri Sacrificial Ledger — Jacob, Exile, Return, and the Forty-Jubilee Hinge Status: Final; post-final pressure tested July 12 2026; author-invoked Finalization complete; Pass 2 verified; bounded Final File_68 reciprocal pointer applied August 13 2026 Finalization status: Complete July 12 2026; temporary pass-language removed; necessary audit and dependency controls retained; bounded File_57 / File_20 routing and control-document registration applied Pass 2 verification status: Complete July 12 2026; machine diff, change-class audit, 253/253 arithmetic checks, 30/30 lint / dependency checks, and source-section coverage audit PASS; not a pressure test Pressure-test status: Current; full post-final pressure test complete July 12 2026; independent arithmetic, ledger-conservation, phase, state-firewall, dependency-routing, claim-status, and publication-clean checks PASS; bounded stale pass-language cleanup applied; no publication blockers; focused reciprocal-routing verification complete August 13 2026 for the bounded File_68 pointer; no new full pressure test claimed Reciprocal-routing verification status: Bounded Final File_68 pointer applied and focused machine-diff, dependency, guard, and Markdown checks completed August 13 2026; no new full pressure test. Register Agreement status: File_58 vocabulary and fifty Machine Guards registered at State_Vocabulary_Register v1.24 Part D §D.22; Restart Capsule v11.23 routing current; bounded File_57 and File_20 updates focused pressure tested; File_68 reciprocal guard registered at State Vocabulary Register v1.40 Part D §D.32 and routed through Restart Capsule v11.39; no pre-existing proof-bearing state or Primary anchor changed Source-history status: Repository conversion of the previously published human-facing article “Feast of Tabernacles as Cipher: How Numbers 28–29 Encodes Jacob, Exile, and Return (with Jubilees as Second Witness)” Primary domain: Calendar; Comparative; Regular; Prophetic; Theological Traditions: MT; LXX; SP; BJ / Jubilees; Enochian; NT / Johannine by comparison Canonical source: Markdown Classification: Applied List–Chronology / Sacrificial Ledger UUID: PROTOCOL_TISHRI_SACRIFICIAL_LEDGER Primary textual corpus: Numbers 28–29; Leviticus 16 by subordinate overlay; Genesis 32–33; Genesis 41; Genesis 45–46; Genesis 50; 1 Enoch 89; Jubilees 7; Jubilees 13; Jubilees 16 Primary values: 7; 14; 16; 21; 30; 33; 40; 49; 60; 66; 70; 110; 182; 189; 280; 360; 400; 430; 490; 550; 1274; 1323; 1960 Secondary comparison values: 4; 5; 282; 285; 287 Primary chronology anchors: 2166 BC; 2006 BC; 1929 BC; 1909 BC; 1896 BC; 1876 BC; 1859 BC; 1846 BC; 1446 BC; 1406 BC; 606/605 BC; 587/586 BC; 537/536 BC; 516 BC; 6 BC Appendix-only File_58 derived comparison coordinates: 1806 BC; 1873 BC Rounded Scaffold comparison endpoints: 1916 BC; 1806 BC Appendix-only dependency-controlled comparison label: 1906 BC Dependency-controlled comparison anchors: 1973 BC; 1826 BC; 1749 BC; 1694 BC; 1661 BC; 622 BC; 573 BC; 466 BC; 458 BC; 445 BC; AD 31t/32n; AD 32t; AD 65 Related files: File_00; File_01; File_03; File_04; File_05; File_06; File_08; File_09; File_12; File_13; File_14; File_15; File_16; File_17; File_18; File_20; File_22; File_29; File_51a; File_54; File_57; File_68 Major operators: printed-animal numeral ledger; complete ritual-animal ledger; slaughtered-offering subset; five-drove source-order operator; purity partition; sex partition; sex/purity dual-partition comparison; female source-order cumulative display; printed-household subtotal ledger; category-partition operator; declared category-order operator; maternal-household pairing; bracket/interior pairing; Genesis 33 three-group household ordering; appendix-only Genesis 46 chronology tests; count-to-chronology projection; male-first clean sequence; unclean framing sequence; animal-year projection; shemitah ×7; same-side BC span; civil cross-axis span BC + AD − 1; local festival-order reversal; tradition-local −33; tradition-local −182; tradition-local −215 Major modal states: surface sacrificial-list state; selected sacrificial-list cipher state; Numbers-only 280 state; Enochian fixed-week state; lunar comparison state; Leviticus 16 complete ritual-animal ledger state; Leviticus 16 slaughtered-offering subset state; 280/282/285/287 comparison-matrix state; animal-year precedent state; shemitah-scale state; source-order state; category-major reorder state; five-drove source-order state; purity-partition 490/60 state; sex-partition 490/60 state; sex/purity dual-partition invariance state; female source-order 400/430/470/490 state; male-first clean sequence state; unclean framing sequence state; Joseph good/bad polarity state; Genesis 46 famine-context animal-year state; 1 Enoch 89 flock-reception state; Genesis 46 four-household subtotal state; Genesis 33 three-group household order state; appendix-only Genesis 46 23/33/14 chronology sequence state; appendix-only Benjamin 1906 BC shared-label state; appendix-only 1873 BC late-famine derived state; Rachel-ewe lexical state; Leah disputed bovine-etymology state; Rachel-household 14 / Joseph 7 + 7 structural state; Bilhah-household 7 single-heptad state; Genesis 46 66/70 headcount state; Genesis 46 MT 70 / LXX 75 comparison state; appendix-only Entry-plus-70 projection state; appendix-only 1806 BC bilateral 360/400 coordinate state; appendix-only Joseph Rounded 40/30/40 symmetry state; appendix-only Jacob–Joseph 30/40 corroboration state; appendix-only Jacob mourning 40/70 state; MT Jacob lane; LXX −33 lane; SP −215 lane; BJ / Jubilees comparison state; cumulative comparison state; Johannine endpoint proposal state; future Johannine-file handoff state Revision basis: 490d Repository Style Guide v2.5; Restart Capsule v11.23; Project Procedures v3.5; State Vocabulary Register v1.24; File_57 Final with bounded File_58 routing update; latest supplied File_14, File_16, and File_20 Final sources; author clarification on declared local cipher operators; author clarification on the Genesis 46 famine context and Joseph Rounded 40 + 30 + 40 structure; author clarification on 1 Enoch 89 flock symbolism and the Rachel 14 / Bilhah 7 household substructure; author direction routing Ezra and Genesis 46 chronology projections to appendices as speculative future-study material; author decision adopting the compact complete Leviticus 16 +5 overlay ledger; Pass 2 verification report; author-invoked Finalization; supplied source article; Final File_68 after the August 13 2026 Finalization refresh; State Vocabulary Register v1.40; Restart Capsule v11.39

File_58 — The Numbers 28–29 Tishri Sacrificial Ledger

Related Repository Files

Source-history note: The WordPress article remains the human-facing publication source-history layer. This Final Markdown file is the canonical AI-forward repository source. Publication-layer reading instructions, typography notes, figure placeholders, and drafting-assistance prose do not carry repository proof weight.

File_68 182×7=1274 reciprocal note

Final File_68 cites File_58's independently derived 182×7=1274 and the parallel 1260/1274 calendar forms only as corroboration for the generation-resolved accordion. The Numbers 28–29 ledger supplies an independent 182-based calendar witness; it does not generate the File_68 rails.

Machine Guard [FILE_58 FILE_68 182×7 CALENDAR-LEDGER ROUTING]: Final File_68 may cite 182×7=1274, 1260=3.5×360, and 1274=3.5×364 as File_58-controlled collateral evidence. File_58 retains the sacrificial-list boundary, 182/189/280 ledger, Enochian fixed-week state, and all chronology applications. File_68's 180/182 cells, full-resolution coordinates, Flood boundaries, and Sanctuary matrix are not imported into File_58 as proof or Primary anchors.

0. File-function and controls

0.1 File-function

File_58 records the Numbers 28–29 Tishri 1–22 sacrificial ledger as an applied demonstration of the Biblical List–Chronology Template.

The file argues that the bounded sacrificial list has two simultaneous functions:

1. a surface legal, ritual, and calendrical register;
2. a secondary printed-animal numeral ledger whose declared arithmetic may be projected into chronology.

The primary ledger produces:

182; 189; 280
1274; 49; 490; 1323; 1960

The file then tests those constants against Jacob, Exile, Return, Exodus, Conquest, BJ / Jubilees, the MT / LXX / SP comparison field, selected Genesis animal lists, and a dependency-controlled Johannine endpoint proposal.

The file does not claim that every list automatically encodes chronology. It adopts the File_57 rule that a candidate list must be bounded, every load-bearing numeral must be accounted for, the ledger and sequence operators must be declared before chronology is tested, and alternative states must remain visible.

Argument-control rule: Textual data and arithmetic facts carry the base layer. Structural inference may support the argument only when the list boundary, ledger state, category partition, sequence, scale, direction, and chronology operator are explicit. Historical-critical design hypotheses, typological readings, and providential synchronizations do not replace arithmetic or source control.

Interpretive-posture note: The file does not raise the claim-status of a pattern merely because collateral evidence accumulates. Collateral evidence may make a reading more coherent within the local narrative and within ancient scribal or Second-Temple numerical habits, while the intended meaning remains unproved. The descriptive phrase midrash-like may be used only for associative, list-sensitive interpretation; it does not assert a formal rabbinic genre or date. Modern prose expectations are not treated as the sole standard for what an ancient list could communicate, but ancient intelligibility remains a historical-critical hypothesis rather than an arithmetic fact.

0.2 Working state register

Modal-state rule: A shared number, date-label, animal, species, sex, category, or sequence does not create identity unless list boundary, ledger state, category partition, sequence operator, node-class, unit, and chronology operator agree.

0.3 File map

Machine Guard [FILE MAP RESTRAINT]: The File map exists for AI retrieval. Do not expand it into a prose-heavy duplicate of the heading hierarchy.

0.4 Claim-status control

Primary-burden rule: The primary argument rests on the bounded Numbers 28–29 ledger, exact arithmetic, explicit Genesis animal-year precedent, and repeated category-controlled structures. No formal probability model is supplied.

0.5 Operator register

0.6 Machine Guards

Machine Guard [SELECTED LISTS ONLY]: The authorial methodology permits testing potentially broad narrative-list application, including Genesis lists, but no list becomes an active cipher merely because it contains numbers. Each list must satisfy the File_57 selection and anti-cherry-picking controls.

Machine Guard [DISPLAYED-NUMERAL SUFFICIENCY]: In a declared symbolic list state, count the numerals supplied by the text. Unnumbered dependents, offspring, attendants, or implied members do not add an inferred quantity to the cipher ledger. The surface narrative remains valid, but speculative reconstruction of an unstated physical total is outside the printed-number operator.

Machine Guard [ALL ROWS USED ONCE]: A declared category-order sequence must use every bounded numerical row exactly once unless the file explicitly opens an overlapping printed-number state. Do not omit an inconvenient row, duplicate a favorable row, or invent an unstated quantity.

Machine Guard [CATEGORY BASIS REQUIRED]: Reordering must follow a category supplied by the text or controlled by the canonical corpus: species, sex, clean/unclean classification, good/bad polarity, maternal household, festival unit, or another explicitly justified category. A chronology target may not generate the category after the fact.

Machine Guard [SEQUENCE PREDECLARATION]: Declare the primary and secondary sort keys before calculating chronology. State whether the active sequence is source order, sex-major order, purity order, polarity order, maternal-household order, frame order, or local reversal.

Machine Guard [MINIMAL DETERMINISTIC REORDERING]: Once the category hierarchy is declared, preserve the original relative order inside each category unless a second sort key is also declared. Prefer the smallest deterministic transformation that accounts for all rows.

Machine Guard [SOURCE ORDER / CIPHER ORDER NON-COLLAPSE]: The printed narrative sequence and a declared cipher sequence are simultaneous states. Do not rewrite the biblical text as though the category-major order were its surface order.

Machine Guard [CLEAN / UNCLEAN CLAIM SPLIT]: Species and sex are textual data. Clean / unclean classification is a canonical Torah classification. The chronological function of the partition is structural inference.

Machine Guard [ESAU 550 NON-HEADCOUNT SPECULATION]: The Genesis 32 symbolic total is the sum of the displayed numerals, 550. The words “with their young” do not license guessing an additional camel-young count. The physical herd may have contained unnumbered young, but that question is outside the cipher ledger.

Machine Guard [FIVE-DROVE SOURCE ORDER]: Preserve Genesis 32’s five textual droves—goats, sheep, camels, cattle, and donkeys—as a source-order state. Category-major sequences may be tested separately, but they must not replace the printed procession.

Machine Guard [SEX / PURITY DUAL-PARTITION]: The displayed numerals yield 490/60 under both purity and sex partitions. State which partition is active. Do not treat the two partitions as identical categories merely because their totals coincide.

Machine Guard [FEMALE 400/430/470/490 VALUE REGISTER]: The female source-order cumulative values 400, 430, 470, and 490 may be compared with the Affliction–Exodus, Entry–Exodus, Entry–Conquest, and LXX Haran–Conquest spans. They do not form one single-anchor chronology walk; each comparison must name its own endpoints.

Machine Guard [DONKEY ROW TRANSLATION STATE]: The final donkey row may be rendered “male donkeys” or “young donkeys / foals” in English translations. File_58 may use the male-row state only where the chosen textual rendering is declared. The printed numeral 10 remains stable.

Machine Guard [MALE-FIRST CLEAN SEQUENCE]: For the active clean chronology sequence, use male goats 20, rams 20, bulls 10, female goats 200, ewes 200, and cows 40. This is the declared sex-major sequence, not the Genesis source order.

Machine Guard [UNCLEAN FRAMING SEQUENCE]: For the active unclean chronology sequence, use female donkeys 20, camels 30, and male donkeys 10. This is the declared donkey-frame sequence, not the Genesis source order.

Machine Guard [GENESIS 33 / GENESIS 46 CROSS-SCENE ORDER]: The 23 + 33 + 14 order is not the printed Genesis 46 order. It is a declared cross-scene sequence supplied by Genesis 33: handmaids and children, Leah and children, Rachel and Joseph. Preserve both source orders as distinct states.

Machine Guard [HANDMAID 23 / KEY-OF-23 NON-AUTOMATICITY]: The handmaid subtotal 16 + 7 = 23 is an arithmetic list value. It may be compared with the repository Key of 23, but it does not automatically activate the 25/23 operator or any Key-of-23 expansion without a separately declared state.

Machine Guard [LOCAL 460 NON-COLLAPSE]: The span 1906 BC → 1446 BC = 460 belongs to the Benjamin-to-Exodus comparison generated by the 23/33/14 sequence. Do not collapse it with the regular or cumulative 2nd Cainan 460, Watcher 460, or another same-valued repository state.

Machine Guard [BENJAMIN 1906 SHARED-LABEL]: The 1906 BC landing in the 23/33/14 sequence may be compared with File_01’s Benjamin birth label. Do not collapse it with the BJ Abraham Call state also labeled 1906 BC.

Machine Guard [1873 FAMINE COORDINATE]: 1873 BC is a derived late-famine comparison point, two years before the 1871 BC famine-end shorthand. Do not promote it to a primary event anchor without separate source control.

Machine Guard [GENESIS 46 SUBTOTAL / HEADCOUNT NON-COLLAPSE]: The four printed household subtotals 33, 16, 14, and 7 sum to 70, while Genesis 46 separately states 66 direct descendants who came with Jacob and 70 for the house of Jacob in Egypt. Preserve the printed-subtotal, entrant, and household-total ledgers as distinct textual states.

Machine Guard [GENESIS 46 VERSE-TOTAL CONTROL]: File_58 uses the explicit verse-level totals 33, 16, 14, and 7. Do not silently repair the Leah-name enumeration, add unnamed persons, or subtract named persons in order to manufacture the stated 33.

Machine Guard [MT 70 / LXX 75 NON-COLLAPSE]: The MT household total 70 and the LXX / Acts comparison total 75 are distinct textual-tradition states. File_58’s present maternal-household arithmetic is MT 70; the 75 state must be separately declared before use.

Machine Guard [SEVENTY PERSONS / SEVENTY YEARS CLAIM SPLIT]: The household total 70 is textual datum. The projection 1876 BC → 1806 BC = 70 is structural inference under count-to-chronology. Do not state that Genesis 46 explicitly converts the persons into years.

Machine Guard [FAMINE-CONTEXT PRECEDENT]: Genesis 41 explicitly equates the seven good and seven bad cows with years, and Genesis 45 places Jacob’s household descent within that same seven-year famine field. Treat this as proximate narrative warrant for testing the household 70 as years, not as an explicit equation of persons with years.

Machine Guard [FLOCK TYPOLOGY CLAIM STATUS]: The description of Jacob’s seventy-person covenant household as God’s flock is a typological / theological reading. It may explain why a people-count could participate in the animal-time grammar, but it does not carry the arithmetic proof burden.

Machine Guard [ENOCH FLOCK / YEAR NON-COLLAPSE]: 1 Enoch 89 establishes the symbolic substitution of Jacob’s sons and descendants as sheep and flocks within a historical apocalypse. It does not state that their numerical total equals years. Use 1 Enoch as reception-history evidence for the flock encoding, Genesis 41 as the explicit animal-year precedent, and classify the application of Genesis 46’s 70 to a seventy-year span as structural inference.

Machine Guard [RACHEL 14 / JOSEPH 7+7 CLAIM SPLIT]: Rachel’s household subtotal 14, Joseph’s inclusion within that household, and Joseph’s interpretation of 7 + 7 cows as 7 + 7 years are textual data and arithmetic facts. The proposal that Rachel’s 14 intentionally encodes Joseph’s fourteen cow-years is structural inference, not textual equation.

Machine Guard [BILHAH 7 SINGLE-HEPTAD RESTRAINT]: Bilhah’s household subtotal 7 is an explicit textual total. It may be compared with Rachel’s 14 as one heptad beside two heptads, but it must not be converted into years without a separately declared operator and target.

Machine Guard [RACHEL / LEAH LEXICAL RESTRAINT]: Rachel’s name securely means “ewe.” Leah’s proposed “cow / wild cow” etymology is disputed and competes with a derivation related to weariness. Rachel’s lexical datum may support flock symbolism; Leah’s bovine proposal remains collateral only.

Machine Guard [1806 SHARED-LABEL NON-COLLAPSE]: File_58’s 1806 BC Entry-plus-70 coordinate is a derived comparison node. It must not be collapsed with File_03’s Rounded Scaffold clarity-only Joseph death at 1806 BC, File_03’s BJ Abraham death at 1806 BC, or Joseph’s standard death at 1805 BC.

Machine Guard [JOSEPH ROUNDED 40/30/40 STATE]: The sequence 1916 → 1876 → 1846 → 1806 = 40 + 30 + 40 is active only under the File_51a Rounded Scaffold comparison state. Preserve 1876 BC as Entry and 1846 BC as Affliction / Bondage origin. Do not convert the rounded endpoints into ordinary MT event dates or use the symmetry to overwrite File_03.

Machine Guard [ROUNDED JOSEPH AGE NON-LITERAL]: The Rounded Scaffold span 1916 BC → 1876 BC = 40 is not Joseph’s textual age at Entry. The textual chronology remains 30 + 7 + 2 = 39, with standard Joseph dates 1915–1805 BC. The rounded 1916–1806 BC life is methodological and comparison-only.

Machine Guard [JACOB MOURNING 40 / 70 CLAIM SPLIT]: Genesis 50 explicitly states forty embalming days and seventy mourning days. The 30 + 40 = 70 reading is a derived remainder display, not an independently printed 30, and it presumes the forty-day embalming interval is included within the seventy-day mourning horizon.

Machine Guard [JOSEPH POLARITY PRECEDENT]: Genesis 41 explicitly equates cows with years and distinguishes good and bad groups. This supplies textual warrant for animal-year and polarity methods; it does not prove every later animal list without local controls.

Machine Guard [NUMBERS-ONLY / LEVITICUS-16 FIREWALL]: The controlling 280 total is Numbers-only. The Leviticus 16 rite is a separate overlay state and must not be silently folded into the base ledger.

Machine Guard [LEVITICUS-16 OVERLAY LEDGER]: The Leviticus 16 +5 is the complete displayed ritual-animal ledger: 1 bull + 2 rams + 2 goats = 5. It includes the live goat because the text numerically specifies two goats within the paired rite. The slaughtered-offering subset is 4 and must not be substituted silently for the displayed ritual ledger. Declare the overlay explicitly as 285 or 287 according to the active Sabbath state. No independent chronological significance is claimed for 285 or 287 in this file.

Machine Guard [PRIESTLY / PROPHETIC / ENOCHIAN NON-COLLAPSE]: Priestly 336, Prophetic 360, and Enochian 364 are distinct registers. The fixed-week 280 state is Enochian 364, even though the list itself is sacrificial and priestly in function.

Machine Guard [1260 / 1274 PARALLEL STATES]: 1260 = 3.5 × 360 and 1274 = 3.5 × 364 are parallel calendar states. Do not describe one as a correction of the other without an explicitly declared transformation.

Machine Guard [FESTIVAL REVERSAL NON-MIRROR]: A local festival-order reversal is not Protocol 1, Protocol 2, inverse-number reversal, or formal Mirror.

Machine Guard [MT / LXX / SP OFFSET LOCALITY]: The −33, −182, and −215 shifts are local comparison operators. Do not propagate them globally or collapse them with Sojourn 215, Exodus 215, or unrelated variant mechanisms.

Machine Guard [T/N PHASE DECLARATION]: Every t/n landing must state its phase convention and be checked component-wise. An unsuffixed integer subtraction does not by itself prove a paired Tishri/Nisan label.

Machine Guard [KINGS 49/50 NON-CORRECTION]: The historical and schematic Kings ledgers are adjacent states. The goats’ 49 may corroborate a 49 member but does not repair or replace the Kings chronology.

Machine Guard [REGULAR / CUMULATIVE NON-COLLAPSE]: Cumulative chronology is a method, not a fourth manuscript tradition. Its dates and operators must remain dependency-controlled.

Machine Guard [JOHANNINE ENDPOINT DEPENDENCY]: AD 31t/32n and AD 32t remain proposal states until their phase arithmetic and File_13 dependencies are verified.

Machine Guard [AUTHORIAL / PROVIDENTIAL FIREWALL]: Local list construction may support a historical-critical design hypothesis. Remote chronological or cross-corpus agreement does not prove ancient access; classify it as providential synchronization or exploratory corroboration where appropriate.

Machine Guard [FILE_57 / FILE_58 ROUTING]: File_57 retains the compact Numbers 28–29 precedent and routes the full sacrificial ledger, manuscript lanes, historical applications, narrative-list sequences, and Johannine synthesis to File_58. File_20 Recommended Cross-File Update 22 is fulfilled by File_58. Do not reverse this control direction.

Machine Guard [MIDRASH-LIKE NON-ANACHRONISM]: The term midrash-like may describe associative numerical interpretation, intertextual regrouping, or list-sensitive reading that could be intelligible in an ancient scribal setting. It must not be used to claim that the source belongs to a later formal rabbinic genre or to prove compositional intent.

1. Narrative-list category and sequence protocol

1.1 General methodological hypothesis

The authorial working hypothesis is that category-controlled numerical arrangement may occur broadly across Genesis narratives and lists. File_58 therefore treats the Esau gift sequence not as an isolated exception but as a worked example of a potentially general list grammar.

The hypothesis is general but locally proven:

• general, because the same kinds of partitions recur in genealogies, animal visions, gifts, household lists, and sacrificial ledgers;
• local, because each list must independently declare its boundary, categories, sequence, operator, and null tests.

Potential application does not equal automatic activation.

1.2 Three sequence layers

These layers may coexist. The cipher-order layer does not claim that the surface text was printed in the same order.

1.3 Permissible category sources

A category-order operator may draw from:

1. explicit row labels in the immediate text;
2. explicit literary polarity, such as good / bad;
3. canonical legal classification, such as clean / unclean;
4. genealogical or household identity, such as Leah / Zilpah / Rachel / Bilhah;
5. sex, species, birth order, or named office;
6. feast, day, or sacrificial category;
7. a second sort key declared before chronology is tested.

1.4 Genesis precedents

Joseph: polarity and animal-year

Genesis 41 supplies two explicit controls:

7 good cows = 7 years
7 bad cows  = 7 years

The text itself defines both the polarity groups and the animal-year operator.

Jacob’s household entering Egypt: four households and the 70 register

Genesis 46 closes four maternal-household blocks with explicit verse-level totals:

The primary printed-subtotal arithmetic is:

33 + 16 + 14 + 7 = 70

The order is already category-controlled by the four maternal houses. It produces several exact internal structures without changing the printed order.

Household-pair structure:

Leah + Zilpah   = 33 + 16 = 49 = 7 × 7
Rachel + Bilhah = 14 + 7  = 21 = 3 × 7
49 + 21 = 70

Bracket/interior structure:

outer members: 33 + 7  = 40
inner members: 16 + 14 = 30
40 + 30 = 70

Running-total structure:

33
33 + 16 = 49
49 + 14 = 63 = 9 × 7
63 + 7  = 70 = 10 × 7

Additional local observations:

16 = 4 × 4
14 = 2 × 7
7  = 7

The value 33 is structurally active through both 33 + 16 = 49 and 33 + 7 = 40; File_58 does not need to force 33 itself into a seven-multiple.

The twelve sons also preserve a maternal-household partition:

Leah 6 + Zilpah 2 + Rachel 2 + Bilhah 2 = 12

Rachel’s ewe-household: 14, Joseph’s 7 + 7, and Bilhah’s 7

Rachel’s Hebrew name securely means ewe. Her Genesis 46 household subtotal is:

14 = 7 + 7

That subtotal includes Joseph, the dreamer who interprets Pharaoh’s two cow groups as years:

7 good cows = 7 years
7 bad cows  = 7 years
7 + 7 = 14

The correspondence is therefore internal to Rachel’s maternal household:

Rachel (“ewe”) household = 14
Joseph within that household interprets 14 cows as 14 years

Bilhah, Rachel’s handmaid and household extension, contributes:

7

This yields a compact maternal comparison:

Rachel = 14 = 2 × 7
Bilhah = 7  = 1 × 7
Rachel + Bilhah = 21 = 3 × 7

The printed subtotals, Joseph’s membership in Rachel’s household, and Joseph’s 7 + 7 cow-year interpretation are textual data and arithmetic facts. The proposal that Rachel’s 14 was arranged to echo Joseph’s fourteen cow-years, or that Bilhah’s 7 functions as a single heptadic unit beside Rachel’s double heptad, is structural inference.

Lexical caution: Rachel’s name securely means “ewe.” Leah’s name has sometimes been associated with “cow” or “wild cow,” but that etymology is disputed and competes with a derivation related to weariness. File_58 may retain the Leah/cow proposal only as collateral lexical evidence.

This establishes Genesis 46 as more than a generic family list: the text supplies the categories and closes each category with its own numeral.

Genesis 33 three-group order

Before Jacob meets Esau, Genesis 33 arranges the household in three groups:

1. the two handmaids and their children;
2. Leah and her children;
3. Rachel and Joseph.

Applied to the Genesis 46 maternal subtotals, this supplies the declared category order:

handmaids: 16 + 7 = 23
Leah:               33
Rachel:              14
                     --
total:               70

This is a textually grounded regrouping operator. All attempts to project 23 + 33 + 14 or other arrangements of the household 70 into dates are classified as speculative future-study material and are preserved in Appendix D rather than in the main argument.

Personnel and household totals

The maternal subtotals must not be confused with one undifferentiated physical travel count. Genesis 46 separately states:

66 = direct descendants who came with Jacob, excluding the sons’ wives
70 = the house of Jacob in Egypt

The four printed maternal subtotals also sum to 70. File_58 therefore treats 70 as the MT covenant-household total, not simply as “seventy children and grandchildren who physically traveled.” The LXX / Acts 75 belongs to a separate textual-tradition state and is not imported into the MT 33 + 16 + 14 + 7 calculation.

Proximate narrative warrant: the seven bad cows and the covenant household

The household descent does not occur in a neutral narrative setting. Genesis 41 has already defined the seven lean cows as seven famine years, and Genesis 45:6 locates Jacob’s descent after two famine years with five still to come. The covenant household 70 therefore enters Egypt inside the same narrative field in which animals explicitly represent years.

This supplies immediate contextual warrant for testing the household count under count-to-chronology:

7 bad cows = 7 famine years
2 famine years elapsed + 5 remaining = 7
70-person covenant household enters during that seven-year field

The proposal that the 70 persons may function as 70 years remains structural inference. The description of the household as God’s flock is a typological / theological reading that explains the fit with the animal-time grammar but does not replace the arithmetic or textual controls.

Second-Temple flock reception: 1 Enoch 89

The Animal Apocalypse of 1 Enoch retells the patriarchal and Exodus history through a sustained animal code. Jacob is represented as a sheep who begets twelve sheep. Joseph is transferred among the wolves, the remaining eleven sheep are brought to live with him, and Jacob’s descendants multiply into many flocks before the wolves oppress them and destroy their young.

The symbolic correspondences are therefore historical and structural:

Jacob and his sons = sheep
Jacob’s descendants = multiplying flocks
Egypt / Egyptians = the domain of the wolves
Egyptian oppression = wolves attacking the flock

This is more than a passing analogy. It is an ancient Jewish symbolic retelling of the Entry and Exodus field in which Jacob’s children and descendants are encoded as a flock.

The passage does not say:

70 sheep = 70 years

It therefore does not prove File_58’s 70 persons → 70 years proposal. It does, however, demonstrate that a Second-Temple Jewish interpreter could understand Jacob’s household as a numbered animal collective within symbolic history.

Genesis 41 and 1 Enoch 89 supply complementary controls:

Genesis 41: animals may explicitly represent years
1 Enoch 89: Jacob’s household may explicitly be represented as sheep / flocks
Genesis 46: the bounded household total is 70

File_58 then tests whether the numbered flock-total 70 also functions chronologically. That final step remains structural inference.

Later in the Animal Apocalypse, the seventy-shepherd framework and numerical recording of the shepherds’ conduct further demonstrate a Second-Temple conceptual field combining Israel-as-sheep, the number seventy, historical periodization, and numerical accountability. This remains reception-history evidence rather than proof that Genesis 46’s 70 was intended as seventy years.

Appendix-only chronology applications of the household 70

The Genesis 46 household arithmetic, famine context, Rachel/Joseph heptads, and 1 Enoch flock reception remain in the main methodology because they establish the textual and reception framework. The following chronological applications are more conjectural and do not carry the File_58 proof burden:

• projecting the whole household 70 from 1876 BC to 1806 BC;
• arranging the households as source order, household pairs, bracket/interior pairs, or the Genesis 33 three-group order and testing them as successive year intervals;
• comparing the derived 1806 BC coordinate with Rounded Joseph;
• comparing Genesis 46 40 + 30, Rounded Joseph 30 + 40, and Genesis 50 40/70;
• translating the proposed 1876–1806 BC rail by Daniel’s 1290.

Appendix D preserves these observations, exact arithmetic, state guards, and untested sequence options as speculative research notes for possible future development. Their removal from the main body is a proof-burden decision, not a rejection of the observations.

Esau’s five droves: source order and dual 490/60 partitions

Genesis 32 presents five separated droves under servant control:

The five-drove source order is itself textually controlled. The same nine printed numerals then yield the identical partition under two independent classifications.

Purity partition:

clean = goats 220 + sheep 220 + cattle 50 = 490
unclean = camels 30 + donkeys 30 = 60

Sex partition:

female = 200 + 200 + 30 + 40 + 20 = 490
male   = 20 + 20 + 10 + 10 = 60

The equality may be displayed:

clean / unclean = 490 / 60
female / male   = 490 / 60

The two partitions are categorically independent even though they return the same totals. Their equality is arithmetic fact; whether the list was deliberately selected to carry both partitions is structural inference.

The female rows also generate a source-order cumulative register:

200
200 + 200 = 400
400 + 30  = 430
430 + 40  = 470
470 + 20  = 490

These values correspond to an expanding chronology field:

1846 BC → 1446 BC = 400   Affliction → Exodus
1876 BC → 1446 BC = 430   Entry → Exodus
1876 BC → 1406 BC = 470   Entry → Conquest
1896 BC → 1406 BC = 490   LXX Bethel/Haran → Conquest

This is a nested value register, not one continuous date walk from a single starting anchor. The increments also expose the internal construction:

400 + 30 + 40 + 20 = 490

where 30 is the Entry/Affliction difference, 40 is the Exodus/Conquest difference, and 20 is Jacob’s Haran-service interval on the active LXX lane.

File_58 also retains two declared chronology sequences:

Clean male-first sequence:
20 male goats → 20 rams → 10 bulls →
200 female goats → 200 ewes → 40 cows

Unclean framing sequence:
20 female donkeys → 30 camels → 10 male / young donkeys

Each displayed numerical row is used exactly once within its declared partition.

1.5 Why the reorder is not arbitrary

The clean sequence is deterministic after the sort keys are declared:

Primary key: clean animals
Secondary key: male before female
Tertiary key: goats → sheep → cattle

The unclean sequence is a declared frame:

female donkey block → camel block → male donkey block

The chronology is tested only after those keys are fixed. The targets do not select the order retroactively.

1.6 Null-test requirements

A proposed category sequence is strengthened when:

• every displayed row receives a function;
• the same hierarchy produces multiple independent landings;
• the sequence preserves internal textual or canonical categories;
• a related list uses the same grammar;
• alternative plausible sequences are recorded rather than suppressed.

It is weakened when:

• a numeral is omitted or duplicated;
• a category is invented only after a target is noticed;
• the sequence requires undeclared switching between source order and category order;
• the claimed chronology depends on guessed physical quantities not supplied by the text.

2. Textual corpus and ledger boundary

2.1 Controlling corpus

The controlling sacrificial corpus is Numbers 28–29 from Tishri 1 through Tishri 22:

• regular daily offerings;
• Sabbaths falling inside the declared window;
• New Moon;
• Trumpets;
• Day of Atonement;
• Sukkot Days 1–7;
• Eighth Day.

Leviticus 16 is a distinct rite and remains outside the controlling total. It is opened only as the subordinate comparison ledger defined in §4.3.

2.2 Calendar-state declaration

The principal calculation operates in the Enochian fixed-week 364 state:

Tishri 1 = Wednesday
Sabbaths = Tishri 4, Tishri 11, Tishri 18

The three Sabbaths add six lambs. A lunar comparison may produce a fourth Sabbath and 282, but that state does not alter the principal 280 calculation.

2.3 Counting rule

Every stated sacrificial animal is counted once within the declared boundary. Offerings described as “besides” the regular offering are added rather than substituted.

3. The Numbers-only 280 ledger

3.1 Category table

Arithmetic checks:

44 + 6 + 11 + 10 + 10 + 189 + 10 = 280
75 + 18 + 176 + 11 = 280

3.2 Sukkot subtotal

70 bulls + 14 rams + 98 lambs + 7 goats = 189
70 + 14 + 98 = 182
182 = 364 ÷ 2

The identity of 182 as both the goat-excluded Sukkot subtotal and half of 364 is an arithmetic fact. Its chronological or manuscript-lane function is structural inference.

3.3 The 270 → 273 → 280 register

280 − 10 Eighth-Day animals = 270
270 + bull + ram + goat = 273
273 + 7 lambs = 280

The values are related but retain separate register identities:

4. Calendar-state architecture

4.1 Controlling fixed-week state

The principal 280 total is generated in the Enochian fixed-week 364 state:

Tishri 1 = Wednesday
Sabbaths inside Tishri 1–22 = Tishri 4, 11, 18
Three Sabbaths × two lambs = 6

The calendar-state claim and the sacrificial-list claim must remain distinct. Numbers 28–29 supplies the offerings. The Enochian fixed-week state supplies the placement of three Sabbaths inside the selected window.

4.2 Priestly / Prophetic / Enochian firewall

The source-history phrase “364-day priestly scheme” is therefore normalized to Enochian 364-day fixed-week state, with priestly / Second-Temple comparison by dependency.

4.3 Lunar comparison and Leviticus 16 overlay

A lunar comparison state may place four Sabbaths within the same nominal Tishri 1–22 window:

280 + 2 additional Sabbath lambs = 282

Numbers 29:11 distinguishes its festival goat from the separate atonement sin offering. Leviticus 16 supplies the fuller atonement rite from Aaron’s household and the congregation:

The two goats form one displayed ritual pair, although one is slaughtered and the other is sent away alive. File_58 therefore distinguishes:

complete ritual-animal ledger = 5
slaughtered-offering subset   = 4

The complete displayed-animal ledger is the relevant +5 overlay under File_58’s printed-number methodology. The resulting comparison matrix is:

These are subordinate comparison states. They do not alter the controlling Numbers-only 280 state and presently carry no independent chronological proof burden. The source estimate that the combined four-Sabbath condition occurs “about once in seven years” is retained only as an exploratory calendar note until independently demonstrated.

4.4 Parallel half-week calendars

The source-history language of “compression” is replaced by a parallel-calendar comparison:

1274 = 3.5 × 364
1260 = 3.5 × 360
1274 − 1260 = 14

1274 is the Enochian half-week form. 1260 is the Prophetic half-week form. Neither corrects the other. The comparison with Jacob’s 14 years is structural inference.

5. Shemitah-scale ledger

5.1 Sukkot over seven years

Checks:

182 × 7 = 1274
7 × 7 = 49
1274 + 49 = 1323
189 × 7 = 1323
70 × 7 = 490

5.2 Full Tishri 1–22 window over seven years

280 × 7 = 1960
1960 = 40 × 49

At Tishri 1:

(New Moon 11 + Trumpets 10) × 7 = 21 × 7 = 147

The equality with Jacob’s lifespan is arithmetic correspondence. Its literary role is structural inference.

5.3 Controlling versus collateral values

The primary sacrificial-ledger constants are:

182; 189; 280; 1274; 49; 490; 1323; 1960

Values derived from remote chronology, genealogy, later reception, or cross-tradition comparison are collateral evidence. They may strengthen coherence without becoming independent proof that Numbers 28–29 was composed as a chronology cipher.

6. MT Jacob–Exile–Return applications

6.1 Exact same-side landings

These rows are arithmetic facts under unsuffixed same-side BC subtraction. Their interpretation as Jacob–Exile–Return architecture is structural inference.

6.2 Phase-resolved Jacob-death route

The exact Nisan-phase spine is:

1859n BC → 585n BC = 1274
585n BC → 536n BC = 49
1859n BC → 536n BC = 1323

The first span is the Sukkot subtotal without goats across one shemitah:

1274 = 182 × 7

The second span is the goat component:

49 = 7 × 7

The historical exile and return fields may also be displayed as phase envelopes:

586t/585n BC
537t/536n BC

The 49-year relation is exact componentwise across those envelopes:

586t BC → 537t BC = 49
585n BC → 536n BC = 49

Accordingly, the 1274 lands exactly at the Nisan member 585n BC, while the full 1323 lands exactly at the Nisan member 536n BC. The Tishri members remain corresponding adjacent phase labels. File_58 does not introduce 1860t/1859n as a new Jacob-death pair.

6.3 Seventy-year collateral field

The exact exile/restoration intervals remain visible:

606 BC → 536 BC = 70
586 BC → 516 BC = 70

Comparisons between these intervals and Genesis 46’s household 70 are classified as speculative collateral research. The Entry-plus-70 projection, Daniel-1290 interval translation, 1290/1260 = 30 head pair, Rounded Joseph 40/30/40, and Genesis 50 mourning comparison are preserved in Appendix D. They do not carry the main MT Jacob–Exile–Return proof burden.

6.4 Forty-jubilee civil endpoint

The ordinary civil cross-axis span checks:

1929 BC → AD 32 = 1929 + 32 − 1 = 1960
1859 BC → AD 32 = 1859 + 32 − 1 = 1890 = 189 × 10

The phase form AD 31t/32n is treated in §11 as a dependency-controlled endpoint proposal.

7. Declared sequence tests

7.1 Forward Sukkot-day sequence

The seven Sukkot day totals are:

30; 29; 28; 27; 26; 25; 24

After ×7, the forward sequence from 1859 BC is:

The 1446 BC, 536 BC, and 466 BC landings are arithmetic facts under the declared sequence.

7.2 Reverse-order festival sequence

The source-history term “mirrored run” is normalized to reverse-order sequence, because no formal Mirror protocol is active.

The 676 BC row lies 70 years before 606 BC:

676 − 606 = 70

Its role is collateral corroboration, not a primary anchor.

7.3 Restoration-order sequence

From 1929 BC, apply the Eighth Day and Sukkot first:

70 + 1323 = 1393
1929 − 1393 = 536

Then apply the remaining blocks:

Atonement 70
Trumpets 70
New Moon 77
Sabbaths 42
Daily 308
Total = 567

Civil cross-axis control:

536 BC → AD 32 = 536 + 32 − 1 = 567

The sequence is a declared local restoration-order operator. Its theological association with “turning captivity” is typological reading.

7.4 Genealogical yardstick

Two inclusive name-counts are retained:

Adam → Isaac = 21 names
Jacob → Ezra = 21 names in the telescoped priestly genealogy
21 + 21 = 42

The conversion:

21 × 70 = 1470 = 3 × 490

is arithmetic fact. The use of 70 as a generational yardstick and the extension from Ezra to Messiah are schematic structural inference. Full treatment is moved to Appendix E and does not carry the Numbers-ledger proof.

8. BJ / Jubilees and Enochian comparison

8.1 Isaac 273 + 7 = 280

The File_20-controlled comparison preserves:

273 + 7 = 280
273 = 3 × 91
280 = 7 × 40

The festival-calendar and circumcision data are textual data within BJ / Jubilees. The cross-corpus relation to the Numbers ledger is structural inference.

8.2 Noah’s 1 + 1 + 7 + 1

Jubilees 7 supplies a single-day offering pattern comparable with:

1 bull + 1 ram + 7 sheep + 1 goat = 10

This is a derivative ancient witness to the same numerical form. It does not establish direct dependence on Numbers 29.

8.3 Abraham and Sukkot

Jubilees’ Abrahamic Sukkot material supports the historical plausibility of symbolic festival counting in a Second-Temple setting. It remains a non-canonical derivative witness under File_20 controls.

8.4 Forty-jubilee comparison

The source associates Jubilees’ Abram/Bethel chronology with a 1960 = 40 × 49 hinge. This is retained as a source-history comparison and requires File_20 source-control for exact AM/BC conversion. It is corroborative rather than load-bearing.

9. Prophetic-span interface

9.1 1290 and 1335

Exact same-side rows include:

1876 − 586 = 1290
1871 − 536 = 1335

The broader famine-end phase forms remain File_16/File_17-controlled.

9.2 1260 / 1274

1260 = 3.5 × 360
1274 = 3.5 × 364
difference = 14

The relation to Jacob’s 14 years is structural inference. Do not describe 1260 as a repaired 1274.

9.3 Sukkot bulls and Danielic 490

70 bulls × 7 = 490

The equality is arithmetic fact. The reading of Sukkot’s descending bulls as Daniel 9’s 69 + 1 cadence is typological / structural interpretation.

9.4 Northern and southern judgment comparisons

The source retains the File_16/File_17 comparison field:

1876/1871 → 726/721 = 1150
1876 → 586 = 1290

The actual/schematic Samaria firewall remains active. These rows corroborate the prophetic field but do not arise from the Numbers ledger.

10. Kings and Temple dual-ledger comparison

10.1 Historical and schematic anchors

File_08 controls:

Historical Temple foundation: 967/966 BC
Schematic Temple pivot:       1017/1016 BC

The associated 49/50 difference is an adjacent-state dual ledger, not an error correction.

10.2 Preserved 430 blocks

The goat-derived 49 may corroborate one adjacent-state member. It does not generate or repair the Kings chronology.

10.3 Source-history “Jubilee Gap”

The human-facing article described the raw reign-sum surplus as approximately 49.5 years. File_58 normalizes that observation to the File_08-controlled adjacent 49/50 dual-ledger state rather than treating 49.5 as an executable correction.

The phrase “Jubilee Gap” is retained as source-history shorthand for the Kings dual-ledger difference. It must not imply that co-regencies have been solved by subtracting the sacrificial goats.

11. Johannine endpoint proposal and future-file handoff

11.1 Civil-span base

The arithmetic base is exact:

1929 BC → AD 32 = 1960
1960 = 40 × 49

AD 32 is therefore an executable civil endpoint of the 1960 span.

11.2 Phase-labeled endpoint

The source proposes:

AD 31t/32n = terminal phase pair
AD 32t     = following Tabernacles threshold

This is not ordinary civil-year arithmetic. File_58 does not yet possess a controlling Johannine chronology that fixes John 7, John 8, or the proposed terminal feast to these phase labels. The phase pair and the following AD 32t threshold therefore remain dependency-controlled historical-critical / typological proposals.

11.3 Future Johannine-file handoff

The author anticipates one or more later repository files drawn from a larger study of the Gospel of John and its numerics. Those files may establish a fuller feast sequence, ministry chronology, Temple clock, or phase-resolved date field.

Until such a file is finalized:

• File_58 controls only the exact 1929 BC → AD 32 = 1960 arithmetic;
• AD 31t/32n and AD 32t remain proposals;
• File_58 does not use the Johannine identification as proof of the Numbers ledger;
• a later John-focused file may confirm, refine, relocate, or reject the proposed phase labels;
• any later promotion requires a bounded File_58 dependency update rather than silent retrojection.

11.4 “Not yet fifty”

The relation among John 8:57, Herod’s Temple rebuilding, and a 49/50 threshold is retained as a historical-critical / typological hypothesis:

AD 32 − 50 = 19 BC
AD 32 − 49 = 18 BC

It does not prove the date of John 7 or establish that “fifty” was intended as a Jubilee cipher.

11.5 John 5 alternatives

The Passover and Tabernacles identifications of John 5 remain appendix-level reception-history options. File_58 does not use either option as a chronological premise.

12. LXX −33 lane

12.1 Local state

The −33 operator is local to the Jacob–Exodus family-unit field. It is not a global LXX correction.

The source-history decomposition is the File_04-controlled family-unit state:

33 years in Canaan + 397 years in Egypt = 430
1843 BC − 1446 BC = 397

The 33 + 397 interpretation places Jacob’s return from Haran at 1876 BC and Entry into Egypt at 1843 BC. It does not replace the MT 430-Egypt state, where Entry itself is 1876 BC.

12.2 Exact LXX landings

1896 − 606 = 1290
1876 − 586 = 1290
1826 − 536 = 1290

1826 − 1749 = 77
1749 − 1406 = 343 = 7³

1896 − 622 = 1274
1896 − 573 = 1323
1406 − 622 = 784 = 16 × 49
1406 − 573 = 833 = 17 × 49

The 622 BC and 573 BC event identifications remain dependency-controlled comparison labels.

The source also preserves a Conquest / land-rest companion under the LXX lane:

1889 BC → 1406 BC = 483
1406 BC → 1399 BC = 7
483 + 7 = 490

The 1889 BC label is the close of Jacob’s first seven-year work interval in the LXX state. The 1406/1399 BC Conquest and land-rest labels remain File_06-controlled. The arithmetic is exact; its Daniel-9 interpretation is structural / typological comparison.

12.3 Jacob-birth calculation

1973 − 567 = 1406
1973 − 1274 = 699

The article’s former “approximately 700 BC” wording is not an exact integer equation. Any 700t/n display requires a separate phase derivation and remains an audit item.

12.4 Macro endpoint

1896 BC → AD 65 = 1896 + 65 − 1 = 1960

The Neronian / Temple-horizon interpretation is historical comparison, not primary proof.

13. Esau and Joseph narrative ledgers

13.1 Printed-number total

clean = 200 + 20 + 200 + 20 + 40 + 10 = 490
unclean = 30 + 20 + 10 = 60
female = 200 + 200 + 30 + 40 + 20 = 490
male = 20 + 20 + 10 + 10 = 60
grand total = 550
490 − 60 = 430

The 550 is the displayed-numeral ledger. Unnumbered camel young do not introduce guessed cipher quantities. The same 490/60 result under purity and sex is a dual-partition convergence, not a collapse of purity into sex.

13.2 Five-drove source order and female cumulative register

The textual drove order is:

goats → sheep → camels → cattle → donkeys

The female-row cumulative values are:

200 → 400 → 430 → 470 → 490

They compare with four nested chronology spans:

The value sequence is text-order arithmetic. Its alignment with nested chronology is structural inference. Because the four spans do not share one fixed head and tail, the table is not represented as a single sequential date walk.

13.3 Male-first clean chronology sequence

Declared order:

20 male goats
20 rams
10 bulls
200 female goats
200 ewes
40 cows

Starting from 1896 BC:

The landings are arithmetic facts under the declared operator. The sequence’s intended design is historical-critical inference.

13.4 Unclean framing sequence

Declared order:

20 female donkeys
30 camels
10 male donkeys

Starting from 1896 BC:

1896 − 20 = 1876
1896 − 50 = 1846
1896 − 60 = 1836

1876 − 1446 = 430
1846 − 1446 = 400
1836 − 1446 = 390
1836 − 1406 = 430

13.5 Joseph’s explicit animal-year warrant

Genesis 41 explicitly equates the good and bad cows with years. This is the direct textual precedent. The application of that grammar to Esau’s gift and Numbers 28–29 remains locally controlled structural inference.

13.6 Collateral, not claim escalation

Genesis 46, Genesis 50, the Rounded Joseph 40/30/40, Esau’s 490/60, and Joseph’s 7 + 7 are collateral evidence within the same Jacob–Joseph period. Their accumulation increases contextual coherence; it does not change an inference into textual proof.

14. SP −215 lane and the 182 hinge

14.1 Offset field

MT → LXX = 33
LXX → SP = 182
MT → SP = 215
33 + 182 = 215

These are local Jacob–Exodus state differences.

14.2 Exact substitutions

1274 − 1092 = 182
1323 − 1141 = 182
1092 = 3 × 364

1714 − 622 = 1092
1714 − 573 = 1141

The 49 goat block remains:

1092 + 49 = 1141

14.3 Mid-feast comparison

John 7:14’s “middle of the feast,” the Sukkot midpoint, the 182 subtotal, and the LXX-to-SP difference are structurally comparable. The text does not explicitly identify the manuscript offset with the festival subtotal.

14.4 Abraham-line 1290

1876 − 586 = 1290

In the SP / Sojourn-division state, 1876 BC functions as Abraham Call / Death of Terah rather than Jacob Entry. Shared labels do not create shared events.

15. Cumulative comparison state

15.1 Method boundary

Cumulative chronology is a lifespan-stacking method, not a fourth manuscript tradition. It may function as a comparison lane, but it must not be called a fourth canonical witness.

15.2 Verified cumulative rows

15.3 Aaron/Moses phase state

The File_22-controlled phase display is:

1937t BC → 1447t BC = 490
1933n BC → 1446.5 BC = 486.5
486.5 + 3.5 = 490

This is not ordinary decimal chronology.

15.4 Cumulative Jacob-birth phase pair

The canonical Aaron/Tishri phase-resolved equation is:

2083.5 BC − 1446.5 BC = 637
637 = 13 × 49

The prior human-facing article displayed the relation as:

2083 BC − 1446 BC = 637

That whole-year shorthand preserves the difference because both exact phase-resolved endpoints were reduced by 0.5. File_58 retains it only as source history. The 637 result does not belong to the Moses/Nisan pair:

2080 BC − 1446 BC = 634

15.5 Probability restraint

The cumulative correspondences are collateral. No formal probability model is supplied, so phrases such as “near-impossible” or “vanishingly unlikely” are removed.

16. Synthesis and argument limits

16.1 What the file establishes directly

The file directly establishes:

1. the bounded Numbers 28–29 Tishri 1–22 numeral ledger;
2. the exact totals 182, 189, and 280;
3. the exact seven-year expansions 1274, 49, 490, 1323, and 1960;
4. the declared sequence outputs and their arithmetic landings;
5. the explicit Genesis 41 animal-year precedent;
6. the existence of multiple controlled collateral structures in the Jacob–Joseph field.

16.2 What remains inferential

The file does not directly prove:

• that Numbers 28–29 was composed to encode every listed historical landing;
• that Genesis 46 explicitly converts seventy persons into seventy years;
• that the Johannine author used the proposed forty-jubilee endpoint;
• that MT, LXX, and SP offsets were designed around the Sukkot subtotal;
• that every remote convergence was available to one ancient scribe.

These remain structural inference, historical-critical hypothesis, typological reading, shared-tradition evidence, or providential synchronization according to scope.

16.3 Ancient interpretive plausibility

The absence of an explicit modern-style explanation is not by itself evidence against a list-based numerical reading. Ancient biblical and Second-Temple literature regularly preserves genealogies, rosters, heptads, festival counts, symbolic animals, and associative scriptural interpretation. File_58 therefore tests whether a list-sensitive, midrash-like numerical reading could have been intelligible to an ancient scribe or reader.

This is a reception-context hypothesis. It prevents modern genre assumptions from deciding the question in advance, but it does not prove authorial intent.

16.4 Final claim-status statement

The Numbers ledger and arithmetic are the proof-bearing layer. The Jacob–Exile–Return landings form the primary structural inference. Genesis 46, Genesis 50, Rounded Joseph, Esau, Joseph’s cows, BJ / Jubilees, manuscript lanes, Kings, cumulative chronology, and Johannine material function as collateral evidence with locally declared claim status.

Appendix A. Arithmetic ledger

Appendix B. Change-class and arithmetic audit notes

B.1 Explicit arithmetic corrections

1. 1973 − 1274 = 699, not an exact unsuffixed 700. Any 700t/n form requires phase derivation.
2. The exact 1470 Ezra-side pair is 1928 BC → 458 BC or 1929 BC → 459 BC. The compressed 1929/1928 → 458 wording is not one executable equation.
3. 536 BC → 458 BC = 78, not 77. The former “functions as 77” statement is moved to exploratory source history.
4. 537t → 445t = 92; the former “behaves as 91” statement is not executable arithmetic and is moved to exploratory source history.
5. The chronological direction of the former 445 → 515 → 585 line is normalized to 585 → 515 → 445 = 70 + 70.
6. The legacy cumulative 2083 → 1446 = 637 row is retained only as source-history shorthand. The canonical executable form is 2083.5 → 1446.5 = 637; the Moses/Nisan pair 2080 → 1446 equals 634.
7. The source’s Ezra 457 BC option and its statement 1444 BC → 965 BC = 480 inclusive are not adopted as executable File_58 arithmetic. The ordinary same-side difference is 479; any inclusive 480 state requires a separately declared boundary convention and controlling chronology.

B.2 Terminology corrections

• 364-day priestly scheme → Enochian 364-day fixed-week state.
• 1274 → 1260 compression → parallel Enochian / Prophetic half-week forms.
• mirrored run → reverse-order sequence unless a formal Mirror protocol is opened.
• fourth canonical witness → cumulative comparison method.
• proof, decisive, near-impossible, vanishingly unlikely → state-controlled inference language.

Appendix C. Author-decision ledger

C.1 Resolved decisions

1. Cumulative Jacob birth: Adopt 2083.5 BC → 1446.5 BC = 637 = 13 × 49 as the canonical Aaron/Tishri phase equation. Retain 2083 → 1446 only as source-history shorthand. Do not derive 637 from the Moses/Nisan pair 2080 → 1446 = 634.
2. Phase route: Retain the route in the main body on the exact Nisan spine: 1859n → 585n = 1274; 585n → 536n = 49; 1859n → 536n = 1323. Preserve 586t/585n and 537t/536n as phase envelopes, with the 49 relation checked componentwise. Do not introduce 1860t/1859n as a new Jacob-death pair.
3. Enoch / Rachel household clarification: Include 1 Enoch 89 as reception-history evidence that Jacob’s descendants could be represented as sheep / flocks; retain Rachel = “ewe” as secure lexical datum; classify Rachel’s 14 / Joseph’s 7 + 7 and Bilhah’s 7 as structural household correspondences, not proof that persons equal years.
4. Johannine dating: Retain AD 32 as the exact civil endpoint of 1929 BC → AD 32 = 1960. Retain AD 31t/32n and AD 32t as dependency-controlled proposal states pending one or more future Gospel-of-John numerics files. A future finalized John file may promote, refine, relocate, or reject the phase labels through a bounded cross-file update.
5. Esau dual partition and Genesis 33/46 sequence: Register the five-drove source order, purity 490/60, sex 490/60, female 400/430/470/490 value register, and the Genesis 33 three-group order applied to Genesis 46 as 23 + 33 + 14. Preserve 1906 BC as a Benjamin shared-label state and 1873 BC as a derived late-famine coordinate.
6. Appendix routing: Keep the Ezra material appendix-only. Move all chronological projections of Genesis 46’s household 70—including alternative sequence arrangements, the 23 + 33 + 14 date walk, Entry-plus-70, Daniel-1290 translation, Rounded Joseph comparison, and Genesis 50 30/40 comparison—to a speculative future-study appendix. These observations are preserved but do not carry the main File_58 argument.
7. Leviticus 16 overlay: Adopt the compact complete ritual-animal ledger 1 bull + 2 rams + 2 goats = 5, retain 4 as the slaughtered-offering subset, and display the subordinate 280/282/285/287 matrix. Do not develop 285 or 287 as active chronological ciphers in File_58.

C.2 Author-decision closeout

All author-decision items are resolved. No unresolved author decision remained at Pass 2, Finalization, or the post-final pressure test.

Appendix D. Speculative Genesis 46 chronology tests and future-study register

D.1 Status and scope

This appendix preserves possible chronological applications of Genesis 46’s household 70. The textual household totals and their arithmetic remain established in §1.4. The date applications below are classified as speculative future-study material.

The purpose of preservation is methodological:

• do not discard potentially meaningful structures merely because they are not presently proof-bearing;
• do not allow a promising date fit to determine the list order retrospectively;
• keep each sequence, anchor, state, and operator explicit for later testing;
• do not cite this appendix as proof that Genesis 46 intended 70 persons = 70 years.

D.2 Available household sequence states

The same four maternal subtotals permit several textually or structurally defined arrangements:

Machine Guard [GENESIS 46 APPENDIX SEQUENCE PREDECLARATION]: A sequence must arise from the printed list, a textual cross-scene order, or a declared structural pairing before dates are tested. Do not permute the four subtotals merely to reach a desired chronology target.

D.3 Genesis 33 three-group chronology test

Genesis 33 orders the family as handmaids, Leah, then Rachel. Applied to the Genesis 46 subtotals:

handmaids: 16 + 7 = 23
Leah:               33
Rachel:              14
                     --
total:               70

Projected from Jacob’s 1929 BC Bethel/Haran anchor:

1929 BC → 1906 BC = 23
1906 BC → 1873 BC = 33
1873 BC → 1859 BC = 14
1929 BC → 1859 BC = 70

Collateral observations:

1906 BC → 1446 BC = 460
1873 BC → 1871 BC = 2

File_01 authorizes 1906 BC as a Benjamin birth label in one active state, but the same year also carries other node-classes. 1873 BC is a derived late-famine comparison coordinate, not a primary event anchor. The subtotal 23 does not automatically activate the repository 25/23 operator.

Classification:

• sequence arithmetic: arithmetic fact;
• use of Genesis 33 to order Genesis 46: textually grounded structural operator;
• chronology landings and intended design: speculative structural inference / historical-critical hypothesis.

D.4 Whole-household Entry-plus-70 projection

Once count-to-chronology is opened provisionally:

1876 BC − 70 = 1806 BC

The derived coordinate has these exact comparisons:

2166 BC − 1806 BC = 360
1806 BC − 1446 BC = 360
1806 BC − 1406 BC = 400

Thus:

Abraham birth → 1806 BC → Exodus = 360 + 360
1806 BC → Conquest = 400

These are arithmetic facts after the anchors are invoked. The use of Genesis 46’s 70 as years and the event significance of 1806 BC remain speculative.

D.5 Daniel-1290 translation of the proposed seventy-year rail

The proposed upper interval and the historical restoration interval have the same length:

1876 BC → 1806 BC = 70
586 BC → 516 BC = 70

The whole upper rail translates by 1290:

1876 BC − 1290 = 586 BC
1806 BC − 1290 = 516 BC

[1876 BC → 1806 BC] − 1290
=
[586 BC → 516 BC]

The internal 30 is controlled by the paired prophetic heads terminating at 586 BC:

1876 BC → 586 BC = 1290
1846 BC → 586 BC = 1260
1290 − 1260 = 30

The same head pair appears toward the Exodus:

1876 BC → 1446 BC = 430
1846 BC → 1446 BC = 400
430 − 400 = 30

The remaining proposed Joseph segment is:

1846 BC → 1806 BC = 40

No 556 BC midpoint is active or required.

D.6 Rounded Joseph 40 + 30 + 40

File_51a supplies Joseph’s rounded comparison life 1916–1806 BC; File_03 preserves the standard life 1915–1805 BC.

Rounded comparison:

1916 BC − 1876 BC = 40
1876 BC − 1846 BC = 30
1846 BC − 1806 BC = 40
40 + 30 + 40 = 110

Standard comparison:

1915 BC − 1876 BC = 39
1876 BC − 1846 BC = 30
1846 BC − 1805 BC = 41
39 + 30 + 41 = 110

The Rounded Scaffold reveals a comparison-layer symmetry. It does not correct Joseph’s textual age 39 at Entry or his standard death 1805 BC.

D.7 Genesis 46 / Genesis 50 / Rounded Joseph 30/40 comparison

The following three contexts may be compared:

Genesis 46 households:        40 + 30 = 70
Entry → rounded Joseph death: 30 + 40 = 70
Genesis 50 mourning field:    40 + 30 = 70  [derived remainder]
Rounded Joseph whole life:    40 + 30 + 40 = 110

Genesis 50 explicitly supplies 40 embalming days and 70 mourning days. The 30 is derived as 70 − 40; the text does not print a separate thirty-day interval.

Classification:

• component arithmetic: arithmetic fact under declared states;
• cross-context comparison: speculative structural corroboration;
• deliberate scribal design: historical-critical hypothesis;
• providential coordination: theological interpretation.

D.8 Future-study restraint

The appendix records the observations because ancient list-sensitive interpretation may differ from modern prose expectations, and promising research often begins as a constrained hypothesis. Nevertheless:

• no sequence here is promoted into the main Numbers 28–29 proof;
• no date landing is a new primary repository anchor;
• no repeated 70, 40, 30, 23, or 460 is automatically identical to every other state carrying that number;
• future promotion requires a dedicated verification pass or a later controlling file.

Appendix E. Genealogical and Ezra source-history material

The following observations are retained as collateral / appendix material:

• Adam → Isaac: 21 inclusive names.
• Jacob → Ezra: 21 inclusive names in the telescoped priestly genealogy.
• 21 × 70 = 1470 = 3 × 490.
• Ezra 8:35: 12 / 96 / 77 / 12.
• 1781 BC → 458 BC = 1323.
• 458 BC → AD 33 = 490 under civil cross-axis arithmetic.
• exact paired 1470 displays require 1928 → 458 or 1929 → 459.

These observations do not carry the primary Numbers-ledger burden.

Appendix F. Selected source-control bibliography

• Biblia Hebraica Stuttgartensia.
• Rahlfs–Hanhart, Septuaginta.
• von Gall, Der hebräische Pentateuch der Samaritaner.
• Tsedaka, The Israelite Samaritan Version of the Torah.
• Josephus, Jewish Antiquities.
• Charles; Wintermute; VanderKam on Jubilees.
• Nickelsburg and VanderKam on 1 Enoch.
• Brown–Driver–Briggs and standard Hebrew lexica on רָחֵל (“ewe”); Leah etymology retained as disputed.
• Ben-Dov; Glessmer; Talmon; VanderKam on Second-Temple calendars.
• Milgrom; Levine; Ashley on Numbers.
• Smith on LXX Genesis chronology.
• File-specific repository dependencies listed above.

Appendix G. Appendix-only source-history observations

The Final source retains the following source-article observations so that argument control does not become silent deletion. They remain appendix-only and are not presently load-bearing.

G.1 Jacob tithe and Levi echo

2006 BC → 536 BC = 1470
1470 ÷ 10 = 147

1929 BC → 1782 BC = 147

The relation to Jacob’s Bethel tithe vow and to Levi’s death is retained as typological / structural interpretation. Exact paired-date variants such as 1928/1929 and 1781/1782 require state declaration.

G.2 Peter’s 77 / 70 × 7 comparison

The source compares Jacob–Esau age 77 with Matthew 18:21–22’s 77 or 70 × 7 textual field. This is reception-history / typological comparison and does not establish a chronology operator.

G.3 Terah, 60, and the 430 backbone

The source compares MT and SP Terah states, Acts 7:4, and a possible +60 reset. File_58 retains this only as File_04/File_16-dependent source history. It does not reconstruct Terah chronology locally.

G.4 Enochic animal and week imagery

The principal 1 Enoch 89 flock-reception evidence is now integrated into §1.4 because it directly governs the interpretive plausibility of reading Jacob’s household as a symbolic flock. The seventy shepherds, Apocalypse of Weeks, and broader Enochic periodization remain supplementary reception-history context. They support ancient animal, agent, heptad, and numerical-history idioms without proving direct literary dependence on the proposed Numbers ledger.

G.5 John 5 alternatives and numeric signals

The source preserves two readings of John 5:

• Passover within a longer ministry chronology;
• Tabernacles within the proposed forty-jubilee field.

The man’s 38 years, the 38 + 2 = 40 comparison, and Sheep Gate imagery are typological / reception-history observations. They do not determine the feast or date.

G.6 Ezra 8:35 and Nehemiah 8

The 12 / 96 / 77 / 12 offering pattern, the Tishri 1–22 setting of Nehemiah 8, and the Ezra–Nehemiah 1470 comparisons remain appendix-level. The incorrect or non-executable 77/91 contractions identified in Appendix B are not restored as arithmetic facts.

The source’s alternate 457 BC Ezra date and 1444 BC → 965 BC = 480 inclusive comparison are preserved only as source history. File_58 does not activate that boundary convention or use the row as proof.

G.7 Daniel 9 sixfold outcome and clean/unclean theology

The source relates the clean 490 to Daniel 9:24’s sixfold purpose and to priestly clean/unclean separation. This remains a typological / theological reading; the arithmetic base is 490 − 60 = 430.

G.8 Source-history implications

The source proposes:

• a list-sensitive compositional method in Numbers;
• Second-Temple reception through BJ / Jubilees and Enochic literature;
• Johannine use of Temple and feast numerics;
• support for the primary 1446 BC Exodus state.

File_58 retains these as argument conclusions with differentiated claim status. File_58 does not use the ledger independently to prove the Exodus anchor, which remains File_05-controlled.

Finalization control

Author-invoked Finalization is complete.

• Status is set to Final.
• Pass 2 remains the completed verification layer; the separately author-invoked post-final pressure test is now complete.
• Temporary drafting and unresolved-item language has been removed from the active source; the pressure test removed two stale active Pass 1B labels without changing content.
• Necessary audit notes, claim-status boundaries, and dependency notes remain active.
• No unresolved author-decision item remains.
• The Johannine endpoints remain dependency-controlled proposal states pending one or more later Gospel-of-John numerics files.
• Machine-ingestion controls remain retrieval and non-collapse controls; the source has not been converted into JSON, prompt pairs, or another derived AI format.

Cross-file disposition at Finalization

Completed:

1. File_57 now retains the compact Numbers 28–29 precedent, registers source-order / category-order methodology, and routes the full corpus treatment to File_58.
2. File_20 Recommended Cross-File Update 22 is marked fulfilled by File_58.
3. State Vocabulary Register v1.24 registers the File_58 post-final pressure-test closure at Part D §D.22 and updates the File_20 / File_57 pressure-test routing statements.
4. Restart Capsule v11.23 records File_58 as post-final pressure tested without promoting local or appendix-only coordinates to Primary-anchor status.
5. A Repository_Change_Archive addendum records the Finalization and bounded control updates; a future full Archive replacement may absorb that addendum when the active Archive source is mounted.

Publication and preservation follow-up, not source-Finalization blockers:

6. Advance the publication manifest from v7 to v8 and add File_58.
7. Add the canonical raw-source URL and update the raw-source index, File Index, sitemap, and existing stable WordPress article in place.
8. Synchronize GitHub once for the File_57/File_58 edition, then create the coordinated release and external archival captures.

Future dependency review:

9. When a later Gospel-of-John numerics file is finalized, conduct a bounded File_58 review of AD 31t/32n, AD 32t, John 5, John 7–8, and the Temple 49/50 field. Do not promote or alter the current proposal silently.

Revision Log

• File: File_58
• Revision date: July 12 2026
• Style Guide version: v2.5
• Restart Capsule version: v11.23
• Passes completed: Pass 0; Pass 1A; Pass 1B; Pass 2; Finalization; post-final Pressure Test
• Unresolved issues: none; dependency-controlled Johannine proposals remain explicitly provisional rather than unresolved
• Author decisions made: printed-numeral sufficiency; five-drove source order; purity/sex dual 490/60 partition; female 400/430/470/490 value register; male-first clean sequence; unclean framing sequence; Genesis 46 four-household method; Genesis 33 three-group 23/33/14 order; Benjamin 1906 shared-label restraint; collateral-evidence claim posture; midrash-like reception-context restraint; cumulative Jacob 2083.5 → 1446.5 = 637; exact Nisan phase route; Daniel-1290 seventy-rail translation; 1 Enoch 89 flock reception; Rachel 14 / Joseph 7 + 7; Bilhah 7 single-heptad restraint; Johannine civil-endpoint / future-file handoff; Ezra appendix-only disposition; Genesis 46 chronology tests appendix-only speculative disposition; compact complete Leviticus 16 +5 overlay ledger with 4 slaughtered subset and 280/282/285/287 matrix
• Authorial-direction handling: all seven consolidated author-decision items resolved by explicit author direction; Pass 2 found no new substantive author decision
• Cross-file updates completed at Finalization: bounded File_57 update; bounded File_20 update; State Vocabulary Register v1.24; Restart Capsule v11.23; Repository_Change_Archive addendum. Publication manifest, indexes, WordPress, GitHub, and external archives remain publication-stage follow-up.
• Pass 2 result: PASS — 253/253 arithmetic checks; 30/30 lint / dependency checks; all source sections accounted for by integration, correction, or explicit appendix routing
• Finalization result: PASS — status set to Final; no unresolved author-decision item; Register v1.23 and Capsule v11.22 routing applied; bounded File_57 / File_20 updates completed; no arithmetic or claim-status layer changed
• Post-final pressure-test result: PASS — independent arithmetic and conservation suite, phase and civil-span audit, claim-status / Machine Guard audit, refreshed dependency audit, and bounded File_57 / File_20 routing checks complete; two stale active Pass 1B labels removed; no arithmetic, anchor, operator, modal state, theological claim, or dependency boundary changed
• Status: Final; post-final pressure tested July 12 2026; author-invoked Finalization complete; Pass 2 verified