Can a release include tolerances, write-off limits and approval rules?

**Can a release include policies, or only transactions?**

A release can include both. Policies matter because many allocation decisions are rule-bound rather than arithmetic.

**Which policies are typical?**

- Rounding or bank-fee tolerance, such as differences below a stated amount being absorbed. - Write-off authority by role, so a clerk, a team lead and a finance manager have different limits. - Hold rules: how long unidentified money sits as unapplied before it is escalated or returned. - Dispute handling: whether disputed amounts can be allocated to, or must be skipped. - Ordering rules: oldest first, specified invoice first, or payer instruction first.

**In what form do they appear?**

Both as readable text the agent retrieves with a `get_policy` tool and as structured thresholds the environment uses to accept or reject actions. Keeping the two aligned lets you test whether an agent follows the text, and lets the grader check against the thresholds.

**Can policies differ between tasks?**

Yes. Varying a tolerance or an authority limit across otherwise identical tasks is a clean way to test whether the agent reads policy or memorises a habit.

**Are the policies those of a specific business?**

No. They are generated, informed by direct observation of how businesses work, and shaped to your scenario. Inspect them for plausibility, and for any resemblance that concerns you, before use.