When Biblical Time Spans Meet: Supporting Tables and Source Notes

This appendix accompanies “When Biblical Time Spans Meet: The Key of 23 in Action”. It records the exact spans and endpoint choices behind the introductory diagrams. The current canonical Markdown files govern the calculations; the detailed companion develops the fuller discussion under those controls.

The dates below have different functions. Regular dates belong to the selected chronology. Variant dates require stated additions. Schematic dates mark positions in an assigned genealogical arrangement. Generated dates are outputs of an expansion. A shared number does not erase those distinctions.

A. Complete endpoint ledger

Each expansion row identifies the original pair, the endpoint held fixed, the ratio, and the output. All lengths are years. “Backward” means toward an earlier date, which has a larger BC number.

Original spanSettingFixed endpoint / directionExact expansionGenerated endpoint / status
4114 → 1446 BCRegular normal MT; no Terah/Cainan additionsExodus 1446 BC; backward2668 × 25/23 = 29004346 BC; generated comparison head
4304 → 1406 BCRegular MT-based variant: +60 Terah, +130 restored second CainanConquest 1406 BC; backward2898 × 70/69 = 29404346 BC; generated comparison head
4836 → 6 BCSchematic Luke-side 70-year positionsBirth hinge 6 BC; backward4830 × 70/69 = 49004906 BC; Jared opening boundary in selected model
4836 → 6 BCSchematic Luke-side 70-year positionsBirth hinge 6 BC; backward4830 × 25/23 = 52505256 BC; Adam opening boundary in selected model
4836 → 6 BCSame schematic input; earlier endpoint heldEnoch position 4836 BC; forward4830 × 70/69 = 4900AD 65; schematic Christ-generation closing boundary

Download the endpoint ledger (CSV) · All study data with source hashes (JSON) (ZIP).

Rows using the same input are alternative applications. In particular, the two expansions of 4830 begin separately with the unexpanded span. No row authorizes multiplying their outputs by the other ratio.

B. The two paths to 4346 BC

The controlling calculation is File 22 §§9.1–9.4, supported by the regular chronology and variant definitions in File 18 §§1.6 and 2.1.2. The normal Creation endpoint is 4114 BC; the Exodus and Conquest anchors are 1446 BC and 1406 BC. Here 4114 BC is the completed Creation endpoint. Adam’s Year-6 coordinate, 4116 BC, is a distinct node and is not substituted into either input.

Path / settingsOriginal spanExpansionAfter expansionShared result
Standard MT path; Normal regular MT; standard/full Egypt Sojourn setting4114 − 1446 = 26682668 × 25/23 = 29002900 + 40 = 29404346 → 1406 BC = 2940
Variant path; +60 Terah and +130 regular restored second Cainan4304 − 1406 = 28982898 × 70/69 = 2940No further extension4346 → 1406 BC = 2940

Download both paths (CSV) · Return to Figure 2.

There are two different increments: 2900 − 2668 = 232 and 2940 − 2898 = 42. The fact that both paths reach 4346 BC does not mean that their original lengths or their increases were equal.

The first path stops its multiplication at the Exodus. Its subsequent 40-year extension to the Conquest remains unscaled:

(4114 − 1446) × 25/23 + 40 = 2940

The second path expands the complete variant Creation-to-Conquest span:

(4304 − 1406) × 70/69 = 2940

Both yield 1406 + 2940 = 4346 BC. File 22 calls this generated head “Super-Creation.” The term identifies an expanded comparison coordinate; it does not establish an additional historical Creation event.

C. What the +60 and +130 additions mean

The first path uses the normal regular MT setting, with Creation at 4114 BC. The second opens two optional adjustments together:

ComponentYearsRole in this example
Normal regular MT Creation4114 BCStarting chronology; retained in the first path
Terah adjustment+60Optional older placement of the upstream genealogy
Restored second Cainan+130Regular begetting-age contribution in the restored-Cainan variant
Variant Creation4304 BCInput for the second path only

