Can customers receive different policy versions for the same correction case?

**Can the same underlying case support several policy variants?**

A task pack could pair a stable record set with alternative generated policies. One variant might permit a supervisor to approve a correction, while another requires an independent reviewer when the supervisor prepared the request.

**What needs to change alongside the policy?**

The expected decision, permitted action sequence and explanatory rubric must match the selected variant. Changing the policy text while retaining an old answer label creates contradictory training material.

**How does a customer know which policy governs the task?**

Each case can carry a `policy_version_id` and an applicability date. A policy bundle can define whether applicability follows the original transaction date, the request date or another supplied rule. That choice should be explicit rather than inferred from document ordering.

**What does this give a reseller?**

It supports a product that tests whether models read governing instructions instead of memorising case outcomes. Catalogue metadata should identify variants as related cases so customers can keep them together when constructing evaluation splits and avoid treating them as independent evidence of generalisation.