Description
Add a diagram (Mermaid, following the style of ONBOARDING_FLOW_DIAGRAM.md) showing the path from an in-app action to a dashboard number: module emits event → listener persists to AnalyticsEvent → nightly job rolls up → provider reads → API → frontend.
Why this matters
A visual data-flow diagram makes it much faster for new contributors to understand where their change fits in the pipeline.
Files to touch
backend/src/analytics/ANALYTICS_FLOW_DIAGRAM.md
Acceptance Criteria
Notes
This issue is part of the new analytics module effort (tracking, aggregation,
and reporting on player/game activity). Please keep new code inside
backend/src/analytics/ following the same module/controller/service/provider
layout used by existing modules (e.g. progress, streak, quests).
Description
Add a diagram (Mermaid, following the style of
ONBOARDING_FLOW_DIAGRAM.md) showing the path from an in-app action to a dashboard number: module emits event → listener persists toAnalyticsEvent→ nightly job rolls up → provider reads → API → frontend.Why this matters
A visual data-flow diagram makes it much faster for new contributors to understand where their change fits in the pipeline.
Files to touch
backend/src/analytics/ANALYTICS_FLOW_DIAGRAM.mdAcceptance Criteria
Notes
This issue is part of the new
analyticsmodule effort (tracking, aggregation,and reporting on player/game activity). Please keep new code inside
backend/src/analytics/following the same module/controller/service/providerlayout used by existing modules (e.g.
progress,streak,quests).