Transient porosity generated at the serpentinization front
Bibliographic record
Abstract
Serpentinization ubiquitously affects ultramafic rocks that interact with water, with strong implications for the origin of ancient microbial ecosystems, the chemical budget of the ocean, and the rheology of the oceanic crust. The increase in volume associated with this reaction, and its consequences for reaction progress, have been debated for over a century. Serpentine minerals are ~40% more voluminous than olivine, which suggests that fully serpentinized peridotite should have negative, or at least very low, porosity. Recent studies have proposed that self-propagating, reaction-driven fracturing can facilitate serpentinization reactions, but the nanoscale mechanisms by which fluid is transported through serpentinized fractures in order to react with fresh olivine surfaces remain poorly understood. To address this issue, we studied a sample of serpentinized harzburgite collected during ODP expedition 209 at site 1274, using Focused Ion Beam – Scanning Electron Microscopy (FIB-SEM)-assisted tomography. We specifically targeted the interface between the serpentinized peridotite and the unaltered primary mineralogy. The resultant images illustrate the presence of nanopores within the serpentine alteration products, primarily at the interface with the unreplaced minerals. Importantly, no pores were observed in the serpentine away from the grain boundaries with olivine, suggesting that these nanopores form during the initial stage of reaction, and then disappear with further reaction progress. We argue that the observed nanoporosity is an intrinsic feature of the serpentinization reaction, and that its transient presence during serpentinization is vital for facilitating reaction progress. We suggest that the transient nature of the pores arises from the opposing kinetics and thermodynamics of the replacement reaction. The former promotes the formation of voids that enhance the advective transport of fluids to the reaction front, while the latter drives the reduction of pore space by means of recrystallization of the serpentine aggregates and minimization of the interfacial energy.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.001 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.001 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".