Can generated packs include different policy variants for the same handover?

**Can a release contain different operating policies?**

A buyer can ask for generated policy variants that govern the same underlying case structure. In retail operations, one policy may allow a store manager to refer a damaged return directly to inventory control, while another requires a quality review first.

**What would change in the records?**

The case facts can remain fixed while `policy_variant_id` identifies the applicable rule set. Expected actions and explanations must change with the policy. This supports tasks that require reading the supplied rules rather than relying on a familiar process pattern.

**Can customers combine the variants?**

They can use them together if every task clearly identifies its governing policy. Removing that identifier would create ambiguous supervision, because different answers could each be valid under different rules.

**What should a reseller request?**

Ask for variant definitions, applicability conditions and an explanation of which decisions each variant changes. Do not market a generated policy as legal guidance or an organisation's actual procedure. Its role is to establish the operating rules of the licensed task or environment and make the expected behaviour inspectable.