Can a release contain different referral policies without mixing their answers?

**Can a generated pack contain more than one referral policy?**

Yes. A release could contain separate policy configurations for different service lines or operating contexts. One configuration might route a request directly to a specialist queue; another might require a frontline clarification before that transfer.

**How do the expected answers stay consistent?**

Each case can reference a policy_id and policy_version. Expected actions should be derived from that referenced version, with the relevant clauses included in the task context or made available through a policy lookup. A later version should not silently replace the basis of an existing answer key.

**Are these policy documents statements of current law?**

They should be presented as the operating rules supplied for the task. Any claim that a configuration reflects external requirements needs separate substantiation and a defined scope. Generated policy text should not be marketed as regulatory approval.

**What should a reseller retain?**

Retain version identifiers, configuration descriptions and the relationship between cases and rules. If customers receive only one variant, their export should still identify it. This makes differences between products explainable and prevents a combined catalogue from presenting incompatible routing actions as equally correct for the same context.