careful-delete

Destructive operations can be safeguarded with mandatory safety checks that assess blast radius, require explicit confirmation, and document authorization before proceeding. This prevents irreversible deletions by embedding confirmation workflows into your delete, drop, or destructive action commands.

Audit-ready documentation automatically records what was deleted, when, and who authorized it. Safety checks integrate confirmation and pre-mortem workflows to create an auditable trail of deliberate, recorded consent for any destructive action.

Yes. Safety checks apply across file systems, databases, and version control triggers. The workflow guides blast radius assessment and explicit confirmation whether you're deleting files, dropping database tables, or performing version control operations.

Pre-mortem and risk assessment workflows help you evaluate blast radius before confirming deletion. The safety cycle chains these deliberate steps—assess impact, obtain explicit confirmation, and document what happened—ensuring no destructive action proceeds unexamined.

Unguarded deletes risk accidental or reckless data loss. Safety-checked deletes enforce a multi-step workflow: blast radius assessment, mandatory explicit confirmation, and automatic documentation, transforming destructive operations from risky impulses into deliberate, auditable decisions.