What should I list when specifying environment state for a sample request?

When you ask for a sample, a precise state specification lets it exercise your harness instead of merely showing data shapes. Cover the following.

- Domain and payer type: utility, insurer, freight, clinic or professional services, and whether payers are businesses or individuals. - Record types you need linked: accounts, invoices or instalments, credit notes, payments, cases and notes. - Match patterns to include: one-to-one, one-to-many, many-to-one, short-pay, overpayment, duplicate and no-reference. - Remittance quality range: structured references, free text, truncated bank descriptions and missing detail. - Policy set: tolerances, authority limits, hold periods and dispute rules, in text and in thresholds. - Tool surface: which read and write actions your agents have, and what errors they return. - Reference outcomes: single accepted end state, accepted set, or constraints. - Initial state size per episode, so resets stay fast in your infrastructure.

Supply what you can and leave the rest open. A pilot is the place to settle the rest, including how closely the generated records should follow your own schema. The sample is generated material, so plan to inspect it for grounding and disclosure risk as part of the review.