Can a set-up release include policies, exceptions and environments?

**Can a release include the policies that govern set-up, or only the resulting records?**

Both. A release can include a policy set describing matching rules, evidence requirements, waiver authority and activation order, alongside the records those rules produced. That lets a buyer check outputs against stated rules rather than guessing at them.

**Can it include cases that go wrong?**

Yes. A pack could include duplicate parties, approvals with missing fields, conditions that conflict with a product rule, and requests withdrawn after approval. Scope the mix of normal and exceptional cases in a pilot.

**Can we get a simulated environment, not just files?**

A simulated environment could expose tool actions such as `search_party`, `create_account`, `attach_condition` and `open_task`, with state that resets between runs. Which tools and how much state to include is a scoping decision.

**Can records be shaped to a customer's industry?**

Domain vocabulary, product codes and role names can be adjusted, for example towards telecommunications, a clinic's patient registration, or a retail loyalty programme. Ask what can be varied and what stays fixed.

**Is any of it real?**

No. The output is generated. Because it is informed by direct observation of how businesses operate, ask to inspect how it was grounded and what disclosure risk remains before you license it onward.