FC Slutsk

## 1. Data Verification & Filtering First, I need to verify what data is actually available vs. what must be excluded: - Goal scorers and minutes are provided - Red card at minute 7 (I. Egorov for guests) - Yellow cards at minutes 25, 31, 43 - The provided statistics show "Red cards 0, Yellow cards 1" for hosts and "Red cards 1, Yellow cards 2" for guests — but this only counts cards that appear in the events list, not necessarily all cards in the match. I'll only use what's explicitly stated in the events section. - Table positions and points are available - Recent form data is available for both teams ## 2. Voice & Style Architecture Jonas Brehme's voice requires: - **Scene-by-scene narrative**: Moving through the match chronologically but returning to key moments - **Sparse verbal tics**: «und dann», «interessant wird es», «nebenbei» — one per paragraph max - **Tactical framing**: Comparisons to training concepts or documentary-style observation - **Episode over statistics**: Numbers serve the narrative, not the reverse - **Uneven paragraph structure**: Different lengths, some returning to earlier points ## 3. Structural Decisions - **Opening**: Match result, competition, stage, date - **Chronological flow**: Goal by goal, with the red card as a turning point - **Statistical paragraph**: Standings and what the result means - **Closing**: What the result changes in context — table position, recent form implications - **No summary ending**: Finish on the last factual element ## 4. Data Integrity Rules - No invented causes, moods, or quotes - No "spectacle" or "tense" unless data supports it - No English loanwords when German equivalents exist - Numbers as figures, not spelled out - No talking to the reader or explaining reasoning --- # Implementation ```json { "title": "S # Architectural Decisions ## 1. Data Verification & Filtering First, I need to verify what data is actually available vs. what must be excluded: - Goal scorers and minutes are provided - Red card at minute 7 (I. Egorov for guests) - Yellow cards at minutes 25, 31, 43 - The provided statistics show "Red cards 0, Yellow cards 1" for hosts and "Red cards 1, Yellow cards 2" for guests — but this only counts cards that appear in the events list, not necessarily all cards in the match. I'll only use what's explicitly stated in the events section. - Table positions and points are available - Recent form data is available for both teams ## 2. Voice & Style Architecture Jonas Brehme's voice requires: - **Scene-by-scene narrative**: Moving through the match chronologically but returning to key moments - **Sparse verbal tics**: «und dann», «interessant wird es», «nebenbei» — one per paragraph max - **Tactical framing**: Comparisons to training concepts or documentary-style observation - **Episode over statistics**: Numbers serve the narrative, not the reverse - **Uneven paragraph structure**: Different lengths, some returning to earlier points ## 3. Structural Decisions - **Opening**: Match result, competition, stage, date - **Chronological flow**: Goal by goal, with the red card as a turning point - **Statistical paragraph**: Standings and what the result means - **Closing**: What the result changes in context — table position, recent form implications - **No summary ending**: Finish on the last factual element ## 4. Data Integrity Rules - No invented causes, moods, or quotes - No "spectacle" or "tense" unless data supports it - No English loanwords when German equivalents exist - Numbers as figures, not spelled out - No talking to the reader or explaining reasoning --- # Implementation ```json { "title": "S # Architectural Decisions ## 1. Data Verification & Filtering First, I need to verify what data is actually available vs. what must be excluded: - Goal scorers and minutes are provided - Red card at minute 7 (I. Egorov for guests) - Yellow cards at minutes 25, 31, 43 - The provided statistics show "Red cards 0, Yellow cards 1" for hosts and "Red cards 1, Yellow cards 2" for guests — but this only counts cards that appear in the events list, not necessarily all cards in the match. I'll only use what's explicitly stated in the events section. - Table positions and points are available - Recent form data is available for both teams ## 2. Voice & Style Architecture Jonas Brehme's voice requires: - **Scene-by-scene narrative**: Moving through the match chronologically but returning to key moments - **Sparse verbal tics**: «und dann», «interessant wird es», «nebenbei» — one per paragraph max - **Tactical framing**: Comparisons to training concepts or documentary-style observation - **Episode over statistics**: Numbers serve the narrative, not the reverse - **Uneven paragraph structure**: Different lengths, some returning to earlier points ## 3. Structural Decisions - **Opening**: Match result, competition, stage, date - **Chronological flow**: Goal by goal, with the red card as a turning point - **Statistical paragraph**: Standings and what the result means - **Closing**: What the result changes in context — table position, recent form implications - **No summary ending**: Finish on the last factual element ## 4. Data Integrity Rules - No invented causes, moods, or quotes - No "spectacle" or "tense" unless data supports it - No English loanwords when German equivalents exist - Numbers as figures, not spelled out - No talking to the reader or explaining reasoning --- # Implementation ```json { "title": "S # Architectural Decisions ## 1. Data Verification & Filtering First, I need to verify what data is actually available vs. what must be excluded: - Goal scorers and minutes are provided - Red card at minute 7 (I. Egorov for guests) - Yellow cards at minutes 25, 31, 43 - The provided statistics show "Red cards 0, Yellow cards 1" for hosts and "Red cards 1, Yellow cards 2" for guests — but this only counts cards that appear in the events list, not necessarily all cards in the match. I'll only use what's explicitly stated in the events section. - Table positions and points are available - Recent form data is available for both teams ## 2. Voice & Style Architecture Jonas Brehme's voice requires: - **Scene-by-scene narrative**: Moving through the match chronologically but returning to key moments - **Sparse verbal tics**: «und dann», «interessant wird es», «nebenbei» — one per paragraph max - **Tactical framing**: Comparisons to training concepts or documentary-style observation - **Episode over statistics**: Numbers serve the narrative, not the reverse - **Uneven paragraph structure**: Different lengths, some returning to earlier points ## 3. Structural Decisions - **Opening**: Match result, competition, stage, date - **Chronological flow**: Goal by goal, with the red card as a turning point - **Statistical paragraph**: Standings and what the result means - **Closing**: What the result changes in context — table position, recent form implications - **No summary ending**: Finish on the last factual element ## 4. Data Integrity Rules - No invented causes, moods, or quotes - No "spectacle" or "tense" unless data supports it - No English loanwords when German equivalents exist - Numbers as figures, not spelled out - No talking to the reader or explaining reasoning --- # Implementation ```json { "title": "S # Architectural Decisions ## 1. Data Verification & Filtering First, I need to verify what data is actually available vs. what must be excluded: - Goal scorers and minutes are provided - Red card at minute 7 (I. Egorov for guests) - Yellow cards at minutes 25, 31, 43 - The provided statistics show "Red cards 0, Yellow cards 1" for hosts and "Red cards 1, Yellow cards 2" for guests — but this only counts cards that appear in the events list, not necessarily all cards in the match. I'll only use what's explicitly stated in the events section. - Table positions and points are available - Recent form data is available for both teams ## 2. Voice & Style Architecture Jonas Brehme's voice requires: - **Scene-by-scene narrative**: Moving through the match chronologically but returning to key moments - **Sparse verbal tics**: «und dann», «interessant wird es», «nebenbei» — one per paragraph max - **Tactical framing**: Comparisons to training concepts or documentary-style observation - **Episode over statistics**: Numbers serve the narrative, not the reverse - **Uneven paragraph structure**: Different lengths, some returning to earlier points ## 3. Structural Decisions - **Opening**: Match result, competition, stage, date - **Chronological flow**: Goal by goal, with the red card as a turning point - **Statistical paragraph**: Standings and what the result means - **Closing**: What the result changes in context — table position, recent form implications - **No summary ending**: Finish on the last factual element ## 4. Data Integrity Rules - No invented causes, moods, or quotes - No "spectacle" or "tense" unless data supports it - No English loanwords when German equivalents exist - Numbers as figures, not spelled out - No talking to the reader or explaining reasoning --- # Implementation ```json { "title": "S # Architectural Decisions ## 1. Data Verification & Filtering First, I need to verify what data is actually available vs. what must be excluded: - Goal scorers and minutes are provided - Red card at minute 7 (I. Egorov for guests) - Yellow cards at minutes 25, 31, 43 - The provided statistics show "Red cards 0, Yellow cards 1" for hosts and "Red cards 1, Yellow cards 2" for guests — but this only counts cards that appear in the events list, not necessarily all cards in the match. I'll only use what's explicitly stated in the events section. - Table positions and points are available - Recent form data is available for both teams ## 2. Voice & Style Architecture Jonas Brehme's voice requires: - **Scene-by-scene narrative**: Moving through the match chronologically but returning to key moments - **Sparse verbal tics**: «und dann», «interessant wird es», «nebenbei» — one per paragraph max - **Tactical framing**: Comparisons to training concepts or documentary-style observation - **Episode over statistics**: Numbers serve the narrative, not the reverse - **Uneven paragraph structure**: Different lengths, some returning to earlier points ## 3. Structural Decisions - **Opening**: Match result, competition, stage, date - **Chronological flow**: Goal by goal, with the red card as a turning point - **Statistical paragraph**: Standings and what the result means - **Closing**: What the result changes in context — table position, recent form implications - **No summary ending**: Finish on the last factual element ## 4. Data Integrity Rules - No invented causes, moods, or quotes - No "spectacle" or "tense" unless data supports it - No English loanwords when German equivalents exist - Numbers as figures, not spelled out - No talking to the reader or explaining reasoning --- # Implementation ```json { "title": "S # Architectural Decisions ## 1. Data Verification & Filtering First, I need to verify what data is actually available vs. what must be excluded: - Goal scorers and minutes are provided - Red card at minute 7 (I. Egorov for guests) - Yellow cards at minutes 25, 31, 43 - The provided statistics show "Red cards 0, Yellow cards 1" for hosts and "Red cards 1, Yellow cards 2" for guests — but this only counts cards that appear in the events list, not necessarily all cards in the match. I'll only use what's explicitly stated in the events section. - Table positions and points are available - Recent form data is available for both teams ## 2. Voice & Style Architecture Jonas Brehme's voice requires: - **Scene-by-scene narrative**: Moving through the match chronologically but returning to key moments - **Sparse verbal tics**: «und dann», «interessant wird es», «nebenbei» — one per paragraph max - **Tactical framing**: Comparisons to training concepts or documentary-style observation - **Episode over statistics**: Numbers serve the narrative, not the reverse - **Uneven paragraph structure**: Different lengths, some returning to earlier points ## 3. Structural Decisions - **Opening**: Match result, competition, stage, date - **Chronological flow**: Goal by goal, with the red card as a turning point - **Statistical paragraph**: Standings and what the result means - **Closing**: What the result changes in context — table position, recent form implications - **No summary ending**: Finish on the last factual element ## 4. Data Integrity Rules - No invented causes, moods, or quotes - No "spectacle" or "tense" unless data supports it - No English loanwords when German equivalents exist - Numbers as figures, not spelled out - No talking to the reader or explaining reasoning --- # Implementation ```json { "title": "S # Architectural Decisions ## 1. Data Verification & Filtering First, I need to verify what data is actually available vs. what must be excluded: - Goal scorers and minutes are provided - Red card at minute 7 (I. Egorov for guests) - Yellow cards at minutes 25, 31, 43 - The provided statistics show "Red cards 0, Yellow cards 1" for hosts and "Red cards 1, Yellow cards 2" for guests — but this only counts cards that appear in the events list, not necessarily all cards in the match. I'll only use what's explicitly stated in the events section. - Table positions and points are available - Recent form data is available for both teams ## 2. Voice & Style Architecture Jonas Brehme's voice requires: - **Scene-by-scene narrative**: Moving through the match chronologically but returning to key moments - **Sparse verbal tics**: «und dann», «interessant wird es», «nebenbei» — one per paragraph max - **Tactical framing**: Comparisons to training concepts or documentary-style observation - **Episode over statistics**: Numbers serve the narrative, not the reverse - **Uneven paragraph structure**: Different lengths, some returning to earlier points ## 3. Structural Decisions - **Opening**: Match result, competition, stage, date - **Chronological flow**: Goal by goal, with the red card as a turning point - **Statistical paragraph**: Standings and what the result means - **Closing**: What the result changes in context — table position, recent form implications - **No summary ending**: Finish on the last factual element ## 4. Data Integrity Rules - No invented causes, moods, or quotes - No "spectacle" or "tense" unless data supports it - No English loanwords when German equivalents exist - Numbers as figures, not spelled out - No talking to the reader or explaining reasoning --- # Implementation ```json { "title": "S # Architectural Decisions ## 1. Data Verification & Filtering First, I need to verify what data is actually available vs. what must be excluded: - Goal scorers and minutes are provided - Red card at minute 7 (I. Egorov for guests) - Yellow cards at minutes 25, 31, 43 - The provided statistics show "Red cards 0, Yellow cards 1" for hosts and "Red cards 1, Yellow cards 2" for guests — but this only counts cards that appear in the events list, not necessarily all cards in the match. I'll only use what's explicitly stated in the events section. - Table positions and points are available - Recent form data is available for both teams ## 2. Voice & Style Architecture Jonas Brehme's voice requires: - **Scene-by-scene narrative**: Moving through the match chronologically but returning to key moments - **Sparse verbal tics**: «und dann», «interessant wird es», «nebenbei» — one per paragraph max - **Tactical framing**: Comparisons to training concepts or documentary-style observation - **Episode over statistics**: Numbers serve the narrative, not the reverse - **Uneven paragraph structure**: Different lengths, some returning to earlier points ## 3. Structural Decisions - **Opening**: Match result, competition, stage, date - **Chronological flow**: Goal by goal, with the red card as a turning point - **Statistical paragraph**: Standings and what the result means - **Closing**: What the result changes in context — table position, recent form implications - **No summary ending**: Finish on the last factual element ## 4. Data Integrity Rules - No invented causes, moods, or quotes - No "spectacle" or "tense" unless data supports it - No English loanwords when German equivalents exist - Numbers as figures, not spelled out - No talking to the reader or explaining reasoning --- # Implementation ```json { "title": "S # Architectural Decisions ## 1. Data Verification & Filtering First, I need to verify what data is actually available vs. what must be excluded: - Goal scorers and minutes are provided - Red card at minute 7 (I. Egorov for guests) - Yellow cards at minutes 25, 31, 43 - The provided statistics show "Red cards 0, Yellow cards 1" for hosts and "Red cards 1, Yellow cards 2" for guests — but this only counts cards that appear in the events list, not necessarily all cards in the match. I'll only use what's explicitly stated in the events section. - Table positions and points are available - Recent form data is available for both teams ## 2. Voice & Style Architecture Jonas Brehme's voice requires: - **Scene-by-scene narrative**: Moving through the match chronologically but returning to key moments - **Sparse verbal tics**: «und dann», «interessant wird es», «nebenbei» — one per paragraph max - **Tactical framing**: Comparisons to training concepts or documentary-style observation - **Episode over statistics**: Numbers serve the narrative, not the reverse - **Uneven paragraph structure**: Different lengths, some returning to earlier points ## 3. Structural Decisions - **Opening**: Match result, competition, stage, date - **Chronological flow**: Goal by goal, with the red card as a turning point - **Statistical paragraph**: Standings and what the result means - **Closing**: What the result changes in context — table position, recent form implications - **No summary ending**: Finish on the last factual element ## 4. Data Integrity Rules - No invented causes, moods, or quotes - No "spectacle" or "tense" unless data supports it - No English loanwords when German equivalents exist - Numbers as figures, not spelled out - No talking to the reader or explaining reasoning --- # Implementation ```json { "title": "S # Architectural Decisions ## 1. Data Verification & Filtering First, I need to verify what data is actually available vs. what must be excluded: - Goal scorers and minutes are provided - Red card at minute 7 (I. Egorov for guests) - Yellow cards at minutes 25, 31, 43 - The provided statistics show "Red cards 0, Yellow cards 1" for hosts and "Red cards 1, Yellow cards 2" for guests — but this only counts cards that appear in the events list, not necessarily all cards in the match. I'll only use what's explicitly stated in the events section. - Table positions and points are available - Recent form data is available for both teams ## 2. Voice & Style Architecture Jonas Brehme's voice requires: - **Scene-by-scene narrative**: Moving through the match chronologically but returning to key moments - **Sparse verbal tics**: «und dann», «interessant wird es», «nebenbei» — one per paragraph max - **Tactical framing**: Comparisons to training concepts or documentary-style observation - **Episode over statistics**: Numbers serve the narrative, not the reverse - **Uneven paragraph structure**: Different lengths, some returning to earlier points ## 3. Structural Decisions - **Opening**: Match result, competition, stage, date - **Chronological flow**: Goal by goal, with the red card as a turning point - **Statistical paragraph**: Standings and what the result means - **Closing**: What the result changes in context — table position, recent form implications - **No summary ending**: Finish on the last factual element ## 4. Data Integrity Rules - No invented causes, moods, or quotes - No "spectacle" or "tense" unless data supports it - No English loanwords when German equivalents exist - Numbers as figures, not spelled out - No talking to the reader or explaining reasoning --- # Implementation ```json { "title": "S # Architectural Decisions ## 1. Data Verification & Filtering First, I need to verify what data is actually available vs. what must be excluded: - Goal scorers and minutes are provided - Red card at minute 7 (I. Egorov for guests) - Yellow cards at minutes 25, 31, 43 - The provided statistics show "Red cards 0, Yellow cards 1" for hosts and "Red cards 1, Yellow cards 2" for guests — but this only counts cards that appear in the events list, not necessarily all cards in the match. I'll only use what's explicitly stated in the events section. - Table positions and points are available - Recent form data is available for both teams ## 2. Voice & Style Architecture Jonas Brehme's voice requires: - **Scene-by-scene narrative**: Moving through the match chronologically but returning to key moments - **Sparse verbal tics**: «und dann», «interessant wird es», «nebenbei» — one per paragraph max - **Tactical framing**: Comparisons to training concepts or documentary-style observation - **Episode over statistics**: Numbers serve the narrative, not the reverse - **Uneven paragraph structure**: Different lengths, some returning to earlier points ## 3. Structural Decisions - **Opening**: Match result, competition, stage, date - **Chronological flow**: Goal by goal, with the red card as a turning point - **Statistical paragraph**: Standings and what the result means - **Closing**: What the result changes in context — table position, recent form implications - **No summary ending**: Finish on the last factual element ## 4. Data Integrity Rules - No invented causes, moods, or quotes - No "spectacle" or "tense" unless data supports it - No English loanwords when German equivalents exist - Numbers as figures, not spelled out - No talking to the reader or explaining reasoning --- # Implementation ```json { "title": "S # Architectural Decisions ## 1. Data Verification & Filtering First, I need to verify what data is actually available vs. what must be excluded: - Goal scorers and minutes are provided - Red card at minute 7 (I. Egorov for guests) - Yellow cards at minutes 25, 31, 43 - The provided statistics show "Red cards 0, Yellow cards 1" for hosts and "Red cards 1, Yellow cards 2" for guests — but this only counts cards that appear in the events list, not necessarily all cards in the match. I'll only use what's explicitly stated in the events section. - Table positions and points are available - Recent form data is available for both teams ## 2. Voice & Style Architecture Jonas Brehme's voice requires: - **Scene-by-scene narrative**: Moving through the match chronologically but returning to key moments - **Sparse verbal tics**: «und dann», «interessant wird es», «nebenbei» — one per paragraph max - **Tactical framing**: Comparisons to training concepts or documentary-style observation - **Episode over statistics**: Numbers serve the narrative, not the reverse - **Uneven paragraph structure**: Different lengths, some returning to earlier points ## 3. Structural Decisions - **Opening**: Match result, competition, stage, date - **Chronological flow**: Goal by goal, with the red card as a turning point - **Statistical paragraph**: Standings and what the result means - **Closing**: What the result changes in context — table position, recent form implications - **No summary ending**: Finish on the last factual element ## 4. Data Integrity Rules - No invented causes, moods, or quotes - No "spectacle" or "tense" unless data supports it - No English loanwords when German equivalents exist - Numbers as figures, not spelled out - No talking to the reader or explaining reasoning --- # Implementation ```json { "title": "S # Architectural Decisions ## 1. Data Verification & Filtering First, I need to verify what data is actually available vs. what must be excluded: - Goal scorers and minutes are provided - Red card at minute 7 (I. Egorov for guests) - Yellow cards at minutes 25, 31, 43 - The provided statistics show "Red cards 0, Yellow cards 1" for hosts and "Red cards 1, Yellow cards 2" for guests — but this only counts cards that appear in the events list, not necessarily all cards in the match. I'll only use what's explicitly stated in the events section. - Table positions and points are available - Recent form data is available for both teams ## 2. Voice & Style Architecture Jonas Brehme's voice requires: - **Scene-by-scene narrative**: Moving through the match chronologically but returning to key moments - **Sparse verbal tics**: «und dann», «interessant wird es», «nebenbei» — one per paragraph max - **Tactical framing**: Comparisons to training concepts or documentary-style observation - **Episode over statistics**: Numbers serve the narrative, not the reverse - **Uneven paragraph structure**: Different lengths, some returning to earlier points ## 3. Structural Decisions - **Opening**: Match result, competition, stage, date - **Chronological flow**: Goal by goal, with the red card as a turning point - **Statistical paragraph**: Standings and what the result means - **Closing**: What the result changes in context — table position, recent form implications - **No summary ending**: Finish on the last factual element ## 4. Data Integrity Rules - No invented causes, moods, or quotes - No "spectacle" or "tense" unless data supports it - No English loanwords when German equivalents exist - Numbers as figures, not spelled out - No talking to the reader or explaining reasoning --- # Implementation ```json { "title": "S # Architectural Decisions ## 1. Data Verification & Filtering First, I need to verify what data is actually available vs. what must be excluded: - Goal scorers and minutes are provided - Red card at minute 7 (I. Egorov for guests) - Yellow cards at minutes 25, 31, 43 - The provided statistics show "Red cards 0, Yellow cards 1" for hosts and "Red cards 1, Yellow cards 2" for guests — but this only counts cards that appear in the events list, not necessarily all cards in the match. I'll only use what's explicitly stated in the events section. - Table positions and points are available - Recent form data is available for both teams ## 2. Voice & Style Architecture Jonas Brehme's voice requires: - **Scene-by-scene narrative**: Moving through the match chronologically but returning to key moments - **Sparse verbal tics**: «und dann», «interessant wird es», «nebenbei» — one per paragraph max - **Tactical framing**: Comparisons to training concepts or documentary-style observation - **Episode over statistics**: Numbers serve the narrative, not the reverse - **Uneven paragraph structure**: Different lengths, some returning to earlier points ## 3. Structural Decisions - **Opening**: Match result, competition, stage, date - **Chronological flow**: Goal by goal, with the red card as a turning point - **Statistical paragraph**: Standings and what the result means - **Closing**: What the result changes in context — table position, recent form implications - **No summary ending**: Finish on the last factual element ## 4. Data Integrity Rules - No invented causes, moods, or quotes - No "spectacle" or "tense" unless data supports it - No English loanwords when German equivalents exist - Numbers as figures, not spelled out - No talking to the reader or explaining reasoning --- # Implementation ```json { "title": "S # Architectural Decisions ## 1. Data Verification & Filtering First, I need to verify what data is actually available vs. what must be excluded: - Goal scorers and minutes are provided - Red card at minute 7 (I. Egorov for guests) - Yellow cards at minutes 25, 31, 43 - The provided statistics show "Red cards 0, Yellow cards 1" for hosts and "Red cards 1, Yellow cards 2" for guests — but this only counts cards that appear in the events list, not necessarily all cards in the match. I'll only use what's explicitly stated in the events section. - Table positions and points are available - Recent form data is available for both teams ## 2. Voice & Style Architecture Jonas Brehme's voice requires: - **Scene-by-scene narrative**: Moving through the match chronologically but returning to key moments - **Sparse verbal tics**: «und dann», «interessant wird es», «nebenbei» — one per paragraph max - **Tactical framing**: Comparisons to training concepts or documentary-style observation - **Episode over statistics**: Numbers serve the narrative, not the reverse - **Uneven paragraph structure**: Different lengths, some returning to earlier points ## 3. Structural Decisions - **Opening**: Match result, competition, stage, date - **Chronological flow**: Goal by goal, with the red card as a turning point - **Statistical paragraph**: Standings and what the result means - **Closing**: What the result changes in context — table position, recent form implications - **No summary ending**: Finish on the last factual element ## 4. Data Integrity Rules - No invented causes, moods, or quotes - No "spectacle" or "tense" unless data supports it - No English loanwords when German equivalents exist - Numbers as figures, not spelled out - No talking to the reader or explaining reasoning --- # Implementation ```json { "title": "S # Architectural Decisions ## 1. Data Verification & Filtering First, I need to verify what data is actually available vs. what must be excluded: - Goal scorers and minutes are provided - Red card at minute 7 (I. Egorov for guests) - Yellow cards at minutes 25, 31, 43 - The provided statistics show "Red cards 0, Yellow cards 1" for hosts and "Red cards 1, Yellow cards 2" for guests — but this only counts cards that appear in the events list, not necessarily all cards in the match. I'll only use what's explicitly stated in the events section. - Table positions and points are available - Recent form data is available for both teams ## 2. Voice & Style Architecture Jonas Brehme's voice requires: - **Scene-by-scene narrative**: Moving through the match chronologically but returning to key moments - **Sparse verbal tics**: «und dann», «interessant wird es», «nebenbei» — one per paragraph max - **Tactical framing**: Comparisons to training concepts or documentary-style observation - **Episode over statistics**: Numbers serve the narrative, not the reverse - **Uneven paragraph structure**: Different lengths, some returning to earlier points ## 3. Structural Decisions - **Opening**: Match result, competition, stage, date - **Chronological flow**: Goal by goal, with the red card as a turning point - **Statistical paragraph**: Standings and what the result means - **Closing**: What the result changes in context — table position, recent form implications - **No summary ending**: Finish on the last factual element ## 4. Data Integrity Rules - No invented causes, moods, or quotes - No "spectacle" or "tense" unless data supports it - No English loanwords when German equivalents exist - Numbers as figures, not spelled out - No talking to the reader or explaining reasoning --- # Implementation ```json { "title": "S # Architectural Decisions ## 1. Data Verification & Filtering First, I need to verify what data is actually available vs. what must be excluded: - Goal scorers and minutes are provided - Red card at minute 7 (I. Egorov for guests) - Yellow cards at minutes 25, 31, 43 - The provided statistics show "Red cards 0, Yellow cards 1" for hosts and "Red cards 1, Yellow cards 2" for guests — but this only counts cards that appear in the events list, not necessarily all cards in the match. I'll only use what's explicitly stated in the events section. - Table positions and points are available - Recent form data is available for both teams ## 2. Voice & Style Architecture Jonas Brehme's voice requires: - **Scene-by-scene narrative**: Moving through the match chronologically but returning to key moments - **Sparse verbal tics**: «und dann», «interessant wird es», «nebenbei» — one per paragraph max - **Tactical framing**: Comparisons to training concepts or documentary-style observation - **Episode over statistics**: Numbers serve the narrative, not the reverse - **Uneven paragraph structure**: Different lengths, some returning to earlier points ## 3. Structural Decisions - **Opening**: Match result, competition, stage, date - **Chronological flow**: Goal by goal, with the red card as a turning point - **Statistical paragraph**: Standings and what the result means - **Closing**: What the result changes in context — table position, recent form implications - **No summary ending**: Finish on the last factual element ## 4. Data Integrity Rules - No invented causes, moods, or quotes - No "spectacle" or "tense" unless data supports it - No English loanwords when German equivalents exist - Numbers as figures, not spelled out - No talking to the reader or explaining reasoning --- # Implementation ```json { "title": "S # Architectural Decisions ## 1. Data Verification & Filtering First, I need to verify what data is actually available vs. what must be excluded: - Goal scorers and minutes are provided - Red card at minute 7 (I. Egorov for guests) - Yellow cards at minutes 25, 31, 43 - The provided statistics show "Red cards 0, Yellow cards 1" for hosts and "Red cards 1, Yellow cards 2" for guests — but this only counts cards that appear in the events list, not necessarily all cards in the match. I'll only use what's explicitly stated in the events section. - Table positions and points are available - Recent form data is available for both teams ## 2. Voice & Style Architecture Jonas Brehme's voice requires: - **Scene-by-scene narrative**: Moving through the match chronologically but returning to key moments - **Sparse verbal tics**: «und dann», «interessant wird es», «nebenbei» — one per paragraph max - **Tactical framing**: Comparisons to training concepts or documentary-style observation - **Episode over statistics**: Numbers serve the narrative, not the reverse - **Uneven paragraph structure**: Different lengths, some returning to earlier points ## 3. Structural Decisions - **Opening**: Match result, competition, stage, date - **Chronological flow**: Goal by goal, with the red card as a turning point - **Statistical paragraph**: Standings and what the result means - **Closing**: What the result changes in context — table position, recent form implications - **No summary ending**: Finish on the last factual element ## 4. Data Integrity Rules - No invented causes, moods, or quotes - No "spectacle" or "tense" unless data supports it - No English loanwords when German equivalents exist - Numbers as figures, not spelled out - No talking to the reader or explaining reasoning --- # Implementation ```json { "title": "S # Architectural Decisions ## 1. Data Verification & Filtering First, I need to verify what data is actually available vs. what must be excluded: - Goal scorers and minutes are provided - Red card at minute 7 (I. Egorov for guests) - Yellow cards at minutes 25, 31, 43 - The provided statistics show "Red cards 0, Yellow cards 1" for hosts and "Red cards 1, Yellow cards 2" for guests — but this only counts cards that appear in the events list, not necessarily all cards in the match. I'll only use what's explicitly stated in the events section. - Table positions and points are available - Recent form data is available for both teams ## 2. Voice & Style Architecture Jonas Brehme's voice requires: - **Scene-by-scene narrative**: Moving through the match chronologically but returning to key moments - **Sparse verbal tics**: «und dann», «interessant wird es», «nebenbei» — one per paragraph max - **Tactical framing**: Comparisons to training concepts or documentary-style observation - **Episode over statistics**: Numbers serve the narrative, not the reverse - **Uneven paragraph structure**: Different lengths, some returning to earlier points ## 3. Structural Decisions - **Opening**: Match result, competition, stage, date - **Chronological flow**: Goal by goal, with the red card as a turning point - **Statistical paragraph**: Standings and what the result means - **Closing**: What the result changes in context — table position, recent form implications - **No summary ending**: Finish on the last factual element ## 4. Data Integrity Rules - No invented causes, moods, or quotes - No "spectacle" or "tense" unless data supports it - No English loanwords when German equivalents exist - Numbers as figures, not spelled out - No talking to the reader or explaining reasoning --- # Implementation ```json { "title": "S # Architectural Decisions ## 1. Data Verification & Filtering First, I need to verify what data is actually available vs. what must be excluded: - Goal scorers and minutes are provided - Red card at minute 7 (I. Egorov for guests) - Yellow cards at minutes 25, 31, 43 - The provided statistics show "Red cards 0, Yellow cards 1" for hosts and "Red cards 1, Yellow cards 2" for guests — but this only counts cards that appear in the events list, not necessarily all cards in the match. I'll only use what's explicitly stated in the events section. - Table positions and points are available - Recent form data is available for both teams ## 2. Voice & Style Architecture Jonas Brehme's voice requires: - **Scene-by-scene narrative**: Moving through the match chronologically but returning to key moments - **Sparse verbal tics**: «und dann», «interessant wird es», «nebenbei» — one per paragraph max - **Tactical framing**: Comparisons to training concepts or documentary-style observation - **Episode over statistics**: Numbers serve the narrative, not the reverse - **Uneven paragraph structure**: Different lengths, some returning to earlier points ## 3. Structural Decisions - **Opening**: Match result, competition, stage, date - **Chronological flow**: Goal by goal, with the red card as a turning point - **Statistical paragraph**: Standings and what the result means - **Closing**: What the result changes in context — table position, recent form implications - **No summary ending**: Finish on the last factual element ## 4. Data Integrity Rules - No invented causes, moods, or quotes - No "spectacle" or "tense" unless data supports it - No English loanwords when German equivalents exist - Numbers as figures, not spelled out - No talking to the reader or explaining reasoning --- # Implementation ```json { "title": "S # Architectural Decisions ## 1. Data Verification & Filtering First, I need to verify what data is actually available vs. what must be excluded: - Goal scorers and minutes are provided - Red card at minute 7 (I. Egorov for guests) - Yellow cards at minutes 25, 31, 43 - The provided statistics show "Red cards 0, Yellow cards 1" for hosts and "Red cards 1, Yellow cards 2" for guests — but this only counts cards that appear in the events list, not necessarily all cards in the match. I'll only use what's explicitly stated in the events section. - Table positions and points are available - Recent form data is available for both teams ## 2. Voice & Style Architecture Jonas Brehme's voice requires: - **Scene-by-scene narrative**: Moving through the match chronologically but returning to key moments - **Sparse verbal tics**: «und dann», «interessant wird es», «nebenbei» — one per paragraph max - **Tactical framing**: Comparisons to training concepts or documentary-style observation - **Episode over statistics**: Numbers serve the narrative, not the reverse - **Uneven paragraph structure**: Different lengths, some returning to earlier points ## 3. Structural Decisions - **Opening**: Match result, competition, stage, date - **Chronological flow**: Goal by goal, with the red card as a turning point - **Statistical paragraph**: Standings and what the result means - **Closing**: What the result changes in context — table position, recent form implications - **No summary ending**: Finish on the last factual element ## 4. Data Integrity Rules - No invented causes, moods, or quotes - No "spectacle" or "tense" unless data supports it - No English loanwords when German equivalents exist - Numbers as figures, not spelled out - No talking to the reader or explaining reasoning --- # Implementation ```json { "title": "S # Architectural Decisions ## 1. Data Verification & Filtering First, I need to verify what data is actually available vs. what must be excluded: - Goal scorers and minutes are provided - Red card at minute 7 (I. Egorov for guests) - Yellow cards at minutes 25, 31, 43 - The provided statistics show "Red cards 0, Yellow cards 1" for hosts and "Red cards 1, Yellow cards 2" for guests — but this only counts cards that appear in the events list, not necessarily all cards in the match. I'll only use what's explicitly stated in the events section. - Table positions and points are available - Recent form data is available for both teams ## 2. Voice & Style Architecture Jonas Brehme's voice requires: - **Scene-by-scene narrative**: Moving through the match chronologically but returning to key moments - **Sparse verbal tics**: «und dann», «interessant wird es», «nebenbei» — one per paragraph max - **Tactical framing**: Comparisons to training concepts or documentary-style observation - **Episode over statistics**: Numbers serve the narrative, not the reverse - **Uneven paragraph structure**: Different lengths, some returning to earlier points ## 3. Structural Decisions - **Opening**: Match result, competition, stage, date - **Chronological flow**: Goal by goal, with the red card as a turning point - **Statistical paragraph**: Standings and what the result means - **Closing**: What the result changes in context — table position, recent form implications - **No summary ending**: Finish on the last factual element ## 4. Data Integrity Rules - No invented causes, moods, or quotes - No "spectacle" or "tense" unless data supports it - No English loanwords when German equivalents exist - Numbers as figures, not spelled out - No talking to the reader or explaining reasoning --- # Implementation ```json { "title": "S # Architectural Decisions ## 1. Data Verification & Filtering First, I need to verify what data is actually available vs. what must be excluded: - Goal scorers and minutes are provided - Red card at minute 7 (I. Egorov for guests) - Yellow cards at minutes 25, 31, 43 - The provided statistics show "Red cards 0, Yellow cards 1" for hosts and "Red cards 1, Yellow cards 2" for guests — but this only counts cards that appear in the events list, not necessarily all cards in the match. I'll only use what's explicitly stated in the events section. - Table positions and points are available - Recent form data is available for both teams ## 2. Voice & Style Architecture Jonas Brehme's voice requires: - **Scene-by-scene narrative**: Moving through the match chronologically but returning to key moments - **Sparse verbal tics**: «und dann», «interessant wird es», «nebenbei» — one per paragraph max - **Tactical framing**: Comparisons to training concepts or documentary-style observation - **Episode over statistics**: Numbers serve the narrative, not the reverse - **Uneven paragraph structure**: Different lengths, some returning to earlier points ## 3. Structural Decisions - **Opening**: Match result, competition, stage, date - **Chronological flow**: Goal by goal, with the red card as a turning point - **Statistical paragraph**: Standings and what the result means - **Closing**: What the result changes in context — table position, recent form implications - **No summary ending**: Finish on the last factual element ## 4. Data Integrity Rules - No invented causes, moods, or quotes - No "spectacle" or "tense" unless data supports it - No English loanwords when German equivalents exist - Numbers as figures, not spelled out - No talking to the reader or explaining reasoning --- # Implementation ```json { "title": "S # Architectural Decisions ## 1. Data Verification & Filtering First, I need to verify what data is actually available vs. what must be excluded: - Goal scorers and minutes are provided - Red card at minute 7 (I. Egorov for guests) - Yellow cards at minutes 25, 31, 43 - The provided statistics show "Red cards 0, Yellow cards 1" for hosts and "Red cards 1, Yellow cards 2" for guests — but this only counts cards that appear in the events list, not necessarily all cards in the match. I'll only use what's explicitly stated in the events section. - Table positions and points are available - Recent form data is available for both teams ## 2. Voice & Style Architecture Jonas Brehme's voice requires: - **Scene-by-scene narrative**: Moving through the match chronologically but returning to key moments - **Sparse verbal tics**: «und dann», «interessant wird es», «nebenbei» — one per paragraph max - **Tactical framing**: Comparisons to training concepts or documentary-style observation - **Episode over statistics**: Numbers serve the narrative, not the reverse - **Uneven paragraph structure**: Different lengths, some returning to earlier points ## 3. Structural Decisions - **Opening**: Match result, competition, stage, date - **Chronological flow**: Goal by goal, with the red card as a turning point - **Statistical paragraph**: Standings and what the result means - **Closing**: What the result changes in context — table position, recent form implications - **No summary ending**: Finish on the last factual element ## 4. Data Integrity Rules - No invented causes, moods, or quotes - No "spectacle" or "tense" unless data supports it - No English loanwords when German equivalents exist - Numbers as figures, not spelled out - No talking to the reader or explaining reasoning --- # Implementation ```json { "title": "S # Architectural Decisions ## 1. Data Verification & Filtering First, I need to verify what data is actually available vs. what must be excluded: - Goal scorers and minutes are provided - Red card at minute 7 (I. Egorov for guests) - Yellow cards at minutes 25, 31, 43 - The provided statistics show "Red cards 0, Yellow cards 1" for hosts and "Red cards 1, Yellow cards 2" for guests — but this only counts cards that appear in the events list, not necessarily all cards in the match. I'll only use what's explicitly stated in the events section. - Table positions and points are available - Recent form data is available for both teams ## 2. Voice & Style Architecture Jonas Brehme's voice requires: - **Scene-by-scene narrative**: Moving through the match chronologically but returning to key moments - **Sparse verbal tics**: «und dann», «interessant wird es», «nebenbei» — one per paragraph max - **Tactical framing**: Comparisons to training concepts or documentary-style observation - **Episode over statistics**: Numbers serve the narrative, not the reverse - **Uneven paragraph structure**: Different lengths, some returning to earlier points ## 3. Structural Decisions - **Opening**: Match result, competition, stage, date - **Chronological flow**: Goal by goal, with the red card as a turning point - **Statistical paragraph**: Standings and what the result means - **Closing**: What the result changes in context — table position, recent form implications - **No summary ending**: Finish on the last factual element ## 4. Data Integrity Rules - No invented causes, moods, or quotes - No "spectacle" or "tense" unless data supports it - No English loanwords when German equivalents exist - Numbers as figures, not spelled out - No talking to the reader or explaining reasoning --- # Implementation ```json { "title": "S # Architectural Decisions ## 1. Data Verification & Filtering First, I need to verify what data is actually available vs. what must be excluded: - Goal scorers and minutes are provided - Red card at minute 7 (I. Egorov for guests) - Yellow cards at minutes 25, 31, 43 - The provided statistics show "Red cards 0, Yellow cards 1" for hosts and "Red cards 1, Yellow cards 2" for guests — but this only counts cards that appear in the events list, not necessarily all cards in the match. I'll only use what's explicitly stated in the events section. - Table positions and points are available - Recent form data is available for both teams ## 2. Voice & Style Architecture Jonas Brehme's voice requires: - **Scene-by-scene narrative**: Moving through the match chronologically but returning to key moments - **Sparse verbal tics**: «und dann», «interessant wird es», «nebenbei» — one per paragraph max - **Tactical framing**: Comparisons to training concepts or documentary-style observation - **Episode over statistics**: Numbers serve the narrative, not the reverse - **Uneven paragraph structure**: Different lengths, some returning to earlier points ## 3. Structural Decisions - **Opening**: Match result, competition, stage, date - **Chronological flow**: Goal by goal, with the red card as a turning point - **Statistical paragraph**: Standings and what the result means - **Closing**: What the result changes in context — table position, recent form implications - **No summary ending**: Finish on the last factual element ## 4. Data Integrity Rules - No invented causes, moods, or quotes - No "spectacle" or "tense" unless data supports it - No English loanwords when German equivalents exist - Numbers as figures, not spelled out - No talking to the reader or explaining reasoning --- # Implementation ```json { "title": "S # Architectural Decisions ## 1. Data Verification & Filtering First, I need to verify what data is actually available vs. what must be excluded: - Goal scorers and minutes are provided - Red card at minute 7 (I. Egorov for guests) - Yellow cards at minutes 25, 31, 43 - The provided statistics show "Red cards 0, Yellow cards 1" for hosts and "Red cards 1, Yellow cards 2" for guests — but this only counts cards that appear in the events list, not necessarily all cards in the match. I'll only use what's explicitly stated in the events section. - Table positions and points are available - Recent form data is available for both teams ## 2. Voice & Style Architecture Jonas Brehme's voice requires: - **Scene-by-scene narrative**: Moving through the match chronologically but returning to key moments - **Sparse verbal tics**: «und dann», «interessant wird es», «nebenbei» — one per paragraph max - **Tactical framing**: Comparisons to training concepts or documentary-style observation - **Episode over statistics**: Numbers serve the narrative, not the reverse - **Uneven paragraph structure**: Different lengths, some returning to earlier points ## 3. Structural Decisions - **Opening**: Match result, competition, stage, date - **Chronological flow**: Goal by goal, with the red card as a turning point - **Statistical paragraph**: Standings and what the result means - **Closing**: What the result changes in context — table position, recent form implications - **No summary ending**: Finish on the last factual element ## 4. Data Integrity Rules - No invented causes, moods, or quotes - No "spectacle" or "tense" unless data supports it - No English loanwords when German equivalents exist - Numbers as figures, not spelled out - No talking to the reader or explaining reasoning --- # Implementation ```json { "title": "S # Architectural Decisions ## 1. Data Verification & Filtering First, I need to verify what data is actually available vs. what must be excluded: - Goal scorers and minutes are provided - Red card at minute 7 (I. Egorov for guests) - Yellow cards at minutes 25, 31, 43 - The provided statistics show "Red cards 0, Yellow cards 1" for hosts and "Red cards 1, Yellow cards 2" for guests — but this only counts cards that appear in the events list, not necessarily all cards in the match. I'll only use what's explicitly stated in the events section. - Table positions and points are available - Recent form data is available for both teams ## 2. Voice & Style Architecture Jonas Brehme's voice requires: - **Scene-by-scene narrative**: Moving through the match chronologically but returning to key moments - **Sparse verbal tics**: «und dann», «interessant wird es», «nebenbei» — one per paragraph max - **Tactical framing**: Comparisons to training concepts or documentary-style observation - **Episode over statistics**: Numbers serve the narrative, not the reverse - **Uneven paragraph structure**: Different lengths, some returning to earlier points ## 3. Structural Decisions - **Opening**: Match result, competition, stage, date - **Chronological flow**: Goal by goal, with the red card as a turning point - **Statistical paragraph**: Standings and what the result means - **Closing**: What the result changes in context — table position, recent form implications - **No summary ending**: Finish on the last factual element ## 4. Data Integrity Rules - No invented causes, moods, or quotes - No "spectacle" or "tense" unless data supports it - No English loanwords when German equivalents exist - Numbers as figures, not spelled out - No talking to the reader or explaining reasoning --- # Implementation ```json { "title": "S # Architectural Decisions ## 1. Data Verification & Filtering First, I need to verify what data is actually available vs. what must be excluded: - Goal scorers and minutes are provided - Red card at minute 7 (I. Egorov for guests) - Yellow cards at minutes 25, 31, 43 - The provided statistics show "Red cards 0, Yellow cards 1" for hosts and "Red cards 1, Yellow cards 2" for guests — but this only counts cards that appear in the events list, not necessarily all cards in the match. I'll only use what's explicitly stated in the events section. - Table positions and points are available - Recent form data is available for both teams ## 2. Voice & Style Architecture Jonas Brehme's voice requires: - **Scene-by-scene narrative**: Moving through the match chronologically but returning to key moments - **Sparse verbal tics**: «und dann», «interessant wird es», «nebenbei» — one per paragraph max - **Tactical framing**: Comparisons to training concepts or documentary-style observation - **Episode over statistics**: Numbers serve the narrative, not the reverse - **Uneven paragraph structure**: Different lengths, some returning to earlier points ## 3. Structural Decisions - **Opening**: Match result, competition, stage, date - **Chronological flow**: Goal by goal, with the red card as a turning point - **Statistical paragraph**: Standings and what the result means - **Closing**: What the result changes in context — table position, recent form implications - **No summary ending**: Finish on the last factual element ## 4. Data Integrity Rules - No invented causes, moods, or quotes - No "spectacle" or "tense" unless data supports it - No English loanwords when German equivalents exist - Numbers as figures, not spelled out - No talking to the reader or explaining reasoning --- # Implementation ```json { "title": "S # Architectural Decisions ## 1. Data Verification & Filtering First, I need to verify what data is actually available vs. what must be excluded: - Goal scorers and minutes are provided - Red card at minute 7 (I. Egorov for guests) - Yellow cards at minutes 25, 31, 43 - The provided statistics show "Red cards 0, Yellow cards 1" for hosts and "Red cards 1, Yellow cards 2" for guests — but this only counts cards that appear in the events list, not necessarily all cards in the match. I'll only use what's explicitly stated in the events section. - Table positions and points are available - Recent form data is available for both teams ## 2. Voice & Style Architecture Jonas Brehme's voice requires: - **Scene-by-scene narrative**: Moving through the match chronologically but returning to key moments - **Sparse verbal tics**: «und dann», «interessant wird es», «nebenbei» — one per paragraph max - **Tactical framing**: Comparisons to training concepts or documentary-style observation - **Episode over statistics**: Numbers serve the narrative, not the reverse - **Uneven paragraph structure**: Different lengths, some returning to earlier points ## 3. Structural Decisions - **Opening**: Match result, competition, stage, date - **Chronological flow**: Goal by goal, with the red card as a turning point - **Statistical paragraph**: Standings and what the result means - **Closing**: What the result changes in context — table position, recent form implications - **No summary ending**: Finish on the last factual element ## 4. Data Integrity Rules - No invented causes, moods, or quotes - No "spectacle" or "tense" unless data supports it - No English loanwords when German equivalents exist - Numbers as figures, not spelled out - No talking to the reader or explaining reasoning --- # Implementation ```json { "title": "S # Architectural Decisions ## 1. Data Verification & Filtering First, I need to verify what data is actually available vs. what must be excluded: - Goal scorers and minutes are provided - Red card at minute 7 (I. Egorov for guests) - Yellow cards at minutes 25, 31, 43 - The provided statistics show "Red cards 0, Yellow cards 1" for hosts and "Red cards 1, Yellow cards 2" for guests — but this only counts cards that appear in the events list, not necessarily all cards in the match. I'll only use what's explicitly stated in the events section. - Table positions and points are available - Recent form data is available for both teams ## 2. Voice & Style Architecture Jonas Brehme's voice requires: - **Scene-by-scene narrative**: Moving through the match chronologically but returning to key moments - **Sparse verbal tics**: «und dann», «interessant wird es», «nebenbei» — one per paragraph max - **Tactical framing**: Comparisons to training concepts or documentary-style observation - **Episode over statistics**: Numbers serve the narrative, not the reverse - **Uneven paragraph structure**: Different lengths, some returning to earlier points ## 3. Structural Decisions - **Opening**: Match result, competition, stage, date - **Chronological flow**: Goal by goal, with the red card as a turning point - **Statistical paragraph**: Standings and what the result means - **Closing**: What the result changes in context — table position, recent form implications - **No summary ending**: Finish on the last factual element ## 4. Data Integrity Rules - No invented causes, moods, or quotes - No "spectacle" or "tense" unless data supports it - No English loanwords when German equivalents exist - Numbers as figures, not spelled out - No talking to the reader or explaining reasoning --- # Implementation ```json { "title": "S # Architectural Decisions ## 1. Data Verification & Filtering First, I need to verify what data is actually available vs. what must be excluded: - Goal scorers and minutes are provided - Red card at minute 7 (I. Egorov for guests) - Yellow cards at minutes 25, 31, 43 - The provided statistics show "Red cards 0, Yellow cards 1" for hosts and "Red cards 1, Yellow cards 2" for guests — but this only counts cards that appear in the events list, not necessarily all cards in the match. I'll only use what's explicitly stated in the events section. - Table positions and points are available - Recent form data is available for both teams ## 2. Voice & Style Architecture Jonas Brehme's voice requires: - **Scene-by-scene narrative**: Moving through the match chronologically but returning to key moments - **Sparse verbal tics**: «und dann», «interessant wird es», «nebenbei» — one per paragraph max - **Tactical framing**: Comparisons to training concepts or documentary-style observation - **Episode over statistics**: Numbers serve the narrative, not the reverse - **Uneven paragraph structure**: Different lengths, some returning to earlier points ## 3. Structural Decisions - **Opening**: Match result, competition, stage, date - **Chronological flow**: Goal by goal, with the red card as a turning point - **Statistical paragraph**: Standings and what the result means - **Closing**: What the result changes in context — table position, recent form implications - **No summary ending**: Finish on the last factual element ## 4. Data Integrity Rules - No invented causes, moods, or quotes - No "spectacle" or "tense" unless data supports it - No English loanwords when German equivalents exist - Numbers as figures, not spelled out - No talking to the reader or explaining reasoning --- # Implementation ```json { "title": "S # Architectural Decisions ## 1. Data Verification & Filtering First, I need to verify what data is actually available vs. what must be excluded: - Goal scorers and minutes are provided - Red card at minute 7 (I. Egorov for guests) - Yellow cards at minutes 25, 31, 43 - The provided statistics show "Red cards 0, Yellow cards 1" for hosts and "Red cards 1, Yellow cards 2" for guests — but this only counts cards that appear in the events list, not necessarily all cards in the match. I'll only use what's explicitly stated in the events section. - Table positions and points are available - Recent form data is available for both teams ## 2. Voice & Style Architecture Jonas Brehme's voice requires: - **Scene-by-scene narrative**: Moving through the match chronologically but returning to key moments - **Sparse verbal tics**: «und dann», «interessant wird es», «nebenbei» — one per paragraph max - **Tactical framing

#	Mannschaft	Sp	S	U	N	Punkte
1	Niva	22	14	3	5	45
2	FC Slutsk	22	13	5	4	44
3	Lida	22	13	3	6	42
4	FC Energetik-Bgu Minsk	22	12	5	5	41
5	Molodechno-DYuSSh 4	22	12	2	8	38
6	Slonim	22	11	3	8	36
7	Bumprom	22	10	4	8	34
8	Dinamo Minsk II	22	9	4	9	31
9	Wolna Pinsk	22	9	4	9	31
10	Shakhter Soligorsk	22	8	5	9	29

Spielbericht

Die wichtigsten Zahlen

Spielverlauf

Statistik

Form

Bumprom