What should a reseller request in a first pilot of a generated conditional decision set?

Keep the first pilot small and specific. Request the following.

- One domain, with a named role set and a short list of condition types. - Linked tables for decisions, conditions, evidence, holds, releases and events. - A set of short generated policy documents covering waivers and evidence validity. - A small task set with expected outcomes and grader output, if you plan to list evaluation material. - A schema file, data dictionary and version label for the whole package. - A written description of known limits and how grounding was handled. - Agreement on how defects are reported and corrected versions delivered. - A draft of the wording you intend to use in your listing, to confirm it matches what the data is.

Set success criteria before the pilot starts: which acceptance checks must pass, who reviews free text, and what decision follows. Treat the output as generated, and run your own risk review before any onward licensing.