Second-Screen Broadcast Synchronization and Live Web Polling Framework

Role: Lead Frontend Real-Time Systems Engineer with deep expertise in WebSocket mesh networks and broadcast synchronization.

Context

• Broadcast Entity: {{broadcast_network}}
• Real-Time Communication Engine: {{websocket_gateway_engine}}
• Client UI Framework: {{frontend_ui_library}}
• Master Timecode Source: {{sync_timecode_source}}
• Peak Transaction Burst: {{expected_burst_transactions}}
• Content Moderation Architecture: {{moderation_pipeline}}

Task

Produce a resilient second-screen broadcast synchronization and live polling framework for {{broadcast_network}} that maintains sub-second interactive sync with {{sync_timecode_source}} while processing {{expected_burst_transactions}} on {{frontend_ui_library}}.

Method

1. Establish time-drift compensation algorithms pairing client system clocks with {{sync_timecode_source}} over NTP/WebRTC data channels.
2. Architect a bi-directional event bus through {{websocket_gateway_engine}} to fan out broadcast trivia, live polls, and viewer reactions.
3. Formulate client-side write-behind queuing and optimistic UI updates to sustain {{expected_burst_transactions}} without UI freezing.
4. Design server-side traffic shedding and delta-compression protocols to preserve message throughput during viral voting spikes.
5. Integrate interactive payload filtering with {{moderation_pipeline}} before public stream aggregation.
6. Structure a seamless fallback mechanism to Server-Sent Events (SSE) and HTTP/3 long-polling if WebSocket connections degrade.
7. Detail state-reconciliation logic for viewers joining mid-broadcast or recovering from brief network disconnects.

Constraints

• MUST maintain client UI interactivity at a minimum of 60 FPS on mobile browsers during peak inbound message bursts.
• MUST NOT broadcast unmoderated freeform user submissions that bypass {{moderation_pipeline}}.
• MUST synchronize interactive cues within 250ms of {{sync_timecode_source}} across 95% of active web clients.
• Network reconnection routines must utilize randomized exponential backoff to prevent thundering herd crashes.

Output format

1. Synchronization Protocol Spec: Drift calculation mathematical model and clock-alignment handshake.
2. High-Throughput Event Lifecycle: Ingestion, buffering, aggregation, and broadcast topology (max 300 words).
3. Reconnection and State Recovery Matrix: Table defining disconnect durations, cache strategies, and reconciliation actions.
4. Moderation and Rate Limiting Architecture: Structural rules for inbound vote and comment throttling.

Self-review

• Verifies that optimistic UI updates on {{frontend_ui_library}} accurately reconcile with delayed server confirmations.
• Confirms {{websocket_gateway_engine}} failover does not drop active user vote tallies.
• Validates timecode parsing integrity when broadcast video latency varies across regional distributions.