Which licence questions matter when generated material enters an agent development pipeline?

**Does access to a generated sample establish permission for every later use?**

The buyer should confirm the applicable licence rather than infer broader rights from access. Sample inspection, model training and redistribution are distinct intended uses that should be addressed explicitly.

**Which uses should an agent team describe?**

Explain whether material will enter fine-tuning, retrieval indexes, internal evaluation suites, demonstration environments or externally shared failure reports. Include derived artifacts such as edited tasks, annotated traces and test cases extracted from simulation runs.

**What about external services and collaborators?**

Ask whether the proposed licence covers processing through the team's chosen model services, access by contractors and sharing across relevant entities. Describe the actual access pattern so the discussion concerns concrete use rather than an undefined internal-use label.

**What can be established before starting?**

A buyer can prepare a use map and ask MirrorFirm to confirm the permitted scope in the applicable documentation. No particular permission should be assumed from this checklist. Public accessibility through a website, export or MCP interface does not by itself answer every downstream licensing question.