# Reflection Template For Counter Vine

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: Record whether the game turned on `Bazaar of Baghdad`, recursive `Vengevine` pressure, free stack interaction, permanent hate, creature combat, or opposing graveyard hate; name only the visible cards that caused the turn.

- Mulligans: Check whether the opener had a real plan before keeping, especially `Bazaar of Baghdad`, `Serum Powder`, multiple free creatures, `Hollow One`, or enough interaction to survive without Bazaar. Flag keeps that had action but no velocity.

- Serum Powder: Track whether `Serum Powder` exiled critical density such as `Bazaar of Baghdad`, `Vengevine`, `Basking Rootwalla`, `Blazing Rootwalla`, or free blue cards for `Force of Will` and `Force of Negation`. Note whether the new hand actually improved the plan.

- Mana: Review every game where `Wasteland`, `Strip Mine`, `Karakas`, `Yavimaya, Cradle of Growth`, or `Petrified Hamlet` mattered. Ask whether using a land as disruption delayed a needed cast of `Collector Ouphe`, `Fury`, `Basking Rootwalla`, or `Blazing Rootwalla`.

- Velocity: Count turns where `Bazaar of Baghdad` activation converted into graveyard pressure, `Hollow One` cost reduction, `Squee, Goblin Nabob` recursion, or `Master of Death` recursion. Flag Bazaar activations that discarded resources without producing pressure or protection.

- Engine: Confirm whether `Vengevine` triggers were produced by legal creature casts and not assumed from graveyard presence. Note missed creature-chain turns involving `Basking Rootwalla`, `Blazing Rootwalla`, `Hollow One`, and `Master of Death`.

- Interaction: Review each `Force of Will`, `Force of Negation`, `Mindbreak Trap`, `Mental Misstep`, `Force of Vigor`, `Ravenous Trap`, and `Noxious Revival` decision. Ask whether the chosen target was the actual bottleneck or whether the deck spent protection on a low-impact object.

- Removal: Mark whether `Fury` removed a creature that changed race math, protected attacks, or stabilized combat. Flag games where `Fury` was stranded, pitched too early, or pointed at a creature that did not affect the clock.

- Sideboard: Compare post-board draws against the planned role cards. Ask whether `Leyline of the Void`, `Ravenous Trap`, `Collector Ouphe`, `Force of Vigor`, `Karakas`, `Yavimaya, Cradle of Growth`, `Petrified Hamlet`, and the extra `Fury` had visible targets or diluted the pressure plan.

- Closing: Identify games where early pressure failed to close after the first wave. Ask whether the pilot preserved `Squee, Goblin Nabob`, `Master of Death`, `Noxious Revival`, or extra creatures for a second `Vengevine` wave.

- Role: Record whether the deck was supposed to race, disrupt, or recover after hate. Flag turns where the pilot stayed defensive while ahead on clock or attacked while interaction should have been protected.

- Mistakes: Note any legal-action mismatch, pass with relevant interaction, missed `Bazaar of Baghdad` activation, poor pitch-card choice, or attack into visible bad combat. Separate rules-engine uncertainty from strategic error.

- Stranded cards: List cards stuck in hand or exile without function, especially `Fury`, `Force of Vigor`, `Force of Negation`, `Mindbreak Trap`, `Collector Ouphe`, `Karakas`, and `Petrified Hamlet`.

- Over/underperformers: Track which exact cards won games, stabilized games, or failed repeatedly. Separate matchup-specific performance from global quantity conclusions.

## Existing User Requests
No additional user reflection requests were supplied.
