Core Sample Logging Protocol¶
Procedure — instantiates Stratigraphic Time-Ordering Inference
Records depth, material transitions, inclusions, and sampling metadata for core-based sequences before any order or age is inferred.
A core is a one-dimensional column pulled out of a layered body — ice, lakebed mud, seafloor sediment, a soil monolith — and once it is out of the ground, whatever the field team fails to write down is gone. Core Sample Logging Protocol is the disciplined recording procedure that captures, for that single extracted column, exactly what is physically there: the depth of every material change, the colour and grain of each interval, the inclusions, the gaps where recovery failed, and the metadata of how each slice was cut and sent for analysis. Its one defining commitment is that it records observation, not interpretation — it produces a custody-grade description of the medium and its boundaries, and it stops short of saying which layer is older or how old it is. That restraint is the whole point: everything downstream depends on a log nobody can accuse of smuggling a conclusion into the raw data.
Example¶
A glaciology team retrieves a 90-metre ice core from an inland plateau. As each 1-metre section comes up the barrel, a logger works it top-to-bottom on a cold-room bench. She records depth in metres to the centimetre; describes each interval (clear bubble-poor ice, then a cloudy banded stretch, then a dark 3-millimetre lamina at 61.4 m that looks like volcanic ash); notes inclusions — trapped air bubbles, a dust band, a hairline fracture. Where the core came up shattered between 44.1 and 44.2 m she logs a 10-centimetre recovery gap rather than pretending the column is continuous. Finally she writes the sampling plan into the log: 5-centimetre increments to the isotope lab, the ash lamina bagged separately for geochemistry.
The output is not a history of the plateau. It is a column log that lets an analyst two years later know that the ash at 61.4 m is a real observed feature, that there is a genuine 10-centimetre hole at 44 m, and that the isotope samples came at 5-centimetre spacing — so nobody has to trust memory, and nobody can quietly invent a layer that was never seen.
How it works¶
Logging proceeds strictly down the column. Each interval gets a standardized description — a fixed colour reference, grain-size class, and structure — so two loggers describe the same mud the same way. Every material transition is marked as a boundary at its exact depth, with a note on whether the contact is sharp or gradational. Recovery is logged honestly: what length came up versus what length of hole was drilled, and where the shortfall sits, because a compacted or missing interval is preservation loss, not evidence of nothing happening. The sampling scheme — increment size, which intervals were subsampled for which assay — is written into the same record so resolution is auditable. What the protocol deliberately does not do is decide top-is-younger or attach a date; it hands a clean medium description to the mechanisms that reason about order.
Tuning parameters¶
- Description granularity — how fine a change earns its own logged interval. Finer logging captures thin marker layers but slows the work and can bury signal in detail.
- Recovery threshold — the shortfall length that triggers a flagged gap. A low threshold surfaces every drilling loss; too low and every core reads as riddled with holes.
- Sampling increment — the depth spacing of subsamples. Tighter spacing raises temporal resolution downstream but multiplies lab cost and can outrun what the medium can actually resolve.
- Descriptor standardization — how rigidly loggers must use fixed vocabularies and colour charts. More rigour improves cross-logger consistency; less allows nuance a code can't capture.
- Metadata depth — how much custody and instrument context each sample carries. Richer metadata protects provenance but adds recording overhead.
When it helps, and when it misleads¶
Its strength is that it freezes a perishable, one-shot observation into a permanent, inspectable record, and it enforces the separation the archetype demands: it describes the medium and its boundaries without pretending to know the sequence. A later reviewer can always trace an interpretation back to a specific logged interval.
Its failure mode is that the logging act itself distorts what it records. Drilling can smear, stretch, or "flow-in" material, and soft or soluble layers are preferentially lost, so a naive reader may treat a drilling artefact as a real deposit or read logged depth as if it were undistorted original position — a mistake the principle of superposition only licenses for undisturbed strata.[n1] The classic misuse is treating depth as a clock: deeper is not uniformly older when compaction and hiatuses vary down the column. The guarding discipline is to keep the log purely descriptive, flag every recovery gap and suspected drilling artefact as a preservation note, and leave ordering and dating to the mechanisms built for them.
How it implements the components¶
layer_bearing_medium_definition— the log opens by naming the column: what medium it is, how it formed, and what a depositional unit means in it.layer_boundary_identification— every material, colour, or structural transition is recorded as a boundary at an exact depth.sampling_resolution_plan— the increment spacing and per-interval subsampling scheme are written into the record, making resolution explicit and auditable.preservation_bias_assessment— recovery gaps, compaction, and preferentially lost soft intervals are logged as flags on what the column failed to preserve.
It does not apply a relative_ordering_rule (that is Stratigraphic Section Diagram and Relative Chronology Matrix), does not run the interpretive disturbance_and_discontinuity_audit (that is Layer Disturbance Audit Checklist), and supplies no cross_layer_correlation_anchor or absolute_time_anchor (that is Marker-Horizon Correlation). The protocol logs the column; it does not order, correlate, or date it.
Related¶
- Instantiates: Stratigraphic Time-Ordering Inference — it produces the raw, custody-grade medium description the rest of the inference depends on.
- Sibling mechanisms: Layer Disturbance Audit Checklist · Marker-Horizon Correlation · Relative Chronology Matrix · Stratigraphic Section Diagram · Version-History Commit Graph
Editorial Notes¶
Form Classification¶
Form family: Record, Log & Register
Rationale: The mechanism accumulates standardized depth intervals, material transitions, recovery loss, structures, and sampling metadata into an auditable core history before interpretation, so its operative form is a sample log.
Nearest alternative: Protocol, Workflow & Routine — Logging proceeds down the column under a standard sequence, but the durable actual sequence and provenance record is the mechanism's primary output.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Earth Sciences
Origin pattern: Convergent development
Present-day reach: Specialized
Rationale: Field geology and stratigraphy cohered standardized core logging of depth, lithology, boundaries, inclusions, recovery gaps, and sampling context before interpretation.
Related originating lineages:
- Archaeology & Paleontology — Excavated cores and stratigraphic specimens developed parallel provenance, depth, context, and handling logs.
- Marine Science & Oceanography — Oceanographic coring materially shaped shipboard sectioning, depth indexing, handling, and repository protocols.
Review resolution: Earth sciences remain primary, while archaeology and marine science independently institutionalized closely related core-provenance protocols. Convergent origin better captures these parallel field traditions than treating one as a mere application.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] The principle of superposition, formalized by Nicolas Steno in 1669: in an undisturbed sequence of deposited layers, each layer is younger than the one beneath and older than the one above. The qualifier "undisturbed" is exactly why a log must flag recovery gaps and drilling artefacts rather than treating depth as an automatic proxy for age. ↩