Sep 2026· Zenodo (CERN European Organization for Nuclear Research)
Abstract
Frontier model capability has improved rapidly for four years while the rate at which organisations convert artificial intelligence pilots into production has not. This paper argues that the two facts are connected, and that the binding constraint is no longer reasoning quality but continuity: what an autonomous system carries from one operating cycle to the next. Four independent lines of published evidence are assembled. A frontier laboratory's own usage data shows computer and mathematical tasks at roughly 35 percent of consumer conversations and close to 44 percent of first-party API traffic, with software error correction the single most frequent task. Enterprise research attributes an approximately 95 percent pilot failure rate not to model quality but to a learning gap. Time-horizon measurement shows long 50 percent horizons alongside much shorter 80 percent horizons. And long-horizon agent performance degrades sharply when a task is embedded in a longer interaction history even while the required information remains inside the context window, which locates the failure in architecture rather than in information availability. The paper then examines the same pattern in defense programmes, argues that stored facts, larger context windows and similarity-based retrieval are each insufficient for continuity, specifies eight properties a continuity layer must exhibit, proposes a falsifiable two-cycle evaluation protocol, and states four checkable predictions. This is a position and architecture paper. It presents no original empirical work and no validation of the author's own systems. The author declares a competing interest as co-founder and Chief Executive Officer of Rebootix AI, Inc. Companion preprint: 10.5281/zenodo.22557263.
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