The Exodus at the Center: A Detailed Study of the 980-Year Scaffold

At the end of the 430 years, to the very day, all the LORD’s divisions went out of the land of Egypt.

— Exodus 12:41, Berean Standard Bible (BSB)

The Exodus closes a long period of waiting and begins Israel’s journey toward the land. In the chronology used on this website, its date, 1446 BC, also stands at the center of a carefully defined numerical arrangement:

1936 BC → 1446 BC → 956 BC = 490 + 490 = 980 years.

The equality is simple; the meaning of its endpoints is more demanding. The first, 1936 BC, is second Cainan’s death in a restored regular genealogy with +60 Terah and the minimum, or shorter, Sojourn setting. The last, 956 BC, is calculated from a schematic Judges ledger extended by the wilderness and Joshua periods. Their symmetry compares declared chronological settings. It does not make both endpoints independently dated historical events.

This detailed study develops the argument behind The Exodus at the Center: Two 490-Year Spans. It begins with the genealogical and Judges evidence, then follows the resulting relationships into Jacob’s household, Solomon’s construction periods, and a bounded Flood comparison. The governing canonical study is File 64, The Jephthah–Judges Sanctuary Nexus; File 18’s chronological tables control the selected dates.

1. The central comparison

Figure 1 · Detailed study

Two equal spans around the Exodus

All three coordinates are BC dates. The endpoints come from explicitly identified model states.

1936 BC

Restored Cainan’s death

Regular variant: +60 Terah; minimum Sojourn.

1446 BC

The Exodus

The center of this same-side comparison.

956 BC

Schematic Judges endpoint

Joshua-extended 490-year ledger.

490 years1936 − 1446
490 years1446 − 956
490 + 490 = 980 yearsThe arrangement stays entirely within BC chronology. It does not activate a BC–AD Mirror protocol.
1936 − 1446 = 490 and 1446 − 956 = 490. This same-side symmetry is distinct from a BC–AD Mirror calculation.

Sources: File 64 §8.8: the Exodus-centered 490 + 490 structure · File 18 §1.3.1: Cainan’s four regular date states · Exodus 12:41: narrative setting (BSB).

Full table and explanation

Model and calculation details

The left endpoint is the death of the restored second Cainan in the regular +60 Terah, minimum-Sojourn state. It is not the ordinary MT genealogy. The right endpoint is calculated by the Joshua-extended schematic Judges ledger. The total distance is 1936 − 956 = 980 years. No civil BC–AD crossing occurs, so no −1 correction applies. File 64’s local complement around 1446 is not a new formal Mirror protocol.

Static image alternativeAn entirely BC arrangement: 1936 BC, restored second Cainan’s death in the +60 Terah and minimum-Sojourn variant; 1446 BC, the Exodus; and 956 BC, the schematic Judges endpoint. Each side of the Exodus is 490 years; the whole span is 980 years. It is not a BC–AD Mirror calculation.

Download SVG source (ZIP) · Open PNG

Both arms lie entirely within BC chronology. As time advances, the BC labels decrease, so the calculations are:

MeasurementCalculationYears
Left endpoint to the Exodus1936 − 1446490
Exodus to the right endpoint1446 − 956490
Entire arrangement1936 − 956980

The midpoint check is (1936 + 956) ÷ 2 = 1446. Addition here tests the midpoint; subtraction measures the distance. The sum 2892 is therefore not a 2892-year span between the endpoints.

Three kinds of evidence meet in the diagram:

DateCoordinateStatusBasis
1936 BCRestored second Cainan’s deathRegular variant: +60 Terah; minimum Sojourn2396 − 460 = 1936
1446 BCExodusFixed repository historical anchorCenter of the comparison
956 BCJoshua-extended Judges endpointSchematic duration ledger1446 − (40 + 40 + 410) = 956

Throughout this study, historical identifies an event date within the repository’s regular historical chronology. Variant identifies an explicitly selected alternate chronological setting. Schematic identifies a coordinate generated by an ordered numerical construction. The diagram brings those categories into comparison while preserving their differences.

The main historical baseline remains the normal MT chronology: 430 years in Egypt, Exodus in 1446 BC, Conquest in 1406 BC, Joshua’s death in 1366 BC, and the historical Temple foundation in 966 BC. The special settings used for Cainan or Jacob are identified where they enter the argument.

2. Cainan and the 1936 BC endpoint

Second Cainan belongs between Arphaxad and Shelah in Luke 3:35–36 (BSB). He is distinct from the earlier Kenan in Adam’s genealogy. The textual distinction is equally important: MT and SP Genesis 11 omit this second Cainan, while the LXX includes him. The model considered here restores him within a regular genealogy; it does not claim that his name appears in the MT text.

Brenton’s English Septuagint, Genesis 11, supplies the numerical inputs: Cainan lives 130 years before fathering Sala, then another 330. Sala is the name rendered Shelah in the chronology. The calculated lifespan is 130 + 330 = 460 years. In that linked edition, the Cainan passage is an unnumbered continuation between the printed verses 13 and 14.

Four settings, not one unqualified date

File 18 §1.3.1 preserves the following four restored-Cainan positions:

Shelah birth BCCainan birth BCCainan death BCTerah +60Egypt yearsSetting
248126112151Active430Both variants
242125512091Inactive430Full-Egypt comparison only
226623961936Active215Selected article state
220623361876Inactive215Minimum state

The selected row can be checked from Shelah’s birth in 2266 BC:

2266 + 130 = 2396 BC, Cainan’s birth; 2396 − 460 = 1936 BC, his death.

