A bounded agent request

1. Agent01AgentRequestThe agent submits a purchase request through its WAYLOCK identity: an amount and currency, a destination and a purpose.
2. WAYLOCK02WAYLOCKIdentityWAYLOCK confirms the agent is registered, verified and active in this workspace.Other path: If the agent is paused or revoked, the request does not proceed.
3. WAYLOCK03WAYLOCKPermission and limitsWAYLOCK checks the request against the current permission version: its scope, its ceiling and its time window.Other path: Outside the permission, the outcome is DENY. No executable instruction is produced.
4. WAYLOCK04WAYLOCKPolicyWAYLOCK evaluates the request under the agent’s effective policy version and records which version applied.Other path: If the permission is not bound to the agent’s effective policy version, the outcome is DENY.
5. WAYLOCK05WAYLOCKApproval thresholdThis request is above the approval threshold, so the outcome is APPROVAL_REQUIRED.Other path: Within the permission and below the threshold, the outcome is ALLOW without human review.
6. Person06PersonHuman reviewA person reviews the exact request: amount and currency, action, destination, source and agent. The decision is recorded.Other path: If the person declines, the decision is recorded and the request does not proceed. Once the permission or policy version has changed or the request has expired, no decision can be recorded and the request does not proceed. A changed amount, currency, payee or purpose needs a new approval.
7. WAYLOCK07WAYLOCKAuthorizationWAYLOCK evaluates the request again with the recorded decision. An authorized request is not a payment.Other path: Even after approval, the outcome is DENY if the agent or the permission no longer allows the request.
8. Not available yet08Not available yetExecutionExecution through a compatible rail is not available yet. An authorized request is not sent anywhere.

Illustrative request. No live customer, amount or provider is shown.