Skip to content

Ussher chronology

James Ussher’s seventeenth-century biblical chronology dating creation and world history through a harmonized literal reading of scripture and classical sources.

Version
v1 · 2026-09-08 · History
Domain-specific #
7376
Origin domain
history of chronology
Subdomain
history of chronology

Core Idea

It is a historical scholarly system rather than a modern scientific timescale, different editions and calendars can shift displayed dates and association with current young-Earth creationism should not erase its early-modern textual methods. Genealogies reign lengths synchronisms and external chronologies are aligned into one continuous sequence, anchored to calendrical and astronomical assumptions to assign absolute dates to biblical events. The abstraction is therefore identified by a declared carrier, a transformation or constraint over that carrier, and an invariant that tells an analyst whether the named structure is genuinely present.

Scope of Application

Ussher chronology belongs to history of chronology and is useful where the analyst can specify the typed history of chronology carrier, including objects, relations, parameters, conventions, evidence, boundaries, and comparison targets, then evaluate the author work and publication date, source corpus of Old Testament and other biblical texts, genealogies reigns and synchronisms, classical and Near Eastern historical sources, calendar chronology and textual-version assumptions, anchor events and calculation rules, dated creation and subsequent events, uncertainty and variant editions and historical reception and scientific supersession are explicit.

Clarity

The abstraction clarifies a crowded vocabulary by making the author work and publication date, source corpus of Old Testament and other biblical texts, genealogies reigns and synchronisms, classical and Near Eastern historical sources, calendar chronology and textual-version assumptions, anchor events and calculation rules, dated creation and subsequent events, uncertainty and variant editions and historical reception and scientific supersession are explicit the center of the account.

Manages Complexity

Without the abstraction, an analyst must reason directly over many local details: the carrier roles, admissibility assumptions, competing conventions, derived invariants, boundary cases, and proof or validation obligations specific to Ussher chronology. Ussher chronology compresses them into the roles in the structural signature. That compression permits comparison across instances without erasing the variables that determine validity. It also exposes which details may be varied safely and which are constitutive.

Abstract Reasoning

  1. Identify the carrier. State what the elements, states, objects, or observations are: the typed history of chronology carrier, including objects, relations, parameters, conventions, evidence, boundaries, and comparison targets. Reject examples whose alleged carrier belongs to a different problem. 2. Lock the constitutive rule. Express the author work and publication date, source corpus of Old Testament and other biblical texts, genealogies reigns and synchronisms, classical and Near Eastern historical sources, calendar chronology and textual-version assumptions, anchor events and calculation rules, dated creation and subsequent events, uncertainty and variant editions and historical reception and scientific supersession are explicit independently of one notation or implementation.

Knowledge Transfer

Knowledge transfers strongly among subfields of history of chronology because they reuse the typed history of chronology carrier, including objects, relations, parameters, conventions, evidence, boundaries, and comparison targets, Genealogies reign lengths synchronisms and external chronologies are aligned into one continuous sequence, anchored to calendrical and astronomical assumptions to assign absolute dates to biblical events., and type the carrier, state every parameter and convention in the definition, test that the author work and publication date, source corpus of Old Testament and other biblical texts, genealogies reigns and synchronisms, classical and Near Eastern historical sources, calendar chronology and textual-version assumptions, anchor events and calculation rules, dated creation and subsequent events, uncertainty and variant editions and historical reception and scientific supersession are explicit, compare the nearest accepted identity, and report counterexamples, uncertainty, and limiting cases.

Relationships to Other Abstractions

Local relationship map for Ussher chronologyParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.Ussher chronologyDOMAINPrime abstraction: Temporal Dynamics — is a kind ofTemporalDynamicsPRIME

Current abstraction Ussher chronology Domain-specific

Parents (1) — more general patterns this builds on

  • Ussher chronology is a kind of Temporal Dynamics Prime

    The proposed strict upward parent is prime:temporal_dynamics.

Hierarchy path (1) — routes to 1 parentless root

Neighborhood in Abstraction Space

Ussher chronology sits in a sparse region of the domain-specific corpus (65th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.

Family — Cultural Symbols & Interpretive Schemes (10 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-09-08