Flood Day–Year Part 4b: Full Tables and Source Notes

This is the active supporting study for Noah’s Flood: Seasonal Columns and Chronological Mirrors. All table values retain their event, state, phase and counting qualifications.

Sources and the scope of the supporting study

This document accompanies Part 4b: Noah’s Flood—Seasonal Columns and Chronological Mirrors. It preserves the substantive calculations, alternative registers and interpretive leads of the original discussion. Its table headings name which values are ordinary chronological anchors, cumulative coordinates, symbolic day–year projections or proposed comparative states. Corrections repair equations or event assignments; absence from the repository Canon alone does not remove novel research.

The calendar section supplies the four columns, older counters, intercalation, regular comparisons and probability questions. The Mirror and cumulative section supplies the civil and seasonal operations, prophetic-period families, Enoch, all twenty-six cumulative lifespans and the Sumerian chart. The figure/person/event index (data ZIP) directly connects diagrams to passages and tables. All downloadable CSVs retain their named column fields and may be opened in a spreadsheet.

Current source captures and a block-by-block conservation inventory accompany the publication package. The reader does not need those editorial records to follow the calculations; each active table explains its own state.

Research history and continuing leads

The original records a research beginning on 22 October 1991, approximately forty hours of work weekly, and an important refinement of the Flood studies on 12–13 September 2024. It describes a study of roughly sixty thousand words at that stage, alongside about a dozen related draft books. These are the author’s research-history statements, not independent counts of the present replacement article.

The author describes knowing the Lord as Teacher as the chief reward of the work. This conviction explains the interpretive interest in the numerical patterns; it does not replace arithmetic or textual verification. A suggestion that a 2024 moment might have an exact-hour relationship was not worked through with a complete calendar calculation in the source. It remains an undeveloped lead, rather than a verified date or forecast.

The chromosome analogy similarly illustrates the repeated pairing of 23 and 46. It is an analogy, not biological evidence of how biblical chronology was composed. The number 1176 = 3.5 × 336 is retained as a proposed priestly half-week lead. Its numerical value is established; a claimed Mirror correspondence needs specified endpoints and a declared reflection protocol before it can become a tested comparison.

The study’s language of large and small scrolls, nested time and repeated patterns describes a theological synthesis. Each scale transformation must still name its units. A nominal day mapped to a year, and a nominal year mapped to 360 years, are different stages; neither can be omitted merely because the final result is attractive.

Additional links retained from the developing discussion

The earlier origins 751/750 + 180 = 931/930 and 721/720 + 180 = 901/900 prompted a comparison with the Northern Kingdom. The ordinary division anchor is 930 BC in the repository’s register; its declared preceding seasonal companion is 931. The source’s schematic terminal reference 721 gives 210 from 931 and 209 from 930. This is a selected endpoint analogy, not proof that the projected origin independently dates the kingdom’s history. The two origins and both spans remain visible.

The expanded Creation-to-Flood length 1656 × 25/23 = 1800 = 5 × 360 is also read beside Lamech’s death five years before the MT Flood: 2463 → 2458 BC. Mapping five nominal 360-day years gives 1800 days, and a further day–year projection compares that measure with 1800 symbolic years. The stages are distinct; five ordinary years do not literally occupy 1800 years.

A 490-year span contains seventy seven-year sabbatical cycles. The source proposes this as the background for the land’s missed Sabbaths and its seventy-year rest in 2 Chronicles 36:21, BSB, alongside Daniel’s seventy sevens and flood imagery. The numerical count is exact; the text does not independently identify the beginning of a unique 490-year period through that count alone.

The Adam/Eve purification proposal includes two endpoint placements, not merely two names for the same calculation:

Both branches use the same 604800 = 1800 × 336 = 1680 × 360 ideal day-volume. Neither branch establishes that Genesis states Adam’s or Eve’s cleansing date. They preserve the original interpretation of a remainder while the calendar section supplies the independently reproducible volumes and placements.

The source’s Revelation 12 reading also specifically proposes that the woman’s seed through Christ becomes renewed sons of God taking the place of the rebellious angelic sons of God. The slow precessional timepiece is interpreted as an image of the saints’ enduring life. This preserves the proposed angelic/human role comparison; it is not an explicit identification of the twelve stars or a measured duration stated in Revelation.

Calendar registers and the four seasonal columns

These tables preserve the detailed Flood day–year model, including its alternative boundaries. They distinguish the narrated events from the thirty-day-month calendar used to calculate their positions, the day–year projection applied to those positions, and the interpretations that connect the resulting numbers. A date in a symbolic column is a projected label. It does not redetermine Noah’s historical date.

The regular comparisons use the MT full-430-year Egypt framework, with the Exodus at 1446 BC and the ordinary Gear-2 Flood at 2458 BC. The fixed regular Arphaxad node is 2456 BC. Terah’s +60 alternative is declared when opened; MT/SP restored second Cainan remains off, while the LXX comparison retains its native second Cainan. Nisan is the default. SP dates used beside the MT in the comparison grid have been equalized to the same full-430 framework, rather than silently importing the SP native 215-year Egypt setting. File 18 §§2–4 controls these distinctions.

The three schematic day registers remain distinct:

The Priestly ledger is a foundational register, not a failed solar calendar. The bridge 336 + 28 = 364 adds four weeks without altering its baseline. A physical solar mean, the intercalated 360-day reconstruction, and the exact rational Key-of-23 operators are additional, separately declared calculations. File 12 §§5–7A and File 17 §14 supply the controls.

The final four-column ledger

All entries below are symbolic BC labels. Column headings retain the source’s window-length names, 720, 750, 900 and 930. They are not four separately dated historical Floods. For an explicitly declared elapsed marker d, the source’s later morning ledger calculates the label by L − d. The Tishri columns add 180 to the corresponding Nisan labels. The 750 and 930 columns carry the optional extra 30 relative to their partners.

The complete marker ledger, including offsets and qualifications, is available as CSV (data ZIP). “Earth completely dry; exit follows” represents the second month’s twenty-seventh day, followed by the command to leave. The command and departure receive no separate date in Genesis 8:14–19 (BSB). The new-year notice in Genesis 8:13 (BSB) concerns the dry ground surface and removal of the covering, an earlier stage.

The “forty-day rain ends” row concerns the rain, not the entire Flood. The 150-day rise/prevailing-water interval reaches the Ark’s rest. It begins at the outbreak and includes the forty-day rain; those spans are not added as two successive periods. Genesis 7:11–12, 24 (BSB) and Genesis 8:3–4 (BSB) supplies the underlying dated narrative.

The model places the raven and the first dove in one release group. Scripture narrates the raven first, then the dove, but does not state that their release occurred in the same hour, on the same day, or seven days apart. This remains a reconstruction. There are three dove releases, in Genesis 8:8, 10 and 12 (BSB), and two explicitly recorded subsequent seven-day waits. The late transcript’s statement that the dove was sent only twice confuses two later rereleases with the total number of releases.

Numbered days, completed intervals and morning/evening

