Evidence-based approaches to managing Canadian oil sands tailing pond waste: tighter regulations and greater transparency are needed
Bibliographic record
Abstract
The mining of oil sands in northern Canada has resulted in the production of vast amounts of a waste byproduct called oil sands process-affected water (OSPW). These OSPWs are chemically complex and spatially varied toxic mixtures stored in human-made lakes called tailing ponds, which collectively hold more than 1 billion m3 of OSPW, cover 300 km2, and are leaking pollutants into groundwater and connected watersheds. Governments have permitted extraction from the oil sands for decades despite the industry’s inability to develop methods to safely treat and dispose of OSPW as a precondition for continued operations. As an alternative to building more tailings ponds to enable continued operation and storage, the federal government is reviewing a proposal to permit the so-called “treat-and-release” of OSPW from existing tailing ponds into the already-compromised Athabasca watershed, despite an existing information asymmetry: operators and governments know more about the risks than do those who are asked to accept them. Treat-and-release of OSPW represents the transfer of risk from operators to the public and the ecosystems. This approach must apply the highest standard of care to ensure that no further harm is incurred at these waste storage sites and in the downstream receiving environment. This opinion piece summarizes the OSPW problem, offers a new approach for setting acceptable exposure standards (no further exposure), and requests transparent and credible independent scientific assessment of releases and alternate options. No further exposure combines metrics in baselines of indicator chemicals, standard toxicity reference values (TRVs), and biological indicator species to provide the requisite fundamental protection of humans and ecosystems. Transparency requires: a robust chemical and toxicological characterization of OSPW; the creation of a government-run public website for data exchange; and consensus decision-making principles.
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.225 | 0.526 |
| Meta-epidemiology (narrow) | 0.002 | 0.002 |
| Meta-epidemiology (broad) | 0.006 | 0.006 |
| Bibliometrics | 0.017 | 0.012 |
| Science and technology studies | 0.006 | 0.008 |
| Scholarly communication | 0.022 | 0.015 |
| Open science | 0.014 | 0.009 |
| Research integrity | 0.018 | 0.021 |
| Insufficient payload (model declined to judge) | 0.009 | 0.002 |
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".