'Release work' is a distinct, boundary-facing accountability labour that gates client-facing AI drafts, separate from articulation work

generative-ai-at-workcscwaccountability-labourarticulation-workkenyanigeriasmall-businesssingle-source-cap

Abdulhamid, Nyairo, Ankrah & O'Neill's qualitative CSCW interview study of generative-AI use in Kenyan and Nigerian small businesses (arXiv:2610.31344, 2026) proposes "release work" as a specific form of accountability labour: the certification that a single AI-assisted artifact is defensible before it crosses a boundary to an external, client-facing audience. The paper distinguishes release work from the older CSCW concept of articulation work (Schmidt and Bannon 1992) on three grounds: its object is narrower (the defensibility of one artifact crossing a boundary, not a mesh of interdependent tasks); its trigger differs (external accountability at the moment of circulation, rather than task interdependence among collaborators); and, decisively, release work "can be discharged by one worker with no cooperative activity to articulate."

Three empirical markers mark release work in the data: verification gates tied to domain standards, post-hoc traceability reconstruction when AI-supplied sources fail, and non-delegation boundaries — explicit refusals to let AI output make high-stakes calls. Illustrative examples from the interviews: a financial-services consultant who alone cross-checked every AI response "before I use it," and an R&D lead who held that "the financial decisions... still remain with me" regardless of AI assistance. The paper frames this as solo, individually-discharged accountability work rather than a coordination problem — the central move that separates it from articulation work's cooperative frame.