Can a release include policies, queue state and exceptions, not just cases?

**Can a release include policies and not just cases?** Yes, a buyer can ask for them. Policies can be written as numbered rules with conditions, required evidence, routing targets and exception paths. Tying each decision to a `rule_id` lets a grader check reasoning, not only the outcome.

**Can it include queue state?** A simulated environment could hold queues with cases already waiting, some ageing, some flagged, and workloads per team. That lets a task ask where a case should go given current load, not only given its category.

**Can it include exceptions?** Yes. Exceptions are often where the value lies: a late document accepted by an approver, a duplicate that is actually a legitimate second request, or a case that changes category after more information arrives. Each can carry the approver role and the stated reason.

**Can it include conflicting or outdated information?** A dataset can include submissions whose details contradict earlier records, or policies with effective dates so that the correct rule depends on when the case was lodged.

**Is any of this real business data?** No. The material is generated. It is informed by direct observation of how businesses operate, and a buyer should inspect a sample for grounding and disclosure risk before use.

**Is everything included by default?** No. Scope the layers you need in a pilot.