What should a buyer specify when requesting a generated set-up release?

Being specific at request time reduces rework. This list covers what a generation brief for set-up should settle.

- **Domain and product mix.** For example, retail credit accounts, insurance policies or utility connections, and the share of each. - **Systems in scope.** Name the record types and tools your agent will touch, such as customer, account, service, task and note. - **Case mix.** The proportion of clean new customers, near-matches, reopened records, incomplete approvals and cases that should be refused. - **Policy set.** The rules that should govern branching, written in plain language and structured form, including any region or customer-type variants. - **Fault injection.** Which tool errors, timeouts and conflicting states to include, and whether they are transient or permanent. - **Expected outcomes.** Record-level end states and required handovers, kept in a separate answer key. - **Format and identifier style.** JSONL or Parquet, ID patterns, date formats and any field names you need to match. - **Splits and seeds.** Training, validation and held-out evaluation sets, with fixed seeds for repeatable regeneration.

Not every item needs a final answer on day one. A pilot can start with a narrow selection and widen once you have seen how the first release behaves against your harness.