veles-content/strategies/pauper/turbo_fog/1/reflection.md

Reflection Template For Turbo Fog

For each loss, name one primary cause and one secondary cause. For each win, name the card, package, or tactical policy that most contributed to the win. Classify each result as a card quantity problem, card selection problem, mana problem, tempo problem, matchup problem, sideboard problem, pilot sequencing problem, or closing-power problem. Report mana performance, sideboard impact, stranded cards, overperforming cards, underperforming cards, and whether the Deck Strategy or Tactical Policy guidance was followed.

• Deciding factor: Identify whether the game was won or lost by fog density, mana development, stack interaction, library pressure, sideboard hate, or a noncombat axis that Moment's Peace, Tangle, Fog, and Weather the Storm could not answer.

• Mulligans: Record whether the opener had early blue mana, early green mana, at least one draw or selection spell, and a survival plan before the first lethal combat; flag keeps that relied on Simic Growth Chamber or Dimir Aqueduct without an untapped land.

• Mana: Check whether Growth Spiral, Ash Barrens, Tangled Islet, Foreboding Landscape, and Lorien Revealed helped fix the right colors on time, and note every turn where Arcane Denial or Moment's Peace was stranded by sequencing.

• Velocity: Track whether Brainstorm, Behold the Multiverse, Lorien Revealed, and Embrace the Paradox found new fogs, counters, or Stream of Thought quickly enough, or whether they were cast while lethal combat required holding mana.

• Engine access: Record when Stream of Thought became the win condition, whether it was protected by Arcane Denial, Muddle the Mixture, or Dispel after sideboard, and whether waiting would have improved safety.

• Prevention timing: Audit each Moment's Peace, Tangle, Fog, and Weather the Storm for necessity; mark whether it prevented lethal, preserved a key life buffer, or was spent before the opponent committed enough public pressure.

• Interaction use: Review each Arcane Denial target and ask whether the countered object actually beat fogs, life gain, draw, or decking, since giving the opponent cards is only acceptable against decisive threats.

• Graveyard handling: Note whether Bojuka Bog or Faerie Macabre hit a visible graveyard payoff, recursion target, flashback card, or reanimation window, and flag any use that happened only because cards were present.

• Sideboard impact: After sideboarding, measure whether Dispel, Hydroblast, Blue Elemental Blast, Faerie Macabre, or the extra Stream of Thought had legal, relevant targets; identify any sideboard card that diluted fog density without changing the matchup.

• Closing: Record how many turns elapsed after survival was stable before Stream of Thought or decking pressure began; flag games where the pilot kept drawing without moving toward a win.

• Role accuracy: Ask whether the pilot correctly stayed as hard control, shifted into inevitability, or mistakenly played like a tempo deck by spending mana on low-impact draw during required defense turns.

• Mistakes and stranded cards: List every stranded card by exact name, including Arcane Denial without blue mana, Weather the Storm without meaningful storm/life pressure, Embrace the Paradox with unsafe timing, or sideboard blasts without legal red targets.

• Overperformers and underperformers: Name the cards that changed the game state most often, then separate true performance from matchup texture, draw order, and whether the rules engine offered legal actions at the expected windows.

• Card text verification: Mark any line involving Heritage Reclamation, Foreboding Landscape, or exact Stream of Thought recursion if the pilot's reasoning depended on text not confirmed by the rules engine; write Card text check required in the run notes.