The +60 Terah setting is active in that row, while the +215 Sojourn setting is not. The minimum setting uses the shorter, 215-year Egyptian stay. Adding the Sojourn 215 moves the relevant earlier dates into the full-430-years-in-Egypt comparison; the Exodus itself remains fixed at 1446 BC. This differs from the separate, subordinate operation that relocates the Exodus by 215 years.

The +60 adjustment compares an age of 130 rather than 70 for Terah at Abraham’s birth, moving Terah and the earlier ancestry while retaining the selected Abraham date. It therefore has a defined genealogical scope. It is not an automatic shift of every event in the article. In particular, the earlier Cainan variant can be compared with the fixed Exodus without changing the normal historical dates of Joshua or the Temple.

The 130-year step and the 460-year lifespan

A regular chronology follows successive begetting ages. Restoring Cainan therefore introduces the 130-year genealogical step into the appropriate earlier ancestry. A cumulative chronology adds successive lifespans and uses 460 for his insertion. Those operations must remain separate.

Here, 460 measures Cainan’s own lifespan, 2396–1936 BC. The dates belong to the regular restored genealogy. Calling this a “cumulative +460 variant” would misidentify the active method. Nor would a native LXX sequence need another insertion of a figure it already contains.

Download the complete Cainan settings.

3. The complete Judges ledger

The other endpoint begins with a different kind of calculation. File 64 counts eighteen expressly stated year-durations in Judges 3:8–16:31, retaining each once in the order of the passages. Their sum is 410.

All passage links below open the BSB. The digits and running totals are our tabulation, not Scripture quotations.

No.PeriodCategoryYearsRunning totalPassage (BSB)
1Cushan-rishathaim / Mesopotamian servitudesubjugation88Judges 3:8
2rest after Othnielrest/rule/judgeship4048Judges 3:11
3Eglon / Moabite servitudesubjugation1866Judges 3:14
4rest after Ehudrest/rule/judgeship80146Judges 3:30
5Jabin / Canaanite oppressionsubjugation20166Judges 4:3
6rest after Deborah and Barakrest/rule/judgeship40206Judges 5:31
7Midianite oppressionsubjugation7213Judges 6:1
8rest in Gideon’s daysrest/rule/judgeship40253Judges 8:28
9Abimelech rulesrest/rule/judgeship3256Judges 9:22
10Tola judgesrest/rule/judgeship23279Judges 10:2
11Jair judgesrest/rule/judgeship22301Judges 10:3
12Ammonite oppressionsubjugation18319Judges 10:8
13Jephthah judgesrest/rule/judgeship6325Judges 12:7
14Ibzan judgesrest/rule/judgeship7332Judges 12:9
15Elon judgesrest/rule/judgeship10342Judges 12:11
16Abdon judgesrest/rule/judgeship8350Judges 12:14
17Philistine subjugationsubjugation40390Judges 13:1
18Samson judges in the days of the Philistinesrest/rule/judgeship20410Judges 15:20; 16:31

The category totals provide a second way to check the arithmetic:

CategoryValuesTotal
Six periods of subjugation8 + 18 + 20 + 7 + 18 + 40111
Twelve periods of rest, rule, or judgeship40 + 80 + 40 + 40 + 3 + 23 + 22 + 6 + 7 + 10 + 8 + 20299
Complete ledger111 + 299410

The second category is descriptive bookkeeping: Abimelech’s rule, for example, is not being called a peaceful rest. More fundamentally, adding all the printed durations does not establish 410 consecutive historical years. The historical narratives allow overlap. Judges 15:20 (BSB), for instance, places Samson’s judgeship within the days of the Philistines.

Three rules protect the tally. Samson’s twenty years, repeated in Judges 16:31, count once. Jephthah’s retrospective 300 in Judges 11:26 is a territorial summary, not a nineteenth tenure or oppression. Finally, inferred periods for leaders without a stated duration are not inserted into the inventory.

Extending the ledger to 490

Figure 2 · Detailed study

How the right-hand 490 is assembled

The schematic ledger combines two forty-year components with the 410-year Judges inventory.

40Wilderness

Biblical duration; the model begins at the Exodus.

+ 40Joshua overlay

Derived: 1406 − 1366 = 40. Not a printed Judges duration.

+ 410Judges inventory

Eighteen duration rows. Samson’s 20 is counted once.

40 + 40 + 410 = 490
1446 − 490 = 956 BC

A schematic serial inventorySome historical periods overlap. The 410-year tally is an arithmetic construction, not a claim that all eighteen periods occurred consecutively.
40 + 40 + 410 = 490; 1446 − 490 = 956 BC. Joshua’s forty years are a derived overlay, not an additional duration printed in Judges.

Sources: Deuteronomy 2:7: wilderness forty years (BSB) · Joshua 24:29: Joshua’s death and age (BSB) · File 18: regular Conquest and Joshua coordinates · File 64 Appendix A: the eighteen-row Judges inventory.

Full table and explanation

Model and calculation details

The wilderness contributes 40 years. The regular chronological dates 1406 BC for the Conquest and 1366 BC for Joshua’s death yield the derived Joshua overlay of 40. File 64 sums eighteen stated Judges duration rows to 410, counting Samson’s 20 years once. This is a serial arithmetic inventory: overlapping historical events are not made consecutive by adding their durations. Jephthah’s retrospective 300 years are not added to the 410 tally.

Static image alternativeThree components of the 490-year schematic ledger: wilderness 40 years; Joshua overlay 40 years, derived from 1406 to 1366 BC; and eighteen Judges duration rows totaling 410 years. The sum is 490; subtracting it from 1446 BC gives the schematic endpoint 956 BC. The Joshua overlay is visibly distinguished as derived.

Download SVG source (ZIP) · Open PNG

