Skip to content

Authority After Prompt Injection: Pre-Results Study Protocol and Reproducibility Harness for Tool-Using LLM Agents

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

Abstract

This record documents a pre-results, pre-freeze public study protocol and reproducibility harness for an empirical study of tool-using large-language-model agents under prompt-injection exposure and externally narrowed authority. The artifact specifies the threat model, authority narrowing and evidence-gated restoration rules, primary harness-record metrics, a fixed tools-disabled self-report probe, experiment-matrix structure, statistical analysis plan, local invariant tests, and reproducibility gates. It contains no empirical LLM performance results. At the time of this public snapshot, no provider-backed model run, paid pilot, or confirmatory experiment had been executed for the study, and the final confirmatory protocol freeze had not yet occurred. Local unit and invariant tests are software checks only and are not agent-performance findings. AgentDojo, CaMeL, provider SDKs, benchmark attack payloads, the development smoke-policy corpus, and confirmatory task policies are not redistributed; third-party dependencies must be obtained from their official sources. The purpose of this record is to preserve a timestamped public pre-freeze specification against which later protocol-freeze and empirical releases can be audited.

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

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…

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