Revocation is not expiration
Expiration ends permission at a scheduled time; revocation ends it early; suspension temporarily blocks use. Each requires precise, verifiable semantics.
Propagation and consistency
Revocation must invalidate derived rights and caches within documented guarantees. For consequential actions, consult authoritative current state, check mandate version or epoch and fail closed if freshness cannot be established.
Race conditions, replay and recovery
Account for in-flight actions, retries, duplicates and subdelegations. Record effective time, decision correlation and observed result. Revocation does not automatically undo settled transactions.
Practical scenario
A user revokes an agent while checkout is underway. The next trust evaluation blocks use; an already authorized payment may require a separate cancellation process.
Controls and evidence
- Explicit ACTIVE / SUSPENDED / REVOKED / EXPIRED states
- Fresh version check before material actions
- Cache, retries and subdelegation handling
- Audit events without implying automatic reversal