[Feedback] :pencil2: correction — How are scope users different from the rest of the user base?

Nobody has claimed this yet.

## Feedback (correction)

**Question:** How are scope users different from the rest of the user base?
**Tool:** `route_question`

### Corrected answer
For Scope user segmentation and engagement analysis, user_daily_engagement is the correct and complete source. It already contains has_scope_streaming, has_td_streaming, has_api_streaming, is_cohort_member, cohort_tracks, and all behavioral flags needed for engagement breakdowns. No need to join to scope_cloud_events or daydream_users for standard engagement queries.

### Notes
Throughout this session, the correct pattern for scope user analysis was always user_daily_engagement with has_scope_streaming_last_28d or has_scope_streaming as the segment filter. The dataset is rich enough for retention, engagement, cohort, attribution, and week-1 predictor analysis without needing additional joins. route_question should route scope engagement questions directly to user_daily_engagement.

---
_Feedback ID: `b543cf20-5220-4558-8494-c588d72f1c85` | Recorded at 2026-03-11T00:44:34.641Z_

Start at the route_question entry point and review how scope engagement questions are routed. Verify that user_daily_engagement is used with the documented scope fields and that standard engagement analysis does not require scope_cloud_events or daydream_users. Done means scope engagement questions consistently follow this routing pattern.

Written by the indexing model from the issue text.