The wilderness contributes 40 years, supported by Numbers 14:33–34 (BSB). A second forty is derived from the repository’s 1406 BC Conquest to Joshua’s death in 1366 BC. Scripture states Joshua’s age at death as 110 in Joshua 24:29 (BSB), but does not print a separate forty-year reign for him. His regular lifespan remains 1476–1366 BC.

With that Joshua interval explicitly added, the construction is:

40 + 40 + 410 = 490; 1446 − 490 = 956 BC.

This is the source of the article’s right endpoint. It is a calculated close of the extended ledger, not a historical redating of Samson’s death to 956 BC.

Download the eighteen-entry Judges ledger, including both category running totals.

4. Jephthah’s 300 and the direct 430-year route

The complete ledger is not the only route considered by File 64. Its simplest route to the important 1016 BC coordinate begins with Jephthah’s territorial argument in Judges 11.

The distinction between the two sides of the Jordan matters. The retrospect concerns Israel’s occupation east of the Jordan. The canonical chronology places that occupation in 1407 BC and Jephthah’s local schematic speech/accession coordinate in 1107 BC:

1407 − 1107 = 300.

The west-Jordan Conquest is one year later, 1406 BC. Measured from that coordinate to the same Jephthah point, the span becomes:

1406 − 1107 = 299.

The 300 and 299 are thus different geographical starting points measured to the same endpoint. They are not competing totals for an unchanged pair of dates. File 64 also distinguishes the 1107 speech/accession coordinate from its 1106 completed-boundary companion; this calculation retains 1107 throughout.

The six stated durations from Jephthah’s own judgeship through Samson give the remaining tail:

PeriodYearsBSB passage
Jephthah6Judges 12:7
Ibzan7Judges 12:9
Elon10Judges 12:11
Abdon8Judges 12:14
Philistine subjugation40Judges 13:1
Samson20Judges 15:20
Total916 + 7 + 10 + 8 + 40 + 20

Starting from the Exodus gives 40 wilderness + 299 west-Jordan interval + 91 tail = 430. Consequently:

1446 − 430 = 1016 BC.

The route combines a historically anchored retrospect with a serial compositional tail. It does not make every subsequent judgeship and oppression historically consecutive. Its result is the schematic lesser Judges–Sanctuary Nexus: a shared coordinate reached by the model and then compared with other chronological patterns.

Notice also that two different calculations yield 299. One is the Conquest-to-Jephthah difference just described; the other is the sum of the twelve rest/rule/judgeship entries in the complete ledger. Their equality can be studied, but the derivations must not be exchanged.

5. Three routes, three endpoints, one terminal module

The direct Jephthah route, the full printed-duration ledger, and the Joshua-extended ledger can now be placed side by side.

RouteComponentsTotalCalculated endpoint
Direct Jephthah40 + 299 + 914301016 BC
Explicit printed-duration40 + 410450996 BC
Joshua-extended40 + 40 + 410490956 BC

They share the Exodus anchor but retain their different inputs. The 430 route ends at 1016 BC; the 450 route ends at 996 BC; the 490 route ends at 956 BC.

Figure 3 · Detailed study

One terminal module, three placements

The same Philistine forty and Samson twenty occupy different coordinates under three declared ledgers.

Schematic module placements; not to scale.

Direct Jephthah route

40 + 299 + 91 = 430

1076 BCPhilistine period opens40 years →
1036 BCSamson period opens20 years →
1016 BCModule closes

1016: closure

Explicit-duration route

40 + 410 = 450

1056 BCPhilistine period opens40 years →
1016 BCSamson period opens20 years →
996 BCModule closes

1016: joint

Joshua-extended route

40 + 40 + 410 = 490

1016 BCPhilistine period opens40 years →
976 BCSamson period opens20 years →
956 BCModule closes

1016: opening

One historical module; three accounting placementsThe three ledgers do not describe three successive copies of the same events.
1016 BC is the module’s closure, joint, or opening, depending on the route. The diagram compares calculations; it does not multiply historical oppressions or judgeships.

Sources: File 64 §§5.2–5.5: routes and terminal-module placements · Judges 13:1: Philistine forty years (BSB) · Judges 15:20: Samson’s twenty years (BSB) · Judges 16:31: the same twenty years restated (BSB).

Full table and explanation

Model and calculation details

Direct Jephthah route: 40 + 299 + 91 = 430, ending at 1016. Explicit-duration route: 40 + 410 = 450, ending at 996. Joshua-extended route: 40 + 40 + 410 = 490, ending at 956. The final 40 + 20 module is therefore 1076→1036→1016, 1056→1016→996, or 1016→976→956 BC. The 299-year West-Jordan corridor and the 299 non-subjugation subtotal in the full inventory have different derivations.

Static image alternativeThree schematic routes place the same forty-plus-twenty terminal module differently. The 430-year route ends 1076, 1036, 1016 BC, with 1016 at closure. The 450-year route ends 1056, 1016, 996 BC, with 1016 at the joint. The 490-year route ends 1016, 976, 956 BC, with 1016 at the opening. They are alternative calculations, not three historical repetitions.

Download SVG source (ZIP) · Open PNG

The final module is the same pair of printed values in each construction: 40 Philistine years + 20 Samson years. Its schematic placement changes with the route:

RoutePhilistine fortySamson twentyPosition of 1016 BC
Direct Jephthah1076 → 1036 BC1036 → 1016 BCclosure
Explicit printed-duration1056 → 1016 BC1016 → 996 BCjoint
Joshua-extended1016 → 976 BC976 → 956 BCopening

The 1016 coordinate appears as closure, joint, and opening. That is the strength of the canonical comparison: one receiving coordinate is encountered at three positions in separately declared constructions. It does not create three historical Philistine oppressions or three Samson tenures.

