Yesterday’s approval is not today’s authority.
A purchase waits for manager approval. Before the approval arrives, the requester loses access or the quote changes.
All use casesMake the boundary explicit.
Retain the pending request and recheck current authority, policy, resource, expiry, quote and approval binding when the workflow resumes.
An unchanged authorized purchase proceeds. Revocation or a changed purchase produces denial or renewed review before dispatch.
Inspect the decision.
Resume an unchanged purchase with current requester authority.
Ready to evaluate
No external action
Select a variation and inspect the local example. This demonstration does not call a model or connect to a business system.
A workflow engine preserves state; it does not replace the authorization owner. Prior approval cannot override revocation.
The controls behind the workflow.
Explore the capabilities that compose around this task, rather than treating each step as a separate product.
Related ways to use DriftGate.
Improve the policy without breaking every agent at once.
A tighter rule prevents one misuse case but could also reject normal order questions across the support fleet.
Rotate a credential with its consumers in view.
A resource credential needs replacement, but several approved workloads depend on its protected reference.