Skip to content

Continuous Mission Intelligence: An Architectural Requirement for Coherent Command Across Heterogeneous Autonomous Systems

Sep 2026 · Zenodo (CERN European Organization for Nuclear Research)
Military Strategy and Technology

Abstract

Defense artificial intelligence has advanced quickly across four layers: operational data integration, command and control, fleet-scale coordination, and platform autonomy. This paper argues that the success of those layers has produced a distinct problem that none of them addresses. As reasoning distributes into sensors, platforms, software agents and command applications, a force can become locally intelligent without becoming collectively coherent. Continuous mission intelligence is defined as the ability of a distributed human-machine system to maintain a current and reconstructable mission state across time, systems and operating conditions, and to use observed consequences to improve the next operating cycle. Six leading systems and programmes are assessed against that definition: Palantir AIP and Gotham, Anduril Lattice, Shield AI Hivemind, the US Army NGC2 programme, NATO digital transformation, and DARPA DICE. Each addresses a major layer of the stack; none addresses continuity end to end. The paper then identifies seven mechanisms by which mission coherence fractures at machine speed, derives eight architectural properties a continuity layer must exhibit, argues that coherence requires federation rather than centralisation, and proposes a two-cycle evaluation protocol that tests whether a second operating cycle begins better informed than the first. This is a position and architecture paper. It presents no empirical validation, no deployment data and no performance claims. The author declares a competing interest as co-founder and Chief Executive Officer of Rebootix AI, Inc.

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

We use cookies to run the site and, with your consent, for analytics and to show ads. See our Cookie Policy.