Can generated tasks include policies that changed between the original entry and its correction?

**Can a release contain more than one policy version?**

Yes. A buyer can ask for generated policy documents with `policy_id`, `version`, `effective_from`, `effective_to` and explicit applicability rules. The task can include both the version used for the original posting and a later version visible when the correction is requested.

**Which version should the agent follow?**

The generated policy must answer that question. A utility adjustment policy might apply the rule in force on the service date, while a separate approval procedure applies at submission time. Selecting the newest document for every decision would then be incorrect.

**Can the task include uncertainty?**

It can include overlapping dates, an incomplete transition notice or a missing historical version. In those cases, the expected action may be to seek clarification rather than infer a rule from document order.

MirrorFirm could generate the policy history, affected entries and tasks that depend on those dates. Buyers should request an evaluator explanation of which date controls each decision. This makes temporal reasoning inspectable and prevents an unexplained answer key from hiding an arbitrary policy choice. Such material tests adherence to the supplied rules without asserting that those rules represent every organisation's practice.