How should a reseller preserve release identity across exports and MCP access?

Ask for a release manifest containing release_id, schema_version, policy_version and an inventory of delivered assets. Each asset can carry a checksum and format declaration, allowing a reseller to distinguish the agreed source package from its own transformed export.

When converting JSONL to Parquet, preserve stable record identifiers and record the transformation version. A row's identity should not depend on its position in a file, since sorting or partitioning can change that position without changing the routing case.

For public MCP access, a resource response can include release_id and schema_version alongside the requested records. Catalogue metadata can point to the same release identity, so a buyer inspecting an online sample can determine whether it matches a downloaded package.

Scope how corrections and incompatible schema changes will be identified before distribution begins. A pilot can test a loader against a deliberately changed schema and check that it reports the mismatch clearly. This gives resellers concrete evidence that their delivery channels preserve release boundaries rather than silently mixing assets.