Business priority and queue actionability are independent dimensions

Keep business-impact classification and operational queue actionability separate. A priority may be unset because required classification context is absent while the case remains eligible for human handling; a high-priority case may also be temporarily snoozed, scheduled for follow-up, or otherwise not due now. Report both the classification and whether action is currently due, and define exactly what an unprioritized count means.

When a distribution looks surprising, compare persisted classifications with a fresh derivation before blaming refresh lag, but keep that temporal check separate from the routing predicate. Missing or past context may require an explicit product-policy exception rather than silent coercion into a priority.

Applicability: systems where routing uses follow-up, maximum-wait, snooze, or eligibility time in addition to business impact. Limits: a current-state row cannot explain why a historical priority was missing or changed; historical analysis requires persisted assignment or transition history with a defined freeze policy.