Active meditators
0
Current concurrent meditation presence from the global monitor.
Public Analytics Surface
3/3 live public feeds connected for this render
Edge telemetry, made public
The live meditation pulse behind the Equanimity platform.
The ingestion pipeline, global monitor, and rollup APIs already existed. This page now turns that public surface into a readable live snapshot instead of leaving it hidden behind route handlers.
Live now
Public metrics from the active pipeline.
These cards are backed by the public analytics bindings already exposed in the app layer: global live stats, meditation rollups, and geographic presence.
Countries now
0
Distinct countries currently reporting active meditation sessions.
Streams today
1
Canonical stream starts aggregated for today.
Minutes today
0
Total meditation duration accumulated today across the public aggregate.
Geographic footprint
Which countries are meditating right now.
Country presence is coming straight from the global monitor feed.
Live country presence is not currently available.
Regional balance
Regional concentration without a chart dependency.
Regions are ranked by active meditators and rendered as proportional bars for a quick read.
No regional live data is available for this render.
Pipeline signals
Proof that the public site is wired into the real telemetry surface.
App opens
0
Application opens aggregated today from canonical event-family rollups.
Recommendation clicks
0
Recommendation clickthrough signal aggregated for today.
Content impressions
0
Content impressions recorded by the discovery surface today.
Buffering events
0
Buffering events recorded today, exposed for public operational transparency.
What changed
This page now closes a real analytics gap.
The public website already exposed analytics route handlers, but the home page never consumed them.
The new home page reads the existing public live stats, meditation rollups, and presence feeds directly from the shared analytics layer.
The admin-cms stream URL logging stub remains open and is tracked in the backlog because the canonical event contract still needs a proper event family for that case.