The Ark-entry row retains 681/680 and its corresponding other-column alternatives. The source expressly labels the earlier value as exclusive and the later as inclusive. In the later dove rows it reverses that order: 404 inclusive / 403 exclusive, then 397 inclusive / 396 exclusive. Each pair records a counted-week alternative. It must not be silently turned into an unrestricted one-year shift, or uniformly assigned a Tishri/Nisan meaning.

A numbered seventh day is reached after six completed days. The source also considers a daylight-oriented half-day framing: 0.5 + 6 + 0.5 =7. A morning-to-morning or evening-to-evening calculation must keep the selected boundaries; a partial seventh day is not automatically a completed seven-day interval. The suggested daylight entry of animals, morning visibility of mountains and fourth-day appearance of the luminaries are narrative/phase interpretations, not independently supplied hour-stamps. Similarly, a seven-day unit can be represented through its opening boundary, its seventh numbered day, or its completion. Those are distinct counters for one time-unit. The paired values preserve that distinction; they do not imply two physical releases of the same bird.

The source also makes a particular seasonal analogy: evening maps to autumn and morning to spring. It explicitly uses 711 BC evening / 710 BC morning, 481 BC evening / 480 BC morning, and an evening raven label 411 BC beside its morning 410 BC. These declarations are retained as phase readings within the symbolic model. Genesis gives the olive-leaf dove’s evening return, but does not timestamp the raven’s departure. The inference that its darker plumage and departure evoke night is interpretive, rather than a new textual datum.

The original Part 4a companion preserves an earlier 721/751 rendering. The difference is explained by its numbered-day and opening/completion labels; those old entries should not be treated as a second set of independent observations. In particular, the earlier sequence has a separate initial seven-day gap before the first dove, while the later Part 4b table groups the raven and first dove. Both reconstructions belong in the record, with their different assumptions visible. The earlier duplicate dry-earth row is resolved by identifying the two new-year boundary views as surface dryness, followed later by complete dryness.

CSV: earlier/later model history (data ZIP); complete earlier 721/751 ledger (data ZIP). The earlier first-dove position remains available as a conditional inferred-gap reconstruction; it is not discarded merely because the later release grouping differs.

This uniform ledger is a thirty-day-month reconstruction. The older 410/417-day comparisons also choose their own origins. From creation-anniversary ordinal day 7 to closing ordinal day 417 the difference is 410; from Flood ordinal day 47 to day 417 it is 370. The number 417 is a numbered closing position, not 417 elapsed days after the Flood began. The older mountain-to-exit comparison uses 417 −270 =147 =3×49, a mixed opening/completion counter. The uniform completed interval is 416 −270 =146. The proposed three-jubilee correspondence is retained with its original counter declaration;147 is not silently described as the uniform completed duration.

Festival analogies and their two-day offsets

CSV: festival offsets (data ZIP). The VII/15 comparison is two days before the Ark’s VII/17 rest. In a Tishri-start month numbering, the corresponding spring-side month is compared with Passover/Unleavened Bread. Under that same alternative numbering the eighty-seventh numbered-day rain-end position lies two days after Kislev 25, the later Hanukkah date. The festival comparisons therefore preserve the source’s two-day adjustments while distinguishing them from Genesis’ own calendar statements. They do not establish that Noah celebrated either later feast.

526 BC, used in the selected numerical ladder, is the separate VII/15 comparison in the 720 column, not the Ark’s VII/17 rest at 524 BC. Those markers must not be conflated when counting matches.

Intercalation, physical residues and the Priestly ledger

The declared forty-year cycle

The reconstructed 360-day system uses six six-year segments followed by one four-year segment, each closed by a thirty-day leap month:

6 + 6 + 6 + 6 + 6 + 6 + 4 = 40 years

6 × (6 × 360 + 30) + (4 × 360 + 30) = 14610 days = 40 × 365.25

The reconstruction is anchored at 1446 Nisan BC, then 6 Nisan BC, thirty-six forty-year cycles later. Within the cycle beginning 606 Nisan BC, the closing boundaries are 600, 594, 588, 582, 576, 570 and 566 Nisan BC; each leap month closes its preceding segment. CSV: cycle boundaries (data ZIP).

A leap month may be counted or left outside a schematic span when that choice is declared. Thus 1260 and 1290 can be the uncounted- and counted-insertion expressions of a half-week. A seven-year span can appear as 1260 + 1260, 1260 + 1290, or, if its placement crosses two closures, 1290 + 1290. The insertion’s placement must be stated. File 12 §7A expressly retains this option principle.

This prevents a false conflict between a day-level marker and its surrounding week-unit. The actual date can lie within the mapped week while the numerical comparison uses that week as a unit. The study’s year-scale SP/Egypt/Jerusalem framework and Ezekiel’s day-scale siege patterns employ this same nesting. Their precision is assessed within their declared registers, rather than by forcing every week to be a single exact-day timestamp.

Approximate solar years and exact rational year conversion

The original model compares 460, 1656 and 1196 solar years with their Priestly expansions. The operators are exact:

460 × 25/23 = 500; 1656 × 25/23 = 1800; 1196 × 25/23 = 1300.

When the expanded units are counted at 336 days each, they yield the following day-volumes. The solar comparison in the original uses the approximate tropical reference 365.2422 days. Its remaining fractions must be preserved before rounding.

CSV: solar/Priestly remainders (data ZIP). The source’s approximately eleven, forty-one and thirty days are therefore legitimate approximate physical comparisons. They are not exact astronomical identities. Current Canon also supplies the calibrated reference S_K = 336023/920 and its physical-residue rule N/40 days. That gives 11.5, 41.4 and 29.9 days for the same three spans. The two physical references must be named individually; the calibrated values do not silently replace the old approximate calculation.

The ideal common-ratio reference is K = 8400/23. Under that ideal reference the day-volumes are exactly equal. For example, 1656 × K = 1800 × 336 = 604800 days. Both 1800 Priestly years and 1680 Prophetic years occupy that day-volume: 1800 × 336 = 1680 × 360. Likewise 500 × 336 = 168000 and 1300 × 336 = 436800. These identities keep the calendar units distinct while comparing their volumes.

The thirty- and sixty-day placement alternatives

The intercalated 360-day calendar is a third register. In its declared 1446n epoch, the number of enclosed leap months depends on the particular endpoints. The following table calculates the closures actually included by each interval. A closure at the starting Nisan boundary has already occurred and is excluded; one at the ending boundary is included.

CSV: 360-calendar placement remainders (data ZIP). These values explain why a remaining thirty or sixty days need not be an error. The default 4114→2458 Nisan span contains 289 leap months and is thirty days longer than the ideal 604800-day Priestly volume. The +60 span 4174→2518 contains 290 leap months and is sixty days longer. Both 3654→2458 and 3714→2518 Nisan Jared spans contain 209 closures and exceed 436800 by thirty days.

