What usage rights should we clarify before integrating generated material?

**Does receiving a generated sample establish every usage right we need?**

Do not assume that it does. Ask which uses the proposed licence covers and which components it applies to. Records, task instructions, scoring definitions and environment code may need separate treatment in the delivery description.

**Which intended uses should we describe?**

Explain whether the material will support internal evaluation, model training, demonstrations or a hosted environment used by others. Identify whether users can download underlying records or only interact through tools. If you plan to publish task variants or evaluation traces, raise those uses explicitly.

**What about modifications and derived material?**

Ask how the proposed terms address edited episodes, new scenarios built from supplied schemas and generated outputs retained in training pipelines. Clarify attribution, redistribution and retention questions against the actual proposal rather than inferring permission from a file format.

MirrorFirm's commercial material is generated, synthetic output. That description does not itself settle licensing scope or disclosure risk. A useful first step is a written inventory of intended uses and recipients, which can guide the licence discussion without assuming particular contract terms.