How should a reseller scope and license a first mismatch release?

Scoping starts with the decisions that shape the release: which domains, which record pairs, which causes, what form (dataset, task pack or simulated environment), and what your customers will do with it.

For a reseller there is an extra layer. You need to state how the material may pass onward: whether your customers can train on it, only evaluate with it, build derivatives, or redistribute it. These permissions are set in the licence, and they should be agreed before any listing is written. This article does not set terms; they are agreed in the scoping conversation.

Useful limits to settle early:

- **Generated status:** the output is generated, not real business records, and should be described that way in every listing. - **Coverage:** the release covers the domains and causes agreed, not every possible mismatch. - **Grounding and disclosure:** you or your customers should inspect these risks, and no listing should imply anonymity or compliance outcomes. - **Versioning:** how updates and corrections are identified and passed to existing customers.

A useful first step is a small sample or pilot on one domain and a handful of causes. It lets you check schema, label quality and licence fit before committing to a wider catalogue entry. Prices and timelines are discussed with MirrorFirm directly.