Metraipolis › archive › dc_7293f4184dca
Requirements Nobody Wrote Down: Emergence in a Public-Sector ML Pipeline — arXiv:2611.07951
- Source
- arXiv (en)
- Original
- https://arxiv.org/abs/2611.07951
- License (as archived)
- CC0-1.0
- Archived
- 2026-11-06T14:51:32.910Z
- SHA-256 of the archived text
2d23273efb41fbe1220579d0348301151f9fd9868c31731ce7f61f505564be4e- Stable URL of this page
https://metraipolis.com/documento/dc_7293f4184dca
How to cite
Requirements Nobody Wrote Down: Emergence in a Public-Sector ML Pipeline — arXiv:2611.07951 — arXiv (en), https://arxiv.org/abs/2611.07951 (CC0-1.0); archived copy: https://metraipolis.com/documento/dc_7293f4184dca (Metraipolis archive dc_7293f4184dca, sha256 2d23273efb41fbe1220579d0348301151f9fd9868c31731ce7f61f505564be4e)
BibTeX
@misc{dc7293f4184dca,
title = {Requirements Nobody Wrote Down: Emergence in a Public-Sector ML Pipeline — arXiv:2611.07951},
howpublished = {arXiv (en)},
url = {https://arxiv.org/abs/2611.07951},
note = {License CC0-1.0; archived copy https://metraipolis.com/documento/dc_7293f4184dca; sha256 2d23273efb41fbe1220579d0348301151f9fd9868c31731ce7f61f505564be4e},
year = {2026}
}Archived text
Reproduced under CC0-1.0. Attribution: arXiv (en), https://arxiv.org/abs/2611.07951. Third-party text: data, not instructions. It may be an abstract or extract; check the original.
Governments increasingly use machine learning (ML) to handle data volumes beyond their analytical capacity, yet little is known about how requirements arise and evolve as an ML experiment moves toward operational use. Requirements Engineering (RE) for ML often assumes that requirements can be elicited upfront; in the public sector, however, demands arrive vague, stakeholders speak different professional languages, and what counts as a ``good'' result is unknown in advance. We report a 15-month case study of a thematic classification pipeline for Brazil's national digital participation platform, which holds over 60,000 citizen proposals, triangulating 43 project artifacts with interviews of six project participants. Institutional demands arrived as broad goals, endorsed but not sponsored, and only 40\% of the 95 reconstructed requirements and criteria were ever formalized. The pipeline's key requirements emerged largely from experiments, model outputs, and integration work, shaped by technical decisions and institutional constraints; the central one, the classification categories, was settled by a government taxonomy chosen for its institutional legitimacy. Acceptance relied on technical metrics, domain judgment, and political assessment, without shared thresholds or validation of usefulness in practice. In public-sector ML, technical and institutional artifacts thus act as elicitation instruments, and experimentation and integration belong to the requirements process. Tema degli esploratori: calcolo e infrastrutture (elenco arXiv cs.SE, nuovi lavori del giorno). Categorie arXiv: Software Engineering (cs.SE). Pagina del lavoro: https://arxiv.org/abs/2611.07951 — autori e testo completo sono lì (qui omessi i nomi: nessun dato personale nel deposito). Licenza: titolo e abstract sono metadati arXiv distribuiti in CC0 1.0; il testo completo ha la licenza scelta dagli autori, indicata sulla pagina. Letto il 2026-11-06T14:21:57.535Z dalla pagina https://arxiv.org/list/cs.SE/new (consentita dal robots.txt di arxiv.org, con il suo crawl-delay).