Can a release include policies and exceptions, or only transaction records?

**Can a release include policies and exceptions, or only transaction records?**

A buyer can ask for both. Transaction records show what happened. Policies and exceptions explain why it was allowed, and they are what make a dataset useful for testing judgement.

Policy content can include:

- limits on deferrals, such as a maximum number per term - approval thresholds by role - grace periods and fee caps - rules for calendar edge cases, like a due date on a public holiday - conditions that force escalation, such as a prior broken arrangement

Exception content can include refused requests, reversed payments, duplicate requests, conflicting instructions between channels, and amendments that arrive after a payment has already cleared.

Each exception record can carry a link to the policy clause involved, so a grader can check whether the outcome matches the rule.

**Is the policy text taken from a real business?** MirrorFirm output is generated, informed by direct observation of how real businesses operate, but the policies in a release are written for the generated world. They are not any organisation's actual documents. Ask in a pilot how a given policy set was constructed, and have your own reviewers inspect it for grounding and disclosure risk.

For resellers, this means you can describe a release as records plus rules plus exceptions, and let your customers decide which layers they need.