Skip to main content
Policy answers: what rules govern this action? A Policy defines the organizational business rules an Intent must satisfy. Policies are immutable and versioned — a given policy version’s behavior never changes after publication. If the rules need to change, a new version is published.

​
Policy Reference

Business Transactions don’t embed the full policy; they carry a PolicyReference that pins the exact version evaluated.
FieldTypeDescription
namestringPolicy name, e.g. vendor-payment.
versionstringSemantic version of the policy, e.g. 1.0.0.
schemaVersionstringSchema version the policy document conforms to.
{
  "name": "vendor-payment",
  "version": "1.0.0",
  "schemaVersion": "1"
}

​
Why immutability matters here

Because a Policy Reference pins an exact, immutable version, a Decision made against vendor-payment@1.0.0 today will evaluate identically a year from now — which is what makes Replay possible. Policy evaluation itself lives in the policy package; see Packages → policy.

​
Relationships

  • Policy is loaded and evaluated by the policy package during Decision generation.
  • Validating a policy definition (existence, schema) is exposed over the SDK/API as validatePolicy / POST /policies/validate — see REST API → Policies.