What licence questions matter when generated material becomes part of an environment?

**Does a dataset licence necessarily cover a hosted environment?**

Do not assume that it does. Ask whether the proposed licence covers serving generated records through an interactive product, including tool responses that users can retain. The applicable scope needs to be agreed rather than inferred from file access.

**Which uses should a builder describe?**

Describe internal training, evaluation, modification, use by contractors and inclusion in a customer-facing environment. If records or tasks will appear in downloadable exports or a public MCP server, identify those distribution paths explicitly. A hosted interaction and a downloadable copy can create different practical requirements.

**What about derived material?**

Ask how the licence would treat modified records, additional tasks, agent trajectories and published evaluation examples. Also clarify whether evaluator-only answer material can be shared with downstream users. These are questions for the proposed agreement, not statements of existing MirrorFirm terms.

**What is a useful first step?**

Prepare a short usage description showing who can access each asset and what they can export. Include any attribution, retention or onward distribution requirements the buyer needs. This gives the licensing discussion a concrete basis without inventing prices, contract terms or service levels.