AI & ML
Requirements Nobody Wrote Down: Emergence in a Public-Sector ML Pipeline
arXiv cs.SE0 views
arXiv:2611.07951v1 Announce Type: new Abstract: 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.
Source:https://arxiv.org/abs/2611.07951PreviousA Low Similarity Score Does Not Show Independence after Source-Conditioned Repository RewritingNextReducing Representational Interference in Retrieval Embeddings with Trainable Prefix Tokens
Related posts
Language models generate maximally activating examples for any residual direction
0dev.to

9 Timeouts in Claude Code, Codex and Gemini CLI That Cut Long Test Runs Short
0dev.to
Where JLPT learners lose points: 36,263 first answers by section
0dev.to
Stripe Billing or Chargebee: The Renewal Decides
0dev.to
Layer Rename & Cleanup: batch rename and delete empty layers in Aseprite (free Lite)
0dev.to

Open-Weight LLM vs Hosted API: What Self-Hosting Gives You That an API Can’t
0dev.to