What should we ask to receive in a sample package?

Use this checklist to request a sample package that supports a concrete technical review and makes remaining delivery questions visible before a wider scope is agreed.

- Ask for a package manifest that identifies each file, its purpose and its version, so reviewers can establish exactly which material they inspected together. - Request setup instructions listing runtime dependencies and required credentials, including whether the sample can execute entirely with local substitutes for external business systems. - Include a walkthrough with expected observations at key steps, allowing a reviewer to recognise installation problems before interpreting them as failures of agent reasoning. - Ask for a coverage statement naming included business branches and known omissions, so a compact sample is not mistaken for a comprehensive domain model. - Request an explanation of generation assumptions and grounding boundaries, giving reviewers a basis for questioning business realism and inspecting potentially sensitive detail in outputs. - Specify a defect reporting format that links a concern to an episode and reproducible step, keeping proposed corrections concrete enough for both teams to assess. - Ask for delivery and version-change documentation requirements to be discussed explicitly, without assuming future compatibility, update frequency or support commitments from the sample alone.