Non-Compliance in a Dangerous Time: The Pitfalls of Section 27 of the Surface Rights Act
Bibliographic record
Abstract
The primary purpose of the Surface Rights Act is to avoid litigation when an obstinate landowner rejects all reasonable offers for compensation in exchange for access to their property. When negotiations breakdown, the Surface Rights Board intervenes and establishes the terms, including compensation, of the surface lease. By offering an alternative to a privately negotiated lease, the Act promises to break deadlocks between lessor-landowners and lessee-operators resulting in expedited energy projects. Further, it is hoped that by providing an alternative to the more adversarial judicial system, more amicable relations between landowners and operators will develop even in less than ideal circumstances.Unfortunately, Section 27 of the Surface Rights Act appears to be undermining the goal of facilitating amicable relations. Section 27 aspires to initiate the renegotiation of a surface lease every 5 years. Such renegotiations are necessary so that the parties can review the compensation payable in light of variables arising and evolving over the lease term. These variables include: the compensation that other landowners recently received, the per acre value of the land, the actual loss of use, and other adverse effects such as damages. The problem lies in Section 27’s requirement that obliges the operator to notify the landowner of the opportunity to renegotiate the lease. Predictably, the landowners rely upon this notification requirement. The Act, however, provides no punitive measure for non-compliance; this, in turn, leaves the operator to follow market incentives. Since renegotiating a lease usually costs the operator more through additional compensation payouts, this incentive encourages the operator, as a rational market actor, to ignore the notification requirement. Non-compliance with the requirement frustrates the landowner when he or she discovers they were short changed by the operator; this ultimately undermines the goal of amicable relations. Undermining amicable relations is precisely what the drafters of the Surface Rights Act were attempting to avoid. In contemplation of this regulatory failure, this article explores the pitfalls of this legal quagmire for landowners, the Alberta government, and even the operators who appear to be profiting from the situation.
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 distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.003 | 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.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.000 | 0.001 |
| Insufficient payload (model declined to judge) | 0.000 | 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 teacher head, 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".