What licence questions should developers settle before using a generated routing pack?

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

Do not infer broad rights from access alone. Ask which licence applies to the sample and whether the intended use is covered. Material accessible through a website, download or public MCP server may need its applicable terms checked separately.

**Which uses should the request describe?**

Describe whether the team intends to fine-tune models, run internal evaluations, modify tasks, share material with contractors or distribute a benchmark. Also identify whether generated records will be embedded in a product demonstration or customer-accessible test environment.

**What about derived assets?**

Ask how the licence treats transformed datasets, task adaptations, evaluation outputs and trained model artefacts. These are questions for the agreed terms; their answers should not be assumed from the word ‘synthetic’.

**What should be recorded before work begins?**

Keep the release identifier, applicable licence, permitted users and distribution boundaries with the development project. Clarify any attribution or publication conditions that apply. MirrorFirm could scope a generated pack for the intended use, but the buyer should confirm those rights through the relevant agreement rather than rely on editorial descriptions.