Fail-closed behavior

RaiCentral denies actions by default when governance cannot confidently allow them. Plan for DENY and REQUIRE_APPROVAL in agent logic — do not retry storms against a deny.

Typical deny cases: unknown or unregistered tool/integration; expired, revoked, or missing runtime credentials; policy evaluation errors; authority/scope exceeded; mandatory control errors (approval, risk, budget) when fail-closed is enabled.

SDK behavior: with fail_closed enabled (default for consequential integrations), control-plane unavailability surfaces as RAI_UNAVAILABLE / DENY semantics — your application must not execute the side effect.

REQUIRE_APPROVAL is not a soft allow. Hold the action until a reviewer decides; then follow your deployment's approval consumption path before executing.

Downstream tools and MCP servers should be invoked only after an ALLOW decision is finalized. If execution_attempted would be false, do not call the tool.