Which policy dimensions should a generated configuration pack contain?

Specify these policy dimensions when commissioning generated configurations so each episode has explicit operational rules and variation changes the reasoning required from the agent.

- Define contact frequency limits across channels, including whether a recent manual call also prevents an automated reminder from being sent to the recipient. - State channel restrictions by contact preference and obligation category, with a clear fallback when the preferred route is unavailable for the current case. - Set authority boundaries for fee adjustments, deadline extensions and case closure, identifying which role can approve each change and what evidence is required. - Describe dispute handling rules that identify which obligations are paused, avoiding an account-wide suspension when only one item requires investigation by another team. - Specify priority rules for competing obligations, allowing operational importance to affect work selection without changing the underlying eligibility requirements for individual contact actions. - Include policy effective dates and migration rules, explaining how open cases behave when their governing configuration changes during an active episode of follow-up. - Define exception approval records with reasons and expiry conditions, ensuring departures from the standard process remain visible and cannot become indefinite permissions by accident.