At 3714 Nisan BC a closing leap month occurs. Beginning instead at 3715 Tishri BC includes that month before the Nisan boundary; the Jared-to-Flood comparison therefore acquires another thirty days, making sixty. At the opposite endpoint no such extra insertion occurs. This is an endpoint-placement explanation within the reconstructed cycle. It does not assert that Genesis supplies the cycle or its precise historical execution.

The source’s masculine 40-day and feminine 80-day purification imagery remains a typological application of Leviticus 12 (BSB) and the Adam/Eve garden-entry reading in Jubilees. The model starts from Adam’s sixth-day formation and considers 6+40 =46 beside 6+41 =47, corresponding to the forty-day purification motif and the approximately forty-one-day physical residue. These are declared typological offsets, not a statement that the later Torah labels Genesis’ Flood onset as Adam’s purification. It also considers, separately, sixth- or eighth-day positions for Eve, giving eighty-day endpoints around numbered days 86–88. Genesis does not date Eve’s formation to an eighth day or impose the later childbirth law on Adam. The proposal compares their purification motifs with the forty-day rain and the approximate day-residues; it does not convert the association into an attested Genesis chronology.

The regular year-scale comparisons

CSV: complete regular comparison ledger (data ZIP). These are same-side BC subtractions. The 1846 head is the symbolic 400-year Affliction position before the Exodus, distinct from the 1876 entry into Egypt in the MT’s 430-year framework. The SP 3106 node is its fixed Arphaxad date and also its Gear-1 Flood-start convergence; the Gear-2 Flood is 3108. With +60 opened these become 3166 and 3168, respectively. Thus the Gear-2 two-year Flood-to-Arphaxad interval remains visible beside the Egypt and Jerusalem two-year windows; it does not turn the Gear-1 convergence into a two-year interval.

The SP bridges 3166→1876→586 = 1290 + 1290 and 3106→1846→586 = 1260 + 1260 are useful year-scale comparisons, explicitly opening the 60-year alternative in the first route. File 17 §§12–13A controls the half-week and Ezekiel relations. In the MT comparison, 2456→6 = 2450 = 5 × 490 links the Arphaxad datum with the conception-anchor field.

The source’s 3650 Creation-to-Ark-rest span is 10 ×365, ten common 365-day years. Its echo of Enoch’s 365-year lifespan is typological; ten true-solar years are not exactly 3650 days. The matched 1656 forms retain different Noah nodes: LXX birth, MT Flood, SP primary death. The SP rest-themed Creation-to-Noah-death comparison is therefore distinguished from the MT judgment/Flood comparison.

Two separate civil cross-axis rows, using BC + AD − 1, are 2518 BC→AD 33 = 2550 = 1260 + 1290 and 2516 BC→AD 33 = 2548 = 7 × 364. The transcript’s alternative equation “2550 = 1290 + 1290” is incorrect; that sum is 2580. The AD 33 Passion state is preferred in File 13 §6; AD 30 remains an admitted alternative.

The Ark rested on VII/17; under the alternative seasonal numbering the model compares that with I/17. The proposed resurrection anniversary is a calendar/typological reconstruction, not a Gospel-stated month/day. If I/17 is selected, a forty-day interval on thirty-day months reaches II/27, matching Genesis’ complete-dryness marker. The older assertion of an II/17 exit/ascension anniversary would yield only thirty days and is corrected. The Gospel’s forty-day resurrection-to-ascension span is preserved without claiming that its festival dates are textually explicit.

The exit-related Creation spans compare 3870 = 3 × 1290, 3780 = 3 × 1260, 3600 = 10 × 360 and 5040 = 14 × 360. Their endpoints are separately listed above. The mixed comparison 5554−4114 = 1440 opens LXX +60 while retaining default MT; it is valid arithmetic with different variant settings, not the ordinary matched-state gap. The ordinary matched MT/LXX Creation gap is 1380.

The paired early-ledger comparison 4121→441 and 4114→434 gives 3680 at both ends, or 4000 after 25/23 expansion. It maps the seven-unit Creation week to the seven-unit raven/first-dove interval of that earlier reconstruction. The later morning 440 raven marker is another phase and must not be substituted into the 3680 equation without changing the result.

For the conquest/bird sequence the coherent Nisan single-column rows are 1406→440 = 966 = 483 + 483, 1406→433 = 973 = 490 + 483, and 1406→426 = 980 = 490 + 490. Using the inclusive alternatives 434 or 427 instead changes the completed differences by one. The calculation must name the chosen boundary. The expansion 966 × 70/69 = 980 adds fourteen, corresponding to two seven-unit waits. The 1400→1399 land-rest transition remains distinguished from the six-year 1406→1400 structural close.

Enoch’s ascent at 3127 BC supplies four straightforward comparisons with the final-dove alternatives: 2520, 2550, 2700 and 2730, respectively. The last is 7.5 × 364; 2700 is 7.5 × 360. The associated theme of ascent without return is interpretation. Enoch’s lifespan is 365, while Noah’s is 950; the two people must not be conflated by a transcript typo. The separate Mirror comparisons are evaluated in the Mirror section.

The selected seven-marker ladder

The source selects 894, 710, 664, 526, 480, 434 and 411 BC. These labels draw on different declared columns and boundaries: 894 is the Tishri-column Creation anniversary, 526 is the distinct festival offset, and 411 is the earlier evening raven label. The selection is an interpretive ladder, not seven independent physical events all expressed in one uniform column.

CSV: selected chain (data ZIP). Without the inserted festival marker 526, the internal spacings are 184, 46, 184, 46 and 23, or 8, 2, 8, 2 and 1 units of 23. The two halves 894→664 and 664→434 each occupy 230, followed by 23 to 411: 230 + 230 + 23 = 483. The Prophetic expansion makes 483 × 70/69 = 490, adding seven. Holding 894 fixed moves 411 to 404, a dove-week boundary in the earlier rendering.

The Priestly expansion 460→500 adds forty. That gain is compared with Genesis 8:6’s forty-day interval. The source’s claim that this directly moves the mountain marker 480 to the raven marker 440 lacks a declared 460-unit starting anchor: such an execution would require 940. The legitimate comparison is the amount of extension, forty, rather than an established dated endpoint lock. Holding the explicitly supplied 894→434 span fixed at its start would instead generate 394, and those two operations must not be exchanged.

The earlier six-by-five comparison matrix

CSV: all 30 cells (data ZIP). This earlier matrix excludes the subsequently selected festival 526 marker and uses five regular anchors. Every cell is an exact 23 multiple; the corresponding 46 factor is retained in the CSV, including the half-integer cases in the 411 row. This is a reproducible selected congruence comparison, not an independent probability test.

The associated tenfold patterns are retained with their actual factors: 5494→894 = 4600 = 10 × 460; 5494→664 = 4830 = 10 × 483; 3654→894 = 2760 = 10 × 276; and 4114→434 = 3680 = 20 × 184 = 10 × 368. The old wording “3680 is ten times 184” is corrected. 710→434 = 276, whose comparison with the 276 aboard Paul’s ship is a numerical/typological association. 2458→434 = 2024 = 23 × 88 and 2458→1446 = 1012 = 23 × 44 retain the full/half relationship. Their Priestly expansions are 2200 and 1100, with gains of 176 and 88, respectively.