The same caution applies to the distance between endpoints. 996 − 956 = 40 measures the separation of the 450- and 490-year routes. It is not another biblical oppression to add to the ledger.

A numerical transition into First Samuel

The terminal 40 + 20 has a further literary comparison. 1 Samuel 4:18 (BSB) assigns Eli forty years as judge, and 1 Samuel 7:2 (BSB) supplies a twenty-year marker after the ark reaches Kiriath-jearim. The subjects have changed—from Philistine power and Samson to priesthood, the ark, and Israel’s lamentation—but the whole-year form recurs.

This is a comparison of the texts’ numerical forms, not an instruction to add another sixty uninterrupted historical years. The ark’s seven months in Philistine territory remain part of the narrative (1 Samuel 6:1, BSB). The twenty is a marker within its subsequent stay at Kiriath-jearim, not a wait before its return and not the total duration of its residence there.

The proposed recapitulation is a literary and theological reading. It supports the movement from Judges toward the sanctuary narratives without independently dating their events to the schematic endpoints.

6. The full chronological palindrome

File 64 §8.8 expands the two large arms into a six-interval pattern:

40 + 20 + 430 + 430 + 20 + 40.

Its sequence of intervals reads the same in reverse. Here palindrome describes that numerical arrangement; it does not assert that the biblical narrative itself has been demonstrated to possess this exact literary structure.

Figure 4 · Detailed study

The six intervals form a palindrome

The intervals recur in reverse order on the two sides of the Exodus: 40–20–430 and 430–20–40.

All dates BC. Grouped arms are not drawn to scale; 1446 is one shared center.

Earlier arm · restored Cainan and localized-LXX Jacob

1936 BCCainan death (+60; minimum)40 years →
1896 BCJacob flight (LXX −33)20 years →
1876 BCJacob return (LXX −33)430 years →
1446 BCExodus

Later arm · schematic Judges endpoints

1446 BCSame Exodus center430 years →
1016 BCLesser Nexus20 years →
996 BC450-ledger endpoint40 years →
956 BC490-ledger endpoint
40 + 20 + 430 + 430 + 20 + 40 = 980The last forty is the difference between the 996 and 956 route endpoints; it is not another Philistine oppression.
The outer sixty-year flanks surround two 430-year spans: 60 + 430 + 430 + 60 = 980. The selected nodes retain their distinct chronological states.

Sources: File 64 §8.8: complete palindrome and endpoint safeguards · File 18 §1.3.1: restored Cainan states · File 04: localized LXX −33 Jacob comparison · Genesis 31:41: Jacob’s twenty years (BSB).

Full table and explanation

Model and calculation details

1936 is restored regular Cainan’s death under +60 Terah and minimum Sojourn. Jacob’s 1896 flight/service opening and 1876 return belong to the localized LXX −33 comparison. 1446 is the Exodus. 1016 is the lesser Nexus and direct-route closure. 996 and 956 are endpoints of the 450- and 490-year ledgers. The final 996→956 forty years is a difference between route endpoints, not another Philistine oppression. The two displayed 1446 nodes are the same center.

Static image alternativeEarlier arm: 1936 BC Cainan’s variant death, then forty years to Jacob’s localized-LXX flight at 1896, twenty to his return at 1876, and 430 to the Exodus at 1446. Later arm: the same Exodus at 1446, 430 to the schematic lesser Nexus at 1016, twenty to the 450-ledger endpoint at 996, and forty to the 490-ledger endpoint at 956. The sequence is forty, twenty, 430, 430, twenty, forty.

Download SVG source (ZIP) · Open PNG

BC coordinateFunctionActive setting
1936Second Cainan deathRestored regular Cainan; +60 Terah; minimum Sojourn
1896Jacob flight / service openingLocalized LXX −33 Jacob comparison
1876Jacob return / great NexusLocalized LXX −33 return; shared date with normal-MT Egypt entry, without identity of those events
1446ExodusPrimary textually derived fixed anchor
1016Direct Judges closure / sanctuary coordinateSchematic; distinct from historical Temple foundation in 966 BC
996Explicit 450-year ledger endpointSchematic endpoint
956Joshua-extended 490-year ledger endpointSchematic endpoint

The two outer sixty-year extensions surround the inner double-430:

60 + 430 + 430 + 60 = 980 = 490 + 490.

The 1896 and 1876 BC coordinates need particular care. They are Jacob’s flight/service opening and return in the localized LXX-derived −33 comparison. File 64 starts with the standard Jacob sequence 1929 → 1909 → 1859 BC, corresponding to flight, return after twenty years, and death after a further fifty. Uniformly translating those coordinates by −33 gives:

1896 → 1876 → 1826 BC = 20 + 50 = 70 years.

The translation preserves the lifespan intervals. It does not make the shorter-Sojourn Cainan variant and the localized Jacob variant one continuous ordinary biography. File 04 controls the localized shift; File 64 §§8.3–8.8 controls its use here.

Why the shared 1876 label is not a shared identity

Selected settingWhat 1876 BC identifiesJacob’s Egypt-entry date in that setting
Normal MT, full 430 years in EgyptJacob’s entry into Egypt1876 BC
Minimum/shorter SojournAbraham’s Call1661 BC
Localized −33 Jacob comparisonJacob’s return from Haran1843 BC

In the normal MT comparison, 1876 → 1446 = 430 measures the Egyptian sojourn. In the localized Jacob comparison, 1876 marks his return to Canaan. In the central palindrome it functions as the shared coordinate at which those explicitly different settings can be compared.

The second inner 430, 1446 → 1016, is the schematic Jephthah route. The two equal spans therefore have different evidential origins. Their equality is exact; it does not remove those distinctions.

Download the seven-node palindrome and state labels.

7. Two operations on the sixty-year intervals