The underlying distinction matters. Genesis 11:10–26 in the BSB, representing the MT sequence here, proceeds from Arphaxad to Shelah without a second Cainan. Luke 3:35–36, BSB, includes Cainan between them. The restored regular chronology uses the 130-year input in Brenton’s English Septuagint, Genesis 11, as controlled by File 18 §1.6.

This selective restoration does not turn the whole resulting chronology into an unmodified LXX chronology. Nor does it introduce the cumulative Cainan lifespan of 460 years. The present calculation is explicitly 4114 + 60 + 130. No Samaritan Pentateuch (SP) chronology is being calculated in these examples.

The Terah option compares a 70-year begetting setting with a 130-year setting. The latter harmonizes Terah’s 205-year life in Genesis 11:32, BSB, Abram’s departure at 75 in Genesis 12:4, BSB, and the departure after his father’s death in Acts 7:4, BSB: 205 − 75 = 130, and 130 − 70 = 60. Genesis 11:26 names Terah’s sons together; the 130-year placement is a harmonized chronological reading, not an age stated directly for Abram’s birth in that verse. File 18 §§1.1 and 1.3.1 controls the optional +60 setting and its upstream scope. It remains explicit beside 4304 BC here.

D. The 4830-year example and its named boundaries

These are boundaries of the selected 70-year genealogical display, measured from the fixed 6 BC hinge. They are not ordinary birth dates. Files 43 §3.4, 46 §4.2 and 54 §6 agree on the coordinates used here.

Schematic boundaryBC coordinateOperationSpan to 6 BC70-year unitsGain
Enoch opening4836Original input4830690
Jared opening49064830 × 70/6949007070
Adam opening52564830 × 25/23525075420

Download the boundary table (CSV) · Return to Figure 3.

The input 4830 = 69 × 70 = 23 × 210 supports both exact divisions:

4830 × 70/69 = 4900
4830 × 25/23 = 5250

File 46 calls 4830 a solar-span input. It should not be relabeled as 4830 Enochian 364-day years. The ratios are exact operators in the model; physical calendar comparisons used to explain them elsewhere do not make them exact measurements of the astronomical year.

The displayed interval from Enoch’s position to the hinge contains 69 assigned 70-year units. The earlier Jared boundary adds one unit; the Adam boundary adds six. In Scripture, their relationships occur in Genesis 5:18–24, BSB and Luke 3:37–38, BSB. Those passages identify the people and relationships; the BC coordinates come from the specified numerical model.

E. The same length can have different placements

File 46 supplies both applications of 4830 × 70/69 = 4900. They agree in length while holding opposite ends of the original span.

Held endpointDirectionResulting placementElapsed-year checkModel meaning
Later: 6 BCBackward4906 BC → 6 BC4906 − 6 = 4900Jared opening reached
Earlier: 4836 BCForward4836 BC → AD 654836 + 65 − 1 = 4900Christ-generation closing boundary reached

Download the anchor comparison (CSV) · Return to Figure 4.

For the forward application, 4836 + 65 − 1 = 4900. The same no-year-zero rule gives 6 + 65 − 1 = 70 for the final schematic generation. AD 65 closes that assigned block; it is not a death date for Christ.

Crossing the era boundary is not, by itself, a Mirror operation. A formal reflection requires a separately specified coordinate rule. Here the operation is expansion followed by placement from a fixed endpoint. File 00 §§3.1 and 3.9 supplies the broader distinction.

F. Names, intervals and assigned blocks

The combined-span example below uses the particular counting state retained by File 43. An inventory of 76 figures has 75 intervals between its first and last names. Assigning one block to each figure instead gives 76 blocks. Both counts have a use, but they answer different questions.

Counting stateCounted objectUnits × 70YearsInput to 8050?
Luke intervalsIntervals between 76 figures in the active source inventory75 × 705250Included
Luke names-spanOne assigned block per figure in the same inventory76 × 705320Excluded
Matthew birth-hinge spanIntervals in the undoubled 41-figure arrangement40 × 702800Included
Matthew carrier spanOne assigned block per figure in that arrangement41 × 702870Excluded

Download the counting states (CSV).

