{"slug": "expire-ai-approval-when-the-evidence-changes-not-when-the-screen-closes", "title": "Expire AI Approval When the Evidence Changes, Not When the Screen Closes", "summary": "A developer proposes versioned approval envelopes for AI actions, where consent expires when underlying evidence changes rather than persisting across a session. The system would require re-approval when material fields like the affected order set or total consequence change, showing a focused diff to the reviewer. The approach aims to prevent stale approvals from executing obsolete consent, with rules to distinguish material changes from noise.", "body_md": "A reviewer approves an AI-generated refund plan after seeing 12 affected orders and a $430 total. Before execution, the system refreshes its data: there are now 19 orders and a $760 total. The approval button remains green because the interface treats consent as a property of the session, not of the evidence.\n\nApproval should authorize one versioned action envelope:\n\n```\nplan_id: refund-batch-184\nplan_revision: 7\nevidence_revision: orders-snapshot-31\naction: issue_refunds\nscope: 12 orders\nmaximum_consequence: USD 430\nexpires_at: 2026-07-23T16:30:00Z\napproved_by: reviewer-id\n```\n\nIf material fields change, approval expires. The system asks again and explains why.\n\nPlace decision evidence before the action:\n\nA confidence percentage is not a substitute. It does not tell the reviewer which order is unsupported or what changed.\n\nNot every refresh should interrupt. Write rules before implementation:\n\n| Change | Approval |\n|---|---|\n| wording only | preserve |\n| source timestamp refresh, same values | preserve and update provenance |\n| affected set adds/removes an item | expire |\n| total consequence crosses threshold | expire |\n| execution tool or destination changes | expire |\n| stronger supporting evidence arrives | product-specific; show diff |\n| evidence becomes unavailable | expire |\n\nThe server—not only the browser—must compare the approved envelope with the execution envelope. Otherwise a stale tab can execute obsolete consent.\n\n``` php\nreview revision 7\n-> approve revision 7\n-> evidence changes to revision 8\n-> execution rejects stale approval\n-> card shows a focused diff\n-> reviewer can approve 8, edit scope, or cancel\n```\n\nThe diff should answer “what changed since I approved?” Preserve the old decision in audit history without implying the reviewer approved the new version.\n\nFor accessibility, move focus to a concise change heading only when execution is blocked; do not unexpectedly move focus for background refreshes. Make additions and removals available as text, not color alone. Ensure the affected set is keyboard navigable and summaries remain meaningful at zoom.\n\nThis is a design hypothesis until tested. Use scenario-based sessions with representative reviewers.\n\nAsk participants to decide, explain the authorized scope, respond to the change, and identify whether execution can proceed.\n\nStop a scenario if participants repeatedly approve an action whose changed consequence they cannot describe. That is a safety failure, not merely usability friction.\n\nDo not ask “Do you trust the AI?” Ask: “Which orders are authorized now, what changed, and what would stop you from approving?”\n\nWeak:\n\n```\nThe plan changed. Review again.\n```\n\nStronger:\n\n```\nApproval expired: 7 orders were added after your review.\nPrevious: 12 refunds, up to $430.\nCurrent: 19 refunds, up to $760.\nReview the 7 additions before approving revision 8.\n```\n\nThe stronger copy names the decision-relevant difference without claiming the new plan is wrong.\n\nVersioned approval does not make a harmful action safe, guarantee evidence quality, or replace authorization policy. Some emergency workflows need delegated thresholds rather than repeated prompts. Excessive invalidation can train reflex approval, so materiality rules require monitoring and revision.\n\nThe boundary question is specific: which missing or changed evidence must stop execution, and which update would only add noise?", "url": "https://wpnews.pro/news/expire-ai-approval-when-the-evidence-changes-not-when-the-screen-closes", "canonical_source": "https://dev.to/haaaaaley/expire-ai-approval-when-the-evidence-changes-not-when-the-screen-closes-2dg9", "published_at": "2026-07-23 11:54:56+00:00", "updated_at": "2026-07-23 12:01:00.485035+00:00", "lang": "en", "topics": ["ai-safety", "ai-agents", "ai-products"], "entities": [], "alternates": {"html": "https://wpnews.pro/news/expire-ai-approval-when-the-evidence-changes-not-when-the-screen-closes", "markdown": "https://wpnews.pro/news/expire-ai-approval-when-the-evidence-changes-not-when-the-screen-closes.md", "text": "https://wpnews.pro/news/expire-ai-approval-when-the-evidence-changes-not-when-the-screen-closes.txt", "jsonld": "https://wpnews.pro/news/expire-ai-approval-when-the-evidence-changes-not-when-the-screen-closes.jsonld"}}