Ordinary exact-ratio conversions

CSV: complete ratio ledger (data ZIP). In particular 1748→1900 =950+950 preserves the double-Noah-lifespan comparison; 1794→1950 =5×390 and 1978→2150 =5×430 preserve the Ezekiel siege-number echoes. The 1932→1960 expansion is 40×49, forty jubilees, whether its 1932 input is Arphaxad 2456→rest 524 or Flood 2458→feast 526. Those equal lengths have different endpoint classes.

The Temple comparisons and the held endpoint

John 2:20 supplies the forty-six-year statement; John 2:21 explains the temple-body identification. The calendar equation 20 BC→AD 27 = 46 is an explicit Johannine harmonic in File 13 §8. It is distinct from that file’s preferred ministry/Passion bracket AD 29t/30n→AD 33n/33t and its temple-body event near AD 30. The harmonic label AD 27 must not silently overwrite that event chronology.

CSV: fixed-endpoint Temple projections (data ZIP). The first two rows show 644→700 and 690→700 converging on the same generated AD 37 endpoint when symbolic 664 BC is held fixed. Their operators differ: 25/23 and 70/69. If the later endpoint AD 27 is held, 460→500 moves the projected earlier endpoint from 434 to 474 BC, forty years backward. Holding the earlier dove marker instead moves AD 27 to AD 67. Neither generated endpoint is asserted as a historical date.

For the 414 span, 414 × 70/69 = 420, whereas 414 × 25/23 = 450. Holding 20 BC fixed, the first route moves the earlier marker 434→440, a six-unit extension that can be compared with the inclusive seven-unit week. The source’s equation using 25/23 to reach 420 is repaired rather than retained as executable arithmetic.

The earlier half-week lead 1176 =3.5×336 is also preserved beside 1260 =3.5×360. It is a Priestly-unit half-week, not a fourth arbitrary calendar correction. The source does not supply a complete endpoint execution for its 1176 Mirror reference, so it remains an unworked lead rather than an asserted dated match.

The backward extension provides the context for the source’s theological analogy with Shem and Japheth walking backward to cover Noah’s nakedness. The analogy concerns covering and reversal; the text in Genesis 9:23 (BSB) does not itself state a numerical operation. Similarly, the proposed contrast between thirteen as curse/judgment and seven as completion remains theological interpretation, not an independently established mathematical meaning of every occurrence.

The complete 161-unit comparison grids

161 = 7 × 23. The fourteen reference labels below reproduce the source’s full comparison set, alongside the current canonical primary labels in the same equalized frame.

CSV: reference anchors (data ZIP). Current SP 4414, 3954 and 2758 replace the source’s 4413, 3953 and 2757 in the primary comparison. File 18 does admit Noah’s qualified companion death 2757, but it does not extend that Noah/Shem adjacency to Jared or Creation. The SP Creation-to-Noah-death identity is 4414−2758 = 1656, controlled by File 11 §8.1.

The source itself also records 4414→711 = 3703 beside 4413→710 = 3703. The first is a valid current-primary Creation comparison using the source’s upper Ark-entry boundary. It preserves the seven-unit flanking motif without moving Creation. In each case 3703 = 161 × 23 = 23 × 23 × 7, not 161×7.

Exact matches in the historical selection

CSV: historical exact matches (data ZIP). There are 14, not 15. Their row counts are 2, 1, 3, 1, 2, 3 and 2, an average of exactly two. Six of the fourteen have a 161 factor divisible by three, allowing an integral Prophetic expansion through 483. Their factors are 30,12,9,6,30 and 6. The two factors 30 and two factors 20 are also the source’s emphasized tenfold examples; factor 20 is not divisible by three.

Exact matches with current SP primary rows

CSV: current-primary exact matches (data ZIP). This fixed seven-label grid has 10 exact matches. Its 710 row has none. The separately declared 4414→711 boundary comparison remains available, but is not counted as a match to 710. The historically reported “all seven selected labels have an exact partner” therefore belongs to the older selection. It is not a current-Canon finding about the fixed 710 grid.

Every historical comparison: 98 cells

CSV: all 98 historical comparisons (data ZIP). Each cell satisfies span = 161 × quotient + remainder. A nonzero remainder, including a multiple of 23, is not an exact 161 match. Earlier dialogue lists mixed exact matches with remainder-bearing examples and contains several incorrect remainders; the table above recalculates every cell.

Every current-primary comparison: 98 cells

CSV: all 98 current-primary comparisons (data ZIP). This is a current-data audit, not a replacement historical account. Both grids remain accessible so that the preservation of the source model and the status of its claims can be evaluated separately.

What the exploratory probability examples actually measure

The original study asks whether its alignments are unusually common. That research question is preserved, together with its proposed 4/12, 5/13, 7/66 and 98-cell trial models. The following figures correct their arithmetic while keeping their assumptions visible. They are hypothetical binomial demonstrations, not probabilities that the whole biblical pattern arose by chance.

For independent, identically distributed trials, the calculation would be P(X = k) = C(n,k) p^k (1−p)^(n−k); P(X≥k) sums the upper tail. The study’s dates share endpoints, are chosen after examining several alternatives, and mix counted boundaries and festival offsets. Those dependencies and selection procedures require a specified null model before the formula can be used as evidence.

CSV: exact hypothetical binomial calculations (data ZIP). The 4/12 and 5/13 models use the source’s assumed p =0.033. Its proposed adjustment (1/46)/0.667 is about 0.03259, rounded to 0.033; the factor 0.667 is an assumption rather than an established probability of the allowed phase choices. Adding the actual Flood anchor to the success count is also not an additional random trial: that anchor generated the projected labels.

For the 7/66 illustration, the exact computed upper tail is approximately 0.000581763, rather than the transcript’s 0.000741. More fundamentally, the source counts twelve event rows plus a datum, four columns, twelve extra dual-boundary entries and two literal Flood heads: 13 ×4 +12 +2 =66 slots. Combining the duplicate door-shut and rain-start entries gives the final eleven event classes plus a datum: 12 ×4 +12 +2 =62 slots.

CSV: population audit (data ZIP). Both stages contain 61 unique BC labels. Duplicate slots are not independent observations. The selected seventh anchor-class marker 526 is a festival-offset entry below the event table; it is absent from the declared 66-slot population. The native table contains six labels in the selected congruence class. The phrase “multiples of 46” means spans from the held MT Creation anchor: (4114 − label) mod46 =0. The BC label itself need not be divisible by 46.

The proposed conditional 161 probability also needs its denominator corrected. All fourteen historical reference labels and all seven selected symbolic labels share one residue class modulo 23. If the remaining modulo 7 classes were uniformly distributed, the conditional per-cell probability would be 23/161 =1/7, calculated as (1/161) ÷ (1/23). It is not (1/161)/23, and 1/7 is 14.2857%, not close to 50%. The current SP primary replacements no longer share the same modulo 23 class, so that historical condition is not uniformly true of the corrected 98-cell grid.

