How should a reseller scope a generated release that will be licensed onward?

Scoping starts with the claims you want to make to your own customers. Work back from those.

**Domain and variants.** Decide whether one domain is enough, such as lending, or whether you want several, such as insurance underwriting and utilities connections. Each domain brings its own roles, policies and exceptions.

**Depth.** Choose between decision and condition tables only, a full set with evidence, holds and policies, or a task pack and simulated environment. Deeper packages support evaluation; shallower ones suit narrower training uses.

**Formats and schemas.** Agree JSONL or Parquet, a schema file and a data dictionary, so your ingestion and your customers' pipelines match.

**Versions.** Ask how releases are versioned and how a corrected release replaces an earlier one, so your catalogue can track what each customer holds.

**Onward rights.** Raise early whether you may sublicense, to how many customers or categories, and what documentation and sample extracts you may pass on. Licence terms are agreed with MirrorFirm directly, and this answer does not set them.

**Limits.** The output is generated and synthetic. Plan inspection for grounding and disclosure risk, and word your listing accordingly.