Skip to content
#software testing Open access

Insight to Formal Structure: Discovery Provenance and Research Method (v1.1)

Sep 2026 · Zenodo (CERN European Organization for Nuclear Research)
Scientific Computing and Data Management

Abstract

Version 1.1 update — This revision adds bounded worked examples and reader-accessibility improvements to the September 27, 2026 v1.0 publication. It also adds an explicit disclosure of AI assistance in drafting, mathematical formulation/manipulation, computational checking, adversarial review, and research organization, together with clarification of the paper’s independent-research and peer-review status. The revision does not modify ASD/BAS v2.9 canon, establish new empirical validation, or alter the paper’s principal technical claims. Formal research rarely begins with its final variables. A question is noticed before it is typed; a recurring failure is recognized before its mechanism is separated; a resemblance is compelling before its evidentiary value is known. Applied Semantic Dynamics / Branch Admissibility System (ASD/BAS) developed through this pre-formal territory as well as through later mathematics, software, falsification, archive reconstruction, and external confrontation. This paper reconstructs that discovery process without granting discovery provenance evidentiary authority. It distinguishes author-reported intellectual motive from documentary historical evidence, and both from the later technical methods used to derive or test formal claims. The recurring developmental motions are not a single continuous genealogy. They include abstraction from narrative to structural relation; decomposition when one representation carries too many responsibilities; compression followed by collision and bounded repair; negative and failed implementation as information; and analogy used as a question generator rather than as proof. Recovered software history further shows that engineering frequently exposed underspecified distinctions before the later framework supplied cleaner formal boundaries. [2–4] A particularly important strand concerns structural analogy. The author reports that theological assumptions about lawful created order, and later physics/theology pattern-play, helped direct attention toward recurring questions involving authority, jurisdiction, burden, transfer, irreversibility, and consequence. Those sources are treated here as discovery provenance only. The project itself progressively imposed the rule that theology or analogy may generate a question but may not validate the answer. The eventual Structural Isomorphism Discovery Program (SIDP) formalized that firewall by separating structural observation, abstraction, provenance sealing, neutral hypothesis formation, independent attack, result freeze, and only then provenance reopening. [5,6] The contribution of this paper is therefore methodological rather than autobiographical proof. It shows how a research program can preserve the reasons a question became visible while subjecting the resulting claim to methods that do not care where the question came from. The governing distinction is: how the question was discovered ≠ why the answer should be believed.

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.