Under the merely illustrative independent 98-trial model with p=1/7, at least the actually observed fourteen historical matches has probability approximately 0.543818. At least fifteen would be 0.429353, not 0.9999. Treating the dates as independent unrestricted integers with p = 1/161 instead would ignore the deliberate modulo 23 conditioning.

The historical alternative “at least one match in each of seven rows” calculation used 1−(13/14)^14. That assumes p = 1/14, without deriving it from the 161 or conditional 7 residue problem. Its corrected value is 0.645665 per row and 0.0467788 for seven independent rows, rather than the reported 0.6513 and 0.0282. With the historical conditional p = 1/7, the corresponding values would be 0.884457 and 0.423385. CSV: row-coverage illustrations (data ZIP). Neither version resolves the dependence caused by sharing the same fourteen reference dates among all seven rows.

The value of the comparisons therefore lies first in reproducible arithmetic, explicit alternatives, narrative placement and theological coherence. The original proposed combined odds with another study of Genesis birth dates remain a research proposal: no joint null model, independence proof or complete second-study trial ledger is supplied here. The numbers above do not establish an extreme statistical certainty of divine design.

Source corrections and continuing research

The numerical models, calendar alternatives and theological interpretations remain available. Incorrect arithmetic, incorrectly assigned people, and event labels contradicted by the biblical text are repaired. The full correction ledger (data ZIP) identifies the original block, the rejected formula and its corrected execution. The unchanged original transcript remains at its original address.

Additional research can strengthen the model by keeping four things separately reproducible: the dated textual narrative, each calendar and phase rule, the chosen comparison set, and any proposed null model. The gain is a clearer account of the same research, capable of further refinement without treating every source-era label as an equally current chronological anchor.

Mirror, cumulative and Sumerian comparisons

These tables support the Part 4b Flood study. They retain its larger chronological comparisons while showing the operation used in each case. A symbolic BC or AD coordinate represents a position in a calculation; it does not claim that Noah released a bird in that historical year.

The principal controls are File 00 §3.9, File 09 §3 and Appendix A, File 18 §§6A–6C, File 22 §§5–7, and Files 21 and 34 for the Sumerian constructions. The dated source capture and unchanged original chart accompany the publication package.

1. Three operations that must remain distinguishable

Converting a year to astronomical notation changes its label. For example, 6 BC is astronomical year −5. It does not reflect the date or alter an elapsed span. For ordinary BC–AD spans the civil calculation is BC + AD − 1: there is no civil year zero.

The Canon also preserves precise numeric-year Mirror nodes, such as 1406 BC → AD 1406. Their elapsed comparison is 1406 + 1406 − 1 = 2811. A separately declared Protocol 1 comparison instead uses the AD 1405 target and gives 2810. These are different operations and cannot silently replace one another.

For a half-year seasonal pair, File 09 Appendix A requires suffix inversion:

Yt / (Y − 1)n BC → AD (Y − 1)t / Yn.

Here t means Tishri and n means Nisan. The BC pair 1407t / 1406n is about half a year wide; its AD counterpart is 1406t / 1407n, also half a year wide. Both same-season component comparisons give 2812. Writing AD 1406n / 1407t would create a one-and-a-half-year pair and would fail the exact phase comparison.

The averaged value of the two single-date spans is also 2812, but averaging is an explanation of this particular paired state, not a general rule for arbitrary date ranges. The Canon’s simplified seasonal model centers these pairs on the start of January 1, AD 1, associated with the traditional circumcision and naming datum. This is a chronological model; it does not claim that Scripture supplies every month, day and hour used in it.

Download the phase-pair register (data ZIP).

2. Four crisscross comparisons: 980 and 966

The later Flood ledger places the first raven/dove sending at morning coordinates 410, 440, 590 and 620 BC. Its final dove-flight alternatives include the completed-week coordinates 396, 426, 576 and 606 BC. Comparing them with the indicated AD-side surface-dry coordinates gives:

Each cell uses BC + AD − 1. Thus 410 + 571 − 1 = 980 and 396 + 571 − 1 = 966. The difference is 14, corresponding to the two explicitly stated seven-day waits in Genesis 8:10–12. The comparison expands by 966 × 70/69 = 980, or 483 + 483 → 490 + 490.

Where exact seasons are opened, the raven pair 411t / 410n BC compares with AD 570t / 571n, the paired counterpart of 571t / 570n BC. Both components then return 980. The corresponding pairs are 441t / 440n → AD 540t / 541n, 591t / 590n → AD 390t / 391n, and 621t / 620n → AD 360t / 361n. This explains why an AD label must carry its proper phase after pairing rather than simply inherit the BC-side suffix.

The final-dove pairs marked inclusive/exclusive in the original are counted-week alternatives. They are not automatically Tishri/Nisan pairs. The 966 column expressly chooses the completed-week endpoint; selecting 397 rather than 396, for example, changes that integer comparison to 967.

The underlying raven-to-uncovering interval is 50 nominal days, 310 → 360, in the author’s selected 360-day reconstruction. Genesis 8:7 and 8:13 associate the raven’s movements with the receding waters and later report the uncovered ground surface. Complete earth-dryness is the later second-month, twenty-seventh-day notice, not this first-month surface-dry notice. The reconstruction that sends the raven at night and the first dove the following morning remains a proposed reading; the numerical fit does not establish those hours as stated narrative facts.

Download all four 980/966 comparisons (data ZIP).

The four 966 units from Conquest to the mirrored Flood

The source’s longer chain becomes exact when its seasonal components are displayed consistently:

The whole span is 3864 = 4 × 966 = 8 × 483. For example, 1406n BC → AD 2459n gives 1406 + 2459 − 1 = 3864. The source’s compressed unsuffixed 1406 BC → AD 2458 gives 3863 and must not be used as the proof of 3864. The association between four paired spans and the four pairs of people saved in the Ark is typological interpretation of the arrangement.

3. Creation and the Conquest: 5520 and 6900

Creation’s endpoint and the Conquest’s paired AD-side counterpart provide a compact comparison:

At the other ends of the windows, MT 4122t / 4121n BC compares with AD 1399t / 1400n and again gives 5520. LXX 5502t / 5501n BC gives 6900 to that same target. These equal component spans preserve the seven-year width of each schematic window.

Jared’s regular birth occurs 460 years after the normal MT Creation endpoint. Therefore 5520 − 460 = 5060, and 5060 × 25/23 = 5500. The source reads 6000, 5500, 7000 and 7500 through the six-day, morning/evening and seventh-day-rest motifs. The proposed seven-and-a-half-unit extension is an Enochian comparative interpretation; Genesis’ Creation week remains seven days.

The LXX-to-MT difference used here is 1380 = 23 × 60, comparing matched Terah states. The separate cross-variant comparison 5554 − 4114 = 1440 intentionally combines LXX +60 with normal MT and cannot replace that matched 1380 difference.