The 76-name Luke inventory is the active source-model selection, not a statement that every printed edition of Luke contains that same count. The BSB’s wording in Luke 3:33 includes Admin and Arni. The model’s single Ram entry must therefore be distinguished from the BSB’s Admin and Arni when counting the genealogy. Counting Jesus through Adam in this BSB edition gives 77 human figures; including God gives 78 entries. The model’s single Ram selection gives 76 human figures. Scripture quotations retain the BSB wording; no names have been silently changed to fit the model.

Likewise, Matthew’s 40-interval input belongs to the undoubled 41-figure arrangement used here. Matthew 1:17, BSB, states the three groups of fourteen, while the treatment of their shared boundaries requires its own counting convention. File 69 also analyzes a 42-slot Jeconiah-overlap arrangement. That later slot attribution does not replace the File 43 branch used for this calculation. File 43 §§2–5 · File 69’s count and boundary controls.

G. A combined span: 8050 becomes 8750

File 43 combines Luke’s 75 intervals with Matthew’s 40 intervals, assigning 70 years to each:

5250 + 2800 = 8050
8050 × 25/23 = 8750
8750 − 8050 = 700 = 10 × 70

Figure 5 · The Key of 23 in Action

Combining two genealogical spans

Luke’s interval count and Matthew’s birth-hinge span supply the locked inputs.

Luke intervals75 × 70 = 5250

Intervals between names.

Matthew birth hinge40 × 70 = 2800

The specified birth-hinge span.

5250 + 2800 = 8050

8050 × 25/23 = 8750
8750 − 8050 = 700

Selected counts: Luke’s Ram-based 76-figure model; Matthew’s undoubled 41-figure arrangement. These are model counts, not an unmodified BSB inventory.

A duration comparisonDo not assign a date endpoint without a separate anchored calculation. “MirrorVolume” is this source’s span-provenance label, not a formal Mirror operation.

Keep the inputs distinct: Luke’s 5320 names-span and Matthew’s 2870 carrier-span do not replace 5250 and 2800 here.

5250 + 2800 = 8050; 8050 × 25/23 = 8750. The increase is 700 years. This diagram compares durations.

Sources: File 43 §5: MirrorVolume 8050 and expansion 8750 · Counting inventory: names, intervals and assigned blocks.

Full table and explanation · Introductory article

Model and calculation details

File 43 distinguishes Luke’s 75 intervals at 70 years each, 5250, from a 76-name span of 5320. It also distinguishes Matthew’s birth-hinge 40 × 70 = 2800 from the carrier 41 × 70 = 2870. Only 5250 + 2800 enters the source’s MirrorVolume 8050. The 25/23 expansion gives 8750 and an increment 700. The terminology MirrorVolume names span provenance; it does not supply a formal Mirror-coordinate operation. No dated output endpoint is assigned in this figure. The count selection uses Luke’s Ram-based 76-figure model and Matthew’s undoubled 41-figure arrangement. The Luke inventory is not an unmodified count of the BSB edition.

Static image alternativeLuke’s 75 schematic intervals times 70 give 5250 years. Matthew’s 40-unit birth-hinge span times 70 gives 2800. Adding them gives 8050; multiplying 8050 by 25/23 gives 8750, an increase of 700. These are duration inputs and outputs with no date endpoint or Mirror reflection. The selected model uses Luke’s Ram-based 76-figure model and Matthew’s undoubled 41-figure arrangement, rather than an unmodified BSB count.

Download SVG source (ZIP) · Open PNG

The 700 is the generated increase. It is not an independently supplied third input. Nor may 5320 replace 5250, or 2870 replace 2800, merely because those other counts also occur in the genealogical discussion.

No fixed endpoint is assigned to this addition and expansion. It therefore establishes a duration relationship, not a new date. File 43’s technical name “MirrorVolume” labels the provenance of the combined span; it does not activate coordinate reflection, the formal BC–AD Mirror, or digit reversal. Its associated theological interpretation remains distinct from the exact arithmetic. File 43 §5.

H. Source boundaries and omitted claims

