How should a reseller scope and license a generated booking release?

Scoping a release for resale starts with what your customers will do with it, then works back to content, format and licence.

**Content.** Choose product types, the mix of clean and exception cases, whether policies and delegations are included, and whether the release is records only, tasks, or a simulated environment. A narrow, well-described release is easier to list than a broad one.

**Format.** Decide on Parquet for tables, JSONL for events and tasks, and the schema version your platform ingests.

**Licence.** Onward licensing is a term to agree, not something to assume. Ask what you may do with the release: list it, sublicense it, bundle it, adapt it, and for how long. Ask what disclosures you must pass on to your customers, including that the content is generated.

**Updates.** Agree how corrections and new versions are handled, and how your customers are told.

**Limits.** State what the release is not: not real records, not a compliance reference, and not evidence of anonymity or approval by any regulator.

A useful first step is a small sample with a defect-reporting path, reviewed against your intake checks. Prices, timelines and terms are set in the scoping conversation with MirrorFirm, so keep figures out of a listing until then.