Stratigraphic Time Ordering Inference

Reconstruct what happened when by treating preserved layers as ordered evidence, while checking for missing, mixed, inverted, or disturbed strata before making causal claims.

Version

v1 · 2026-08-24 · History

Solution archetype #

1018

Problem family

Identity, Provenance & Integrity Failure

Problem subfamily

Temporal Record Lineage & Reproducibility

Essence

Reconstruct what happened when by treating preserved layers as ordered evidence, while checking for missing, mixed, inverted, or disturbed strata before making causal claims.

Stratigraphic Time-Ordering Inference is the pattern of turning a layered record into a defensible history. It is useful when a system, site, archive, codebase, sediment sequence, or institutional process has accumulated in layers and the original events are no longer directly observable. The archetype asks the interpreter to read layer order, boundary transitions, marker correlations, and disturbance evidence before making claims about chronology or causation.

The central caution is that a layer is evidence, not a complete story. A layer can be missing, mixed, inverted, overwritten, compacted, eroded, rebased, redacted, or selectively preserved. The archetype therefore combines ordering logic with uncertainty discipline.

Compression statement

This archetype converts layered accumulation into historical inference. It defines the layer-bearing medium, detects boundaries between strata, applies a relative-order rule, looks for discontinuities and disturbance, correlates marker features across layer sequences, anchors relative order where possible, and records uncertainty so a plausible sequence of events can be reconstructed without pretending that every layer is complete, pure, or causal.

Canonical formula: sequentially deposited layers + interpretable boundaries + relative-order rule + disturbance audit + correlation anchors -> defensible chronology and causal-history reconstruction

When This Archetype Applies

Complete catalog groundingAt least one sufficient condition set is fully represented by existing primes or domain-specific abstractions.

Diagnostic problem

A system contains accumulated layers, traces, versions, deposits, or records, but the events that produced them are no longer directly observable. The interpreter needs a defensible chronology and causal history without confusing layer order with complete, undisturbed, or self-explanatory evidence.

Applicability expression5 distinct conditions

Layered ordered evidenceandDecision-relevant chronologyandUnobservable original processandPotentially disturbed orderingandCross-record chronology alignment

Algebraic1∧2∧3∧4∧5

groundedpartly groundedopen

5 conditions, all required.

5Required in every casenumbered 1–5

These hold no matter which pattern applies.

1

Layered ordered evidence · grounded

Evidence is arranged in layers, strata, versions, ordered deposits, stacked records, or sequential traces. more

primeGeometric Chronology— Read temporal order from the spatial or geometric structure a sequence of events leaves in a preserving medium.

and — also required

2

Decision-relevant chronology · grounded

The historical sequence matters for explanation, accountability, diagnosis, dating, reconstruction, or future action. more

primeGeometric Chronology— Read temporal order from the spatial or geometric structure a sequence of events leaves in a preserving medium.

and — also required

3

Unobservable original process · grounded

Direct observation of the original process is unavailable, incomplete, expensive, or impossible. more

primeGeometric Chronology— Read temporal order from the spatial or geometric structure a sequence of events leaves in a preserving medium.

and — also required

4

Potentially disturbed ordering · grounded

Layer position plausibly encodes order, but disturbance, missing intervals, mixing, editing, erosion, or reworking may have occurred. more

primeGeometric Chronology— Read temporal order from the spatial or geometric structure a sequence of events leaves in a preserving medium.

and — also required

5

Cross-record chronology alignment · grounded

Multiple layer sequences, sites, repositories, or logs need to be correlated into a common chronology. more

primeGeometric Chronology— Read temporal order from the spatial or geometric structure a sequence of events leaves in a preserving medium.

Other requirements and context (1)

Why these sit outside the expression

Supporting context — it may accompany or help interpret the situation, but it is not a load-bearing condition in a sufficient diagnostic set.

• Supporting contextCausal interpretation depends on distinguishing earlier conditions, transition events, later overlays, and later reinterpretations.

Coverage

5 of 5 conditions grounded.

Read the methodology · Download the trigger-logic data

Core problem

The structural problem is not merely that history exists. The problem is that history is preserved indirectly in strata. An analyst sees accumulated deposits, records, versions, revisions, or traces, but needs to know what happened first, what came later, what is missing, and which transitions might explain present conditions.

