What files, manifest and licence fields should a pilot hand-off include?

Starting is simpler when delivery, versioning and licence data are specified as fields. A pilot hand-off can include the following.

- **Files:** cases.jsonl, ground_truth.jsonl (evaluation only), policies.json, and Parquet tables for larger ledgers or event logs, each with a schema file. - **Manifest:** a manifest.json listing every file with a version string, a checksum and the schema it follows. - **Partitions:** train and eval folders with disjoint case_id sets, so a customer cannot accidentally tune on evaluation cases. - **Licence file:** a machine-readable licence.json with flags such as sub_licensable, training_use, evaluation_use, derivatives_allowed and redistribution_allowed, set to what was agreed. - **Provenance note:** a statement that content is generated, plus guidance on inspecting grounding and disclosure risk. - **Environment package:** if requested, a definition of tools, argument schemas, reset call and audit log format. - **Defect log:** a simple JSONL where reviewers record case_id, defect type and status, which MirrorFirm can respond to in the next version.

Your platform can ingest the manifest and licence file to populate catalogue fields and enforce what customers may do. Keep pilot identifiers stable into the full release, so defects and fixes remain traceable.