Unsafe actions

Symptom

The workflow can change external state without adequate permission, preview, rollback, monitoring, or stop behavior.

Diagnose

For unsafe actions, identify the first point where evidence, context, deterministic validation, qualified review, or an external-action boundary failed. A more detailed prompt is not a substitute for repairing that missing condition.

Correct the workflow

• Lower autonomy.
• Constrain the tool contract.
• Add explicit approval and deterministic stops.

Confirm the fix

Repeat the original unsafe actions failure and related edge cases. Verify that the changed workflow detects or prevents it, preserves an escalation route, and stops safely when the required condition is absent.

For this unsafe actions correction, record what changed, which test proves the correction, who reviewed it, and what condition would reopen the issue. One successful example is insufficient; include the missing, conflicting, malformed, or adversarial inputs relevant to this failure.