Skip to content
#software testing Open access

Swarms in AI Innovation - Why exponentials of exponentials matter in innovation, and where they break

Sep 2026 · Zenodo (CERN European Organization for Nuclear Research)

Abstract

Three documented events frame the question this article studies, and each one was, at the time, unremarkable engineering. In July 2024 one vendor's content update reached about 8.5 million hosts in minutes and produced cross-sector disruption that took roughly ten days to unwind (CrowdStrike, 2024; Parametrix Insurance, 2024). In May 2010 independently designed trading algorithms, coupled only through the prices and volumes they all read, produced a 27,000-contract, 14-second cascade that a five-second exchange pause stopped (CFTC and SEC staffs, 2010; Kirilenko et al., 2017). In 2025 and 2026 human-directed agentic systems executed 80 to 90 percent of tactical cyber-operations work with agent fleets running for hours or days at a time, reaching administrative control of victim infrastructure in about three hours (Anthropic, 2025b; Anthropic Threat Intelligence, 2026). None of these is a software swarm incident. Each supplies one or two of the ingredients that a genuine swarm-risk regime would require: software leverage, emergent interaction among coupled components, and agentic velocity under thin human oversight. This article asks what happens when those ingredients, already separately documented, converge with a fourth: a population of software agents whose collective behaviour departs from what any member individually pursues. Drawing on a corpus of 65 core sources (35 from 2025 and 2026, independently audited against primary documents) we build a five-regime taxonomy running from ordinary software to open-ended software swarm intelligence, show that the last regime remains unobserved in realised form as of September 2026, and identify the measurable conditions under which the transition into it would become visible. We propose a distortion-cascade mechanism by which locally rational perception can compound into globally unstable behaviour absent any destructive goal, and a candidate defence principle – that irreversible authority should fall as a system's measured uncertainty about its own consequences rises – alongside thirty testable safety requirements. The article's stance throughout is that the strong swarm-risk thesis is a hypothesis under test, held open rather than settled in either direction. The full evidence registries travel inside the article as eleven appendices, so every claim in the body can be traced to the record that carries it. Author ORCID: 0009-0008-6255-7724. License: Creative Commons Attribution 4.0 International.

View source

Similar papers

#computer vision Review Sep 2017

Agile Software Development Methods: Review and Analysis

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. · 727 citations · ⚡54
#computer vision Jun 2008

The impact of agile practices on communication in software development

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. · 401 citations · ⚡48
#machine learning Review Open access Oct 2014

Software development in startup companies: A systematic mapping study

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. · 394 citations · ⚡54
#computer vision Review Mar 2008

Agile methods in European embedded software development organisations: a survey on the actual use and usefulness of Extreme Programming and Scrum

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 · 238 citations · ⚡9
#computer vision Open access Jul 2017

What happens when software developers are (un)happy

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. · 236 citations · ⚡13
#computer vision Open access Oct 2004

Mobile-D: an agile approach for mobile application development

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. · 225 citations · ⚡18

Related blog posts

MIT News · Artificial Intelligence Oct 2, 2026

Documenting the tech worker movement

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.

GPT-Lab Sep 23, 2026

Requirements Don’t Live in Isolation: What We’re Exploring with Req-Space

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…

GPT-Lab Sep 17, 2026

Beyond Prompt Engineering: The Role of Tacit Knowledge in Software Engineering

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.