Rethinking Artifact Evaluation for Software Engineering in the Age of Generative AI
Not on the map. Why?
Abstract (arXiv)
Peer review in software engineering research operates under tight time constraints, while generative AI has substantially reduced the human effort required to produce polished research narratives. Reviewer attention is often spent on aspects of submissions such as writing quality or literature positioning that have become relatively less effort-intensive to address, rather than on evaluating the scientific substance of a paper. At the same time, assessing whether methods are implemented correctly, analyses are sound, and claims are supported by evidence remains effort-intensive and dependent on human expertise. In software engineering research, this substance is frequently embodied in artifacts, including code, data, evidence and analysis samples, and experimental infrastructure. In this position paper, we argue that artifact evaluation should be treated as a first-class component of peer review. We frame peer review as an attention allocation problem, examine how generative AI weakens narrative quality as a signal of rigor, and argue that artifact evaluation should play a more prominent role in peer review decisions.
Key facts. Cited by 2 papers in the map (data through 14 Oct 2026). First posted on arXiv 26 Jan 2026.
Builds on
No reference list yet.
Built on by
Citing papers per year: 2026: 2.
2 papers.
- 2026ResearchLoop: An Evidence-Gated Control Plane for AI-Assisted Researchcited by 3
- 2026Agent-Based Software Artifact Evaluationcited by 0
- 2026ResearchLoop: An Evidence-Gated Control Plane for AI-Assisted Research27 May 2026
- 2026Agent-Based Software Artifact Evaluation2 Feb 2026