What should a sample request include before a pilot is agreed?

Use the sample request to make your inspection needs explicit, so the resulting generated material can support a practical discussion about suitability and remaining limits.

- Ask for a grounding description explaining which operational patterns inform generation and which details are constructed to serve the proposed task. - Request a disclosure-risk review approach covering distinctive combinations of details, rather than accepting synthetic generation as sufficient assurance on its own. - State required handling restrictions for your team, including whether sample material may enter shared development systems or external model endpoints. - Ask which requested variations the sample demonstrates and which remain untested, so attractive examples do not silently stand for broader coverage. - Identify the people who will review business plausibility and technical usability, with a clear way to record disagreements between those perspectives. - Request a list of known simplifications, especially omitted process branches that could affect how your production agent interprets an otherwise familiar task. - Define the decision the sample should enable, such as proceeding to a scoped pilot or revising requirements before further material is generated.