Skip to content

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.

Solution archetype #
1018
Problem family
Identity, Provenance & Integrity Failure
Problem subfamily
Temporal Record Lineage & Reproducibility

The Diagnostic Story

Symptom: Analysts need to establish what happened first, but the evidence is arranged in layers that may be incomplete, disturbed, or overwritten. A tempting causal story presents itself from the visible layer order, but nobody has checked whether intervals are missing, records were rebased, or earlier deposits were reworked by later events. Different investigators examining different partial sequences disagree about chronology in ways that cannot be resolved without an explicit method for aligning them.

Pivot: Treat the layered medium as an evidence-bearing sequence: identify the strata or layers, establish relative order through observable layer relations and markers, check explicitly how layers formed and whether they were disturbed, correlate markers across sequences to build a common chronology, and state the reconstructed history with explicit confidence levels and documented alternatives. Relative order is the foundation; causality and duration require additional evidence.

Resolution: A defensible relative chronology emerges with visible uncertainty rather than confident narrative built on unstated assumptions. Gaps, missing layers, disturbed records, and alternative sequences remain legible rather than papered over. The reconstruction can be audited and revised when new evidence appears because the inference chain is documented.

Reach for this when you hear…

[geology] “The story you tell from the outcrop is only as good as your check for unconformities — if there's a missing million years in there, the whole sequence means something different.”

[software incident review] “The git log tells me the order commits were merged, not the order the bugs were introduced — those are different questions and I need to know which one I'm actually answering.”

[forensic accounting] “The transaction record shows what happened last, not what happened first — we've had to unwind three levels of ledger entries just to find the original misclassification.”

When This Archetype Applies

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

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.

Show the applicability expression

Applicability expression5 distinct conditions

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

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.

2

Decision-relevant chronology · grounded

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

3

Unobservable original process · grounded

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

4

Potentially disturbed ordering · grounded

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

5

Cross-record chronology alignment · grounded

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

Other requirements and context (1)

Why these sit outside the expression

Supporting contextit 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.

5 of 5 conditions grounded.

Read the methodologyDownload the trigger-logic data

Mechanisms / Implementations

  • Core Sample Logging Protocol: Records depth, material transitions, inclusions, and sampling metadata for core-based sequences before any order or age is inferred.
  • Layer Disturbance Audit Checklist: Forces review of the disturbances — mixing, gaps, deletion, backfill — that could invalidate a naive layer-order interpretation.
  • 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.
  • 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.
  • 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.

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

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.

Geological Core Sequence Reconstruction · domain variant · recognized

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

Digital Version-History Stratigraphy · implementation variant · recognized

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

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.

Editorial Notes

Problem Classification

Classification: Identity, Provenance & Integrity FailureTemporal 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.