MétaCan
Menu
Back to cohort
Record W4415643420 · doi:10.1111/rego.70084

Managing Complaint Mechanisms for Regulatory Enforcement: Evidence From Human Rights Institutions During the <scp>COVID</scp> ‐19 Pandemic

2025· article· en· W4415643420 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.
fundA Canadian funder is recorded on the work.
aboutThe title or abstract carries a Canadian signal from the geographic lexicon.

Bibliographic record

VenueRegulation & Governance · 2025
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicRegulation and Compliance Studies
Canadian institutionsConcordia University
FundersConcordia University
KeywordsComplaintEnforcementBeneficiaryIntermediarySanctionsHuman rightsProcess (computing)

Abstract

fetched live from OpenAlex

ABSTRACT How do regulatory bodies ensure that including the beneficiaries of regulation in regulatory processes improves governance? In many regulatory arrangements, beneficiaries' “fire alarm” monitoring and reporting of targets' violations via complaint mechanisms activate regulatory bodies' enforcement role. This article theorizes how beneficiaries may misuse complaint mechanisms, undermine regulators' performance, and prompt regulators to adopt strategies within and beyond the complaint process to regulate beneficiaries' behavior. It argues regulators' assessment of the issues driving misuse and their enforcement approach (cooperative or deterrent) affect their strategies for influencing beneficiaries. Case studies of two Canadian human rights institutions, which have different enforcement approaches but experienced similarly extreme levels of beneficiary misuse during the COVID‐19 pandemic, evaluate these theoretical claims. Overall, the study illustrates potential enforcement challenges arising from using beneficiaries as intermediaries for monitoring and reporting violations and how regulating beneficiary participation may be required to improve decentralized regulatory governance.

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.

Full frame distilled prediction

Teacher imitation

Not 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.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesScience and technology studies
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.729
Threshold uncertainty score0.999

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0030.000
Scholarly communication0.0000.001
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.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.

Opus teacher head0.050
GPT teacher head0.285
Teacher spread0.236 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it