Skip to content
MirrorFirm

What licence questions should a lab resolve before using a release?

Licence review should distinguish model training, internal evaluation, shared access and public release of examples or results, without assuming that one permitted use covers every downstream activity.

**Does access to a sample establish rights to train on it?**

Do not infer that from access alone. Ask which uses the applicable licence permits, including training, fine-tuning, internal evaluation and retention of derived artefacts. MirrorFirm's generated output remains a commercial product whose permitted uses need to be understood.

**What if several teams or external collaborators need access?**

Describe the intended access pattern and ask how it is covered. Internal availability, contractor access and redistribution to another organisation are different questions. Avoid assuming that downloading a file resolves all of them.

**Can a lab publish benchmark examples or evaluation results?**

Ask separately about publishing aggregate results, quoting records and distributing task or environment files. Public access through an MCP endpoint should not be treated as evidence of unrestricted reuse rights.

**What should we provide before licence review?**

A concise use description can identify the intended model activities, access groups, publication plans and retention needs. These are questions to resolve in the applicable agreement, not statements of existing MirrorFirm terms or a substitute for reviewing them.

Describe intended uses explicitly and confirm the applicable rights before incorporating generated material into lab workflows.

Audience:
Model labs
Content type:
FAQ
Buyer question:
Scope and getting started

Content release: r-a220eb6e099b243b

More on Service routing