What release metadata should travel with a complaint pack when a reseller repackages it?

Ask for a machine-readable release manifest alongside the generated payload. Useful fields include `release_id`, `schema_version`, `policy_bundle_version`, `asset_paths`, `checksums`, `generated_material_notice` and `licence_reference`. A licence reference identifies the applicable document; it should not be replaced by an inferred permission flag.

When a reseller converts JSONL to Parquet, filters records or renames fields, it can create a derivative manifest with `source_release_id`, `transformation_id` and a field mapping. Preserve stable case identifiers or supply an identifier map so customer-reported defects can be traced through the conversion.

MirrorFirm could scope these metadata requirements as part of the initial sample. The reseller can test ingestion by checking file integrity, required fields and referential consistency before publishing its own package.

Also define how a replacement release is distinguished from a format-only rebuild. A changed policy bundle may alter expected decisions even if the case text looks unchanged. Downstream customers need enough lineage to decide whether to rerun evaluations or retain an earlier version. This makes release management an explicit part of the onward product rather than an undocumented consequence of repackaging.