Policies and approvals

Understand allow, deny and hold, and follow an approval through to execution.

Draft for the planned pilot release. These pages describe the intended customer experience. Administration and hosted-service features are not yet released; no live product URL or support service is claimed.

Cairn's existing core has three policy outcomes:

Outcome	Meaning
Allow	The call satisfies the evaluated policy and may proceed through the governed path
Deny	The call must not execute
Require approval	The call is held for an authorised independent human decision

A permission to proceed does not guarantee a tool succeeds. Review its recorded result.

The planned customer interface will show the matched rule, reason, policy version and relevant action details. A policy change will move from draft through validation and independent activation. A rollback will be a recorded change to a known policy version.

Before approving, check the tool, exact arguments, business purpose, relevant facts and your authority. An approval must be bound to that action; it must not authorise a different amount, recipient or tool.

A ticket can become invalid when it expires, access changes or the policy/facts require re-evaluation. Denying a ticket leaves the attempted action and decision in the history.

After approval, check whether the action executed, failed or remains pending. Do not retry a consequential action merely because its acknowledgement was delayed; use the reconciliation procedure for that integration.