What should we request in a sample to decide whether to proceed?

Use this checklist to request a sample that supports an explicit pilot decision.

- State the agent behaviour the sample must reveal. - Request a complete episode with an inspectable starting state. - Ask for a documented unsuccessful path and its consequence. - Include an expected outcome with supporting rationale. - Request known omissions and unsupported business actions. - Identify the buyer's reviewer for operational plausibility. - Agree how findings will drive proceed, revise or stop.

A sample should answer a purchasing or engineering question. If the uncertainty is whether agents can recover from returned work, a collection of clean transfers will not resolve it. Ask for material that makes the uncertain behaviour observable.

The buyer's review should combine environment engineering and workflow judgement. A package can load correctly while representing an implausible business decision; a believable scenario can still lack enough state to execute.

Keep acceptance criteria specific to the proposed use. Record which findings require a correction, which are acceptable scope limits and which would make the pilot unsuitable. This avoids treating an attractive demonstration as evidence for every future environment requirement and gives a revision request a concrete basis.