Full Supporting Tables: Noah’s Flood Day–Year Datums

These tables accompany Noah’s Flood: Day–Year Datums and the Pattern of New Creation. They preserve the legacy research’s numerical content while making the selected state, origin, day boundary and fixed anchor explicit. The normal historical comparison follows the MT, Nisan reckoning, 430 years in Egypt, Gear 2, and no restored second Cainan or +60 Terah unless named. The symbolic 721/751 columns are comparison grids, not replacement Flood dates.

Genesis supplies the narrative dates; the continuous 360-day count and the day–year lift are declared research operations. File 12’s reconstructed intercalation option preserves both counted and uncounted insertions. The older source is retained unchanged at its original address.

Table links

• 1. Three considered origins
• 2. Regular anchors and the optional Terah state
• 3. The reconstructed forty-year cycle
• 4. The two year-opening windows
• 5. The complete 721/751 projection ledger
• 6. Uniform counters beside the inherited labels
• 7. Bird stages and the Temple-date correspondence
• 8. What 370, 410 and 417 count
• 9. Seven-unit arrangements and the Arphaxad choice
• 10. The point-for-point 3430 comparison
• 11. Jared, the forty-unit gain and the 430 cycles
• 12. Exact expansions and the two fixed-anchor choices
• 13. Expansion preserves the declared component sums
• 14. Two coherent placements of the expanded whole chain
• 15. The original chart’s seven successive spans
• 16. Original lower AM labels and current explicit readings
• 17. The LXX inset: matched states and elapsed intervals
• 18. What the inset preserves at fixed later targets

1. Three considered origins

The original discussion considered these three possible datums before developing the Arphaxad comparison. Its second candidate was phrased as “the end of the 601st year,” but interpreted as 600 years and one day: an ambiguous ordinal/year-turn expression, rather than the completed end of another entire year. The table makes the counter distinction explicit. These candidates are not three independently supplied biblical month-and-day dates.

The assistant’s preliminary 2456−47 = 2409, 2456−197 = 2259 and 2456−361 = 2095 calculations were not adopted by the author. They survive in the unchanged original; the adopted columns below use signed distances of 720/750 from the selected symbolic zero.

Download this table as CSV (data ZIP).

2. Regular anchors and the optional Terah state

The working baseline is MT, Nisan, full 430 years in Egypt, normal Gear 2, no restored second Cainan and no +60 Terah. The +60 fork affects the upstream Terah-and-earlier field; the later named targets remain fixed. File 18 supplies the full manuscript and variant tables, and File 07 controls the Creation node classes.

The copied legacy historical-reference table was broader than this argument and mixed chronological states. The local list supplies the needed research anchors; the complete regular tables remain available directly through File 18. Native LXX Cainan and an MT restored-Cainan comparison are distinct from the no-Cainan MT baseline here.

Download this table as CSV (data ZIP).

3. The reconstructed forty-year cycle

The declared schedule has six stages of six years and one stage of four years. A thirty-day month closes each stage. Its epoch is selected at 1446n BC and recurs at 6n BC, 36 complete forty-year cycles later. The 606n examples display the same phase used in the Ezekiel series.

The exact arithmetic is 40 × 360 + 7 × 30 = 14610 = 40 × 365.25. The mechanism is a reconstructed calendar scheme, not an intercalation schedule expressly reported in Genesis. File 12 §7A also preserves the option to reckon a schematic span with or without its intercalary month. BC closing residues modulo 40 are 0, 6, 10, 16, 22, 28 and 34.

Download this table as CSV (data ZIP).

4. The two year-opening windows

The normal two-year window crosses a closure at 2456n; the +60 window has no closure before its 2516n endpoint. These sample phases therefore support the original 750/720 distinction. They begin at the modeled year opening, not at month 2 day 17.

The corresponding symbolic origins are reusable grids, irrespective of which literal Terah state a later comparison selects. In particular, the +60 Creation-week comparison below uses Column B as a cross-state comparison; it does not claim that the +60 two-year sample itself contains an insertion. Signed zero displays as 1 BC; −720 and −750 display as 721 and 751 BC. This is coordinate labeling, not a formal Mirror reflection. File 00 §3.9 controls the distinct Mirror vocabulary.

Download this table as CSV (data ZIP).

5. The complete 721/751 projection ledger

For every row, Column A = 721−d BC and Column B = 751−d BC. The two columns are exactly thirty projected years apart. These are symbolic comparison coordinates; the regular Flood remains 2458 BC in the baseline. The missing publication table is reconstructed from the original author’s explicit rule and event labels.

Label 361 was formerly called complete earth drying. Its value is conserved with its proper Genesis 8:13 surface-dry completion role; complete earth drying belongs to 417 and Genesis 8:14. Genesis passages can be read directly in Genesis 7, BSB and Genesis 8, BSB.

Download this table as CSV (data ZIP).

