How should an agentic system handle a task that requires both reversible and irreversible actions?
Answer: Classify actions by reversibility: perform reversible actions autonomously; require human confirmation before each irreversible action
Action classification is a key design principle: reversible actions (reads, soft deletes, staging changes) can be performed autonomously. Irreversible actions (hard deletes, sends, publishes, payments) require a human-in-the-loop confirmation gate. Uniform treatment is either too restrictive (blocking all autonomy) or too permissive (no safety on irreversible actions). Relying on rollback after the fact is poor design.