How should a reseller prepare a generated release for repeatable customer delivery?

Define a delivery manifest before building format adapters. Useful fields include `release_id`, `schema_version`, `policy_bundle_version`, `artefact_path`, `checksum`, `licence_reference` and `transformation_version`. The licence reference points to the applicable agreed document; the manifest itself should not invent permissions.

When converting JSONL records into Parquet tables, preserve identifiers, relationship cardinality, null semantics and ordered event arrays. Record any deliberate flattening or omission. A format conversion that drops an unresolved-state flag can change the answer to a task even when the customer-facing text remains identical.

Maintain a mapping between source fields and reseller fields, with validation results attached to the transformed package. Validate relationship integrity and compare representative task outcomes before delivery. Treat a changed field meaning as a compatibility issue, not merely a renamed column.

A useful first integration step is to convert a bounded sample and reconstruct it through the downstream loader. Inspect whether the same requests, dependencies and allowed outcomes survive that round trip. Resellers can then define an update process that identifies affected customers and artefacts without promising a release schedule or support level that has not been agreed.