Age Is Not Evidence of Staleness: A Recency Decay Is a One-Rate Survival Model, the Rate Belongs to the Fact Rather Than the Clock, and the Silent Change Only a Rate Could Catch Is the Case No Agent-Memory Benchmark Scores
Oct 2026· Zenodo (CERN European Organization for Nuclear Research)
Information Retrieval and Search Behavior
Abstract
(c) 2026 Pranay Mahendrakar. Licensed under CC BY 4.0. Language agents that keep memories across sessions usually discount a record by how long ago it was written or last read. That discount was introduced to decide what an agent attends to, but it is increasingly read as a statement about whether a record is still true. This paper examines that second reading. Taken as a validity claim, an exponential recency term is a survival model with a constant hazard and a single rate shared by every record in the store. The time-sensitive knowledge literature, together with more than two decades of web-crawl measurement, contradicts the single rate: how fast an answer goes out of date differs by orders of magnitude across kinds of fact, and on the benchmark that splits questions by that rate, accuracy falls sharply with it. The paper then complicates the obvious remedy of attaching the rate to the predicate. Two published operationalisations of volatility, one by relation type and one by per-fact edit history, reach opposite conclusions on the same question, and within-class variation is large. It shows by standard derivation that pooling heterogeneous rates makes the pooled hazard fall with age, so a long-unchanged value is evidence of stability. Age since last confirmation and duration held before it therefore point in opposite directions, and a single timestamp cannot separate them. Finally, it observes that the systems and conversational-memory benchmarks located here invalidate a memory only when a later observation contradicts it. The case where only a volatility prior could help, a change the agent never hears about, is scored by no conversational-memory benchmark located here, and the one controlled study that withholds a change and budgets verification does not vary elapsed time or how volatile the fact is. It closes by stating a decision structure as an algorithm and specifying a benchmark that would settle the open parts.
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.eduOct 8, 2026