This comes up in archaeology, geology, digital incident response, environmental forensics, archive interpretation, organizational policy history, and any setting where the visible present is a stack of earlier deposits and later overlays.

Intervention logic

The archetype proceeds through six moves:

1. Define the layer-bearing medium.
2. Identify the boundaries between layers.
3. Apply a domain-appropriate relative-ordering rule.
4. Audit disturbance, discontinuity, and missing intervals.
5. Correlate markers across separate sequences.
6. Record the chronology with confidence, alternatives, and unresolved gaps.

Only after these moves should the reconstructed sequence be used for causal interpretation. The pattern supports causal reasoning, but it does not allow temporal order alone to substitute for causal evidence.

Key components

Stratigraphic Time-Ordering Inference turns a layered record — sediment, archives, commit histories, policy versions — into a defensible history without pretending that layer order is the same as complete or causal evidence. The reconstruction is built up in stages. The Layer-Bearing Medium Definition comes first because different media form and fail differently: a sediment core, a git commit, and an archived memo can all be ordered, but their disturbance rules diverge. The Layer Boundary Identification then locates the recognizable contacts, transitions, timestamps, or version edges on which any sequence claim depends, since weak boundaries produce weak claims. With boundaries fixed, the Relative Ordering Rule makes the before/after logic explicit and domain-appropriate — superposition in deposits, parent-before-child in version histories — stated rather than silently assumed.

The remaining components supply the discipline that separates this archetype from naive superposition. The Disturbance and Discontinuity Audit is the main safeguard, checking for mixing, inversion, erosion, deletion, rebasing, or selective preservation that would break a literal reading of order. When several partial sequences must be aligned, the Cross-Layer Correlation Anchor uses marker horizons, tags, fossils, or shared anomalies to connect them into a common chronology. Finally, the Chronology Uncertainty Record keeps confidence levels, alternatives, gaps, and unresolved contradictions visible, preserving auditability and preventing the reconstruction from hardening into an overconfident story. Only after these moves should the inferred sequence inform causal interpretation, and even then temporal precedence alone is never treated as proof of causation.

Component	Description
Layer-Bearing Medium Definition ↗	The interpreter first identifies the medium that preserves sequence: soil layers, sediment cores, artifact deposits, archived policies, commit histories, log streams, case files, or institutional records. The medium matters because different media form and fail differently. A sediment layer, a git commit, and an archived memo can all be ordered, but the rules for disturbance are different.
Layer Boundary Identification ↗	A chronology depends on recognizable boundaries. These might be soil contacts, material transitions, cuts and fills, ash layers, timestamps, record separators, branch edges, release tags, migration records, or document versions. Weak boundaries produce weak sequence claims.
Relative Ordering Rule ↗	Each domain needs an explicit rule for translating observed layer relations into before/after claims. In deposits, lower layers may usually be older than upper layers. In version histories, parent commits precede children. In archives, earlier retained versions may precede later overlays. The rule must be stated, not assumed.
Disturbance and Discontinuity Audit ↗	This is the main safeguard. The interpreter checks for mixing, inversion, erosion, missing layers, contamination, post-depositional alteration, deletion, overwriting, rebasing, backfilled logs, branch merges, or other processes that break naive order reading. A chronology without a disturbance audit is fragile.
Cross-Layer Correlation Anchor ↗	When multiple sequences must be aligned, the archetype uses marker horizons, tags, fossils, chemical signatures, release identifiers, shared anomalies, or known external events. These anchors help connect partial histories into a common sequence.
Chronology Uncertainty Record ↗	The output should record confidence, alternatives, gaps, and unresolved contradictions. This preserves auditability and prevents the reconstruction from hardening into an overconfident story.

Common mechanisms

Stratigraphic section diagrams make spatial layer relations visible. Core sample logs preserve depth sequence and sampling metadata. Marker-horizon correlation aligns separate sequences. Version-history commit graphs reconstruct digital order. Layer disturbance audit checklists force review of missing or mixed strata. Relative chronology matrices store pairwise before/after/unknown relations so contradictions can be detected.

Mechanisms should be selected by medium. Physical deposits need exposure, sampling, and section representation. Digital histories need graph, branch, deployment, and migration tools. Archives need provenance, document lineage, and preservation-bias review. High-stakes contexts need custody, safety, and independent review.

