Distributed agent workflows often cache delegated authority at tool gateways, allowing agents to act on behalf of users or other agents. When that authority needs to be revoked, the system can report the revocation at several points: when the issuer commits the change, when transport acknowledges it, or when the receiver persists it. According to the new arXiv preprint (2610.15991), none of these observations actually proves that revocation is complete.

The gap matters because a gateway that still holds a cached delegation may continue to act on stale permissions. The paper's title states the problem directly: revocation is not complete at receipt. To address this, the paper proposes an 'executable outcome contract' for distributed agent-tool gateways, which appears intended to define and verify the final outcome of a revocation rather than relying on intermediate signals.

This is a preprint, so it has not been peer-reviewed, and the abstract does not provide implementation details of the proposed contract. But the core claim is clear: in distributed agent workflows, reporting a revocation is not the same as ensuring it has taken effect.