# Reflection Template For Bant Beanstalk

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 was won or lost by early mana, visible battlefield pressure, a resolved `Up the Beanstalk`, a sweeper window, a copied permanent, a sideboard card, or failure to close after stabilizing.

- Mulligans: Ask whether each kept hand had castable early mana, at least one bridge or engine card, and a realistic first interaction point through `Ride's End`, `Day of Judgment`, `Fumigate`, `Ancient Cornucopia`, or `Up the Beanstalk`. Flag keeps that relied on drawing specific lands before acting.

- Mana: Track whether `Floodfarm Verge`, `Hushwood Verge`, `Willowrush Verge`, `Meticulous Archive`, `Lush Portico`, `Hedge Maze`, `Restless Vinestalk`, `Blossoming Sands`, or `Thornwood Falls` entered at the wrong time for the required spell. Note every game where `Ancient Cornucopia` fixed the curve, arrived too late, or was stranded by pressure.

- Velocity: Check whether `Up the Beanstalk` entered before `Overlord of the Hauntwoods`, `Overlord of the Mistmoors`, `Doppelgang`, or `Ornate Imitations` when the board allowed it. If not, record whether the deviation was forced by legal actions, survival pressure, or a sequencing mistake.

- Engines: Record how many cards `Up the Beanstalk` generated before the game ended, how often Overlords stabilized the board, and whether `Omenpath Journey`, `Mythweaver Poq`, or `Lurker in the Deep` mattered before the opponent’s plan decided the game.

- Removal: Review each `Ride's End`, `Day of Judgment`, and `Fumigate` decision for timing. Ask whether point removal answered a threat that changed the sweeper schedule, or whether it was spent on a creature a planned reset would already handle.

- Copy effects: For each `Doppelgang` and `Ornate Imitations`, record the visible target, mana spent, immediate board impact, and whether waiting would have increased value or exposed the game to lethal pressure. Flag casts with no decisive target.

- Sideboard: After sideboarding, ask whether `Authority of the Consuls`, `Three Steps Ahead`, `Rest in Peace`, `Thieving Aven`, or `Seized from Slumber` matched the revealed opponent plan. Card text check required for `Thieving Aven` and `Seized from Slumber`; judge their role only from legal action text and observed outcomes.

- Closing: Record whether the deck stabilized but failed to convert the game with `Overlord of the Hauntwoods`, `Overlord of the Mistmoors`, `Doppelgang`, `Ornate Imitations`, `Restless Vinestalk`, `Mythweaver Poq`, or `Lurker in the Deep`.

- Role: Ask whether the pilot correctly became control against fast pressure, midrange engine against fair decks, and permission-aware tapout control after adding `Three Steps Ahead`.

- Mistakes: Identify any pass with available relevant action, any sweeper held through lethal pressure, any premature engine spell into visible danger, and any missed chance to develop `Up the Beanstalk` before a high-cost spell.

- Stranded cards: List cards stuck in hand at game end and why: color, total mana, no target, bad timing, opponent pressure, or sideboard mismatch.

- Overperformers and underperformers: Rank cards by observed game impact, not expectation. Separate main-deck cards from sideboard cards so tuning does not confuse matchup tools with core engine pieces.

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