Parameter dimensions

Important parameters include layer granularity, sampling resolution, boundary clarity, expected disturbance rate, dating precision, correlation strength, preservation bias, number of sequences being aligned, and consequence of overclaiming. A low-stakes organizational history may tolerate a rough relative chronology; a forensic or safety-critical investigation may require independent anchors and more formal uncertainty handling.

Invariants to preserve

The inferred order should remain traceable to observed layer relations. Relative order should not be reported as exact date or duration unless independently anchored. Gaps and disturbances should remain visible. Domain-specific layer formation rules should be respected. Evidence provenance should be maintained. Another interpreter should be able to inspect why the sequence was inferred.

Expected outcomes

When successful, this archetype produces a defensible relative chronology, reveals missing or disturbed intervals, improves causal-history reasoning, distinguishes earlier foundations from later overlays, and gives later reviewers a documented basis for revising the reconstruction when new evidence appears.

Failure modes

The most common failure is naive superposition: assuming visible layer order always equals true chronological order. Other failures include treating sequence as causation, ignoring missing layers, over-aligning weak markers across sites, sampling at the wrong resolution, and reading old layers through present-day categories.

The main safeguards are disturbance audits, independent anchors, explicit separation of sequence from causality, preservation-bias assessment, and uncertainty records.

Neighbor distinctions

The closest neighbor is Layered Record Accumulation. That archetype concerns preserving successive layers so history remains interpretable. Stratigraphic Time-Ordering Inference concerns reading existing layers to reconstruct chronology and causal history. The two are complementary and merge-sensitive.

It is also distinct from Layered Abstraction, which designs conceptual or functional strata; Accumulation Compaction, which compresses accumulated history; Traceability Linking, which connects records and outcomes; and Versioned Evolution, which manages explicit artifact versions. These neighbors may supply mechanisms or inputs, but they do not replace the layer-order inference pattern.

Examples

In archaeology, excavators distinguish an original occupation layer from a later fill layer and a modern utility trench. In geology, analysts correlate ash layers and fossils across outcrops to reconstruct a regional sequence. In software, engineers use commit graphs and deployment logs to determine whether a rollback restored code while leaving a later schema layer intact. In environmental forensics, sediment layers help determine whether a pollutant pulse preceded or followed a flood deposit. In organizational history, archived policy versions reveal that a current rule is a later overlay on an older exception process.

Non-examples

Choosing a layered architecture for a new system is not this archetype. Deleting old logs after summarizing them is not this archetype. Reading a single trusted timestamp is not this archetype. Inferring causation merely because one layer appears below another is a misuse of the archetype, not a valid instance.

Review note

This draft is recommended for use with human review. The main review issue is whether the encyclopedia should keep this as a standalone layer-based inference archetype or consolidate it as a major variant under Layered Record Accumulation.

Common Mechanisms

6 documented mechanisms across 4 implementation forms.

The grouping reflects forms represented among the mechanisms currently documented for this archetype; an absent form is not necessarily an impossible implementation.

Analysis, Modeling & Optimization · 3 mechanisms

• Marker-Horizon Correlation — Aligns separate sequences into one timeline using a distinctive shared layer, and pins that timeline to the calendar when the marker is independently dated.
• Relative Chronology Matrix — Stores every pairwise before/after/unknown relation with its evidence so contradictions can be detected and candidate causal transitions flagged.
• Version-History Commit Graph — Reconstructs the true sequence of a codebase from parent-child commit edges — not timestamps — and surfaces rebases and rewrites that disturbed it.

Assessment, Review & Assurance · 1 mechanism

• Layer Disturbance Audit Checklist — Forces review of the disturbances — mixing, gaps, deletion, backfill — that could invalidate a naive layer-order interpretation.

Record, Log & Register · 1 mechanism

• Core Sample Logging Protocol — Records depth, material transitions, inclusions, and sampling metadata for core-based sequences before any order or age is inferred.

Representation, Specification & Plan · 1 mechanism

• Stratigraphic Section Diagram — A to-scale drawing of one exposed profile that renders each layer, its contacts, and its superposition order directly readable off the page.

Related Abstractions

Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.

