Which licence questions should a lab resolve before using a generated release?

**Does access to a sample establish rights for every downstream use?**

The buyer should confirm the applicable licence rather than infer broader permissions from access. Sample inspection, model training, internal evaluation and redistribution are different uses to discuss.

**What should a lab describe when requesting terms?**

Explain whether the material will enter training runs, remain in a held-out evaluation set, support contractor work or appear in an externally accessible benchmark. Include intended use of transformed records, task derivatives and excerpts in research reports.

**What about public MCP access or downloadable exports?**

Confirm which content and usage rights apply to each delivery route. Public discoverability alone should not be treated as permission to redistribute an entire pack or publish restricted evaluation answers.

**What should remain separate from the licence discussion?**

Technical fitness and disclosure review still need inspection. Permission to use generated material does not establish that it fits a particular evaluation or resolves grounding and disclosure concerns.

A useful first step is a written usage map covering who will access the material, what they will do with it and which outputs they intend to share.