Oct 2026· Zenodo (CERN European Organization for Nuclear Research)
Distributed systems and fault tolerance
Abstract
HEAIN-CORE-1.1 [5][6] showed that the seven core algorithms (P1–P7) of the HEAIN Core Protocol run correctly on real hardware. Promotion under Role Transformation (P6), however, was limited to one level per process lifetime. Once a node had been promoted to act for its parent, it stopped watching everything above that slot. If the grandparent then failed, only a sibling that had never been promoted could take over. This paper presents HEAIN Core Protocol 1.2 (HEAIN-CORE-1.2), which turns promotion into a multi-level chain through four mechanisms: (1) passive discovery of the next ancestor from heartbeat data that already flows, with no ancestor chain configured in advance; (2) an acting stack that keeps only the levels the node still holds; (3) handoff to siblings through explicit Raft membership change; and (4) leader-only ascent, which prevents split-brain between siblings. Each ascent still moves exactly one tier per P6 invocation, so the One-Tier-At-A-Time rule of HEAIN-CORE-1.0 [3][4] is preserved. All mechanisms were live-tested on a real seven-node topology on an HP Z840 over mTLS. A code review after testing found four defects, which were fixed and re-tested before the v1.2 tag. The paper reports seven remaining limitations, which define the agenda of HEAIN-CORE-1.3. Keywords: HEAIN Core Protocol, Multi-Level Promotion, Role Transformation, Cascading Failure, Raft, Fractal Governance, Edge Computing
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
Related blog posts
MIT News · Artificial Intelligence· news.mit.eduOct 8, 2026
Jennifer Neville did not want to go into computer science—but that’s exactly where she landed. Neville discusses the starts and stops that led to her professional sweet spot and her work identifying “surprising failures” making it hard for AI to handle complexity. The post What AI gets wrong and what failure teaches us appeared first on Microsoft Research.
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.