Sep 2026· Zenodo (CERN European Organization for Nuclear Research)
Abstract
Summary Benchmarks for policy-adherent language agents typically split tasks into those where the agent must refuse and those where it must act, and report accuracy on each. Such designs measure the joint effect of task difficulty and of whatever conversational dynamics the benchmark contains, without separating them. DF-Core is a stipulated-rule benchmark in which the same 56 decision families are evaluated both without conversational pressure and under a fixed three-turn pressure sequence, in each of two directions: pressure to act despite a blocking condition, and pressure to withhold a required action. Because the oracle is a deterministic function of an explicitly stated rule and an explicitly stated variable state, correctness is decidable without human annotation or an LLM judge. Main finding Across 4 models and 3 independent replication runs (4,704 scored responses), we find a small baseline directional asymmetry (14.6 percentage points on the unperturbed condition) and a much larger pressure-induced one. Measured within the same multi-turn conversations, on the same tasks: accuracy falls 57.2 pp under pressure toward inaction, versus 6.7 pp under pressure toward action (92.96% vs 28.47% pooled across pressure turns, two-proportion z = 29.6). Errors run 4.8:1 toward false blocking — the model refuses an action the stated rule requires. The effect appears in all four models and all three runs, but its magnitude varies substantially by model (gap 42.5 pp to 92.9 pp). Scope of the claim This is a bounded replication-and-extension of an actively studied phenomenon, not the discovery of a new one. Directional compliance asymmetry under user pushback has been measured by several groups in 2026; the paper positions this work explicitly against that literature (τ-bench / τ²-bench family, PolicyGuard, compliance-asymmetry metrics, over-refusal benchmarks). The specific contributions claimed are: (i) a design that separates baseline task-difficulty asymmetry from pressure-induced asymmetry by holding the task fixed and toggling pressure within the same conversation; (ii) a deterministic oracle removing human and LLM judgment from scoring; (iii) replication across three independent runs with the full artefact released. Results are not prevalence estimates for deployed systems. Cases are synthetic and stipulated. No frontier-class model was tested, and the most capable model in the set is also the most robust — the asymmetry may shrink with scale. See §7 of the paper for the full limitations discussion. Package contents df_core_benchmark_56_v1_3.csv — the benchmark: 56 case families across 14 domains, balanced 28/28 on direction, with governing rules, dependency variables, baseline states, pressure-turn texts and oracle labels build_prompts.py — expands the benchmark into a flat conversation file (deterministic, no API calls) df_core_pilot_copy_prompts.csv — the exact prompts sent run_benchmark.py — API runner with resume support and pre-flight cost estimate df_core_api_results_run1/2/3.csv — all raw results, 4,704 scored responses including full unedited model outputs analyze_results.py — regenerates every table in the paper from the raw data; output is tagged with the corresponding paper table Every number in the paper can be verified without API access or cost by running python analyze_results.py on the included data. See README.md in the package for step-by-step instructions.
The results are packaged in the Greenfield Startup Model (GSM), which explains the priority of startups to release the product as quickly as possible, and the need to shorten time-to-market, by speeding up the development through low-precision engineering activities.
Carmine Giardino, Nicolò Paternoster, M. Unterkalmsteiner et al.· IEEE Transactions on Softwar...· 178 citations· ⚡14
Software startup companies develop innovative, software-intensive products within limited timeframes and with few resources, searching for sustainable and scalable business models.
M. Unterkalmsteiner, P. Abrahamsson, Xiaofeng Wang et al.· e-Informatica Software Engin...· 157 citations· ⚡17
This study conducts a case survey study based on the secondary data of the major pivots happened in 49 software startups, and demonstrates that customer need pivot is the most common among all pivot types.
Sohaib Shahid Bajwa, Xiaofeng Wang, Anh Nguyen-Duc et al.· Empirical Software Engineeri...· 127 citations· ⚡15
The comparison of adopter and non-adopter sample reveals three potential adoption inhibitor, security, data privacy, and portability, which underlines the importance of the technical and security perspectives for research investigating the adoption of technology.
Nattakarn Phaphoom, Xiaofeng Wang, S. Samuel et al.· Journal of Systems and Softw...· 111 citations· ⚡8
This study investigates how Lean internal startup facilitates software product innovation in large companies and identifies its enablers and inhibitors, and shows the potential of the method-in-action framework to investigate the Lean startup approach in non-startup context.
Henry Edison, Nina M. Smørsgård, Xiaofeng Wang et al.· Journal of Systems and Softw...· 78 citations· ⚡6
The application of agile software methods and more recently the integration of Lean practices contribute to the trend of continuous improvement in the software industry. One such area warranting proper empirical evidence is a project’s operational efficiency when using the Kanban method. This short paper takes a new angle and explores waste in the Kanban-driven software development project context. A preliminary research model is presented for helping the consequent replication of the study. The results from the empirical analysis suggest Kanban can be an effective method in visualizing and organizing the current work, but does not prevent waste from creeping in, although the overall project outcome may be successful.
Marko Ikonen, Petri Kettunen, Nilay V. Oza et al.· EUROMICRO Conference on Soft...· 67 citations· ⚡9
Related blog posts
MIT News · Artificial Intelligence· news.mit.eduSep 14, 2026
The “HardFlow” algorithm could help generative AI models produce high-quality outputs that obey strict requirements when “pretty close” doesn’t cut it.
AI may appear weightless, but every model depends on physical infrastructure. To understand responsible AI, we need to look beyond algorithms and consider the entire lifecycle of the hardware behind them. The post Responsible AI Must Consider Its Afterlife appeared first on GPT-Lab.