Can generated policies change which handover path is valid?

**Can a release include policies as well as case records?**

A release can include generated routing policies, acceptance requirements and exception procedures. For environment builders, those documents are useful when their conditions correspond to enforceable state transitions.

**What should a conditional rule look like?**

In utilities operations, a standard meter access problem can return to scheduling. A recorded site hazard can require review by a safety role before scheduling resumes. The rule changes the permitted path according to a case attribute, rather than assigning every access issue to the same queue.

**Can the environment include an exception?**

A task pack could include a documented exception process with a required justification and an authorised decision role. Invoking the exception should create a review state; it should not immediately bypass the underlying restriction.

**What should the buyer request?**

Ask for a mapping between policy clauses, triggering fields and permitted actions. Also ask how the environment resolves a conflict between general guidance and a more specific rule. Generated policy prose alone cannot establish consistent behaviour if the simulation applies different conditions. The text and transition logic need a shared, inspectable interpretation.