API usage
Anti-patterns
Never do this
Common mistakes that cause unsafe execution.
Fail-closed means execution must stop if safety state is unknown.
❌ Executing on WARN.
❌ Caching decisions and reusing them for new executions.
❌ Retrying blindly after validation failures.
❌ Defining policy client-side or branching on untrusted client input.
❌ Treating BLOCK as recoverable and executing anyway.
Correct posture
Safe defaults for production systems.
When in doubt, block execution and alert your team.
Store decision ids as audit references, not cached permissions.
Handle WARN with an approval gate, not a timeout-based auto-execute.
Disclaimer
This documentation is provided for general information only. It is not legal advice, not a guarantee of compliance, and not a substitute for your own security review. You are responsible for evaluating and meeting any legal, regulatory, and contractual obligations applicable to your use case.