The lower Cainan–Terah comparison provides the coordinates 1936 → 1876 → 1816 BC, separated by 60 + 60. These are selected death-state and shared-node positions: Cainan’s 1936 death uses +60 Terah; the 1816 Terah death is a different, unshifted minimum-Sojourn position. The row compares alternatives rather than one fixed genealogical branch.

File 64 §8.7 translates every member by the same amount, 860 years:

Figure 5 · Detailed study

Translation and reflection give different pairings

Both operations preserve the twin-sixty structure, but they send an input to different output dates.

1. Uniform translation · preserve order

Subtract 860 from each BC label

1936 BC− 860 ↓1076 BCCainan death → direct module opening
1876 BC− 860 ↓1016 BCGreat Nexus → lesser Nexus
1816 BC− 860 ↓956 BCTerah death → extended endpoint

1936 → 1876 → 1816 and 1076 → 1016 → 956 each contain 60 + 60 years.

2. Local complement · reverse order

R1446(b) = 2892 − b

1936 BClocal counterpart ↓956 BC
1876 BClocal counterpart ↓1016 BC
1816 BClocal counterpart ↓1076 BC
The operations agree only at the central pair hereBoth send 1876 to 1016, but their outer pairings differ. These are same-BC operations, distinct from formal BC–AD Mirror protocols.
Uniform translation subtracts 860 from every BC label. The local complement subtracts each label from 2892 and reverses the order. Neither operation here crosses into AD.

Sources: File 64 §8.7: uniform −860 translation · File 64 Appendix D.2: local complement R1446(b) · File 18: distinct Cainan and Terah death states.

Full table and explanation

Model and calculation details

The source rail 1936→1876→1816 has two sixty-year intervals. Subtracting 860 gives 1076→1016→956, preserving order. The local complement R1446(b)=2892−b pairs 1936 with 956, 1876 with 1016, and 1816 with 1076, reversing order. It is a local same-BC symmetry operation, not a repository-wide BC–AD Mirror protocol. The source nodes remain restored Cainan death, the shared great Nexus, and a Terah death state. The Judges rail superposes the direct and Joshua-extended routes without claiming repeated historical events.

Static image alternativeUniform translation by minus 860 maps 1936 to 1076, 1876 to 1016, and 1816 to 956 BC. A separate local complement around 1446, calculated as 2892 minus the BC label, maps 1936 to 956, 1876 to 1016, and 1816 to 1076 BC. The first preserves order; the second reverses it. Neither is a BC–AD Mirror calculation.

Download SVG source (ZIP) · Open PNG

Earlier coordinateUniform translationResult
1936 BC1936 − 8601076 BC
1876 BC1876 − 8601016 BC
1816 BC1816 − 860956 BC

The lower row preserves 60 + 60. The Judges calculations fill it through two different placements of the terminal module: 1076 → 1036 → 1016, under the direct route, and 1016 → 976 → 956, under the Joshua-extended route. The two modules are superposed for comparison; they are not added as two sets of historical events.

A reflection around the Exodus produces the same set of three lower coordinates, but pairs them differently:

1936 ↔ 956; 1876 ↔ 1016; 1816 ↔ 1076.

Uniform translation preserves the order of the three positions. The local reflection reverses it. For this selected row and these operators, both operations arrive at the same set of lower labels. Only the central pair is shared by both mappings. Keeping their arrows distinct is essential to understanding the diagram.

8. Keep the 430, 460, and 490 centers distinct

A repeated interval is not enough to identify a center. Each arrangement must be read from its own endpoints.

ArrangementCoordinates BCEqual armsActual center
Great / lesser Nexus1876 → 1446 → 1016430 + 430Exodus at 1446 BC
Cainan / Joshua / Nexus1936 → 1476 → 1016460 + 460Joshua birth at 1476 BC
Outer shell1936 → 1446 → 956490 + 490Exodus at 1446 BC

The 460-year comparison has a longer extension:

2396 → 1936 → 1476 → 1016 BC = 460 + 460 + 460 = 1380 years.

Its first segment is Cainan’s lifespan in the selected regular variant. The second leads to Joshua’s birth; the third leads to the schematic 1016 coordinate. The equal arms 1936 → 1476 → 1016 are centered on Joshua’s birth, thirty years before the Exodus.

That thirty-year separation explains how some neighboring partitions change. The corridor 1876 → 1016 = 860 divides at the Exodus as 430 + 430, but at Joshua’s birth as 400 + 460. No date has moved; the point of division has changed.

The triple-460 is a further relationship among declared coordinates. It does not change the regular Cainan insertion from 130 to 460, and it is not itself a second proof that the Exodus is the center of the 460-year pair.

9. The historical and schematic Temple dates

The historical Temple foundation remains 966 BC, with the adjacent 967 boundary retained under its stated reckoning. 1 Kings 6:1 (BSB) expresses the time after the Exodus as an ordinal year. The whole-year coordinate comparison used here is 1446 − 966 = 480; the subtraction is the model’s arithmetic, not a reformatted quotation of the verse.

The schematic sanctuary coordinate is 1016 BC. It belongs to the Judges–Kings reconciliation and does not replace the historical foundation. The distinction gives two routes from the normal MT Egypt-entry coordinate:

Route from 1876 BCComponentsEndpointTotal
Through the Exodus to the schematic sanctuary point430 + 4301016 BC860
Through the Exodus to the historical Temple430 + 480966 BC910

Their difference is 50 years. File 08 and File 64 §8.9 retain this historical/schematic distinction in the Kings ledgers.

Figure 6 · Detailed study

Two construction ledgers stay fifty years apart

The 7 + 13 construction pattern is displayed in schematic and historical-rounded whole-year coordinates.

Whole-year comparison lanes; not to scale.

