Sep 2026· Zenodo (CERN European Organization for Nuclear Research)
Topic Modeling
Abstract
This paper proposes a research hypothesis concerning the possibility of identifying the point at which further iterative reconsideration of a task by a large language model ceases to produce substantial improvement. The central idea is based on an iterative tool that does not simply ask a model to answer the same prompt repeatedly. After each generated answer, the tool analyzes the result and constructs a new prompt containing the original task and the previous answer. The model then receives this new prompt, reconsiders the task, checks its previous solution, and generates a new version of the answer. The resulting process can be represented as: Q₀ → A₀ → Q₁ → A₁ → Q₂ → A₂ → … where Q₀ is the original prompt, Aₙ is the model's answer at iteration n, and Qₙ₊₁ is a new prompt constructed from the previous solution. The original prompt Q₀ remains unchanged and serves as the common reference point for evaluating every subsequent answer. For each answer, a measurable quantity Wₙ = W(Q₀,Aₙ) is proposed. The main hypothesis is that, for many tasks, Wₙ will initially increase as the model repeatedly revisits its solution, after which the rate of increase will decrease and eventually reach a stable plateau. This plateau is proposed as a possible indicator of a limit point of iterative self-improvement, beyond which additional computation provides diminishing returns. The paper does not claim that a higher internal score necessarily corresponds to a correct answer. One of the primary experimental objectives is to determine how strongly changes in Wₙ correlate with actual improvements in answer correctness. The proposed approach is presented as a research hypothesis for adaptive determination of reasoning depth and requires empirical validation across different models, task types, and methods for measuring internal confidence.
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
The ongoing work building a Raspberry Pi cluster consisting of 300 nodes is presented, with potential use cases being an inexpensive and green test bed for cloud computing research and a robust and mobile data center for operating in adverse environments.
P. Abrahamsson, S. Helmer, Nattakarn Phaphoom et al.· IEEE International Conferenc...· 110 citations· ⚡7
The results indicate that software developers are a slightly happy population, but the need for limiting the unhappiness of developers remains, and 219 factors representing causes of unhappiness while developing software are identified.
D. Graziotin, Fabian Fagerholm, Xiaofeng Wang et al.· International Conference on...· 84 citations· ⚡6
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.