What should we request in a sample before committing to a broader build?

Ask for a generated sample package that makes its design assumptions and review process visible to both business and engineering reviewers.

- Request the operational assumptions behind the scenario. - Ask for a manifest of included artefacts. - Require a list of unsupported actions and states. - Request explanations for the intended decision outcomes. - Identify generated content and any separate grounding material. - Agree how defects and ambiguities will be recorded. - Define the evidence needed to accept the sample.

A useful review begins with a manual walkthrough before connecting an autonomous agent. A business reviewer can check whether the policy interpretation is coherent, while an engineer checks whether every required action has a defined result. Their findings should refer to the same records and assumptions so disagreements can be resolved precisely.

Grounding and disclosure risk should be inspected where relevant; generated output does not remove that review need. The sample should also state which conclusions cannot be drawn from its limited scope.

This gives the next discussion a concrete basis: correct a contradiction, add a missing action or extend a supported branch, rather than request a larger collection without understanding its behaviour.