Mar 2026· arXiv.org· Vol abs/2603.05069· 0 citations· 20 references
Computer Science
TL;DR
This paper describes how the three layers fit together and a working Flutter prototype on Android that combines them with an ephemeral cloud agent invoked only when the user asks, and a working Flutter prototype on Android that combines them with an ephemeral cloud agent invoked only when the user asks.
Abstract
Personal AI agents face a deployment paradox on mobile: persistent background execution drains the battery and conflicts with platform background limits, yet purely reactive agents miss time-sensitive obligations until the user remembers to ask. We present Jagarin, a three-layer architecture that resolves this through structured hibernation and demand-driven wake. DAWN (Duty-Aware Wake Network) is an on-device scoring engine that runs on the platform's periodic wake and combines four signals (duty-typed optimal action windows, predicted user engagement, the cost of delay, and cross-duty batching) with per-duty adaptive thresholds to decide whether a sleeping agent should stay silent, nudge the user, or offer escalation. ARIA (Agent Relay Identity Architecture) is a commercial email identity proxy that turns institutional email into structured duty records and routes messages by category, removing manual data entry. ACE (Agent-Centric Exchange) is a protocol for machine-readable communication from institutions to personal agents, intended to make email parsing unnecessary in the long run. DAWN and ACE are specified and evaluated in companion papers; this paper describes how the three layers fit together and a working Flutter prototype on Android that combines them with an ephemeral cloud agent invoked only when the user asks. Behavioural signals, thresholds and scoring never leave the device, and every record ARIA extracts is sealed to the device's public key before it is stored, so the relay holds only ciphertext it cannot read. Cloud model exposure is limited to parsing commercial email and to user-initiated escalation, which receives only the structured duty record.
This publication proposes a definition and a classification of agile software development approaches and analyses ten software development methods that can be characterized as being "agile" against the defined criterion.
P. Abrahamsson, O. Salo, Jussi Ronkainen et al.· arXiv.org· 727 citations· ⚡54
The study shows that agile practices improve both informal and formal communication, but indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication.
M. Pikkarainen, Jukka Haikara, O. Salo et al.· Empirical Software Engineeri...· 401 citations· ⚡48
The results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.
Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al.· Information and Software Tec...· 394 citations· ⚡54
The perception of the impact of agile methods is predominantly positive, and several challenge areas were discovered, but based on this study, agile methods are here to stay.
M. Laanti, O. Salo, P. Abrahamsson· Information and Software Tec...· 260 citations· ⚡20
Known for his clear and elegant writing style, Bertsekas shaped fields from control and optimization to large-scale computation and artificial intelligence.
MIT News · Artificial Intelligence· news.mit.eduJul 7, 2026
The professor of physics and inaugural director of the NSF AI Institute for Artificial Intelligence and Fundamental Interactions will lead LNS and continue his research in particle physics.
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.