AUTO SUMO

Architecture and user flow · review information

One chat. One game state.

The viewer stays on YouTube. The operator controls an isolated application. Public information pages have no connection to production Studio or the game server.

Message-to-game architecture

  1. YouTube Live Chat
    Viewer posts a country choice.
  2. Official API → Reader
    One StreamList RPC at a time, using continuation tokens.
  3. Private Node game server
    Validate message, author, duplicate and voting window.
  4. Game output
    Eligible vote affects power; two renderers/encoders publish video to YouTube.

Operational flow: operator authorizes the owner's channel → prepares a broadcast → one reader supplies the game → status and quota are monitored → operator completes the broadcast and shuts down compute. Viewers do not authorize the operator application.

Separate recovery candidate

Batch and continuation are staged together in SQLite before delivery. Node acknowledgement removes the queued payload. Normal short EOF is handled by a bounded reconnect policy with durable quota reservation. Fully atomic game effect, idempotency and acknowledgement integration remains a release gate; the diagram is not a certification that every safeguard is deployed.

Observed connection behavior

Sequential clientRPC durations (seconds)Outcome
Adapted reference10.672 · 10.500 · 10.375Normal EOF, gRPC OK
Candidate10.734 · 10.422 · 10.375Normal EOF, gRPC OK

Continuation succeeded in four of four attempts. Both clients used the same Python/gRPC stack and network path. The cause of the short completions remains unresolved; this is not proof of a Google defect. No foreign-chat text or viewer identifiers are included here.

Review access

This page explains the system but is not an interactive replica or a full feature demonstration. No public demo account exists. Existing YouTube gameplay archives show rendered gameplay, not the full operator OAuth, revocation and data-deletion workflow. Credentials and production access must not be supplied as audit evidence.

Not ready for 24/7 certification. Project-wide API credential brokerage, atomic vote integration, retention/deletion across backups and a complete safe reviewer demonstration remain open. See Privacy Policy for the precise current limitations.