What should I confirm in a release manifest before listing a dataset?

Ask for a manifest that makes the following explicit before you write a listing.

- **Table inventory:** each table or file, its primary key and its foreign keys, so buyers can see how cases link to escalations and decisions. - **Schema version:** a single version string that changes whenever a field, type or meaning changes. - **Rule versions:** the delegation matrix and policy document versions, with effective dates. - **Scenario parameters:** which domains, products, tiers and edge-case types the release covers, and which it does not. - **Task definitions:** task identifiers, instructions, allowed tool actions and how success is graded. - **Known limitations:** areas where text quality, coverage or realism is weaker, stated plainly. - **Licence file:** the permitted uses, including whether and how you may license onward, and any limits on redistributing samples. - **Generation notes:** a description of how the material was generated and what grounding it reflects, so buyers can assess disclosure risk.

If an item is missing, ask for it rather than filling the gap yourself. A listing written from a thin manifest tends to overpromise, and your buyers will find the gaps during their own checks.