veles-content/strategies/alchemy/alchemy_mono_green_counters/1/reflection.md

Reflection Template For Mono Green Counters

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: After each game, record whether Mono Green Counters won or lost because it curved out, assembled Hardened Bonds or Earthbender Ascension early, stuck a large creature, stalled on mana, flooded, or failed to close after developing the board.
• Mulligans: Record every keep with zero Llanowar Elves, one land, five or more lands, no early creature, no scaling piece, or only slow cards such as Wildgrove Summoner, Sapling Nursery, and Fecund Greenshell, then judge whether the visible game rewarded or punished that keep.
• Mana: Track whether Forest, Evolving Wilds, Fabled Passage, and Ba Sing Se sequencing enabled timely green mana, delayed a two-drop, stranded double-spell turns, or forced the pilot to choose between board development and holding up a visible sideboard action.
• Velocity: Note whether Llanowar Elves converted into an actual tempo lead, whether tapped lands erased that lead, and whether the deck spent turns improving future counters while the opponent advanced a faster clock.
• Engine quality: Evaluate whether Hardened Bonds, Earthbender Ascension, Mightform Harmonizer, Sapling Nursery, and Fecund Greenshell produced immediate pressure or sat behind an empty battlefield with no good counter recipient.
• Creature curve: Track which early bodies mattered most: Sazh's Chocobo, Badgermole Cub, Wary Zone Guard, and Icetill Explorer should be judged by damage dealt, blocks forced, counters carried, and survival through visible interaction.
• Removal and disruption pressure: Record whether opponent removal punished one oversized creature, whether spreading counters would have been stronger, and whether Meltstrider's Resolve changed any visible exchange; Card text check required for exact Meltstrider's Resolve mode evaluation.
• Sideboard impact: For each sideboarded game, identify whether Soul-Guide Lantern, Keen-Eyed Curator, Origin of Metalbending, Mossborn Hydra, Meltstrider's Resolve, or Vivien Reid affected a public game object, a combat step, a graveyard line, or a closing clock.
• Closing: Mark games where the deck built a large board but gave the opponent extra draw steps, then identify whether Wildgrove Summoner, Mossborn Hydra, Vivien Reid, Fecund Greenshell, or a wider counter spread would have ended the game sooner.
• Role accuracy: Ask whether the pilot correctly played aggro against slow opponents, stabilizing midrange against creature decks, and resilient threat deployment against removal-heavy decks.
• Mistakes: Flag missed land sequencing, delayed Llanowar Elves, premature priority passes, attacks that lost needed blockers, blocks that sacrificed the only counter engine, and sideboard cards deployed without a visible target.
• Stranded cards: List cards stuck in hand for mana, board-state, timing, or legality reasons, especially Wildgrove Summoner, Sapling Nursery, Earthbender Ascension, Vivien Reid, Mossborn Hydra, and sideboard cards with narrow visible uses.
• Overperformers and underperformers: Record which exact cards repeatedly won games, stabilized races, or failed to matter, separating main-deck performance from sideboard performance.

Existing User Requests

No additional user reflection requests were supplied.