Skip to content
#software testing Open access

The Boundary of the Individual as an Authoritative Causal Present — An Architectural Hypothesis

Sep 2026 · Zenodo (CERN European Organization for Nuclear Research) · 2 citations

Abstract

This study analyzes the publicly disclosable requirements, prior work and evaluation plan for the functional composition B-Core = A-Core + Purple Box / Present. A-Core is a general cognitive and execution system that may also use memory, recurrence and parallel processing. Purple Box / Present is the undisclosed, history-dependent addition; its added role is a research hypothesis. The composition denotes a single B-Core instance. In the deployment examined, the private component remains in a habitat, and the system may use zero or more physical avatars. If connectivity is lost, only the A-Core functions actually deployed locally remain available; the local branch receives no permission to write directly to the central Present. The targeted narrative prior-work map connects conceptual questions of changing embodiment, distributed state authority, offline reconciliation, persistent agent memory and personal identity. A substantial proportion of the public requirements have known antecedents. A new name, a combination of partial mechanisms or an exact expression not established in this targeted review does not establish novelty. Whether the private mechanism is internally identical to or different from another mechanism cannot be determined from the disclosed functional role. The paper distinguishes identification, authority over state changes and continuity of cognitive operation. The uniqueness of committed states is a requirement, not an algorithmic property proved in the manuscript. A finite log may supply a counterexample, but by itself does not prove a general invariant. Physical event history, the accepted record and the permitted effect on the Present are separate objects of inquiry. The main empirical question is G5: what changes when the Purple Box is added to the same A-Core, and does it offer a practical advantage over the strongest technically sound alternative within the same total resource budget? The two comparisons address different estimands. During long-term closed-loop operation, subsequent memory and observations may be consequences of the intervention, so their forced identity cannot be required. The plan requires valid interventions, strong controls and prespecified endpoints. The contribution consists in clarifying compositional and permission boundaries, and organizing falsifiable subhypotheses and comparisons. The study does not present a working Purple Box implementation, a formal system proof or new experimental data. Novelty and added benefit: NOT_ESTABLISHED. The hypothesis is partially testable; full evaluation requires a concrete artifact, an external contract and a preregistered study. © 2026 Omri Bankuti. The public research document and its original figures: Creative Commons Attribution 4.0 International (CC BY 4.0). The undisclosed Purple Box / Present master: PRIVATE / All Rights Reserved. Any separately released public software or test harness: MPL-2.0. The precise scope of the three layers is specified in Sections 21–22.

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

MIT News · Artificial Intelligence Oct 2, 2026

Documenting the tech worker movement

Writing as a participant and researcher, PhD student JS Tan SM ’22 has co-authored a new book about the rise of tech worker protests and the employer backlash that followed.

GPT-Lab Sep 23, 2026

Requirements Don’t Live in Isolation: What We’re Exploring with Req-Space

Requirements in large systems rarely exist in isolation. Their meaning depends on the wider project context - other requirements, policies, decisions, tests, and implementation details. That becomes especially important when AI is used for review, because spotting a possible conflict or gap is only the beginning. ReqSpace explores how AI, visualisation, and connected project context can help reviewers understand those findings, trace the relationships behind them, and focus on the questions that…

GPT-Lab Sep 17, 2026

Beyond Prompt Engineering: The Role of Tacit Knowledge in Software Engineering

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.

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