Morrow: make priority
an explicit decision.

The everyday question.

An incoming request has a title and a priority, but the route into the queue is not always clear. This scenario gives priority a precise meaning: a number compared with a threshold that everyone can inspect.

The smallest useful rule.

Compare the request priority with an explicit threshold. Higher-priority work goes to review; the remaining work follows the standard path.

When priority is equal to or greater than four, the record follows Priority review. Lower priorities follow Standard queue. The exact boundary matters: a priority of four belongs in review, rather than being accidentally excluded.

What the local test tells you.

The output names the record, the selected branch, and the reason. You can change the inputs and run the test again to see the opposite outcome. No actual team, document, notification, or external queue is involved.

A pattern to take away.

A threshold is useful when it can be explained. Showing the comparison beside the route makes the workflow easier to discuss and reduces ambiguity about what happens at the boundary.

Original fictional example. No commissioned client, testimonial, or measured business outcome is implied.