What licence questions matter when generated assets are embedded in an environment?

**Does licensing a dataset automatically cover a hosted environment?**

Do not assume that it does. Ask whether the proposed licence covers embedding generated records in a simulator, serving them through agent tools and allowing external users to interact with them. These are intended-use questions to resolve for the particular release.

**What about downloads and public interfaces?**

Describe whether users can export records, download the environment or retrieve substantial portions through an MCP interface. Access to individual responses can still expose much of a package over repeated sessions. Ask how those distribution paths are treated.

**Can we adapt the material?**

Clarify rights to alter schemas, generate additional variants, combine assets with other material and retain resulting derivatives. Also ask what applies to published evaluation traces, demonstrations and training outputs produced from interactions.

**What should we provide first?**

Prepare a short intended-use map covering internal development, external access, exports and retained artefacts. Ask MirrorFirm to confirm the relevant permissions and restrictions against that map. This scopes a commercial discussion without assuming particular contract terms. Generated material remains subject to the agreed licence; its synthetic nature does not by itself establish unrestricted reuse.