The App Boss Becomes the Human Manager
Omir Kumar and Krishnan Narayanan study AI, apps, and blue-collar gig work in India. Their frame is not automation versus workers. It is whether app-mediated work can keep human accountability where the stakes are highest.
The Paper
The paper is The Algorithmic-Human Manager: AI, Apps, and Workers in the Indian Gig Economy, arXiv:2606.19975 [cs.CY; cs.AI]. arXiv records version 1 on June 18, 2026 and lists Omir Kumar and Krishnan Narayanan as authors. The arXiv comment says it was published by the Centre for Responsible AI at IIT Madras.
The study uses a social-justice frame and a mixed-methods design built around interviews with 16 gig workers and 21 stakeholders, including platform executives, business leaders, and worker advocates. Its domain is location-based blue-collar platform work in India: ride sharing, delivery, home services, warehouses, and dark stores.
The important move is that the paper does not treat AI as a distant replacement machine. It treats AI and digital technology as the practical management layer already allocating tasks, measuring performance, shaping pay, verifying identity, routing grievances, and determining whether a worker can keep earning.
The App as Boss
The worker-facing finding is a familiar contradiction. Platforms expand access to paid work, especially for people with limited alternatives, but the same app becomes the channel through which opaque allocation, incentives, penalties, ratings, and deactivation arrive. The worker may experience the platform as a tool, a market, and a supervisor at the same time.
The paper reports that many workers did not know the term AI or did not believe the company used AI, while still describing effects that belong to algorithmic management. That distinction matters. A worker does not need a vocabulary of machine learning to know that order distribution, pay, or account status has changed without an explanation.
The stakeholder interviews add another layer. Platforms use targeted ads, data pipelines, generative AI for candidate processing, self-onboarding, selfie verification, location tracking, performance metrics, route optimization, handheld warehouse devices, and computer vision in selected workflows. Some of these systems can reduce friction or improve safety, such as fatigue log-off features. Others can make work more brittle when weather, traffic, flooding, infrastructure, customer behavior, or equipment failure is treated as if it were worker failure.
Support as Governance
The strongest governance lesson is hidden in support tickets. Workers in the study engaged heavily with chat support because that was where pay disputes, penalties, account issues, and deactivations became real. Routine operational help may fit a chatbot. High-stakes decisions do not.
The paper describes worker frustration with automated or inadequate grievance systems, especially where complaints lack time-bound resolution, clear justification, or escalation to a person. This is where the phrase human in the loop either becomes real or collapses into decoration. The human is not needed as ceremonial oversight. The human is needed because the worker needs someone with authority to explain, correct, override, and record the decision.
This belongs beside this site's pages on the dashboard boss, hidden AI labor, workplace surveillance, workplace affect scoring, and automated hiring interfaces. The recurring pattern is that management becomes software before accountability becomes software.
The Hybrid Manager
Kumar and Narayanan use the term algorithmic-human manager for a pragmatic middle path: algorithms may allocate and optimize, but fairness, dignity, and due process require explainable systems, worker participation, and human review for high-stakes decisions. They recommend algorithmic transparency, collaborative risk assessments, participatory design, microlearning inside worker apps, peer support, and worker-facing digital and financial literacy.
For government and policy, the paper discusses India's Code on Social Security 2020, state-level efforts in Rajasthan, Karnataka, Jharkhand, Bihar, and Telangana, and proposals for a right to explanation and human review. It also proposes a Unified Workers Interface as digital public infrastructure for portable worker identity, work history, reputation, settlement, social-security administration, and data ownership.
That proposal is powerful and dangerous for the same reason. A portable work ledger could help with benefits, mobility, and accountability. It could also become a cross-platform reputation trap if contestability, correction, privacy, governance, and worker control are weak. Portability without due process is only a larger cage.
What the Receipt Must Add
An algorithmic-human manager needs a receipt at every high-stakes point: allocation rule, wage rule, incentive threshold, penalty trigger, rating input, monitoring signal, identity check, location policy, grievance ticket, human reviewer, decision deadline, appeal route, evidence shown to the worker, correction made, and whether the worker participated in design or audit.
The audit-grade sentence is not "the platform uses AI responsibly." It is: this worker was assigned, paid, rated, penalized, or deactivated under these rules; these data sources were used; this explanation was provided in an accessible language; this human reviewer had authority to change the outcome; and this appeal path actually resolved the case.
Limits
This page reads one arXiv record and one report-style PDF. The interview sample is useful for surfacing mechanisms and lived experience, not for estimating population-wide rates. The PDF text extraction is noisy, so factual checks were made against the arXiv metadata plus readable sections of the PDF: executive summary, methods, findings, policy landscape, recommendations, and appendices. No claim here should be read as proof that every Indian platform uses the same system or produces the same harm.
Sources
- Omir Kumar and Krishnan Narayanan, The Algorithmic-Human Manager: AI, Apps, and Workers in the Indian Gig Economy, arXiv:2606.19975 [cs.CY; cs.AI], submitted June 18, 2026.
- Primary arXiv records checked: abstract page, PDF, and arXiv API metadata, reviewed for title, authorship, submission date, categories, Centre for Responsible AI note, sample sizes, worker and stakeholder findings, policy discussion, recommendations, and limitations.
- Related pages: The Boss Becomes a Dashboard, Feeding the Machine and the Labor That Makes AI Look Automatic, Data Driven and the Workplace That Became a Sensor Network, The Emotion Detector Becomes a Workplace Polygraph, and The Interview Becomes a Model Interface.