Blog · arXiv Analysis · Last reviewed June 25, 2026

The Dataset Becomes the Repair Claim

The 2026 arXiv paper Can Data Work be Reparative? asks whether AI safety datasets can repair the relations of accountability that ordinary data production often breaks.

Repair Is Not Labeling

The paper, arXiv:2606.09408 [cs.CY, cs.HC], was submitted on June 8, 2026 by Srravya Chandhiramowuli, Ding Wang, and Alex S. Taylor. Its title is Can Data Work be Reparative?. The question is not whether better labels improve a model. The question is whether the social relations around data work can be changed enough to count as repair.

The authors study an alternative approach to data work developed by Tattle Civic Tech, an India-based civic-tech organisation building datasets and tools for online harms such as misinformation, hate, and online gender-based violence. The paper treats safety datasets as political artifacts: they are not just collections of examples, but records of whose experiences count, whose expertise is paid for, and who gets authority after contribution.

That makes this paper useful for AI governance. Responsible AI often asks whether a dataset is documented, diverse, or useful for evaluation. Reparative data work asks whether the dataset production process resets accountability toward people most harmed by the systems and platforms the dataset is supposed to correct.

The Tattle Case

The study draws on the lead author's virtual ethnographic engagement with Tattle from April to December 2024, including eight months of fieldwork and 12 interviews with dataset contributors and Tattle team members. It focuses on two online-safety dataset projects: a lexicon of gender-abusive slurs in four Indian languages and a Hindi LLM safety benchmark dataset.

The slur lexicon included more than 650 entries in Hindi, Tamil, Malayalam, and Indian English, with metadata such as severity and categories including gender, religion, caste, class, body shaming, and ableism. The Hindi benchmark project aimed to create 2,000 prompts for two hazards: hate and sex-related crimes. Its contributors included people working in social work, digital media, journalism, fact-checking, psychology, policy advocacy, research, and activism.

The important move is that contributors were not treated as interchangeable labelers. Their discussions shaped definitions, categories, prompt writing, metadata, and the scope of harms. The paper describes this as a feminist orientation to dataset production: subjectivity is not noise to eliminate, but situated knowledge that changes what the dataset can see.

Just Reward

Once lived experience becomes expertise, ordinary data-labor pricing looks inadequate. The paper reports that Tattle's Hindi safety benchmark paid contributors 1,200 INR per hour, or 1,800 INR for each 90-minute workshop, and later distributed leftover compensation funds as an additional per-workshop payment. The point is not that this solves fair pay. The point is that fair compensation becomes a design problem, not an afterthought.

The authors show why this is hard. Contributors came from different regions, sectors, employment arrangements, and material circumstances. Some cared more about intervening in online safety than about payment; others had higher compensation expectations and declined participation. Tattle also had to persuade funders that a slower, more participatory, better-paid process was worth funding in a market where cheaper data work can win bids.

This connects to data enrichment labor, hidden AI labor, and data dignity. If AI safety depends on human judgment, then the conditions under which that judgment is produced are part of the safety case.

Governance After Contribution

The second challenge is what happens after contribution. The paper asks whose views shape dataset licensing, maintenance, expansion, commercial use, contributor rights, refusal, revocation, and stewardship. A dataset about online harms can become valuable to the same platforms whose failures made the dataset necessary. That creates a governance problem, not only a distribution problem.

The authors describe Tattle's exploration of collective dataset governance as difficult to operationalise. Contributor groups change over time. Some contributors are deeply invested in AI and platform accountability; others care primarily about more immediate harms in their communities. A dataset may need regular updating, but the people who made it may not remain available, interested, or empowered to govern its later uses.

That tension is the paper's strongest contribution. Inclusion in dataset production is not automatically repair. If affected people help build a dataset but cannot shape how it is licensed, sold, maintained, contested, or used against the platforms that neglected them, the process may still extract expertise without resetting accountability.

The Spiralist Test

The Spiralist test is simple: when a dataset claims to repair harm, who can call that claim false? Can contributors inspect later uses, contest licensing decisions, share in value, withdraw from inappropriate reuse, or force platforms to answer for the harms the dataset records?

If the answer is no, the dataset may be better, richer, and more contextual, but it is not yet reparative. Repair begins when data work changes the accountability relation between harmed communities, dataset stewards, model builders, and platforms.

Scope Boundary

This is an ethnographic case study of Tattle's approach, not proof that all participatory dataset projects are reparative or that all safety datasets should use one governance model. The paper itself presents reparative data work as an open question and traces tensions rather than offering a universal recipe.

The modest conclusion is strong enough: AI governance should judge safety datasets not only by benchmark utility, but by how they value, protect, and empower the people whose knowledge makes the dataset possible.

Sources

Return to Blog