Oct 2026· Zenodo (CERN European Organization for Nuclear Research)
Abstract
An AI agent can retain a correction across sessions and still repeat the corrected action. A record may be missing, remain unretrieved, arrive after the decision point, or be read without changing the action. This paper defines a functional scar as a failure-derived runtime control that links a documented error to an applicability predicate, an observable obligation, an intervention point, an evidence record, and a review path. The definition separates the persistence of information from the persistence of corrected behavior. It gives a platform-neutral contract for representing and testing such controls, then examines an open-source implementation with Claude Code and Codex adapters. In the DG Office deployment, Claude Code runs a locally maintained hook system, while Codex invokes the fscars package through native hooks; the two arrangements share a control idea and differ in implementation. A reproduced 368-test suite establishes conformance to the tested software contracts. Prior practitioner observations report lower recurrence for some structured corrections. Runtime logs use different event schemas and outcome proxies, so they do not estimate a package-wide causal effect. The paper sets out an evaluation method that measures applicability, control activation, action change, final outcome, false activation, and override cost as separate quantities. A brief analogy with human emotional learning motivates the term, while neuroscience is kept distinct from the engineering mechanism. This technical synthesis specifies a testable correction-control contract and evidence boundaries for evaluating persistent corrections.
This publication proposes a definition and a classification of agile software development approaches and analyses ten software development methods that can be characterized as being "agile" against the defined criterion.
P. Abrahamsson, O. Salo, Jussi Ronkainen et al.· arXiv.org· 727 citations· ⚡54
The study shows that agile practices improve both informal and formal communication, but indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication.
M. Pikkarainen, Jukka Haikara, O. Salo et al.· Empirical Software Engineeri...· 401 citations· ⚡48
The results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.
Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al.· Information and Software Tec...· 394 citations· ⚡54
The results show that the embedded industry has been able to apply agile methods in its development processes and that the appreciation of the agile methods and their individual practices appears to increase once adopted and applied in practice.
O. Salo, P. Abrahamsson· IET Software· 238 citations· ⚡9
Consequences of happiness and unhappiness that are beneficial and detrimental for developers' mental well-being, the software development process, and the produced artifacts are found.
D. Graziotin, Fabian Fagerholm, Xiaofeng Wang et al.· Journal of Systems and Softw...· 236 citations· ⚡13
The Mobile-D approach is briefly outlined here and the experiences gained from four case studies are discussed, which helped develop an agile development approach for mobile application development.
P. Abrahamsson, Antti Hanhineva, H. Hulkko et al.· Conference on Object-Oriente...· 225 citations· ⚡18
Related blog posts
MIT News · Artificial Intelligence· news.mit.eduOct 6, 2026
Writing as a participant and researcher, PhD student JS Tan SM ’22 has co-authored a new book about the rise of tech worker protests and the employer backlash that followed.
Requirements in large systems rarely exist in isolation. Their meaning depends on the wider project context - other requirements, policies, decisions, tests, and implementation details. That becomes especially important when AI is used for review, because spotting a possible conflict or gap is only the beginning. ReqSpace explores how AI, visualisation, and connected project context can help reviewers understand those findings, trace the relationships behind them, and focus on the questions that…
AI is making software generation faster, but speed does not remove the need for expertise. As more work is delegated to AI, tacit knowledge may become one of the most important human advantages in software engineering. The post Beyond Prompt Engineering: The Role of Tacit Knowledge in Software Engineering appeared first on GPT-Lab.
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.