Can we adapt a generated pack for customers with different follow-up policies?

**Can a reseller request customer-specific policy variants?**

A buyer can ask MirrorFirm to scope variants around different triggering conditions, escalation roles or required evidence. Whether the reseller may create and distribute its own variants is a licensing question to settle explicitly.

**Why is replacing the policy document insufficient?**

The policy may control task labels, permitted actions and terminal states. Changing a waiting condition can turn an expected reminder into an instruction to wait. Leaving the old answer attached creates contradictory training material even when every record remains syntactically valid.

**What should a variant request include?**

Specify the policy differences, the affected tasks and the expected treatment of existing evaluation results. Ask whether derived labels will be regenerated, reviewed or marked unsupported. Preserve the relationship between the base release and the variant so downstream customers know which policy produced their material.

**What is a sensible boundary?**

Begin with named policy parameters that the pack is designed to vary. A request to substitute an entirely different process should trigger a fresh scope discussion. This keeps customer adaptation concrete and avoids presenting an unreviewed derivative as equivalent to the original generated product.