Four services on Google Cloud, one event bus, and a learning loop. Pick a flow below and press play to watch a request move through the system.
Each stage feeds the next. Tap a stage to play its flow.
Highlighted nodes are the ones the flow uses. Numbers show the order.
Pub/Sub decouples posting, analytics, coaching and rewards. Every consumer is idempotent: it writes processed/{eventId} first, so a duplicate delivery changes nothing.
Firestore drives the real-time UI. BigQuery holds every metric snapshot, so baselines, attribution, leagues and journeys run as SQL.
The numbers are computed in code, and Gemini explains them. Try the sliders.
Each post is compared to your own rolling median of the last 10 posts of the same format (black line).
Every Monday at 00:00 IST, Cloud Scheduler compares each creator's published posts with their planned cadence. Tap the weeks to try it.
The XP ledger is append-only (xp/{uid}/events/{eventId}), and the level is derived from total XP. If a publish fails because of us, the streak is protected.
| Pressure | Design choice | Google service |
|---|
| Fails | Automatic behaviour | What the user sees |
|---|