Client data, principally supplied by mobile applications, provides:
This separates facts from interpretations and allows psychometric models to be updated without changing the mobile applications.
The consumer application and separate vendor application can use the same ingestion infrastructure, but they should authenticate as different principal types and use different authorization scopes.
Mobile events include
Converts the immutable mobile events into rebuildable session facts and versioned behavioral feature snapshots.
analytics_intake.mobile_events
│
▼
claim pending events under processor lease
│
▼
transactional event projection
├── analytics_fact.game_sessions
├── analytics_fact.game_objective_attempts
├── analytics_fact.group_session_participants
└── analytics_fact.mobile_event_projections
│
▼
refresh affected subjects
│
▼
analytics_model.feature_snapshots
This element publishes normalized mobile analytics into a distributed Citus warehouse, assigns every publishable fact to a trusted analytics zone, conforms shared dimensions, enriches geography from the existing read-only Census/BLS PostgreSQL warehouse, and synchronizes operational catalogs into warehouse reference tables.
This element requires three logical connections:
application_db: writable operational analytics database containing control data cumulative across elements.analytics_warehouse_db: writable Citus coordinator connection used for warehouse publication.public_data_warehouse_db: read-only normalized Census/BLS PostgreSQL connection already maintained by the platform.The Citus coordinator routes distributed writes to workers. The application publisher does not connect directly to individual shard servers.
All routes are internal and must be protected by existing service authentication and analytics-operations RBAC. Mobile and vendor application tokens must not be accepted.
This element converts the mobile analytics pipeline into a production-governed service. It adds retention and erasure orchestration, data-subject export, observability, service objectives, disaster recovery, capacity controls, security hardening, and release gates.