Show reviewers the operation that will run
Build an action review screen around exact targets, changes, impact, expiry and provider evidence rather than an agent-written summary.
A reviewer should be able to answer three questions without trusting the agent's prose: what will change, where will it change, and what evidence will establish the result? Put those answers before the approve button.
Anlyon governed previews contain typed blocks for fields, text differences, impact and limitations. Secret references remain placeholders. Use that structured preview as the basis of review instead of rebuilding a second request from mutable client state.
Put the consequential fields together
| Field | Example question it answers |
|---|---|
| Environment and provider account | Is this test or production, and whose account? |
| Target resource and normalized input | Which payment, recipient or file changes? |
| Amount and unit | Is this $12.50 or 1,250 dollars? |
| Action version and expiry | Which definition runs, and until when? |
| Provider observation time | How old is the state shown during review? |
| Success condition and limitations | What will a confirmed result actually prove? |
For file updates, show the before-and-after text. For an email, expose recipients across to, cc and bcc. For a refund, make currency and minor-unit conversion explicit. A friendly summary can help orientation, but it should not replace these fields.
Keep decisions attached to the preview
Persist the preview identifier alongside the review state. If the user edits input, require a new preview instead of carrying the approval forward. If it expires, show that state and refresh deliberately. Never silently exchange the reviewed request for a newly assembled one.
Review is not completion. After approval, display pending, refused, unknown or the actual receipt grade as appropriate. For Resend, confirmed refers to the provider's send record, not delivery to the recipient's inbox.
Test with a deliberately misleading summary
Use safe fixture data where the agent summary says one recipient but the structured request has two. Confirm the screen reveals the discrepancy. Also test long targets, empty optional fields, expired previews and a changed action version. The reviewer must still be able to find the decision-relevant information.
Use preview block definitions and approval binding. For multi-reviewer workflows, see distinct approver identities.