Skip to content
#software testing Open access

Retained-State Middleware for Governed Selection: Terminology, Evaluation Boundary and Current CAAI Position

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

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

GPT-Lab Nov 3, 2026

Sovereignty Is the Option to Leave

Is your company’s AI sovereign? A practical guide for CIOs on AI vendor lock-in, EU Data Act switching, cloud sovereignty, and testing your exit plan before you need it. The post Sovereignty Is the Option to Leave appeared first on GPT-Lab.

Microsoft Research Blog Oct 30, 2026

From synthetic enterprise data evaluations to real Microsoft Copilot AI confidence

Evaluating Microsoft Copilot at enterprise scale requires test data that captures the full complexity of real organizations, yet real enterprise data contains sensitive information that cannot be used for evaluation under any circumstances. The post From synthetic enterprise data evaluations to real Microsoft Copilot AI confidence appeared first on Microsoft Research.

Microsoft Research Blog Oct 29, 2026

Microsoft Research Focus – Edition #97

Host Sowbhagya Suresh shares some of the latest news and cutting-edge research from across Microsoft—from understanding the challenges facing coding agents to uncovering how people use AI at work and improving extended-range weather forecasting. The post Microsoft Research Focus – Edition #97 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.