6. Uniform counters beside the inherited labels

Let y = 0 for the selected Flood year and y = 1 for the next year. Opening(y, m, d) = 360y + 30(m−1) + (d−1); completion = opening +1. These formulas supply uniform counters. The inherited projection uses completion for ordinary dated days and opening for selected first-of-month rows.

Consequently Ark-rest completion to mountain-top opening is 270−197 =73. Opening to opening is 270−196 =74, as is completion to completion, 271−197 =74. The original assistant’s explanation “two months plus fourteen =73” was incorrect arithmetic; the 73 selected-boundary gap itself survives. Likewise 417−360 =57 mixes covering-opening with drying-completion, whereas 417−361 =56 matches day completions. The opening of the first modeled day is d=0; its occupancy is bounded by 0 and 1. The completion of the seventh day is d=7, rather than seven inclusively enumerated BC labels from 721 to 714.

Download this table as CSV (data ZIP).

7. Bird stages and the Temple-date correspondence

The first-day exception at 270 permits 270+40 =310, the completion of month 11 day 10. With a Tishri opening, the eleventh month corresponds to Av, fifth from Nisan. Jeremiah 52:12–13 places the arrival of Nebuzaradan on the tenth of that fifth month, followed by the burning of the Temple.

This is a proposed correspondence between a reconstructed Flood stage and a stated Jerusalem date, not a date expressly assigned to the raven by Genesis. The bird sequence is read in Genesis 8:6–12, BSB; the historical comparison can be read in Jeremiah 52:12–13, BSB. The Tishri and Nisan alternatives are both retained without merging their month names.

Download this table as CSV (data ZIP).

8. What 370, 410 and 417 count

Changing the origin changes the coordinate without changing the narrative. A 410 construction and a 417 ending label can both be valid, while the selected outbreak-to-drying difference is 370. None of these statements alone establishes a historically observed calendar intercalation.

The complete event sequence and narrative limitations are explained in the main study. A same-day exit after the earth-dry notice is permitted as a reconstruction, but Genesis supplies no separate month-and-day date for exit, altar construction or the rainbow covenant.

Download this table as CSV (data ZIP).

9. Seven-unit arrangements and the Arphaxad choice

The larger patterns give the small date calculations their proposed narrative significance. Each retains its own scale: literal days, years, or a projected day–year unit. The last two rows are theological correspondences built on separately identified coordinates.

Creation’s year-scale wrapper is 4121→4114; the distinct Year-6 interval is 4116→4115, followed by seventh-unit rest 4115→4114. These positions follow File 07. Lamech’s MT 777 and the adopted LXX 753 lifespan are different textual states. The comparison does not replace a lifespan or claim that Genesis explicitly states a seven-year Creation chronology.

Download this table as CSV (data ZIP).

10. The point-for-point 3430 comparison

This selects the +60 literal Creation wrapper and the 751 symbolic origin. The two week brackets stand 3430 apart point for point. They should not be blended with normal 4114 in this particular equation.

“Seventy jubilees” here means seventy declared 49-year units. It neither asserts a continuous historical Jubilee-observance record nor adds fourteen extra years to the corresponding-point span. Counting the eight endpoint labels inclusively is a different operation from measuring the seven-unit bracket.

Download this table as CSV (data ZIP).

11. Jared, the forty-unit gain and the 430 cycles

The 460→500 operation fixes the selected Creation endpoint and advances the other coordinate 40. The subsequent 2940 comparison carries the A endpoint from 714 to 674 by the same amount. A further source interpretation relates that 40 gain to the forty-day rain.

The 1+6 grouping is a typological arrangement with a 460 first component followed by six 490 units. Likewise the seven 430 and eight 430 meanings concern completion and renewal as proposed narrative readings. Their exact arithmetic does not prove a specific historical Watcher descent date. File 17 §10.4 provides the 460/1196 decomposition, and File 22 §§7.11–7.12 develops the Watcher-span companions.

Download this table as CSV (data ZIP).

12. Exact expansions and the two fixed-anchor choices

Every expansion in this table concerns a length. The last two columns show what coordinate follows if one endpoint is held fixed. They are alternatives, not simultaneous changes to an actual biography. For example, fixing Jared 3654 expands 2990 to 3250 and reaches 404; fixing the later 664 endpoint instead moves the comparison head to 3914.

The 1794 span also factors as 13×138, and its 1950 output is 5×390. The 1196 input is 52×23 and 4×299; the distinct Enochian 300/299 operator gives 1200 rather than the Priestly 25/23 output 1300. A span’s 130 coefficient supports the proposed curse/judgment reading; it does not cause the actual Flood date. The Exodus 1446 coordinate precedes the symbolic 664 coordinate, so 782 is read in that forward direction.

Download this table as CSV (data ZIP).

13. Expansion preserves the declared component sums

