Skip to content
Sprint projectJun 21, 2026Bangaluru, India

Gradual Disempowerment at Scale: Measuring Cumulative Agency Erosion in Algorithmic Management of Indian Delivery Workers

Pavitra Kushwaha · Team byteforge

Submitted to Global South AI Safety Hackathon. Sprint projects are early-stage work by participants, not Apart Research publications.

Read the report

Report: Gradual Disempowerment at Scale: Measuring Cumulative Agency Erosion in Algorithmic Management of Indian Delivery Workers

Code (opens in new tab)More on drive.google.com (opens in new tab)
Share

AI safety has many tools for acute model failures but few evals for gradual disempowerment: incremental loss of human influence as automated systems control decision channels. We operationalize Kulveit et al. 2025 as a five-dimension Gradual Disempowerment Score (GDS) for Indian delivery platforms. The pipeline combines Fairwork India evidence for Swiggy and Zomato from 2021-2024, NITI Aayog gig-workforce estimates, and a clearly labeled synthetic predictive lock-in simulation where worker-level allocation logs are unavailable. Results are mixed. GDS peaks around 2022-2023, then falls in 2024 as Fairwork-evidenced contracts and management improve. In 2024, Swiggy scores 37.88 and Zomato 38.28 on a 0-100 risk scale. GDS is best read as a replicable diagnostic for hidden agency erosion, not proof that every public indicator worsened.

Reviews

Judging this Sprint?

Review this project

Your public critique appears on this page without your name. Your private critique is not published; only the Apart team reads it. If you agree below, we share your review with grantmaking.ai (opens in new tab) and the Transformative AI Fund so strong projects can be funded.

Not shown on this page.

Shown on this page, without your name.

Only the Apart team reads this, and funders if you agree below.

Share my name publicly on grantmaking.ai *
Share my private critique with funders *

How much would this matter for AI safety if it worked? How innovative is it? For scores of 4-5: is this actually new to the field, or replicating recent work?

Scoring guide
  1. 1Negligible. No clear problem addressed, or no meaningful novelty.
  2. 2Limited. Addresses a real problem but with a generic or well-trodden approach. Incremental at best.
  3. 3Moderate. Clear problem with a reasonable approach; some novelty in framing or method beyond routine application of existing tools.
  4. 4Significant. Important problem with an original approach, or identifies a neglected problem area. A valuable contribution others could build on.
  5. 5Exceptional. Tackles a critical AI safety problem with a genuinely novel approach, or opens a new research direction. Clear theory of change. You'd be excited to share this with researchers in the area.

How sound are methodology, implementation, and findings?

Scoring guide
  1. 1Seriously flawed. Methodology broken, results uninterpretable, or implementation doesn't work.
  2. 2Weak. Approach has significant gaps: missing validation, flawed experimental design, or incomplete implementation.
  3. 3Competent. Technically solid given the short duration. Methodology makes sense, results are interpretable, limitations acknowledged, work builds toward clear conclusions.
  4. 4Strong. Thorough methodology with convincing validation. Results clearly support conclusions. Immediately useful for future work.
  5. 5Exceptional. Ambitious scope executed rigorously. Surprising findings, novel methods, or unusually robust validation.

How clearly are work, findings, and impact potential communicated?

Scoring guide
  1. 1Incomprehensible. Cannot determine what the project is actually claiming or doing.
  2. 2Hard to follow. Key information buried, missing, or diluted by excessive length. Significant effort to extract main points.
  3. 3Clear enough. Can understand the problem, approach, and results without undue effort. Core content clearly present: problem, method, findings, limitations.
  4. 4Well presented. Easy to follow, well-structured, appropriate level of detail. Target audience would get it quickly.
  5. 5Exceptionally clear. A pleasure to read. Complex ideas made accessible. Could serve as a model for how to present this type of work.

  1. Great presentation. Would be good to also add some context on addressing the privacy, security and anonymizatoin protocols required for safely extract the actual worker data

    Can also expand on the discussion to explain exactly how the dimensions of interpretability, appeals, and lock-in compound mathematically or theoretically would strengthen the justification for the GDS weighting architecture

  2. - interesting attempt to turn gradual disempowerment into measurable questions.

    - underexplored lens for AI governance

    - The main improvement needed is to define more clearly when ordinary platform coordination becomes disempowerment, and to validate the proxy score against worker-level evidence or platform disclosures.

  3. Bridging AI safety's gradual disempowerment framing with labor platform auditing via a replicable metric is genuinely novel and worth developing further. The biggest weakness is D4 (predictive lock-in), which is entirely synthetic and carries the most interesting safety risk. Validating this dimension with even a small set of opt-in worker app traces would transform the paper's most important claim from an assumption into evidence.

  4. This is a thoughtful and regionally grounded AI safety governance submission. The project applies the idea of gradual disempowerment to a concrete Global South setting: algorithmic management of Indian delivery workers on platforms such as Swiggy and Zomato. The proposed Gradual Disempowerment Score is a useful exploratory diagnostic that tries to connect AI safety concerns about loss of human agency with platform-labor evidence, using dimensions such as decision space, interpretability, appeals, predictive lock-in, and exit viability. The report is especially strong in its careful framing: it does not claim that disempowerment monotonically worsens, clearly labels the predictive lock-in component as synthetic, and treats the score as a diagnostic rather than proof of harm. The concise visual presentation and weight-sensitivity check also make the submission easy to evaluate.

    That said, the project should be understood as an early operationalization rather than a mature or strongly validated eval. Algorithmic management, platform labor, and gig-worker precarity are already substantial research areas, and the AI safety connection here is broader and more governance-oriented than in submissions that directly evaluate model behavior or deployed AI systems. The main limitation is construct validity: GDS has not yet been validated against worker-reported agency, ability to contest decisions, health, income stability, or actual allocation outcomes.

    The most AI-specific component, predictive lock-in, is synthetic because platform-level worker logs are unfortunately unavailable, and the weighting scheme remains subjective even with the included sensitivity analysis.

    Overall, this is a promising exploratory submission with clear Global South relevance. A stronger next version would add worker interviews, platform-specific evidence, uncertainty intervals, broader weight sensitivity, and validation against real worker experiences or opt-in app traces.

    Read full reviewShow less

Cite this project

@misc{kushwaha2026gradual,
  title = {{Gradual Disempowerment at Scale: Measuring Cumulative Agency Erosion in Algorithmic Management of Indian Delivery Workers}},
  author = {Pavitra Kushwaha},
  year = {2026},
  month = jun,
  note = {Submitted to Global South AI Safety Hackathon, an Apart Research Sprint},
  howpublished = {\url{https://apartresearch.com/sprints/projects/gradual-disempowerment-at-scale-measuring-cumulative-agency-erosion-in-algorithmic-management-of-indian-delivery-workers-qlxr}},
  url = {https://apartresearch.com/sprints/projects/gradual-disempowerment-at-scale-measuring-cumulative-agency-erosion-in-algorithmic-management-of-indian-delivery-workers-qlxr}
}

Build something like this at the next Sprint

AI Collusion Research Sprint · Oct 23 - 25, 2026