The source’s earlier 894 BC → AD 1406 claim likewise needs its phase shown. Unsuffixed elapsed arithmetic gives 2299. The paired completion 895t / 894n BC → AD 1406t / 1407n gives 2300 on both components. This retains the proposed tenfold relation to the 230-day symbolic interval without silently omitting the civil crossover correction.

The old formula “6900 × 70/23 = 7000” is corrected to 6900 × 70/69 = 7000. The ratios 70/69 and 25/23 are separate transformations.

4. The 1150, 1260, 1290 and 1335 comparisons

The later source uses morning datums 720, 750, 900 and 930. Earlier 721/751 labels and later counted-week alternatives remain accessible in the calendar tables. They must not be flattened into one unnamed counter. An inclusive numbered total counts the opening unit; a completed elapsed total does not.

The Kislev 25 comparison and 1150

On a Tishri-start, thirty-day-month model, Kislev 25 is the nominal 85th day, two days before the 87th-day rain-end marker. Its four projected labels are 636, 666, 816 and 846 BC. The matching exit-associated AD labels are 514, 484, 334 and 304.

The last two columns explicitly open the paired seasonal companion: an exit pair 515t / 514n BC has AD counterpart 514t / 515n. They do not claim that 636 BC → AD 514 is 1150 completed years. With only those two unexpanded labels it is 1149. The alternative reading of Daniel 8’s 2300 evenings and mornings as 1150 full days is retained as an interpretive option, distinct from the straightforward 2300-unit reading.

Download the 1150 counter comparisons (data ZIP).

The 1260 and 1290 family

The source combines 360 + 720 + 180 = 1260, reading these as a time, times and half a time. A declared leap-month insertion adds 30 and gives 1290. The 390-unit counterpart is not the same count as 360 unless the insertion is stated.

At the final table’s raw morning-label level, 720 BC → AD 540 and 900 BC → AD 360 each span 1259 completed years, or an inclusive numbered 1260. Similarly, 720 → AD 570, 750 → AD 540, 900 → AD 390 and 930 → AD 360 give 1289 completed years, or an inclusive numbered 1290. Opening the corresponding outer boundary or phase-expanded partner adds the separately declared unit; it must be visible in the calculation.

One especially clear source comparison already specifies the festival’s preceding evening:

The festival’s fifteenth-day morning labels are 526, 556, 706 and 736; the seventeenth-day Ark-rest labels are 524, 554, 704 and 734. The preceding evening permits a three-day inclusive festival/rest comparison. Its application to Jesus’ ministry, death and resurrection remains a calendar and typological proposal; the source texts do not independently date that ministry to exactly 1260 days or every associated anniversary to an hour.

Download the festival/rest comparisons (data ZIP).

Three families associated with the numbered 1335th unit

The source proposes three four-column crisscross families. Their raw integer endpoint sums are 1334, so ordinary BC + AD − 1 gives 1333 completed years. An explicitly chosen outer AD boundary one unit farther gives 1334 completed years and therefore a locally inclusive numbered 1335th unit.

These are qualified counter constructions. The outer target must be declared rather than silently supplied. The counted-week dove alternatives do not by themselves authorize assigning a particular Tishri/Nisan phase to every slash pair. The table preserves the proposed comparison and its valid arithmetic but does not present the raw morning rows as a completed 1335-year proof.

Daniel 12:12 refers to the end of 1,335 days; the verified BSB and NIV texts do not use an ordinal “1335th day” that forces this reconstruction. The ordinal explanation belongs to the local interpretive model. Also, 46 × 29 = 1334, not 1335.

Download every endpoint and counter in the three families (data ZIP).

Why the differences are significant within the proposal

The two-day Kislev 25/27 and festival 15/17 differences are read beside the two-year Flood-to-Arphaxad anomaly. That association is the author’s interpretive argument; it does not identify all these distinct events, units and counters as one literal duration. The initial priestly lead 336 × 3.5 = 1176 is also preserved, but the original does not supply an independently executable endpoint pair for its 1176 Mirror claim.

5. Enoch: same-side years and AD-side comparisons

The normal MT chronology places Enoch’s taking at 3127 BC, 987 years after 4114 BC. His 365-year lifespan and the Enochic 364-day calendar are related interpretively, while their numerical values remain distinct.

AD 3127 is a stated precise numeric-year Mirror node, not an astronomical relabeling of 3127 BC. The first four rows are entirely BC comparisons and use subtraction; the later rows use BC + AD − 1. The 607/577 endpoints give 2520/2550 respectively, not 2550 twice. The 427/397 endpoints give 2700/2730 respectively.

The source reads the final dove’s departure without return beside Enoch’s taking and Christ’s ascension, and relates the Spirit’s descent like a dove and His remaining on Jesus to John 1:32–33. The Book of Enoch supplies the Watcher-intermediary context; Scripture’s own taking-of-Enoch narrative does not date it to the anniversary of Noah’s exit. That anniversary remains the proposed thematic correspondence.

The broader source also proposes a triple 1260 extension and an eight-unit analogy using 365. The 365 belongs to Enoch’s lifespan, not Noah’s. Of the four displayed Creation-anniversary labels 714, 744, 894 and 924, the exact cross-axis spans to AD 3127 are 3840, 3870, 4020 and 4050. The 3870 = 3 × 1290 row is valid; none of those four raw comparisons gives 3780 = 3 × 1260. The triple-1260 and unspecified 365-extension leads remain preserved as proposals whose missing endpoint operation has not been recovered, rather than as verified equations.

Download the Enoch comparison register (data ZIP).

6. The complete cumulative MT register

Cumulative chronology adds the selected 26 lifespans in succession rather than following their overlapping ordinary biographies. The Moses/Nisan line spans 12600 years from Adam’s 14006 BC internal Year-6 coordinate to Moses’ death/Conquest in 1406 BC. The full Creation window is 14011–14004 BC. Its endpoint, internal coordinate and seven-year envelope answer different questions.

The exact Aaron/Tishri line is 3.5 years earlier in phase than the Moses/Nisan line. The original transcript’s whole-year three-year bands are retained in the downloadable register, alongside the Canon’s phase-resolved values. The ordinary three-year branch and exact 3.5-year phase branch are both valid in their stated reckonings. Aaron’s lifespan remains 123 and Moses’ remains 120; a phase separation does not change either lifespan.

The two-year Shem resolution on either side of the ordinary three-year separation supplies the forwarded 2 + 3 + 2 = 7 envelope. Opening the exact 3.5-year branch instead requires the separately identified 7.5-year phase spread; it does not make the integer seven-year display wrong. The warning’s 120 years lie inside the cumulative Shem/Flood structure and are not an additional life to add again to the 26-life sum.

The cumulative table prints the Flood and Arphaxad under the same broad envelope. Those entries retain distinct event markers within the Shem resolution; they do not assert that the ordinary Flood outbreak and Arphaxad’s birth happened on the same day or in the same literal year.

