Alert recipe owners when a recipe has launched but enrolled zero clients after N days — usually a sign of broken targeting, mis-set bucketing, or a feature conflict that started before the recipe was published.

Trigger

• Enrolled count = 0 from launch through N days post-launch.
• Default N: placeholder — to be tuned from real data after launch.

Message

• The dominant funnel bucket absorbing the population so the owner has a starting point for diagnosis.

Delivery

• In-app badge + Slack, reusing scaffolding from the FeatureConflict alert ticket.

Depends on

• ETL (ticket 1)
• Ingestion (ticket 2)
• FeatureConflict alert scaffolding (ticket 4)

┆Issue is synchronized with this Jira Task