What should a pilot request to MirrorFirm include?

A clear pilot request saves rounds of revision. Put these points in writing before the sample is generated.

- **Domain and record pairs:** named precisely, for example freight invoice against delivery record, not just logistics. - **Root causes:** a list of causes, including at least one case type where the correct action is to escalate or change nothing. - **Form:** dataset, task pack or simulated environment, and the file formats your platform ingests, such as JSONL or Parquet. - **Partitions:** separate training and evaluation sets, if your customers will do both. - **Licence permissions:** sub-licensing, training use, evaluation use, derivatives and redistribution, stated as what you need. - **Disclosure wording:** the text your listing will use to say the data is generated and to point buyers to grounding and disclosure checks. - **Review plan:** who inspects the sample, which defects count as blocking, and how corrections are returned. - **Versioning:** how updates and fixes will be numbered and passed on, agreed in writing.