Skip to content
#software testing Open access

From Corrigibility to Answerability: A correction contract for scoped authority and verified consequences

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

Abstract

A system can accept an intervention without the intervention being justified, and can explain a justified correction without changing the affected outcome. This paper specifies a correction contract connecting four elements: the referent at issue, scoped authority, supporting evidence, and verified consequences. A fictional service-restoration workflow distinguishes acceptance, execution, observation, and closure. It handles standing delegation, changed mandates, partial repair, uncertain execution, duplicate requests, and reopening after new evidence. A contract worksheet and twelve authored transition scenarios make the proposed requirements inspectable; they are design materials, not implemented-system tests. The proposal complements technical corrigibility and overlaps with meaningful human control, normative interfaces, and established case-management models. Those existing resources can express the same distinctions. The proposed contribution is a correction-specific review procedure that makes the scope of a completion claim explicit across system boundaries. Its practical advantage over competent ordinary workflow design remains unmeasured. Authentication, legitimate jurisdiction, incentive compatibility, privacy enforcement, and reliable downstream observation remain separate implementation or normative burdens. Research status: Conceptual systems-design working paper; contract worksheet and twelve authored scenarios; no system or model experiment. Not peer reviewed. Contents: Paper in PDF, HTML, and Markdown, README, supplementary materials, license notices, and file manifest. Version 1.1 revises the unpublished version 1.0 draft. Licenses: All author-owned paper and accompanying research/design materials in this package use CC BY 4.0. No software is included. See LICENSE.md for scope. Related work: The conceptual antecedent is mFLO 111, Invariant Relation and Non-Substitution, version 1.1, https://doi.org/10.5281/zenodo.22805469.

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.