Personal AI agents face a fundamental deployment paradox on mobile: persistent background execution drains battery and violates platform sandboxing policies, yet purely reactive agents miss time-sensitive obligations until the user remembers to ask. We present Jagarin, a three-layer architecture that resolves this paradox through structured hibernation and demand-driven wake. The first layer, DAWN (Duty-Aware Wake Network), is an on-device heuristic engine that computes a composite urgency score from four signals: duty-typed optimal action windows, user behavioral engagement prediction, opportunity cost of inaction, and cross-duty batch resonance. It uses adaptive per-user thresholds to decide when a sleeping agent should nudge or escalate. The second layer, ARIA (Agent Relay Identity Architecture), is a commercial email identity proxy that routes the full commercial inbox -- obligations, promotional offers, loyalty rewards, and platform updates -- to appropriate DAWN handlers by message category, eliminating cold-start and removing manual data entry. The third layer, ACE (Agent-Centric Exchange), is a protocol framework for direct machine-readable communication from institutions to personal agents, replacing human-targeted email as the canonical channel. Together, these three layers form a complete stack from institutional signal to on-device action, without persistent cloud state, continuous background execution, or privacy compromise. A working Flutter prototype is demonstrated on Android, combining all three layers with an ephemeral cloud agent invoked only on user-initiated escalation.

翻译：个人AI代理在移动设备部署中面临一个根本性矛盾：持续的后台执行会耗尽电池并违反平台沙箱策略，而纯响应式代理则会错过时效性义务，直至用户想起询问。我们提出了Jagarin，一种通过结构化休眠和需求驱动唤醒来解决此矛盾的三层架构。第一层DAWN（职责感知唤醒网络）是一个设备端启发式引擎，它从四个信号计算综合紧急度评分：职责类型化的最优行动窗口、用户行为参与度预测、不作为的机会成本以及跨职责批量共振。它使用自适应每用户阈值来决定休眠代理何时应发出提醒或升级处理。第二层ARIA（代理中继身份架构）是一个商业电子邮件身份代理，它按消息类别将完整的商业收件箱——包括义务、促销优惠、忠诚度奖励和平台更新——路由至相应的DAWN处理器，从而消除冷启动并免去手动数据输入。第三层ACE（以代理为中心的交换协议）是一个协议框架，用于实现从机构到个人代理的直接机器可读通信，取代以人类为目标的电子邮件作为规范渠道。这三层共同构成了从机构信号到设备端行动的完整技术栈，无需持久化云状态、连续后台执行或隐私妥协。一个基于Flutter的工作原型已在Android上演示，该原型将三层架构与仅在用户发起升级时调用的临时云代理相结合。