What delivery elements should a reseller request so releases flow into its catalogue?

A reseller's pipeline usually needs a release to arrive in a form that can be validated, previewed, entitled and updated without manual handling. Ask for these elements in the pilot.

- **Manifest:** one file listing tables, formats, checksums, `schema_version` and `release_id`, so ingest can verify completeness. - **Preview split:** a flagged subset of inputs you can show publicly, with labels and answer keys in separate files. - **Dataset card:** a plain-text description of domain, exception types, record types, generation method in general terms and known limits, which you can pass to customers. - **Licence file:** the onward-licence terms for that release, in a form your system can display and attach to each customer entitlement. - **Versioning:** a stable `release_id` per drop, with a change note describing which tables or tasks differ from the previous one. - **Validation report:** results of referential and amount checks, so you can compare them to your own. - **Environment package:** if included, a container or service description, a `reset(seed)` call, a state export format and a trace log format.

For MCP or API-style access, ask which tool actions are exposed, which are read-only, and whether the reset can be triggered per customer session without affecting others.

Agree these in the pilot, then reuse them for later releases so your ingest stays unchanged.