Approvals and escalation

Overview

An approval should identify the actor, action, target, scope, expiry, and approver. Broad conversational consent is not a durable execution grant.

• Require approval for missing or insufficient identity.
• Bind approval to the exact consequential action.
• Expire approvals quickly.
• Consume single-use grants once.
• Record denials and approval evidence.

Production checklist

• Keep credentials in a server-side secret store.
• Set explicit cost, latency, privacy, provider, and regional constraints.
• Capture route and evaluation evidence for incident review.
• Test timeouts, cancellation, fallback, and denied-policy paths before rollout.