Sep 2026· Zenodo (CERN European Organization for Nuclear Research)
Abstract
A frontier model writes working code and solves competition mathematics. Ask the same model to reconcile three hundred invoices and it loses track of which ones it already processed. A spreadsheet has done that task perfectly since 1985. This article locates the difference, measures it, and names the one operation that closes it. Four reasons this is worth your time. The failure is everywhere and the cause was unnamed. Duplicate actions, stale numbers, a plan built on a fact that changed an hour ago — the industry treats these as separate bugs. They are one mechanism, and this article names it. The field is working on the wrong variable. Almost every 2025–2026 remedy is organised around context length — compress, summarise, evict, fold. This article shows, with the length effect switched off entirely, that length is a bystander. Version multiplicity is the variable. The fix is small, cheap, and measurable. Three operations. The first buys 92% of the available gain and costs less than the baseline it beats. Two standard rebuttals are already dead in the literature. A stronger model leaves the gap open — accuracy falls 92% to 77% on a frontier model, and the gap persists across scale. More memory yields zero recovery: 28% → 28% as memory grows proportionally. The design was specified in 1979 and set aside for tractability. Doyle’s truth maintenance system tracked why each held claim stands, so retracting a premise recomputed what depended on it. Both objections that retired it are engineering, and both are cheaper now. It can be wrong, and it says how. Six tests were committed before any run. Five ran. One refuted the author’s own explanation of the mechanism. The last step is the largest. Repairing the record drives superseded reads to zero and leaves task success flat. Carrying the retirement one step further — into the policy derived from the fact — moves success from 0.782 to 1.000. What this article is. A short, measured account of one mechanism. The experiment is small, the environment is synthetic, and every number is reproducible from the released code. Zero language models were run: that limit is stated here and again at the end. What it uses. The Architecture of Freedom Intelligence — a framework that asks what a system holds as possible before asking what will happen. Section 4 presents it, defends it against its strongest objections, and marks where its own tests located the boundaries.
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 an...
Marko Ikonen, Petri Kettunen, Nilay V. Oza et al.· EUROMICRO Conference on Soft...· 67 citations· ⚡9
Able to defeat top-ranked human players and more efficient than other models, the new system could help decision-makers in military maneuvers or business negotiations.
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.