«Review Line» is a Russian-language Telegram media outlet focused on Dota 2 tournaments. It helps viewers choose matches, understand what’s at stake, and notice critical team decisions during broadcasts. The primary audience consists of people who play Dota 2 but rarely follow the professional scene, as well as viewers returning after a break. For first-time watchers, separate materials are provided covering the rules, roles, and interface.The main format is one match, two segments. A pre-match brief is released: who is playing, why the match is important, which two moments to watch for, and where to stream the event. After the match, a breakdown returns to one of these focal points, explaining a specific episode based on the recording and available data. Between matches, the channel shares information about players, teams, and patches. The planned rhythm is three publications per week.AI assists in drafting. The editor selects the topic, verifies facts, is responsible for explaining the gameplay, and approves the final segment. At this stage, the pipeline is designed; integrating services and publishing to Telegram has not yet begun.

1. Valve and Steam — From Valve’s patch notes, we take the version number, date, and change descriptions. The Steamworks ISteamNews API is used to detect new announcements. The editor verifies the original information and any subsequent clarifications.
2. Tournament Organizers — Match pages and official regulations provide the schedule, participants, stage, series format, results, and a link to the broadcast. Before publishing the brief, the editor double-checks the match time.
3. Teams — Official announcements provide information about team rosters, substitutions, and participant commentary.
4. Match Recordings — From the official recording, the editor selects the episode, records the map number, and describes what is genuinely visible. The time on the in-game clock and the position in the video player are recorded separately.
5. OpenDota — The API provides data on played maps: /proMatches helps locate the map, and /matches/{match_id} retrieves its details. The editor verifies the tournament, the map, and the participating teams. If the required metric is unavailable, the field remains blank.
6. Editorial Calendar — From Homework #2, we take the section, topic, release date, and backup option. The publication time and the match time are stored separately.

n8n and PostgreSQL — collection and storage. Initial setup: check Steam every six hours; check OpenDota every two hours during the selected tournament period. Save the original responses and the time they were received. Record unknown values as null: the absence of a number does not mean zero. If a failure or a change in the response structure occurs, log an error and return the source for inspection. Store tokens in secure settings.Language Model — Draft. Input consists of one match and verified facts. Output includes the status, title, body text, card phrase, archive and spoiler tags, and a list of assertions with fact IDs. The system inserts links from the registry. Project limits are 1800 characters for text with links and 60 for the card title.Write for a Dota 2 tournament viewer. Use only verified facts from the assignment. Explain the term upon first mention. Do not invent scores, rosters, patches, time codes, or reasons for victory. In the brief, provide two pointers without revealing the result. In the analysis, warn about spoilers and return to one pointer. Specify the date for the archive. If facts are insufficient or the information conflicts, return the status needs_review and list what needs to be checked.

Template Rubric — Card. The system inserts the title, rubric, and tags. The archive date and spoiler warning must be visible on the preview. Pre-prepared materials are used for visual content, and verified data is used for graphs. If the text does not fit, it is returned for revision.

Telegram Bot API — Sending. Only the approved version can be published. For current briefs, the match start time is checked no more than 30 minutes before the release. The card and the text are accounted for separately: rerunning the process does not duplicate previously sent content. If a failure occurs and it is unknown whether the text was sent, the editor first checks the channel. A test run is available in a private channel.

Verification Example. In the announcement 7.38c from March 27, 2025, Valve reported adding a missing line to the 7.38 description. The system stores these versions separately, and the editor verifies that the draft mentions the patch note clarification. This announcement does not establish the date when the mechanic itself changed.