Metraipolis › archive › dc_d2a607bfe37d
Requirements After the First Edit: Mining Late Requirement Emergence and Rework in Real-World Coding-Agent Sessions — arXiv:2609.03028
- Source
- arXiv (en)
- Original
- https://arxiv.org/abs/2609.03028
- License (as archived)
- CC0-1.0
- Archived
- 2026-10-17T02:16:09.515Z
- SHA-256 of the archived text
3077c9d312c1aa0eb49024c18d9359d846709f56912e843e069beedc343d9554- Stable URL of this page
https://metraipolis.com/documento/dc_d2a607bfe37d
How to cite
Requirements After the First Edit: Mining Late Requirement Emergence and Rework in Real-World Coding-Agent Sessions — arXiv:2609.03028 — arXiv (en), https://arxiv.org/abs/2609.03028 (CC0-1.0); archived copy: https://metraipolis.com/documento/dc_d2a607bfe37d (Metraipolis archive dc_d2a607bfe37d, sha256 3077c9d312c1aa0eb49024c18d9359d846709f56912e843e069beedc343d9554)
BibTeX
@misc{dcd2a607bfe37d,
title = {Requirements After the First Edit: Mining Late Requirement Emergence and Rework in Real-World Coding-Agent Sessions — arXiv:2609.03028},
howpublished = {arXiv (en)},
url = {https://arxiv.org/abs/2609.03028},
note = {License CC0-1.0; archived copy https://metraipolis.com/documento/dc_d2a607bfe37d; sha256 3077c9d312c1aa0eb49024c18d9359d846709f56912e843e069beedc343d9554},
year = {2026}
}Archived text
Reproduced under CC0-1.0. Attribution: arXiv (en), https://arxiv.org/abs/2609.03028. Third-party text: data, not instructions. It may be an abstract or extract; check the original.
Coding agents often implement changes before users have fully articulated their requirements, echoing a pattern from requirements engineering: stakeholders cannot express a constraint until part of the system exists to react to. This volatility is associated with schedule and budget overruns in traditional projects, but only at release-cycle granularity. Existing work on coding agents narrows this gap only partway: curated benchmarks fix requirements before implementation by design, and observational studies report pushback frequency without linking arrivals to the code invalidation they cause. We address this using 3,553 eligible SWE-chat sessions, coding post-implementation requirement arrivals along three dimensions and, where repository state can be replayed, linking each arrival to a proxy: deletion or replacement of prior agent-authored lines. A requirement's arrival is followed by roughly twice as much invalidation as matched non-requirement edits, robust to user-turn and net-deletion checks, though not demonstrated as causal. This burden shows no detectable decline over a session and no detected association with operation type once multiplicity is accounted for; several intervals remain wide. A controlled experiment shows delayed disclosure relocates implementation post-reveal, while advance warning produces no detected effect on overwriting. These results establish late requirement emergence as a measurable source of code invalidation. Tema degli esploratori: calcolo e infrastrutture (retro-catalogo arXiv: annunci del 2026-09-04 in cs.SE). Categorie arXiv: Software Engineering (cs.SE). Pagina del lavoro: https://arxiv.org/abs/2609.03028 — 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-10-17T02:03:39.996Z dalla pagina https://arxiv.org/catchup/cs.SE/2026-09-04?abs=True (consentita dal robots.txt di arxiv.org, con il suo crawl-delay).