Papers for

enterprise it teams

Papers whose findings have a practical use for this group, as judged from the abstract. Open a paper to read what it means in practice.

Agentic AI staleness driven by refresh schedule not cache age

ChurnBench: A Drift-Aware Benchmark Demonstrating That Refresh Scheduling, Not Cache Age, Governs Staleness in Agentic AI

Abstract: In production, agentic systems answer questions over data that lives in several places and keeps changing: licenses are reassigned, users offboarded, prices changed, contracts renewed. Existing retrieval benchmarks freeze the data, so they cannot ask whether an agent's answer is still true, only whether it found the right passage. We present ChurnBench, an open-source benchmark that generates a four-source enterprise data fabric as a timeline rather than a snapshot. Every change is written to an append-only ground-truth ledger, and gold answers are computed from that ledger, never from the live stores. An answer that was correct when its data was retrieved but wrong when evaluated is therefore detected and labeled a freshness error, distinct from a reasoning error; we validate this by resolving ground truth at both timestamps for every case reported. Using the instrument, we find that when a system refreshes on a schedule, cache age does not predict staleness. Across cache ages of 1, 14, and 28 days, freshness errors were 7, 4, and 4, because scheduled refresh bounds staleness by time-to-live, and no TTL lapse was observed in any window. A controlled ablation confirms the mechanism: disabling tiered refresh raises freshness errors from 4 to 45 at 28 days and leaves them identical at one day. The variable a drift benchmark should sweep is therefore TTL configuration against each entity's rate of change, not drift-window length. ChurnBench, the evaluation harness, and all per-error data are released open source.

Thu 10 SeptSoftware Engineering
The gist
Many AI systems answer questions using data that changes often, like prices or user info. The authors created ChurnBench, a new tool that tracks changes over time so it can tell if an AI's answer was once correct but became outdated. They found that how often the data is refreshed, not how old the stored data is, controls whether answers become stale. This helps developers focus on refresh timing to keep AI answers accurate.
Open 2609.11515v1

JarvisGUI enables coordinated workflows across multiple devices

JarvisGUI: Towards Cross-Device GUI Agents with Dynamic Task Composition

Abstract: Real-world GUI usage frequently involves workflows that span multiple devices and platforms, requiring the transfer of intermediate results, maintenance of shared state, and coordination across heterogeneous environments. However, existing GUI benchmarks overwhelmingly evaluate agents on single-device, statically defined tasks, thus leaving such cross-device capabilities largely unexamined, resulting in an overly optimistic assessment of agents' readiness for real-world usage. We introduce JarvisGUI, a dynamic benchmark that evaluates GUI agents on cross-device workflows requiring coordinated interaction across heterogeneous platforms, including Android, Windows, and Ubuntu. Specifically, JarvisGUI formulates GUI tasks as input-output transformations under a lightweight type system, which allows us to automatically compose multi-step, cross-device workflows and dynamically evaluate agent performance within a unified framework. By evaluating agents in virtual environments spanning multiple operating systems, JarvisGUI reveals that state-of-the-art open-source GUI agents struggle with the state-transfer awareness, cross-platform contextual reasoning, and long-horizon dependency management required for real-world workflows, exposing a critical capability gap invisible to existing benchmarks.

Wed 9 SeptArtificial Intelligence
The gist
Many tasks people do on computers involve working across different devices like phones, laptops, and desktops, but most testing for computer helpers only looks at one device at a time. The authors created JarvisGUI, a system that tests how well these helpers can work across several devices and operating systems by combining tasks in new ways. They found that current helpers struggle with remembering what happened on one device when moving to another and managing complicated, multi-step tasks. This shows that these helpers need to improve before they can help with real-world multi-device workflows.
Open 2609.10451v1