How can resellers preserve release identity across downloads and MCP listings?

Ask for a machine-readable manifest that can accompany each delivery route. Useful fields include `release_id`, `schema_version`, `asset_id`, `asset_digest`, `generated_origin`, `licence_reference` and `task_family`. A reseller transformation can add `derived_release_id`, `source_release_id` and a description of the applied changes.

The same release identity can appear in a catalogue listing, a downloadable archive and an MCP resource response. This lets a customer determine whether two access routes expose the same material. A digest can identify exact file contents, but it does not establish rights or validate the operational quality of those contents.

A pilot could test an import that validates the manifest, resolves task-to-asset references and rejects missing required components. It could also check that the public description still identifies the output as generated after the reseller adds its own product title.

Keep licence references connected to the applicable agreement rather than inventing permissions through metadata. Before exposing a public MCP resource, confirm which assets belong in that delivery scope, particularly reference answers. This makes technical publication a controlled expression of the agreed product boundary.