Schematic construction

1016 BCTemple foundation7 years →
1009 BCTemple completed13 years →
996 BCRoyal house completed

Historical-rounded construction

966 BCTemple foundation7 years →
959 BCTemple completed13 years →
946 BCRoyal house completed

1016 − 966 = 1009 − 959 = 996 − 946 = 50

956 BC is an arithmetic midpoint, not a dated event966 → 956 → 946 = 10 + 10. This does not move the historical Temple foundation from 967/966 BC.
Corresponding nodes differ by fifty years: 1016→966, 1009→959, and 996→946. 1009 BC is a derived intermediate coordinate. The historical Temple reference remains 967/966 BC.

Sources: File 64 §§8.9–8.10: principal Judah +50 and construction rails · File 08: historical Kings / Temple and construction controls · 1 Kings 6:38: seven-year Temple construction (BSB) · 1 Kings 7:1: thirteen-year royal-house construction (BSB) · 1 Kings 9:10: twenty-year building field (BSB).

Full table and explanation

Model and calculation details

The schematic sequence is 1016→1009→996 BC; the historical-rounded comparison is 966→959→946 BC. The 1009 BC label is locally derived as 1016 − 7 (also 959 + 50), not a date printed in File 64. Each gives seven years for Temple construction followed by thirteen for the royal house, matching the twenty-year construction field. These are schematic or whole-year comparison coordinates, not a claim about precise months between all historical building milestones. The 956 BC Judges endpoint is also the arithmetic midpoint of 966 and 946; that observation does not establish a historical event at 956.

Static image alternativeSchematic construction lane: 1016 BC foundation, seven years to 1009 Temple completion, thirteen to 996 royal-house completion. Historical-rounded lane: 966, 959, and 946 BC with the same seven-plus-thirteen pattern. Each corresponding pair differs by fifty years. The historical foundation retains its 967/966 phase pair; 956 is only an arithmetic midpoint of 966 and 946.

Download SVG source (ZIP) · Open PNG

Construction: seven years and thirteen years

1 Kings 6:38 (BSB) gives seven years for the Temple’s construction; 1 Kings 7:1 (BSB) gives thirteen for Solomon’s house. 1 Kings 9:10 (BSB) supplies the twenty-year two-house summary. The resulting 7 + 13 = 20 comparison uses the repository’s whole-year construction display. It does not erase the more precise month-level Temple chronology.

The historical-rounded sequence is 966 → 959 → 946 BC. Its schematic counterpart, fifty years earlier at each position, is 1016 → 1009 → 996 BC. The closing 1016 → 996 segment of the 450-year Judges ledger thus matches the schematic twenty-year construction envelope.

Within the historical-rounded envelope 966 → 946, the coordinate 956 is also the arithmetic midpoint: 10 + 10. This limited observation can be retained. It dates no event at 956 and does not generate the right endpoint of the 980-year study; that endpoint has already been derived from 40 + 40 + 410.

10. Jacob and Solomon: two forms of 7 + 13

Jacob’s years in Haran provide a household-building comparison. Genesis 29:20 (BSB) states his first seven years of service for Rachel. The marriage sequence follows in Genesis 29:21–30, and Genesis 31:41 (BSB) summarizes his service as fourteen years for the two daughters and six for the flock.

The biblical summary is therefore 14 + 6 = 20. For the comparison with Solomon, the same twenty is repartitioned as 7 + 13, where the remaining thirteen means the second seven plus the six. It does not mean thirteen years of marriage service for Rachel, nor that Jacob waited another seven years before marrying her.

The standard Jacob sequence is 1929 → 1922 → 1909 BC: flight/service opening, the marriage field after the first seven, and return after the remaining thirteen. The localized −33 comparison gives 1896 → 1889 → 1876 BC.

Figure 7 · Detailed study

Two Jacob–construction comparisons of 930 years

Each panel compares corresponding positions in a 7 + 13 sequence. The two variant routes are alternatives.

The three columns represent opening, seven-year transition, and twenty-year closure.

Localized LXX −33 Jacob → historical-rounded construction

1896 BC− 930 ↓966 BCOpening / foundation
1889 BC− 930 ↓959 BCMarriage field / Temple completion
1876 BC− 930 ↓946 BCReturn / royal-house completion

Standard Jacob → Northern +33 construction comparison

1929 BC− 930 ↓999 BCOpening / foundation
1922 BC− 930 ↓992 BCMarriage field / Temple completion
1909 BC− 930 ↓979 BCReturn / royal-house completion
7 + 13 = 7 + (7 + 6)Jacob’s remaining thirteen years comprise seven further years for his wives and six for his flocks. The two ±33 comparisons are alternatives; do not stack them.
All six corresponding pairs are 930 years apart. Jacob’s remaining thirteen years are seven further years for his wives plus six for his flocks; they are not thirteen years of service for Rachel.

Sources: File 64 §8.10 and Appendix D.6A: the paired 930 rails · File 04: standard and localized-LXX Jacob states · File 08: construction and Northern comparison controls · Genesis 29:20: first seven years of service (BSB) · Genesis 31:41: fourteen years for wives, six for flocks (BSB).

Full table and explanation

Model and calculation details

The localized LXX −33 Jacob rail 1896/1889/1876 aligns by 930 years with the historical-rounded construction rail 966/959/946. The standard Jacob rail 1929/1922/1909 aligns by 930 with the Northern +33 comparison rail 999/992/979. The −33 on Jacob or the +33 on construction provides an alternative single-variant comparison, not cumulative adjustments to apply together. Intermediate marriage and construction labels are derived comparison coordinates, not new primary historical anchors. Numerical correspondence may support a typological reading but does not prove literary dependence.