The MT warning window 4956–4949 → Flood 4836–4829 spans 120. Its head 4956 → Moses’ birth 1526 spans 3430. The SP cumulative warning window 4836–4829 aligns with the MT Flood window; the SP Flood is 4716–4709, 120 years later. These are comparative cumulative states and do not change the ordinary MT Flood in 2458 BC.

The original also proposes 360 and 360 + 360 from an overlay of Shem’s 600-year members. The warning seam makes an explicit reconstruction possible. Deriving an SP Shem head as 4716 + 600 = 5316 BC, the selected heads read:

The 5316 member is derived here from the selected SP Flood head and Shem’s 600 years; it is not an additional directly displayed row in File 18 §6C. The 360 comparison selects the internal warning seam, while 720 measures the combined outer span. Simply overlapping two 600-year members offset by 120 gives a 480 overlap, so the warning selection must remain visible rather than calling every part of the overlay 360. The original’s design interpretation is retained on these stated conditions.

The original table’s adjoining Joshua line is retained with its state corrected. 1296 BC is a schematic SP cumulative death target, 110 years after the 1406 BC start; File 22 §9A also uses it in the restored-Cainan product comparison. The corresponding forwarded start window is 1411–1404 BC. The source’s 1521–1404 label spans 117 and cannot be identified as Joshua’s 110-year ordinary lifespan. His regular biography remains 1476–1366 BC, also 110 years.

Download the full register, including the original whole-year bands (data ZIP).

Matched Flood and Conquest windows

4836–4829 BC → 1406–1399 BC gives 3430 at both matched endpoints: 4836 − 1406 = 4829 − 1399 = 3430 = 70 × 49 = 7 × 490. The six-year conquest/rest-onset interval 1406–1400 and its ensuing seventh-year position 1399 remain distinguishable inside that seven-year comparison.

The New Testament and judgment envelopes

The birth envelope 6 BC → AD 2 spans seven completed years, with the familiar 6 BC → AD 1 six-year interval and its further year. The judgment envelope is AD 65–72. AD 70 lies inside it; 4836 BC → AD 70 is 4905, not 4900, and 4829 BC → AD 70 is 4898. An event within an envelope must not be substituted for both envelope endpoints.

The source’s 4830 + 35 echoes the tenfold 483 + 3.5 comparison. It reaches AD 30 from the selected head; it does not also yield AD 33 without changing a component. Both targets may be discussed, but they require their own arithmetic.

Download the matched cumulative/NT comparisons (data ZIP).

Shem, the exile and the final dove coordinate

The last row begins at the Flood, not Shem: 5436 − 426 would be 5010. An additional 490 from 426 BC reaches AD 65, since 426 + 65 − 1 = 490; it does not reach 536 BC. This connects the selected 4410 row with the 4900 judgment-week head.

The 536 BC coordinate remains the repository’s restoration/altar reference and the endpoint of the 606 → 536 schematic seventy-year comparison. Daniel 9:1–2 dates its prayer to Darius’ first year; this passage does not independently establish 536 BC as the exact historical year of that revelation. The restoration comparison and the text’s own chronological designation should remain separate.

The two Creation-week comparisons 14011 − 4121 = 14004 − 4114 = 9890 = 23 × 430 form the actual cumulative-to-regular bridge in File 22 §5. This is not the separate Rounded 9900 bridge.

7. Restoring second Cainan: what moves and what stays fixed

The LXX second Cainan supplies 130 + 330 = 460 years. Adding that lifespan to the comparative MT cumulative chain shifts Adam through Arphaxad earlier by 460 years, with Shelah and subsequent rows converging on the original chain. This is a restored-Cainan comparative state, not the normal MT text or a correction to it. A regular genealogical insertion uses the 130-year begetting interval; the cumulative insertion uses the full 460-year lifespan.

The normal regular restored-Cainan lifespan member 2551–2091 BC also spans 460, as File 16 records. Its 2091 endpoint is compared with Abraham’s Call coordinate. Neither this coincidence nor the LXX/MT textual difference establishes the historical motive that the MT “intentionally dropped” Cainan; that statement was stronger than the evidence offered in the dialogue.

Three larger lengths require three separately specified constructions:

The second row supplies an explicit, separately declared reconstruction of the source’s 10580 scalar. It is not the same Mirror state as the following phase-paired row, and it is not the self-mirror span of the entire 5296–5289 envelope. Single same-numeric-year nodes would give 10591 for 5296 BC → AD 5296 and 10577 for 5289 BC → AD 5289. The source’s compressed phrase “to itself in the Mirror” does not suffice to choose an operation by itself.

The third row checks as 14465 + 1406 − 1 = 14464 + 1407 − 1 = 15870. Its week heads, 14472t / 14471n BC → AD 1399t / 1400n, give the same length. Conversion yields 15870 × 70/69 = 16100 = 7 × 2300, or 15870 × 25/23 = 17250 = 7.5 × 2300. The source’s 14466 is the ordinary internal Year-6 coordinate; it is not interchangeable with the endpoint 14464 or the head 14471.

Download the restored-Cainan register (data ZIP).

8. The recovered Sumerian chart and its four states

The unchanged original bitmap is available at its existing image address. The following transcription preserves its comparative research while distinguishing a tablet’s transmitted reign from the author’s assigned biblical counterpart and absolute BC coordinate.

The Oxford ETCSL King List translation, lines 1–39, gives eight antediluvian kings with a combined 241200 years. The chart compares those kings with eight selected biblical figures. It does not claim that the tablet names Adam or Noah, supplies these biblical identities, or contains the modern projected BC dates.

The eight reigns sum to 241200, and 262086 − 20886 = 241200. The full native biblical genealogy is not an eight-name King List. The comparative alignment, including Tammuz/Dumuzid with Mahalalel, is the author’s model.

The original image’s long-state note correctly has Adam 268566, Enoch 66966 → 45966 and Flood 27366, but it leaves Pre-Creation at the short-state 452886. A consistently shifted long-state Pre-Creation is 459366. The short and long rails differ by 6480 throughout. A +30 mode and a selected local +2-year rail are likewise named alternatives, not compulsory corrections to every row. Scaling two ordinary years of 360 nominal days supplies a distinct 720-year macro comparison; +2 and +720 must never be applied as interchangeable local operators.

The 23 post-Flood rulers

The ETCSL translation’s lines 40–94 report a 24510-year subtotal with three months and three-and-a-half days. A selection of its individual whole-year reign values—including the apparatus-dependent 670, 420 and 300—sums to 17980. The Canon calls the corresponding computational states Sumerian A / SKL Short and Sumerian B / SKL Long. This article preserves both states without treating the selected component sum as if it were the same reported subtotal or flattening their textual apparatus.

The duration difference is 6530 = 6480 + 50, while the assigned Flood coordinates differ by 6480 because their terminal anchors differ by 50. The appended three months and three-and-a-half days remain a separate textual datum; under an explicitly opened scalar, 3.5 × 360 = 1260. Their fractional payload is not silently folded into these whole-year tables.

Download the eight-king four-state register (data ZIP) and the 23 selected Kish reigns (data ZIP).

