Large language model inference is usually optimized from the model inward: runtime systems predict future experts from hidden states, router scores, token statistics, or local activation correlations, while dynamic-depth methods decide which model layers can be skipped for the current input. This preprint proposes a different measurement level. A user who repeatedly interacts with a model generates a longitudinal sequence of prompts; those prompts, in turn, induce recurring expert and layer activation signatures. The activation sequence is treated not as the primary object to be explained, but as an observable projection of a recurrent user-specific information trajectory. If these projected trajectories contain stable transition structure, the next likely expert/layer demand can be forecast before the next prompt is fully processed, and in the strongest formulation before the next prompt is even submitted. The forecast can drive anticipatory memory placement: high-probability modules remain GPU-resident, alternative branches are staged in host RAM, and low-probability modules remain in colder storage. A wrong forecast need not change model semantics; it can degrade only latency if the native router or full execution path remains authoritative. The framework combines longitudinal activation graphs, contextual vector representations, probabilistic branching, and hierarchical memory scheduling. It is compatible with mixture-of-experts models, dynamic layer selection, and external graph/RAG memory, while requiring no semantic inspection of hidden representations. The paper formalizes the hypothesis, distinguishes it from current expert-prefetch and dynamic-depth work, proposes conservative and aggressive execution modes, and specifies an empirical validation protocol for user-specific routing graphs.
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 findings show that speed related agile practices are used to a greater extent in comparison to quality practices, and that software startups who adopt the Lean Startup approach do not sacrifice quality for speed more than other startups do.
Jevgenija Pantiuchina, Marco Mondini, Dron Khanna et al.· International Conference on...· 84 citations· ⚡4