Skip to content
#software testing Open access

C2Cognitive Core: Evidence-Bounded Persistent Cognition for AI Coding Agents

Aug 2026 · Zenodo (CERN European Organization for Nuclear Research)

Abstract

Persistent cognition changes the assurance requirements of AI coding agents because durable memories, lessons, reusable skills, structural observations, and derived knowledge can influence later engineering work after repository state, task context, or execution sessions have changed. C2Cognitive Core v1.0.0 presents a repository-resident cognitive-engineering system designed to preserve useful cognition without allowing persistence itself to become repository authority. The system separates physical ingestion, evidence admission, persistent cognition, continuity state, model-facing representation, and repository effects. Bounded Read v2 (BR-v2) constrains physical ingestion before semantic selection. Governed admission evaluates path containment, sensitivity policy, provenance, integrity, freshness, visibility, and applicable authority before information can influence durable cognitive state. Admitted cognition is represented through typed L0-L3 Memory, advisory Skills, source-bound Structural Candidates, derived Wiki state, and bounded Agent Loadouts. Handoff, checkpoint, and resume artifacts preserve work continuity but remain distinct from cognitive truth. Adaptive Context Representation Planning (ACRP) may change representation only after the semantic evidence set has been selected and frozen. Model, cache, routing, and adapter telemetry do not become evidence or write authority. Model and worker outputs remain proposals until current Goal state, lease/fence conditions, exact write scope, rollback basis, and other applicable authorization are revalidated near effect time. C2ModelAdapter v0.5.5 is kept at the host/runtime boundary rather than promoted into persistent cognition. The v1.0.0 release verification includes 59/59 registered checks for each English and Indonesian edition, 71/71 Core regression tests, the 74-test C2ModelAdapter collection, 30,005/30,005 router-combination simulations, 50,001/50,001 effective-route simulations, and a 524,288-state finite progress-liveness analysis with no invariant violation in the declared model. These results are bounded evidence for the executed surfaces and are not a claim of universal correctness, security, provider behavior, or defect absence. C2Cognitive's contribution is a practical cognitive-engineering discipline for making durable agent cognition explicit, inspectable, provenance-bound, freshness-aware, resumable, and authority-bounded during long-horizon AI-assisted software engineering.

View source

Similar papers

#computer vision Review Sep 2017

Agile Software Development Methods: Review and Analysis

Agile - denoting "the quality of being agile, readiness for motion, nimbleness, activity, dexterity in motion" - software development methods are attempting to offer an answer to the eager business community asking for lighter weight along with faster and nimbler software development processes. This is especially the case with the rapidly growing and volatile Internet software industry as well as for the emerging mobile application environment. The new agile methods have evoked substantial amount of literature and debates. However, academic research on the subject is still scarce, as most of existing publications are written by practitioners or consultants. The aim of this publication is to begin filling this gap by systematically reviewing the existing literature on agile software development methodologies. This publication has three purposes. First, it proposes a definition and a classification of agile software development approaches. Second, it analyses ten software development methods that can be characterized as being "agile" against the defined criterion. Third, it compares these methods and highlights their similarities and differences. Based on this analysis, future research needs are identified and discussed.

P. Abrahamsson, O. Salo, Jussi Ronkainen et al. · 728 citations · ⚡54
#machine learning Review Open access Oct 2014

Software development in startup companies: A systematic mapping study

Context: Software startups are newly created companies with no operating history and fast in producing cutting-edge technologies. These companies develop software under highly uncertain conditions, tackling fast-growing markets under severe lack of resources. Therefore, software startups present a unique combination of characteristics which pose several challenges to software development activities. Objective: This study aims to structure and analyze the literature on software development in startup companies, determining thereby the potential for technology transfer and identifying software development work practices reported by practitioners and researchers. Method: We conducted a systematic mapping study, developing a classification schema, ranking the selected primary studies according their rigor and relevance, and analyzing reported software development work practices in startups. Results: A total of 43 primary studies were identified and mapped, synthesizing the available evidence on software development in startups. Only 16 studies are entirely dedicated to software development in startups, of which 10 result in a weak contribution (advice and implications (6); lesson learned (3); tool (1)). Nineteen studies focus on managerial and organizational factors. Moreover, only 9 studies exhibit high scientific rigor and relevance. From the reviewed primary studies, 213 software engineering work practices were extracted, categorized and analyzed. Conclusion: This mapping study provides the first systematic exploration of the state-of-art on software startup research. The existing body of knowledge is limited to a few high quality studies. Furthermore, 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 Open access Jul 2017

What happens when software developers are (un)happy

The growing literature on affect among software developers mostly reports on the linkage between happiness, software quality, and developer productivity. Understanding happiness and unhappiness in all its components -- positive and negative emotions and moods -- is an attractive and important endeavor. Scholars in industrial and organizational psychology have suggested that understanding happiness and unhappiness could lead to cost-effective ways of enhancing working conditions, job performance, and to limiting the occurrence of psychological disorders. Our comprehension of the consequences of (un)happiness among developers is still too shallow, being mainly expressed in terms of development productivity and software quality. In this paper, we study what happens when developers are happy and unhappy while developing software. Qualitative data analysis of responses given by 317 questionnaire participants identified 42 consequences of unhappiness and 32 of happiness. We found consequences of happiness and unhappiness that are beneficial and detrimental for developers' mental well-being, the software development process, and the produced artifacts. Our classification scheme, available as open data enables new happiness research opportunities of cause-effect type, and it can act as a guideline for practitioners for identifying damaging effects of unhappiness and for fostering happiness on the job.

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

Mobile phones have been closed environments until recent years. The change brought by open platform technologies such as the Symbian operating system and Java technologies has opened up a significant business opportunity for anyone to develop application software such as games for mobile terminals. However, developing mobile applications is currently a challenging task due to the specific demands and technical constraints of mobile development. Furthermore, at the moment very little is known about the suitability of the different development processes for mobile application development. Due to these issues, we have developed an agile development approach called Mobile-D. The Mobile-D approach is briefly outlined here and the experiences gained from four case studies are discussed.

P. Abrahamsson, Antti Hanhineva, H. Hulkko et al. · 225 citations · ⚡18

Related blog posts

MIT News · Artificial Intelligence Aug 17, 2026

Q&A: Rethinking how innovation happens

In his latest book, Professor Eugene Fitzgerald examines the forces that turn breakthroughs into value — and why innovation resists simple formulas.