What delivery contract makes a generated pilot reproducible?

Ask for a manifest that identifies `release_id`, `schema_version`, `policy_bundle_version` and the required environment adapter version. Each asset can carry a checksum so the builder can verify that local files match the package selected for a run.

The delivery contract should explain how records arrive, whether through downloadable exports or an agreed retrieval interface. A retrieval response should preserve release identity; fetching content at different times should not silently assemble incompatible versions into one environment.

Include an initial-state fixture and a reset contract describing which persistent stores must be restored. If the simulator uses randomness, record the generator version and seed alongside the fixture. A seed alone is insufficient when the generation logic has changed.

MirrorFirm could scope these generated assets and metadata for a pilot. The buyer can then load a pinned package, run its acceptance checks and retain the manifest with the evaluation results. Subsequent updates should identify schema or behaviour changes so builders can decide whether to migrate existing episodes or keep the earlier version for comparable runs.