The confirmation step isn't the safety net I thought it was

Building a natural-language command app for Android — say something, get a plain-English confirmation, approve it, it executes. The pitch is "nothing happens without your say-so."

Except I hit a gap: the world can change in the seconds between confirmation and execution. User approves "book 2pm with John," but by the time it fires, that slot's gone. Or approves a text to "Sarah," but Sarah's number just changed. The confirmation was correct when shown — it's stale by the time it runs.

Right now the fix is naive: re-check whatever the action actually depends on immediately before firing, and if something material shifted, don't silently proceed — kick it back to the user instead of guessing that the new state still matches their intent.

Curious how others building confirm-before-execute or agentic flows handle that gap. Do you re-validate right before the action, treat it as a transaction with rollback, or just accept the small window and move on?