Aug 2026· Zenodo (CERN European Organization for Nuclear Research)
Abstract
Retained-State Middleware for Governed Selection defines a software category concerned with how retained history is allowed to influence selection among actions that a host system has already declared permissible. The central principle is: retained history is eligible evidence, not automatic authority. This technical note defines retained-state middleware, Retained-State Selection, governed selection, retained-state influence, reference and governed conditions, Decision Records and historical-truth constraints. It also records the current public engineering position of Collapse Aware AI™ (CAAI), developed by Inappropriate Media Limited. Core Gold is the frozen current commercial selector foundation. Evolution 2 is the richer continuity Engineering branch and is not represented as the finished Production commercial offer. Weighted Emergence Layering (WEL) and Active Information Weight (AIW) remain active concepts within the wider CAAI retained-state architecture, while private scoring implementation, thresholds, tuning and protected runtime mechanics remain proprietary. The commercial evaluation problem is deliberately bounded: a host supplies a real or anonymised decision problem, a permitted candidate set and relevant retained history. Reference and governed conditions can then be compared to determine whether retained history materially changes which permitted candidate wins, with replayable and inspectable evidence where supported by the tested system. This document is a terminology, evaluation and claim-boundary record. It is not an implementation specification, source-code disclosure, production API contract, claim of universal efficacy or evidence for a physical law. Collapse Aware AI™ can be evaluated independently as software through Retained-State Decision Audits, bounded Core Gold evaluations, buyer-specific pilots and integration work. Commercial enquiries: collapseawareai@gmail.com
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
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.
A path, a fence, a knot. MindTopo sets a new benchmark for testing how AI understands topological relationships and highlights new opportunities to strengthen spatial reasoning and planning. The post MindTopo reveals VLMs’ spatial reasoning abilities 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.