What should I ask for in a sample or pilot?

A useful sample request is specific enough that you can judge the result in your own harness within a short review.

- A seed state in your preferred format, with a schema and a list of status values. - Tasks covering clean completion, a pending outcome and a referral, so each path is represented. - Expected end states per task, including acceptable variants and forbidden writes. - A rule file where each rule has an id, a plain-language statement and a check. - At least one task with a delayed consequence that exposes an earlier error. - A note on how structure and exceptions were informed, and what grounding or disclosure review you can carry out. - A statement of limits: what the sample does not cover, and what is not guaranteed. - A proposed next step after review, such as widening the domain or adding a second acting role.