What licence questions should an agent development team resolve before starting?

**Does obtaining a sample establish permission for every later use?**

A buyer should confirm the permitted uses rather than infer them from access. Reading a sample, incorporating it into training and redistributing it inside a product are different activities to describe in the licence discussion.

**Which development activities should be covered?**

Explain whether the team intends to fine-tune models, run internal evaluations, share tasks with contractors or let customers execute tasks through a hosted service. Ask how the proposed licence treats transformed records, derived task variants and retained evaluation traces.

**What about publication?**

Clarify whether task text, example records and evaluation outputs may appear in public reports or downloadable packages. A report that quotes complete tasks can distribute more of the underlying material than a report containing aggregate findings.

No particular permission should be assumed here. A useful first step is to provide a concise intended-use description, including who receives the artefacts and where copies persist, then obtain explicit confirmation of the applicable licence scope before broader use.