The introductory selection keeps the calculations that can be displayed with their source settings intact. The detailed Strategic Overlaps study develops the fuller set of examples with their source settings and qualifications.

One significant boundary concerns 6900 → 7000 or 7500. Current File 22 §7.10 treats 6900 as the composite 4600 + 2300 in a restored-Cainan birth-transfer construction. That scalar relationship should not be redrawn as an ordinary Jared-to-Shem dated span using the legacy endpoints. Its component settings require their own explanation, so it is outside this introduction.

More generally, a divisible span does not authorize choosing any convenient ratio, anchor or textual variant. Each comparison needs its stated source setting. Numerical agreement can support a structural interpretation, but no statistical test of chance or proof of ancient authorial intention is supplied by these examples.

I. Person and event figure index

The index links each person or event to the relevant diagram and table. A Scripture link supplies narrative or genealogical context; it does not claim that the passage gives the calculated BC position.

Person / eventFigure linksScripture contextClassification / table
CreationFigure 1; Figure 2Genesis 1:1, BSBCompleted Creation endpoint in the regular MT chronology; Figures 1 and 2; table 1, table 2
ExodusFigure 1; Figure 2Exodus 12:41, BSBFixed 1446 BC chronology anchor; table 1, table 2
Wilderness periodFigure 2Numbers 14:33–34, BSBBiblical 40-year wilderness duration added without scaling in Figure 2; not the generated 4346 BC head; table 2
Conquest / Jordan crossingFigure 2Joshua 4:19, BSBFixed 1406 BC chronology anchor; table 2
TerahFigure 2Genesis 11:26–32, BSBOptional +60 setting in Figure 2; table 2
Second CainanFigure 2Luke 3:35–36, BSBRestored regular +130 setting in Figure 2; table 2
Generated 4346 BC headFigure 1; Figure 2Calculated boundary; no separate narrative eventCalculated comparison coordinate; no new historical event; table 1, table 2
EnochFigure 3; Figure 4Genesis 5:21–24, BSBSchematic 4836 BC position in Figures 3 and 4; table 3, table 4
JaredFigure 3; Figure 4Genesis 5:18–20, BSBSchematic 4906 BC position in Figures 3 and 4; table 3, table 4
Adam in Luke’s genealogyFigure 3Luke 3:38, BSBSchematic 5256 BC opening boundary in Figure 3; table 3
Christ’s model birth hingeFigure 3; Figure 4Luke 3:23, BSB6 BC retained as the selected model hinge; table 3, table 4
AD 65 generation boundaryFigure 4Calculated boundary; no separate narrative eventSchematic end of the assigned Christ-generation block; not a death date; table 4
Luke’s genealogyFigure 5Luke 3:23–38, BSBSelected 76-figure / 75-interval model; BSB inventory differs; table 5
Matthew’s genealogyFigure 5Matthew 1:1–17, BSBUndoubled 41-figure / 40-interval model; table 5

Download the complete figure index (JSON) (ZIP).

J. Sources and downloads

SourceFunction in this study
File 00Exact ratios, fixed-endpoint method and distinction from formal Mirror
File 18Regular dates and the +60 Terah / +130 regular Cainan settings
File 22 §§9.1–9.4Two paths converging on 4346 BC; sixfold 490 interpretation
File 43 §§2–5Schematic genealogy, counted units and 8050 → 8750
File 46 §§2.2 and 4.2Alternative placement and expansion of 4830
File 54 §6Corroborating Jared, Enoch and Adam boundaries
File 69Later count-state controls preserving the selected File 43 relationships

The publication package preserves full canonical captures, original source receipts, the complete official BSB text, relevant chapter captures, editable figures, machine-readable tables and the editorial record. Download all calculation data (JSON) (ZIP).

Scripture quotations: Berean Standard Bible (BSB), public domain.
Scripture references use the Berean Standard Bible (BSB), public domain, except where Brenton’s English Septuagint is explicitly identified. Brenton’s 1851 English Septuagint is public domain. No NET Scripture or translators’ notes are reproduced.