What should I ask for in a pilot sample for a booking environment?

Use this list when you request a first sample, and adjust it to your harness.

- State tables in the formats you can load, with a data dictionary covering types and nullability. - A task file with instructions, seed snapshots, scheduled events and allowed outcomes. - Expected end states or diff specifications for every task, including tasks that should end in an exception. - Policy documents referenced by tasks, with identifiers that match. - A few reference passing and failing trajectories, so you can test your grader. - A manifest listing files, schema versions and the generation seed. - A clear statement of how the sample was produced, what was reviewed, and what limits apply to its use. - The licence terms you will be asked to accept, in writing, before you load anything into production tooling.

Also decide your own acceptance checks before the sample arrives, and name who will run them. That keeps the pilot short and the result easy to explain to colleagues who were not involved.