What licence questions should a buyer resolve before using a generated complaint pack?

**Does buying a pack automatically cover every downstream use?**

The applicable licence needs to answer that question. Ask separately about internal training, internal evaluation, model development and distribution of material to other parties. Do not infer one permission from another.

**What changes when an agent can retrieve the records?**

Clarify whether the intended use includes exposing generated records through a customer-facing tool, public MCP server or downloadable export. Retrieval can distribute source material even when the development team thinks of the integration primarily as an evaluation system.

**What about modified versions and derived artefacts?**

Ask how the licence treats edited cases, translated records, added labels and task packs built from the supplied material. Identify any required notices and whether they need to travel with exported subsets. Model artefacts and redistributed record files may require different treatment in the agreement.

**What should the buyer bring to the discussion?**

Provide a concrete description of users, environments and distribution paths. MirrorFirm could scope generated material around those intended uses, but the agreed terms determine the permissions. Record the answers alongside the release manifest so implementation teams can apply them consistently.