What should a buyer request in a sample package?

Ask for a sample package that lets a technical reviewer complete and inspect the proposed task end to end.

- A plain description of the target model behaviour. - Generated input records with their supporting context. - A task prompt and required response structure. - An annotated reference response with reasoning. - An intentionally incomplete case and expected handling. - A statement of known exclusions and simplifications. - A manifest identifying the package's constituent files.

The reference response should show what a successful submission looks like, including how evidence is cited and how unresolved points are expressed. It should not be merely a polished narrative that leaves the evaluator to infer the actual acceptance criteria.

Known simplifications matter because a sample may omit parts of the wider business process. A logistics review task might begin after delivery reconciliation and therefore say nothing about how discrepancies were originally detected. That boundary should be visible during acceptance.

The buyer's first review can check whether the package is understandable without private explanations from its author. Any required clarification should feed back into the task contract so later users and automated evaluation systems receive the same essential context.