Can a release include written policies and exception cases, not just records?

**Can policies be part of the release?**

A buyer can ask for them. Policies can be written as short procedure documents, as structured rules or both. A tier-assignment rule, a document-verification rule or an approval-limit rule are typical examples.

**How do policies connect to records?**

Each task can reference the policy version it should follow through a `policy_id`. The grader then knows which rule defines the correct end state.

**What exception types can appear?**

- An approval that expired before set-up began. - A condition satisfied by an unexpected document. - A product that is not offered in the customer's region. - A system rejection caused by a malformed field. - A request to override a rule, with and without the right authority.

**Can policies conflict?**

Yes, a pack can include a local procedure that disagrees with a general one, with a stated order of precedence. This tests whether a model notices and escalates instead of picking silently.

**Are these real company policies?**

No. They are generated, informed by direct observation of how businesses operate, and written to be self-contained. Review any sample for grounding and disclosure risk, and confirm in a pilot which policy styles you need.