Sep 2026· Zenodo (CERN European Organization for Nuclear Research)
Abstract
The failure modes of artificial intelligence systems deployed at the edge are not, at their root, failures of model quality, training data adequacy, or algorithmic design. They are failures of architectural composition: the failure to design for the constraints that edge environments impose as boundary conditions rather than as operational variables. This paper develops the doctrine that defines those conditions and specifies how architecture must be composed to operate AI at the edge without collapse. The paper's structural apparatus is a seven-layer architectural framework — Physical, Compute, Data, AI, Applications, Orchestration, Mission — against which every edge AI constraint, failure mode, and governance requirement can be located. Against that spine, the paper develops ten critical considerations, each with a five-part structure: description, layer impact, ramifications, consequences, and human governance role. Five cross-layer failure patterns characterize the architectural dynamics that arise when considerations interact under failure conditions. The Skipjack Protocol operationalizes the thesis as an executable doctrine across all seven layers and all ten considerations. The central claim is this: mission defines the architecture; environment constrains the architecture; data governs the architecture; autonomy executes the mission; human governance defines the boundaries of all four. Edge AI failures are architectural — not technical. Rights envelope: Citation permitted with full attribution. No reproduction, redistribution, or derivative works without written permission. AI/ML training use disallowed. See the citation policy at https://nonsequitur.tech/pubs/citation-policy/ for the full rights envelope. Canonical site URL: https://nonsequitur.tech/white-papers/edge-ai-doctrine/ Public archive: yks-pubs/papers/edge-ai-doctrine-v1-preprint.pdf
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 perception of the impact of agile methods is predominantly positive, and several challenge areas were discovered, but based on this study, agile methods are here to stay.
M. Laanti, O. Salo, P. Abrahamsson· Information and Software Tec...· 260 citations· ⚡20
Computer scientist, entrepreneur, and philanthropist will collaborate with the MIT Schwarzman College of Computing to advance AI and scientific discovery.
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.
MIT News · Artificial Intelligence· news.mit.eduSep 9, 2026
A weeklong summer workshop brought higher education faculty to campus to explore how AI and machine learning materials can be adapted for their classrooms.
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.