What should an environment builder put in the first pilot brief?

Use the first brief to state what the pilot must help you decide, then connect that decision to generated content and observable agent behaviour.

- Name the operational uncertainty you want to resolve, such as whether agents can distinguish billing ownership from account-access ownership when customers describe both ambiguously. - Describe the agent’s starting knowledge and available tools, including any business vocabulary it already receives through system instructions or retrieval outside the supplied environment. - State which actions are consequential within your simulator and which are explanatory only, so a written recommendation cannot accidentally substitute for an executed transfer. - Identify the failure cases that matter to your product, distinguishing recoverable routing mistakes from actions that invalidate an episode or require immediate human review. - Assign review responsibilities for business plausibility, simulator compatibility and evaluation logic, so conflicting feedback has a clear path to resolution during sample inspection. - Specify the evidence needed for an expansion decision, such as reviewable traces across the selected boundary and a documented account of unresolved content defects. - Record exclusions and dependencies, including business rules your team must supply, so the pilot is judged against its agreed purpose rather than an assumed complete organisation.