Apply rollout eligibility across the entire ownership lifecycle

A centralized rollout allowlist is not authoritative if older business filters survive in downstream layers. Apply the same eligibility decision at candidate selection, initial ownership, assignment, pre-send revalidation, inbound attribution, and operator projections; otherwise a case may be admitted then silently rejected, released, or hidden later. Keep lifecycle integrity checks—resolved state, idempotency, current ownership, recipient authorization, and provider receipts—separate from configurable business eligibility. Limits: action-specific safety constraints may remain code invariants when the rollout config does not grant that action.

Applies when: moving support or workflow admission policy from code constants into a central rollout service. Keywords: rollout eligibility admission ownership revalidation inbound projection policy