# Reflection Template For Mono Green

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 the turn where the game stopped being about normal creature sizing and became a race, a stall, or an engine fight. Record whether Mono Green won by early Llanowar Elves pressure, repeated creature development, a scaled threat from Hardened Bonds or Innkeeper's Talent, or a closer such as Surrak, Elusive Hunter, Tyvar, the Pummeler, Frenzied Baloth, or Ouroboroid.

- Mulligans: Check whether kept hands had a castable early creature, enough Forest or other green sources, and a credible second play. Flag any keep where Hidden Grotto filtering, unsupported Hardened Bonds, unsupported Longstalk Brawl, or no-creature support cards delayed pressure.

- Mana: Record whether Llanowar Elves survived long enough to matter, whether two-land hands curved naturally, and whether Hidden Grotto or Oakhollow Village entered sequencing in a way that cost a threat, removal spell, or protection turn. Note any game where the deck had spells but not enough green mana to double-spell.

- Velocity: Count games where Mono Green used turns two through four to add battlefield power instead of waiting with reactive cards. Mark whether Gene Pollinator, Mutable Pupa, Pawpatch Recruit, Fountainport Charmer, Amber-Plate Ainok, or Warden of the Grove produced relevant early pressure from visible board state.

- Engine cards: Evaluate whether Hardened Bonds and Innkeeper's Talent increased damage, broke stalls, or only amplified creatures that were already winning. Flag support-card draws that failed because no creature stayed on board.

- Removal: Review every Longstalk Brawl, Bite Down, Dragon Sniper, Scrapshooter, and fight-style action for target quality. The target should have changed lethal math, removed a key blocker, stopped evasive pressure, or interrupted a public engine rather than simply consuming mana.

- Sideboard: Compare added role cards against public opponent evidence. Bite Down, Scrapshooter, Heritage Reclamation, Keen-Eyed Curator, Scavenging Ooze, Pawpatch Formation, Defend the Rider, Synchronized Charge, Frenzied Baloth, Chittering Illuminator, Surrak, Elusive Hunter, and Tyvar, the Pummeler should each answer a visible matchup need.

- Closing: Check whether large attackers were committed soon enough after the opponent stabilized. Record missed chances to force damage with Surrak, Elusive Hunter, Tyvar, the Pummeler, Frenzied Baloth, Ouroboroid, or Synchronized Charge when legal actions showed a short clock.

- Role accuracy: Label each game as aggressor, stabilizer, or midrange pressure deck. Flag turns where Mono Green acted reactive while ahead, attacked recklessly while behind, or spent mana on low-impact graveyard or utility actions instead of changing board pressure.

- Mistakes: Review attacks that lost the only relevant blocker, protection held through a lethal window, removal aimed at low-impact targets, and support spells cast before creatures. Use Veles-visible legal actions and logged state only; do not infer hidden cards.

- Stranded cards: List cards stuck in hand for multiple turns and why. Separate mana problems from board-dependence problems for Defend the Rider, Longstalk Brawl, Hardened Bonds, Innkeeper's Talent, Dragon Sniper, and expensive sideboard threats.

- Overperformers and underperformers: Name cards by observed game impact, not expectation. A card overperformed only if it changed damage, tempo, survivability, or engine denial in the log; a card underperformed only if it was legal, castable, and still failed to matter.

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