Footnote

Explained match intelligence from synthetic football events: on-screen graphics that explain each moment in a headline and a few lines of text. Entry to the Microsoft Premier League Hackathon ("Inside the Game").

Video, 1:55: https://youtu.be/rT6zPgLGF38. Its footage is filmed from the deployed demo.

The football here is synthetic. The league, clubs, players, officials and matches are fictional and generated by code in this repository. No real match events, footage, clubs, players or crests are used. Names were checked against real people and clubs; see docs/data.md.

Who it's for and why: docs/audience.md. What each viewer sees: docs/experience.md. Scope and done-list: SCOPE.md.

Try it

The demo runs on Azure until judging ends on 10 November 2026, free and with no sign-in: https://ca-web-kwy7jucrk2pdm.whitepebble-d77f6eb9.westus3.azurecontainerapps.io. It replays the showcase match, Saltmarsh Rovers v Kingsferry Athletic, as if it were live.

On the start page, pick who to watch as, where to start and the speed, then Start the replay. A replay begins 30 seconds before the minute picked. Starting as Nadia, the producer, leaves each graphic for her to approve; starting as a fan approves graphics as they're found, and the console's Approve automatically switch changes that either way. Watch as, above the match, switches between the producer and the fans at any point. At 2×, each of these takes a few minutes:

1. 23', as Nadia, the producer. Kingsferry's goal reaches her shortlist with its rank and the reason for it. Evidence lists the events behind the graphic. Agent runs shows the agents' work on it: each MCP match tool called, the checks a draft failed, the time and tokens. Drafts are kept between replays, so the graphic usually arrives with an earlier replay's draft, marked "Agent, reused", and Agent runs shows the run that wrote it. Redraft asks the agents for a fresh one. Approve puts the graphic on air, with Edit and Kill beside it. Then switch to Sam, a fan whose stream runs 40 seconds behind live (20 seconds at 2×): the graphic reaches Sam with the goal, worded as Nadia approved it, or when she approves it if that comes later.
2. 31', as Tom, a blind fan. The described feed tells the match in words for a screen reader, at the detail and pace set in Settings. Marco Dellow's goal is checked by VAR and ruled out for offside; switch to Sam for the decision's graphic, with a still of the pitch at the pass.
3. 60', as Lucía, joining late. She reads what she missed in Spanish, then each graphic in Spanish once Azure AI Translator's version passes code's check; a graphic whose translation fails stays in English, marked as such. The next graphic, on a spell where neither side has control, comes about four minutes in at 2× (two at 4×).
4. 81', as Nadia. The goal is first recorded as Jory Penhallow's own goal. At 84' the data provider credits it to Femi Adeyani: the graphics that cited it are flagged, and the restated graphic comes back to Nadia under Corrections with the correction notice. At full time the recap ends with a sentence from code on the change, whether an agent or the template wrote the rest.

The fifth profile, Priya, owns Teo Varlan in a fantasy league and watches in analyst mode, focused on him, with pass difficulty pinned. A fan's Settings change the mode, club, player in focus, pinned metric, language, stream delay, calm mode, the pitch view and its graphics, and the described feed.

• A replay belongs to the browser that started it: only that browser approves its graphics or stops it, and starting another replaces it. Anyone with its link can watch, until a day after it ends, when it is deleted.
• Up to six replays run at once; a seventh replaces the oldest.
• Each address can start eight replays in five minutes.
• A fresh draft (a graphic's first, or a Redraft) took 8 to 24 seconds in the recorded evaluation run (docs/evaluations.md), and Approve waits for it.

How it runs

flowchart TB
    replayer["Replayer"] -- "feed" --> eh[("Event Hubs")]
    eh --> processor["Processor<br>models, insights, templates"]
    processor -- "checkpoints" --> blob[("Blob Storage")]
    processor -- "state, graphics, jobs" --> pg[("Azure Database<br>for PostgreSQL")]
    pg -- "jobs" --> agents["Agents service<br>Agent Framework writers,<br>MCP match tools, checks,<br>translation, producer's desk"]
    agents -- "drafts, translations" --> pg
    agents -- "Responses API" --> foundry["Foundry<br>gpt-5-mini"]
    agents -- "wording in English" --> translator["Azure AI Translator"]
    agents -- "traces" --> appi["Application Insights"]
    processor -- "events, graphics" --> wps["Web PubSub"]
    agents -- "graphics" --> wps
    wps --> browser["Browser"]
    browser --> web["Web app<br>Next.js"]
    web -- "client tokens" --> wps
    web -- "start, stop" --> replayer
    web -- "snapshots, evidence" --> pg
    web -- "producer's actions" --> agents

The four services run as container apps in one Azure Container Apps environment and authenticate with managed identities, so no service uses a key or password. What each one does, how a replay flows through them, the latency measured on the deployed stack and the cost: docs/architecture.md.

This is the beginning of the README. Read the rest at the original. Read the full README ↗