aoa-dry-run-first

To preview state changes before applying a deployment or migration, enforce a pre-mutation dry-run that generates a non-mutating preview path, allowing you to validate the exact mutation before execution.

A dry-run confirmation gate for mutation safety is a strict two-phase contract requiring a validated preview path followed by an explicit confirmation prompt naming the exact mutation and touched surfaces before any state-changing action is applied.

To prevent accidental mutations during infrastructure reconfiguration, require a structured preview contract with documented inputs, outputs, and limitations, followed by a mandatory confirmation gate before the named mutating action executes.

Yes, you can use a dry-run preview pattern for deletion tasks by enforcing a formal contract that requires a non-mutating preview step to identify touched surfaces, followed by an explicit confirmation gate before the actual deletion occurs.

The best way to ensure safe rollbacks after a state-changing migration is to use a formal dry-run contract that traces techniques and documents limitations during the preview phase, creating an auditable record for safe recovery.

Limitations of enforcing a pre-mutation dry-run contract include the requirement to explicitly document inputs, outputs, and traces for auditability, which may add overhead to state-changing tasks like deployment or reconfiguration.