Built directly on (1)

• Layered Accumulation: Sequential time-ordered deposition in which each new layer rests atop the prior ones, so the position of a layer encodes when it formed and the stack becomes a readable record of history.

Also references 15 related abstractions

• Causality: Cause-effect relationships.
• Collective Memory: Shared narratives.
• Continuity: Smooth change without jumps.
• Continuity vs. Rupture: Gradual vs abrupt change.
• Data Integrity: Accuracy and consistency preserved.
• Deep Time: Extremely long timescales.
• Order: Defines ranking or sequencing relationships.
• Primary vs. Secondary Sources: Firsthand vs analysis.
• Representation: Model complex ideas.
• State and State Transition: Captures system condition and evolution.

▸ Show 5 more

Variants

Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.

Archaeological Stratigraphy Reading · domain variant · recognized

A domain variant that reconstructs human occupation, construction, burial, and disturbance sequence from cultural layers and features.

• Distinct from parent: The parent is cross-domain; this variant uses archaeological field concepts and cultural-context constraints.
• Use when: Cultural deposits or features preserve a layered sequence; The historical question concerns relative occupation phases, construction sequence, or disturbance; Artifacts, cuts, fills, inclusions, or site context can be used as ordering evidence.
• Typical domains: archaeology, cultural resource management
• Common mechanisms: stratigraphic section diagram, relative chronology matrix

Geological Core Sequence Reconstruction · domain variant · recognized

A domain variant that reconstructs environmental, sedimentary, volcanic, or paleontological sequence from cores and exposed strata.

• Distinct from parent: The parent is broader and includes digital, archival, and organizational layers.
• Use when: Layered sediment, ice, rock, or fossil sequences preserve past conditions; Depth, marker horizons, fossil assemblages, chemistry, or texture encode relative order; Absolute dates are partial and must be integrated with relative sequence evidence.
• Typical domains: geology, paleontology, climate reconstruction
• Common mechanisms: core sample logging protocol, marker horizon correlation

Digital Version-History Stratigraphy · implementation variant · recognized

A digital variant that reconstructs system or artifact history from commits, logs, migrations, deployments, and retained versions.

• Distinct from parent: The parent can use physical or archival layers; this variant is specific to digital change histories.
• Use when: A digital artifact or system has accumulated versions, branches, logs, migrations, or deployments; An incident, regression, policy change, or dependency history needs chronological reconstruction; Branches, rebases, deleted logs, or migrations may obscure the apparent order.
• Typical domains: software engineering, data pipelines, configuration management
• Common mechanisms: version history commit graph, relative chronology matrix

Forensic Layer Reconstruction · risk or failure variant · recognized

A forensic variant that reconstructs event sequence from layered physical traces, contamination profiles, files, or custody records.

• Distinct from parent: The parent is general; this variant is high-stakes and accountability-sensitive.
• Use when: An event sequence must be reconstructed for accountability, diagnosis, litigation, safety, or remediation; Evidence is layered, overwritten, contaminated, or partially missing; Chain-of-custody, provenance, and uncertainty must be explicit.
• Typical domains: environmental investigation, incident review, digital forensics
• Common mechanisms: layer disturbance audit checklist, relative chronology matrix

Near names: Stratigraphic Inference, Layer-Order Analysis, Sequential Deposition Inference, Archival Stratification Interpretation, Git Archaeology.

Editorial Notes

Problem Classification

Classification: Identity, Provenance & Integrity Failure → Temporal Record Lineage & Reproducibility

Problem kernel: disturbed accumulated layers obscure chronological lineage

Rationale: Earliest causal condition: A system contains accumulated layers, traces, versions, deposits, or records, but the events that produced them are no longer directly observable. The interpreter needs a defensible chronology and causal history without confusing layer order with complete, undisturbed, or self-explanatory evidence.

Independent corroboration: The earliest necessary condition in the frozen evidence is: A system contains accumulated layers, traces, versions, deposits, or records, but the events that produced them are no longer directly observable. That is a temporal record lineage and reproducibility problem because Overwriting, delayed capture, or unversioned accumulation erases how the present artifact, decision, result, or collective memory formed and prevents faithful reconstruction or replay.

Review outcome: Independent reviewer agreement; high confidence.