AI Debt: Verification Burdens, Rework Externalities, and the Hidden Costs of Asymmetric Generative-AI Adoption

23 May 2026, Version 1
This content is an early or alternative research output and has not been peer-reviewed by Cambridge University Press at the time of posting.

Abstract

Generative AI is usually evaluated through the productivity of the immediate user: faster drafting, more output, lower search cost, and apparent acceleration of professional workflows. This article argues that such evaluation is incomplete. When AI-generated artifacts are under-verified, the costs are often displaced onto downstream recipients: judges, teachers, reviewers, managers, clients, colleagues, and administrative staff who must check, correct, contextualize, or reject low-quality AI output. Building on the software-engineering metaphor of technical debt, the article introduces the concept of AI debt: the accumulated obligation to remediate AI-generated artifacts that were produced faster than they were validated. AI debt has a principal, an interest rate, a debtor, and frequently a different burden bearer. The article develops a conceptual framework, reviews evidence from legal practice, workplace knowledge work, education, academic publishing, and professional services, and proposes governance mechanisms inspired by technical-debt management: debt registers, definition-of-done rules, review gates, automated citation tests, amortization sprints, receiver-side rights, and accountability allocation. The central claim is that responsible AI adoption must be measured at the workflow and system level, not only by individual user time savings.

Keywords

AI debt
technical debt
generative AI
workslop
hallucination
verification burden
externalities
asymmetric adoption
legal technology
human-in-the-loop governance

Comments

Comments are not moderated before they are posted, but they can be removed by the site moderators if they are found to be in contravention of our Commenting and Discussion Policy [opens in a new tab] - please read this policy before you post. Comments should be used for scholarly discussion of the content in question. You can find more information about how to use the commenting feature here [opens in a new tab] .
This site is protected by reCAPTCHA and the Google Privacy Policy [opens in a new tab] and Terms of Service [opens in a new tab] apply.