Static image alternativeFirst panel: localized-LXX Jacob coordinates 1896, 1889, and 1876 BC correspond to historical-rounded construction coordinates 966, 959, and 946; each subtraction is 930. Second panel: standard Jacob 1929, 1922, and 1909 corresponds to Northern-plus-thirty-three construction 999, 992, and 979; again each subtraction is 930. Both sequences have intervals seven and thirteen. The thirteen remaining Jacob years comprise seven plus six.

Download SVG source (ZIP) · Open PNG

Each localized Jacob coordinate lies 930 years before the corresponding historical-rounded construction coordinate:

1896 − 966 = 930; 1889 − 959 = 930; 1876 − 946 = 930.

File 64 §8.10 preserves a parallel route. The standard Jacob sequence is compared with a Northern-Kingdom +33 construction variant, 999 → 992 → 979 BC. This yields the same three differences:

1929 − 999 = 930; 1922 − 992 = 930; 1909 − 979 = 930.

The +33 is a bounded royal-ledger comparison, distinguished from the principal Judah +50. It does not relocate the historical Temple to 999 BC. Conversely, the localized Jacob −33 translates Jacob’s coordinates. The two routes preserve 930 in parallel; the adjustments are not both applied to the same pair to obtain that result.

ComparisonPositionJacob BCConstruction BCSpan
Localized Jacob / historical-rounded constructionOpening1896966930
Localized Jacob / historical-rounded constructionAfter first seven1889959930
Localized Jacob / historical-rounded constructionAfter remaining thirteen1876946930
Standard Jacob / Northern +33 constructionOpening1929999930
Standard Jacob / Northern +33 constructionAfter first seven1922992930
Standard Jacob / Northern +33 constructionAfter remaining thirteen1909979930

The number 930 is Adam’s lifespan in Genesis 5:5 (BSB). Its presence permits an Adamic reading of the household and sanctuary comparison. Jacob’s naming of Bethel as the house of God in Genesis 28:17–22 (BSB) gives the sanctuary theme an actual narrative setting. Genesis 2:21–22 (BSB) describes Adam’s sleep and the formation of the woman; Genesis 28 shows Jacob asleep at the place he later calls the house of God, before the household-building sequence in Haran. The exact 930-year differences are arithmetic facts within the selected settings; the Adam–Jacob–Temple association is typological interpretation, not an independent way to derive the dates.

Download the construction comparison.

11. How this differs from the formal BC–AD Mirror

The 980-year arrangement is a local symmetry around the Exodus, entirely within BC chronology. It should be explained by its actual operation rather than by the visual appearance of a reflected timeline.

File 64 Appendix D.2 writes its local complement as:

R₁₄₄₆(x) = 2892 − x, where 2892 = 2 × 1446.

Here x is a BC label in the specified comparison. The three central pairs illustrate its use:

Radius from the ExodusEarlier BC labelLater BC labelLocal check
430187610161876 + 1016 = 2892
45018969961896 + 996 = 2892
49019369561936 + 956 = 2892

The formula describes equal distances from 1446 BC. It generates no independent historical identity for a calculated endpoint. It also differs from the uniform −860 translation shown earlier: one reverses order around a center, while the other shifts each selected date by the same amount.

OperationPurposeRuleExample / scope
Same-side BC subtractionMeasures a distance within BC chronologyEarlier BC label − later BC label1936 − 1446 = 490
Uniform BC translationMoves every selected coordinate by the same amount, preserving orderx − 8601936/1876/1816 → 1076/1016/956
Local Exodus-centered complementPairs selected BC coordinates across the center, reversing orderR₁₄₄₆(x) = 2892 − x1936 ↔ 956; 1876 ↔ 1016; 1816 ↔ 1076
Formal repository MirrorGenerates counterparts under declared cross-axis coordinate/display and phase rulesProtocol appropriate to the selected single-date or paired-seasonal stateNot the operation used for the BC-only 980-year construction
Civil BC–AD elapsed spanMeasures elapsed years after cross-axis endpoints have been specifiedBC + AD − 1Not applied to these BC-only differences

The repository’s formal Mirror concerns a different axis, the 1 BC / AD 1 boundary, and has its own target-generation rules. File 00 §3.9, File 09 Appendix A, and File 51b distinguish the pure Rounded integer reflection from the seasonal Tishri/Nisan operation. Single-date and paired-seasonal inputs must retain their own rules.

A further distinction separates an underlying signed Rounded coordinate from the way a Rounded date is displayed. Those conventions do not support one blanket rule for every BC label and every AD counterpart. The present article therefore supplies no AD counterpart for 1936 or 956: none is needed for this comparison.

Once ordinary civil BC and AD endpoints have been specified, their elapsed span uses BC + AD − 1, because civil dating has no year zero. Selecting counterpart dates and measuring an elapsed span are different operations. The minus-one correction belongs to the civil cross-axis span; it is not applied to 1936 − 1446, 1446 − 956, or any other BC-only subtraction here.

The local formula also must not be extended beyond its stated BC-label domain by treating a negative answer as an AD year. It is local audit notation, not a new universal Mirror protocol. The formal Mirror retains its wider canonical role; it simply does not supply the operation that establishes this 980-year pattern.

12. A bounded Flood, Noah, and Shem comparison

The original study belongs to a series on the Ark and Flood. File 64 §9A supplies a controlled connection that can be retained after the Judges calculations have established 1016 BC.

The normal MT Flood reference on this website remains Gear 2, 2458 BC. The present comparison explicitly selects Gear 1, 2456 BC, the Flood–Arphaxad comparison coordinate specified by the canonical three-Gear framework. It then opens a separate +60 propagated setting:

2456 + 60 = 2516 BC.

The unshifted and shifted spans to 1016 differ:

