The Principle of Superposition
"In undisturbed layered rock, each bed is younger than the one below and older than the one above."
"In undisturbed layered rock, each bed is younger than the one below and older than the one above."
The principle of superposition holds that in an undeformed sequence of sedimentary rock layers, each layer is younger than the one beneath it and older than the one above it, because the layers were deposited in temporal order from bottom, the oldest, to top, the youngest. It is the most basic rule of relative dating, letting geologists read the order of events directly from a stack of strata. It holds only where the sequence has not been overturned or thrust out of order, a condition that must always be checked.
Rated Empirical: grounded in studies or measurable evidence. The other 608.
Sediment settles under gravity, so each new layer is laid down on top of what came before, building an ordered stack in which depth records age. Superposition sits alongside the companion principles Steno set out: original horizontality, that layers are deposited flat, so tilted or folded strata were moved after deposition; and lateral continuity, that a layer extends sideways until it thins out or meets a barrier. Later principles build on these, including cross-cutting relationships, that a feature slicing through strata is younger than them, and faunal succession, that fossils change in a fixed order up the sequence.
Original horizontality and lateral continuity, articulated with superposition, which together let deformed or discontinuous strata be interpreted against their original deposition.
The later principle, associated with James Hutton, that a fault or intrusion cutting across strata must be younger than the rock it cuts, extending relative dating to igneous and structural features.
Superposition is foundational to relative dating and to the entire geologic time scale. It was the organising rule that let geology become a historical science, working out the relative order of Earth's rock record in the seventeenth to nineteenth centuries, decades to a century before radiometric dating existed in the twentieth. Radiometric dating later attached numbers to that framework; it did not replace it. Every reconstruction of Earth's layered history rests first on reading which bed came before which.
Superposition holds only for undeformed sequences. Tectonic activity can overturn, fold, or thrust older rocks over younger ones, so in mountain belts and other disturbed terrain the simple bottom-is-oldest rule can fail, which is why geologists rely on way-up indicators to find the original top. It also applies cleanly to sedimentary layering and needs care with igneous bodies, since an intrusion can be younger than rock both below and above it, which is the territory of cross-cutting relationships rather than superposition. And it gives only relative, not numerical, ages.
It gives relative, not absolute, ages: it tells you a layer is older or younger than its neighbours, not how many years old, which requires radiometric methods. It is not universal, since in overturned, folded, or thrust-faulted strata older rock can sit atop younger, so assuming bottom-is-oldest in deformed terrain is a real error. And it applies to sedimentary layering, needing care with intrusions and with disturbed sequences such as burrows or later human intrusions.
Yes, as far as the evidence goes. The Principle of Superposition is rated Empirical here: it rests on studies or measurements rather than on a saying.
Rated from two sources. 609 of the 1,116 entries carry this rating. How the scale works.
The best-known laws are the least likely to rest on measurement.
Formulated, with the related principles of original horizontality and lateral continuity, by the Danish anatomist and geologist Nicolas Steno in his 'Prodromus' (1669), based on observations in Tuscany.
Everything above traces to en.wikipedia.org and nps.gov: two secondary sources, accounts of the original rather than the original itself, which has not been located for this entry. Nothing is written from memory, and the method is written down. Spot an error or a better source? Suggest a fix.