When approvals are required
Two conditions trigger a human approval request:-
Transaction amount exceeds the
human_approval_required_abovethreshold. The default is $2,000 per transaction. If the negotiated price on a renewal or any other procurement action exceeds this value, the policy engine blocks autonomous execution and generates an approval link instead. - All vendor switches. Any time the agent recommends switching from the current vendor to a competitor — regardless of transaction size — a human approval is mandatory. The Switch vs. Renegotiate Matrix always requires explicit human sign-off before any vendor migration can proceed.
The policy engine re-evaluates every approval request at the moment of
redemption, not just at creation time. If your policy changes between when a
link was sent and when a supervisor clicks it, the new policy thresholds apply.
How 1-tap approval links work
When the policy engine determines that human sign-off is required, Tavryn:- Generates a unique approval token using HMAC-SHA256 keyed against a server-side secret
- Embeds the token in a link pointing to
/approve/[token] - Delivers the link to your configured notification webhook (Slack, Discord, or a custom endpoint)
What the approval page shows
When your supervisor opens/approve/[token], they see a secure review card containing:
Deal Terms
Vendor name, service, category, the organization requesting approval, and the current “Pending Sign-Off” status.
Price Comparison
Baseline (original) price, negotiated price, annual savings in dollars, and percentage discount achieved.
Policy Compliance
Confirmation that the deterministic policy engine has evaluated the deal — including that the amount exceeds the auto-spend ceiling, which is why human approval is required.
Reviewer Verdict
The adversarial Reviewer Agent’s independent audit result:
AGREE, CHALLENGE, or REJECT, with rationale.Authorizing a deal
To approve, the supervisor clicks Authorize & Lock Escrow on the approval page. This action:- Sends an authenticated POST to
/api/approve/[token] - Triggers the policy engine to re-verify the deal against current thresholds
- Calls the Circle Developer-Controlled Wallets SDK to escrow the negotiated amount in USDC into the Arc EVM smart contract
- Notifies the vendor that payment has been committed
- Records the approval in the append-only audit log
Rejecting a deal
To reject, the supervisor clicks Reject Deal and is prompted to provide structured feedback: Reason codes available:
The supervisor can also add free-text notes. After clicking Confirm Rejection & Save Feedback:
- The transaction is blocked and the token is invalidated
- The rejection reason code and notes are saved to your organization’s override history
- Future negotiation prompts for this vendor incorporate the feedback — for example, if
rate_too_highis the reason, the agent anchors lower in its next opening position - The vendor’s reputation score is adjusted (decremented) to reflect the failed negotiation