The same exact ratio distributes over addition, so the expanded whole equals the sum of the expanded parts. This tests a connected chain, rather than isolated multiplication. It does not by itself identify a historical execution of every generated coordinate.

The Enochian companion in the last row is separately controlled by File 22 §7.12. Exact arithmetic and claims of literary or providential design remain distinct. No chance-probability estimate is supplied by the legacy article.

Download this table as CSV (data ZIP).

14. Two coherent placements of the expanded whole chain

Here all three components are expanded together: 500, 1300 and 1950. The table gives two internally coherent placements. “Jared-related” and “Flood-related” describe generated dividers in the comparison chain, not new dates for either historical person or event.

Do not mix these values with independently expanded pairs from the preceding table. For example, 2354 results from expanding 1196 while fixing historical Jared 3654, whereas 2314 results when the whole chain is expanded with Creation 4114 fixed and the Jared-related divider has already moved to 3614. Both calculations are valid, but their fixed anchors differ.

Download this table as CSV (data ZIP).

15. The original chart’s seven successive spans

The recovered covenant chart supplies 460+414+782+391+138+483+46 =2714 =23×118. The first three legs give 1656 from Creation to Flood; the next three give 1012 from Flood to Exodus; the last 46 reaches 1400. These are seven unequal multiples of 23, grouped as three forming, three filling and one rest.

The covenant associations have different textual status. Noah, circumcision, Jacob’s promise and Sinai are biblical covenant narratives; a covenant at Jared’s or Lamech’s birth is interpretive. The Cainite Lamech’s seventy-sevenfold vengeance (Genesis 4:24) and Noah’s father’s 777 years (Genesis 5:31) belong to distinct persons. Seven ewe lambs and oath-making in Genesis 21:28–31 supply a literary seven/oath association. The 2067 circumcision station concerns Abraham’s age 99 covenant and Isaac promise (Genesis 17), not Isaac’s following 2066 birth or his later eighth-day circumcision (Genesis 21:4). The 1400 endpoint is the beginning of the 1400–1399 division/rest interval: 1446−1400 =46, whereas 1446−1399 =47. The source’s Conquest 3+3+1 grouping partitions the six campaign years structurally, followed by the rest-year interval; no separately dated midpoint is inferred. The historical chart cites Leviticus 19:3, a parents/Sabbaths instruction that does not state those durations. Its citation is preserved as source history. The six-work-years/one-rest-year analogy is supported by Leviticus 25:3–4, BSB; that law likewise does not independently date the campaigns.

Download this table as CSV (data ZIP).

16. Original lower AM labels and current explicit readings

Numbered AM =4114−BC+1; completed years =4114−BC. The principal chart labels 1/461/875/1657/2048/2186/2669/2715 fit the numbered convention. Its lower notes do not all use that same convention and state.

The original chart remains unchanged at its original address. These annotations repair the display without changing lifespans. No universal Year-6 origin is invented to rescue isolated old labels. The distinction between numbered and completed years is controlled by Files 07 and 18.

Download this table as CSV (data ZIP).

17. The LXX inset: matched states and elapsed intervals

The image’s inset says LXX Creation is 23×60 before MT and notes Seth 230 and Noah 23×72. These statements survive when their source state and elapsed-count meaning are declared.

Current File 18 §4 supplies the native-Cainan LXX table; §3.1.4 gives its normal Gear 2 Flood 3238 and fixed Arphaxad 3236. MT keeps its separate 2458/2456 pair. Restoring Cainan in MT would open a new 130-year hinge and change the comparison; that switch is not active here.

Download this table as CSV (data ZIP).

18. What the inset preserves at fixed later targets

The literal shared target stays fixed while the Creation head moves 1380 earlier. Consequently a multiple 23 remains a multiple 23. This is the useful, bounded reading of the inset’s assertion that its post-Flood spans also work in LXX.

It is not a claim that every intervening LXX genealogy row is MT+1380. The later covenant stations in this table remain fixed under the selected matched settings, while Flood and earlier biographies have their own manuscript-specific intervals.

Download this table as CSV (data ZIP).

Interpretation, source history and further reading

The paired Creation brackets, Jared components, 430 cycles, 23-chain and covenant sequence are preserved because together they make the proposed design inspectable. Exact arithmetic does not determine every literary meaning, prove a specific scribal mechanism or supply a probability that the correspondences arose by chance. The Watcher traditions in 1 Enoch 6/10 and Jubilees 4/5 provide a supporting interpretation; their initial descent, later transgression and judgment should be read individually rather than merged into one identical account. Arphaxad’s conception soon after exit is a tentative gestational reconstruction; Genesis does not date it.

The earlier discussion also supplied two historical research pointers: 1290 days/years and their corresponding dates and the Jubilee/Exodus chart. They are retained as source-history links, not promoted into current canonical controls or newly certified tables.

Return to the main article, or consult the current canonical source index. The complete original wording, old table proposals and recovered covenant illustration remain in the complete original.