Desktop Agent Execution Model
Context
The existing implementation registers two OS-level scheduled tasks (daily run and hourly refresh). Both assume that when the task fires:
The local source application is running on the machine.
The target company data file is currently open.
The local port/socket server interface is reachable.
Interaction with Change-Token Synchronization (Note 0001)
Under the change-token model (Note 0001), a missed or delayed run costs latency, never correctness. When the agent eventually runs, it queries "everything modified since watermark $N$," catching up completely regardless of gap duration.
Decision
Models Evaluated
Consequences
• Eliminates silent background failures when the desktop app is closed.
• Complemented by change-token sync (Note 0001) so delayed runs catch up completely.
• Server-side monitoring flags inactive installations if no sync lands within expected windows.
Alternatives & Future Roadmap
• Model A (Scheduled Background): Rejected due to silent failure modes.
• Model B (User-Triggered): Accepted for initial release.
• Model C (System Tray Hook): Deferred for future evaluation once baseline reliability is established.