Brief for the LEVEL call · Services contract with Go3
How Join in Live runs for Go3
Go3's live feed comes in, AI proposes fan games, a person approves them, fans play on their phones. All of it runs in AWS London.
3markets and languages: Estonia, Latvia, Lithuania
~2 sfrom Go3's broadcast to our system
~32 sbefore a streaming viewer sees the moment
~8 sfor the AI to propose a buff
0failed AI requests in a 12-hour live test
Stage 1Shadow tests
Private, nothing shown to fans
4 DecGo / no-go
Needs 4+ good live tests
Stage 2Live pilot
Real fans, limited scope
Stage 3Commercial
Full paid service
01
The service
Four steps, every match.
1Feed in
Go3 sends Sport 1 live: picture plus Estonian, Latvian and Lithuanian commentary.
2AI proposes
It listens to the commentary and drafts polls, predictions and quizzes in each language.
3Person approves
An operator sends, edits or skips each one. Auto Mode is optional.
4Fans play
Buffs reach phones live. Answers come back, leaderboards update.
EuroLeague on Go3 Sport 1: nowPremier League: from 21 Nov (stream lines due from Go3)ET · LV · LT, each written nativelyWho runs match night (Go3 or JiL operator) is still open
02
Architecture
Where each piece runs and how a moment becomes a buff on a fan's phone.
broadcast contentbuff ideasfan answers and results
Go3's stream is not recordedAudio becomes text and one picture every 3 seconds is taken. Nothing is redistributed.
One home: AWS LondonReceiver, AI producer, speech-to-text, database and live push all run in eu-west-2.
Locked-down feedSRT link, encrypted, accepted only from Go3's own IP address.
03
Tech stack
Standard, well-supported building blocks. All on AWS, managed with code.
eu-west-2 · LondonProduction region. A larger multi-region EU tier (for very big audiences) is in testing.
04
Data & privacy
Two separate flows: Go3's content, and fans' personal data. They never mix at the AI model.
Go3 content (commentary, buffs)fan personal datasupport access
Go3Controller
Owns the fan relationship and decides how fan data is used.
Join in LiveProcessor
Handles fan data only on Go3's instructions, under a data processing agreement (DPA).
Data
Where it goes
Kept
Go3 stream
Processed live in London
Not recorded
Commentary text
AI model, to write buffs. Providers don't train on business API data
Proposal logs, for quality
Fan account
Name, email, consent · London database
Agreed in the DPA
Answers and scores
London database · leaderboards and Go3 reports
Agreed in the DPA
Email address
Email service, for sign-in codes only
Delivery only
Sub-processors: AWS · OpenAI · Anthropic via Bedrock · SendGrid / SESNo names or emails sent to AI modelsdevBlink support from India = a transfer: needs safeguards (IDTA / SCCs)Retention, deletion and export at contract end: to agree
05
AI under control
The AI suggests. People and rules decide what fans see.
Human approvallive
Every buff is sent, edited or skipped by an operator.
Stop switchlive
Stop any buff, or the whole event, at once.
Decision loglive
Each proposal is stored with its reason and confidence.
Game statelive
Operator marks pre-game, live, half-time and final, so buffs fit the moment.
Manual fallbacklive
If the feed drops, the operator runs the game by hand.
Quality gatenext
Language lock per feed, no buffs from two-word fragments, confidence floor, duplicate filter.
Go3 can supply match context written by people who know the gameCommit to the process, not to perfect AI output
06
Service levels
The timing is why buffs never spoil the moment.
0 sMoment happens
+2 sJiL receives the feed
+10Buff readyAI + operator
+32 sFan sees itGo3 stream
Match-night coverto agree
Who is on call, for which matches, in which time zone.
Monitoringlive
Alarms and dashboards on every service (SigNoz, CloudWatch).
Scaletested
10,000 simultaneous fans passed. Larger tier in testing.
Latency and uptime as targets, not guarantees, until the pilot proves them
07
Who owns what
A clean line between the platform and Go3's content and audience.
Join in LiveThe platform
Software, AI engine, prompts
Operator and fan apps
Improvements made during the pilot
Built by devBlink for Buffup
Go3Content and fans
Broadcast feed and commentary
Brand and channel
Fan relationship and personal data
Licence to JiL: process the feed only to run the service
To agreeShared
Game results and engagement data
Sponsorship inside buffs
Prizes (prize-competition rules per country)
Use of Go3 name as a reference
08
Mike decides
Pricepilot and commercial
Liability capincl. AI output
Uptime %and service credits
Support hoursmatch-night cover
Term and exitpilot, renewal, notice
Prizeswho runs them
Sponsorshiprevenue split
Patentwhat is disclosed
On the call: explain how it works. For any number or commitment, "I'll confirm in writing."