# Reflection Template For Bant Airbending Combo

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 early acceleration, a resolved engine, a protected tempo attack, a removal exchange, mana failure, or inability to close after stabilizing. Name the cards involved, especially `Llanowar Elves`, `Badgermole Cub`, `Doc Aurlock, Grizzled Genius`, `Interdimensional Web Watch`, `Aang, Swift Savior`, `Appa, Steadfast Guardian`, and `Airbender Ascension`.

- Mulligans: Ask whether the opener had green mana, an early play, and a credible follow-up threat. Flag keeps that relied on `Cavern of Souls`, `Starting Town`, `Floodfarm Verge`, `Hushwood Verge`, or `Multiversal Passage` without proven access to the colors required by the visible hand.

- Mana: Track every turn where a spell was stranded by color, tapped-land timing, creature-type naming, or missing green on turn one. Identify whether the issue came from land mix, too many expensive threats, or sequencing around `Llanowar Elves`.

- Velocity: Check whether `Bramble Familiar`, `Interdimensional Web Watch`, `Michelangelo's Technique`, and `Skycoach Conductor` converted mana into material progress. Card text check required for uncertain velocity cards; evaluate only confirmed actions and visible outcomes.

- Engines: Record whether `Airbender Ascension`, `Doc Aurlock, Grizzled Genius`, `Aang, at the Crossroads`, or `Aang, Swift Savior` was cast too early, too late, or into a known answer. Note whether waiting would have improved protection, mana, or pressure.

- Removal and disruption: Ask whether `Avatar's Wrath`, `Bovine Intervention`, `Erode`, and `Seam Rip` answered the object that mattered most. Mark cases where an answer hit a low-impact target while a public engine, lethal attacker, graveyard payoff, or hate permanent remained.

- Sideboard: Confirm whether every boarded card had a visible job in the matchup. Track dead draws of `Rest in Peace`, `Erode`, `Seam Rip`, `Kutzil's Flanker`, `Quantum Riddler`, `Emeritus of Abundance`, `Beza, the Bounding Spring`, `Bovine Intervention`, and `Avatar's Wrath`.

- Closing: Ask whether the deck attacked soon enough after stabilizing with `Appa, Steadfast Guardian`, `Aang, Swift Savior`, or multiple creatures. Flag games where the board was safe but the pilot kept passing or developing instead of converting pressure.

- Role: Record whether Bant correctly identified itself as aggressor, tempo deck, stabilizer, or combo-engine deck after sideboarding. Flag role conflict when defensive cards diluted pressure without buying enough time.

- Mistakes: List legal actions that looked suspicious from visible state, including missed land drops, unnecessary attacks with needed blockers, pass decisions under pressure, removal fired before a better target appeared, or overcommitting into a public sweeper cue.

- Stranded cards: Count cards held for three or more turns and explain why. Separate color issues, missing legal targets, unclear card text, matchup irrelevance, and deliberate patience.

- Over/underperformers: Name cards that directly changed the game and cards that repeatedly failed their role. Treat singleton results for `Airbender Ascension`, `Michelangelo's Technique`, `Multiversal Passage`, `Beza, the Bounding Spring`, `Bovine Intervention`, `Emeritus of Abundance`, `Kutzil's Flanker`, and `Quantum Riddler` as signals, not proof.

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