2456 − 1016 = 1440 = 4 × 360; 2516 − 1016 = 1500.

Figure 8 · Detailed study

Flood comparisons arrive at the same receiving date

The Judges argument supplies 1016 BC independently. These bounded Flood-Gear spans are corroborative.

Unshifted Gear 1: 2456 − 1016 = 1440 = 4 × 360

Gear-1 / Japheth Flood–Arphaxad rail.

Propagated +60 head: 2456 + 60 = 2516 BC

Noah partition · named +60 state

2516 BCPropagated Gear-1 head350 years →
2166 BCNoah death; shared Abraham-birth label1150 years →
1016 BCJudges receiving date

Shem partition · same +60 state

2516 BCSame propagated head500 years →
2016 BCShem death comparison1000 years →
1016 BCSame receiving date
350 + 1150 = 500 + 1000 = 1500These spans corroborate 1016 BC after the Judges derivation. A shared year label does not identify Noah and Abraham as one person or event.
The unshifted Gear-1 head gives 1440 years. Its explicitly propagated +60 comparison gives 1500, partitioned as either 350 + 1150 or 500 + 1000.

Sources: File 64 §9A and Appendix D.7: bounded Flood corroboration · File 18: Flood-Gear and propagated variant states · Genesis 9:28: Noah’s post-Flood 350 years (BSB) · Genesis 11:11: Shem’s remaining 500 years (BSB).

Full table and explanation

Model and calculation details

2456 is the unshifted Gear-1 / Japheth Flood–Arphaxad rail, not the 2458/2460 Gear-2/Gear-3 states. Propagating +60 gives the 2516 comparison head. Under that named state, Noah’s death is 2166, sharing the regular Abraham-birth label, while Shem’s death is 2016. The Noah and Abraham labels mark a comparison handover, not one historical identity. These spans confirm the receiving-coordinate role of 1016; they do not generate the Judges ledger or make the Flood evidence its primary proof.

Static image alternativeUnshifted Gear 1: 2456 minus 1016 equals 1440, or four times 360. Under the propagated plus-sixty state, the head is 2516 BC. The Noah comparison runs 2516 to 2166 to 1016 with intervals 350 and 1150. The Shem comparison runs 2516 to 2016 to 1016 with intervals 500 and 1000. Both total 1500. Noah’s 2166 is a conditional death coordinate sharing Abraham’s regular birth label.

Download SVG source (ZIP) · Open PNG

Under the named +60 setting, Noah’s death occupies 2166 BC, the same year-label as Abraham’s normal regular birth. Noah’s 350 post-Flood years, stated in Genesis 9:28 (BSB), partition the 1500-year comparison:

2516 → 2166 → 1016 BC = 350 + 1150.

The 1150 is the span from Abraham’s regular birth to the already established schematic coordinate. The shared 2166 label marks a comparison between selected states; it does not identify Noah and Abraham or silently propagate +60 into Abraham’s normal birth date.

Shem supplies another partition. His 500 years after fathering Arphaxad, stated in Genesis 11:11 (BSB), lead from the propagated Arphaxad boundary at 2516 to 2016 BC:

2516 → 2016 → 1016 BC = 500 + 1000.

The 500 is measured from the Arphaxad boundary in this selected comparison. It should not be relabeled as 500 years after every possible Flood-start date. File 11 and File 18 preserve the different Flood gears and event boundaries.

These relationships show additional numerical correspondences arriving at 1016. They are subordinate to its Judges derivation. They neither establish the 1016 coordinate independently nor require a 410/417-day Flood projection to prove the two 490-year arms.

Download the Flood comparison.

13. Numerical structure and theological reading

The central result remains compact. The selected Cainan endpoint lies 490 years before the Exodus; the extended Judges endpoint lies 490 years after it. Within that span, the palindrome 40–20–430–430–20–40 connects selected patriarchal coordinates with three declared ledger endpoints.

The broader comparisons give the geometry a narrative setting. Jacob’s service builds a household; Solomon’s twenty-year construction joins the Temple and royal house. Judges’ closing forty and twenty recur in a different form as First Samuel turns toward priesthood, the ark, and the monarchy. The Exodus stands between the ancestral promises and Israel’s life in the land.

That theological reading should be stated at the level the evidence supports. The durations, differences, and midpoint identities can be checked exactly. The selection and comparison of particular chronological settings is part of the model. Reading providential design in their convergence is a theological interpretation. The arithmetic alone does not establish authorial intention, historical independence of the outer endpoints, or a statistical probability against coincidence.

The 490 = 10 × 49 form can invite comparison with Leviticus 25:8’s seven weeks of years (BSB). It does not by itself establish ten historically observed jubilees on either side of the Exodus. The pattern is most useful when its numerical precision and its interpretive limits remain visible together.

14. Sources and downloadable tables

The controlling sources are File 64, especially §§2–6, 8.3–8.10, 9.1–9.2, 9A and Appendices A/D; File 18 for regular dates and variant settings; File 06 for the Judges bridge; File 08 for Kings and the historical Temple; and File 01 for normal and adjusted Abraham dates. Files 04 and 11 control the localized Jacob and Flood comparisons. Files 00, 09 and 51b control the Mirror distinctions.

Download the combined data file (ZIP), central endpoints, Cainan variants, complete Judges ledger, three routes, terminal modules, palindrome, centers, construction pairs, method comparison, and Flood comparison. The person-and-event figure index (ZIP) links the diagrams to their people, events, passages, and supporting sections.

For a shorter entry point, return to the illustrated introduction or its supporting tables and notes.

Scripture quotations: Berean Standard Bible (BSB), public domain.
Brenton’s English Septuagint is identified separately for its Genesis 11 reading; see edition information.