What should an environment builder put in a sample request?

Use this checklist to write a sample request that tests fit against your intended environment, with explicit assumptions that can be checked during technical review.

- Describe the agent's intended role and existing tool capabilities, identifying which review actions it should perform directly and which require another role's response. - State the business question the sample must resolve, so acceptance depends on useful decision behaviour rather than the apparent richness of generated documents. - Identify deployment constraints such as offline execution or restricted dependencies, allowing the proposed sample to fit the environment where it will actually run. - Specify language and localisation requirements, including Australian date presentation and business terminology where these affect how agents interpret records or formulate requests correctly. - Describe accessibility needs for observations, including whether attachments must have machine-readable text and whether visual layouts carry information essential to the review decision. - Request an inventory of intentional simplifications, enabling your team to judge whether omitted behaviour would materially alter the capabilities you intend to evaluate. - Nominate the evidence needed for a buying decision, such as an executable walkthrough and inspectable failure trace, without assuming a delivery date or price.