What delivery contract should a lab request for reproducible ingestion?

Ask for a release manifest containing `release_id`, `schema_version`, `content_digest`, `policy_bundle_id` and `licence_reference`. Case identifiers should resolve within that release, and documentation should state whether identifiers persist across later revisions.

For downloadable exports, the manifest can list files, formats and checksums. For MCP retrieval, request equivalent release metadata in resource descriptions or responses. A client should be able to pin a release rather than silently consuming whichever content is newest. If pagination is used, specify stable ordering and continuation behaviour for the pinned release.

A pilot ingestion adapter can validate the manifest, load records and produce a local receipt naming the retrieved artefacts. It can reject unsupported schema versions before records reach a training pipeline. Changes to field meaning should be documented separately from additions of optional fields.

For an interactive environment, include the compatible tool schema and reset fixture identifier in the same experiment record. This connects the exported material to the environment that used it and gives reviewers a concrete basis for reproducing a disputed result.