Skip to content
#software testing Open access

P13 pre-output technical amendment: OSF API version 2.2; unchanged scientific design

Oct 2026 · Open Science Framework

Abstract

This is a technical pre-output amendment of the approved P13 registration https://osf.io/pu3mb/ (registered 2026-10-04T13:29:38.207859Z). The original record and artifacts remain preserved. A pre-generation verification error was corrected by changing only two OSF request lines to pin API version 2.2, which returns an explicit UTC timestamp. Strict UTC validation remains unchanged. The original generator/protocol/manifest, actual API snapshots, official source references and exact production diff are retained in provenance. No scientific P13 answering output exists. The populations, contexts, model revisions, generation settings, scoring, H1/H2 rules and analysis are unchanged. Both registrations and this technical correction will be disclosed. The run window starts from this final technical registration. P13 tests whether correctness fragility under grade-preserving evidence exchanges predicts harmful losses after real AI system updates, and whether successor plurality voting reduces losses while preserving observed net gain. The incumbent is Qwen3-8B/BM25; updates are Qwen3-32B/BM25 and Qwen3-8B/bge_reranker_large. Confirmatory analyses use the immutable 629-query P5 estimation split (NQ 180, HotpotQA 175, FEVER 180, SciFact 94). The 420 qualification queries and full 1,049-query panel are descriptive. All 12,588 reconstructed contexts and 18,982 planned generations are fixed before P13 answering outputs. Prior P5b GPT outputs, qualification retrieval scores and parent/P7 results are known. Qwen3-32B previously supplied 1,278 semantic-equivalence judgments involving 250 estimation questions; this exposure is disclosed and is distinct from answering from the P5 contexts. No prior Qwen answering run on these contexts was identified in the recovered source set; the author reports no prior P13 answering outputs. This does not assert absence from pretraining. The amended protocol explicitly freezes a new verified context reconstruction rather than claiming recovery of the original context bytes, and declares both scoring corrections before outputs. MOCK tests and feasibility simulations supply no scientific P13 result. The attached PROTOCOL_P13_AMENDED.md is authoritative for frozen H1/H2 thresholds, event-count and identity gates, paired bootstrap, 14-day stopping rule, software/model pins, descriptive analyses and full reporting regardless of outcome. This is a labeled benchmark audit, not a label-free deployment or safety claim. The P13 folder is a distinct extension of the source project https://osf.io/9x35z/; the earlier P7 registration remains separate. Code frozen UTC: 2026-10-04T13:46:22.593905+00:00 PROTOCOL_P13_AMENDED.md SHA-256: da1a43bd8d1e2afe9e3198b6f4ce1bd6117a51a644ff0339386e88455677cefd SHA256SUMS.txt SHA-256: ae340becf2223d9c87b84c155d053d63629f4e1de60491298452274c2125b2c7 Amended contexts SHA-256: 6a6c12e02b4897571b6fa26b2ec9bf143667f3855529f1a2bef547c6bf872696 P13_UTC_Compat_Registration_20261004.zip SHA-256: 040af6edb2b554c492aefa995588396fdeecb0954362582d7aab6fdd6729f25b

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.