What should an environment builder include in a sample request?

Use this checklist when requesting a sample so the generated material can be assessed against your intended environment rather than judged on appearance alone.

- Describe the agent interface you intend to use, including whether actions arrive through tool calls, forms or a constrained command surface. - State whether other roles act through scripted responses or separate agents, because that choice changes how approval conversations must be represented. - Identify the interaction depth you need, distinguishing a single correction request from a session that carries several related requests forward. - Request a readable walkthrough of one successful run, with the business reason for each action and the state change it produces. - Ask for a statement of simplifications, including business processes represented as fixed inputs rather than simulated decisions within the sample. - Specify which artefacts your reviewers need to inspect locally, such as policy text, action traces and a human-readable view of account changes. - Define the decision the sample will inform, such as runtime compatibility or task suitability, so follow-up work addresses an identified uncertainty.