MétaCan
Menu
Back to cohort
Record W4406377446 · doi:10.1007/s13347-025-00838-z

Why you Should not use CI to Evaluate Socially Disruptive Technology

2025· article· en· W4406377446 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.

fundA Canadian funder is recorded on the work.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenuePhilosophy & Technology · 2025
Typearticle
Languageen
FieldSocial Sciences
TopicPrivacy, Security, and Data Protection
Canadian institutionsnot available
FundersSocial Sciences and Humanities Research Council
KeywordsSociotechnical systemPhilosophy of technologyContext (archaeology)Scope (computer science)HarmGovernment (linguistics)Information privacyKnowledge managementInternet privacyBusinessSociologyRisk analysis (engineering)Computer securityEngineering ethicsPublic relationsPhilosophy of sciencePolitical scienceComputer sciencePsychologyEpistemologySocial psychologyEngineering

Abstract

fetched live from OpenAlex

Abstract Contextual Integrity (CI) is built to assess potential privacy violations of new sociotechnical systems and practices. It does so by evaluating their respect for the context-relative informational norms at play in a given context. But can CI evaluate new sociotechnical systems that severely disrupt established social practices? In this paper, I argue that, while CI claims to be able to assess privacy violations of all sociotechnical systems and practices, it cannot assess the ones that cause severe changes and disruptions in the norms and values of a given context. These types of technology are known as socially disruptive technologies (SDTs) and this paper argues that they are beyond CI’s scope. It follows that at best, a privacy assessment of those technologies by CI would be useless and, at worst, lead to potential harm, including failure to identify privacy violations and unwarranted legitimisation of privacy-threatening technology. Government actors, policymakers, and academics should refrain from relying on CI to assess this type of technology.

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.001
metaresearch head score (Gemma)0.005
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: Theoretical or conceptual
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.934
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.005
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0020.004
Science and technology studies0.0010.001
Scholarly communication0.0000.000
Open science0.0020.001
Research integrity0.0010.001
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.076
GPT teacher head0.366
Teacher spread0.291 · 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