Every additional lead in the original chart

The Etana image’s assertion that some copies give him 1560 is not confirmed by the inspected ETCSL apparatus: it gives 1500 and an alternative 635. Its 1560 dynasty subtotal concerns En-me-nuna and Melem-Kish. The 1560 coordinate difference remains useful and is retained; it should not be converted into an attested Etana reign variant. The ascended-shepherd and miraculous-son parallels are interpreted beside biblical ascension and patriarchal narratives, without making Etana and a biblical patriarch the same historical person.

The chart extends that interpretation through Balih’s 400. Its Abraham-to-Exodus comparison is specifically the 400-year affliction member, 1846 → 1446 BC, rather than the 720 years from Abraham’s birth in 2166 to the Exodus. Balih, as the son associated with Etana’s ascent narrative, is compared with the promised or miraculously given son in the patriarchal story. The author then reads Revelation 12 alongside this theme: a child, ascent to God and the ensuing wilderness period. These are comparative theological readings, not an identification of Balih with Isaac or proof that Revelation borrowed Etana’s story.

The original bitmap prints the Pillar numbers without an era. The AD prefixes are supplied by the current Canon, File 21 §6.3 and Appendix F, which expressly classifies them as Projective Boundary coordinates from the Temple-Time / Ezekiel temple framework. They are model endpoints, not ordinary dated pillars or a forecast of events in those AD years.

9. From 3430-year units to the precessional display

The AD 2024/2025 comment records the original study’s 2024 setting. Under ordinary civil arithmetic the exact 77-unit target is AD 2025: 262086 + 2025 − 1 = 264110. AD 2024 gives 264109. This is a source-era structural comparison, not an updated assertion about the present year or a prediction of an event.

The source’s subtraction 262086 − 259200 produces 2886, not both 2886 and 2166. Abraham’s 2166 BC coordinate is 720 years later than 2886, and his birth to the Exodus 1446 also spans 720. Alternatively, holding the 259200 length while ending at 2166 would require a generated origin of 261366, a different coordinate. The +720 Adam rail 262806 minus the same 259200 length reaches 3606; it does not turn the original subtraction into the 2166 equation.

The nested scaling proposal can now be stated with its units visible: 259200 deep-time years ÷ 360 = 720 biblical comparison years; a further contraction 720 ÷ 360 = 2 nominal year-units; those two year-units may then be mapped to two day-units by the day–year rule. This chain relates the two-year Flood-to-Arphaxad resolution to the larger scale; it does not mean that 259200 ordinary years literally equal two days. Counting the 360-day body separately from the four Enochian seasonal days is a declared counting choice, not literal equality between 360 and 364.

25920 and the corrected square

The repository uses the schematic precessional measure 72 years per degree, yielding 360 × 72 = 25920 years. Its quarter is 6480 and its half is 12960. Modern primary-source descriptions give approximately 26000 years (NASA) or 25800 years (ESO). Thus the exact 25920 here is an idealized structural measure, not an epoch-invariant astronomical measurement or evidence by itself that every ancient source used it.

The near-match with the Key of 23 is:

25920 + 1 = 25921 = 161² = (7 × 23)² = 49 × 23².

The original “(23 × 49)²” is a typographical/arithmetic error: it is 1270129. The corrected square remains central in File 21 Source §14 and Appendix F Note A. Scaling it tenfold yields 259210, ten more than 259200; that difference generates the 2886 versus 2876 terminal pair from the same 262086 origin. This supplies the Jubilee-square comparison without changing the Great-Year definition to 25921.

The link between 49-year cycles, their jubilee-completion imagery and the King List’s 23 rulers is the proposed interpretation of the square; the King List does not expressly give that calculation. Nor is the legacy claim that 25920 was “common in antiquity” independently established by the sources inspected for this rewrite.

The 11270 and 16560 leads

The source combines 23 × 490 = 230 × 49 = 11270 while distinguishing Daniel 8’s 2300-unit expression from Daniel 9’s seventy sevens. It also records 1656 × 10 = 16560 = 23 × 720 as a proposed connection to the Sumerian Flood field. The article does not supply a complete endpoint pair for that specific 16560 claim, so the scalar is preserved as a research lead without inventing a new pair to prove it.

The 1656 comparison occurs at different narrative positions in the selected ordinary textual chronologies: MT Creation → Flood, LXX Creation → Noah’s birth, and the selected SP Creation → Noah’s death. It is not 1656 years from Creation to the Flood in all three traditions. Those different positions are part of the comparative argument.

Download the complete large-scale comparison register (data ZIP).

10. Related SP, Egyptian and interpretive comparisons

The ordinary cross-tradition SP chains 3106 → 1846 → 586 BC = 1260 + 1260 and 3166 → 1876 → 586 BC = 1290 + 1290 remain in the calendar and day–year tables. Here 1846 is the representative 400-year-before-Exodus coordinate, while 1876 is the normal MT 430-year Egypt-entry coordinate. The +60 Terah selection and the Gear-1 or Gear-2 choice must be stated. A comparative use of MT Egypt anchors does not make the native SP sojourn Egypt-only 430. See the SP / Egypt backbone.

The larger comparisons are read within an interpretive framework joining Creation, Flood, Exodus, Conquest and new creation. Revelation 10 combines rainbow, fiery legs, the little scroll, book-eating and seven thunders. The proposed correspondences connect the rainbow with the Flood, the fiery pillars with the Exodus, book-eating with Ezekiel, and the unrecorded thunders with a storm-like interval before judgment. The nesting of trumpets within the seventh seal and the little-scroll scene between the sixth and seventh trumpets provides the literary analogy for nested time scales.

The “great scroll / little scroll” reading contrasts the vast cumulative and Sumerian constructions with individual narrative days projected as years. It remains an interpretation of the imagery; Revelation does not expressly identify its scrolls with these chronological tables. Likewise, the woman, sun, moon and twelve stars of Revelation 12 are read through Christ, the redeemed sons of God and a slow celestial timepiece. Identifying her twelve stars with a zodiacal precessional framework is a proposed astronomical analogy, not the passage’s explicit identification and not a claim about replacing Israel.

The celestial host in Daniel 8:10–14 and the shining wise in Daniel 12:3 supply the source’s angelic/cosmic reading of time. Their presence does not by itself prove that those texts encode a specified precessional equation. 2 Peter 3:3–10 brings Creation, the Flood, future judgment, divine patience and repentance into the same discussion. Its day/thousand-year analogy runs in both directions. The source interprets that reciprocity as permission to attend to both large and small patterns while keeping the passage’s ethical purpose: patience invites repentance and judgment still comes unexpectedly.

The analogy of a fractal describes these repeated structures across scales. It is not a demonstrated formal mathematical fractal, a validated statistical proof, or a basis for assigning a dated future fulfillment. The exact equations, the selected calendar operations, and the theological interpretation remain visible together, so each can be assessed on its own evidence.

Return to the detailed Part 4b article.

Read the unchanged original discussion.