veles-content/strategies/brawl/brawl_etali_primal_conqueror/1/reflection.md

Reflection Template For Etali, Primal Conqueror

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 whether the game was won or lost by ramp speed, commander access, removal timing, combat math, or failure to convert a large threat. Record whether Etali, Primal Conqueror, Etali, Primal Storm, Hit the Mother Lode, Cityscape Leveler, Sundering Titan, or Chandra, Awakened Inferno actually changed the outcome after resolving.

• Mulligans: note whether the opening hand had castable acceleration, red-green mana, and a path to six or more mana. Flag keeps that depended on only Nykthos, Shrine to Nyx, only a fragile creature such as Elvish Mystic or Llanowar Elves, or top-end cards without Utopia Sprawl, Arcane Signet, Cultivate, Invasion of Zendikar, The Celestus, or Chromatic Lantern support.

• Mana: record every game where color access or land count delayed a legal high-impact play. Check whether Command Tower, Stomping Ground, Commercial District, Rockfall Vale, Copperline Gorge, Temple of Abandon, Wooded Ridgeline, Bristling Backwoods, Hidden Nursery, Hidden Volcano, Mirage Mesa, or basics entered in the right sequence for the visible hand.

• Velocity: ask whether the deck saw enough cards before the decisive turn. Track whether Questing Druid, Bitter Reunion, Grapple with the Past, Threats Undetected, Titania's Command, Trumpeting Carnosaur, Geological Appraiser, Curator of Sun's Creation, and Devourer of Destiny produced meaningful selection, recursion, discovery, or pressure.

• Engines: record whether setup permanents created immediate advantage or sat idle. Review Leyline of Abundance, Nissa, Resurgent Animist, Loot, Exuberant Explorer, Mona Lisa, Science Geek, Cloud Key, Evolving Door, Quicksilver Amulet, Purphoros, Bronze-Blooded, Helm of the Host, and Roaming Throne for timing, payoff, and vulnerability to visible interaction.

• Removal: check whether scarce answers were spent on permanents that affected the next turn cycle. Audit Abrade, Archdruid's Charm, Burn Down the House, Meteor Golem, Cityscape Leveler, Sundering Titan, and planeswalker pressure from Rampaging Raptor for target quality and missed legal alternatives.

• Closing: ask whether the deck turned mana advantage into lethal pressure quickly enough. Track whether haste or immediate-impact tools such as Bitter Reunion, Rabbit Battery, Purphoros, Bronze-Blooded, Fanatic of Mogis, Quakebringer, Urabrask, and Rampaging Raptor shortened the clock or were stranded.

• Role: record whether the pilot correctly chose ramp, control, race, or rebuild posture from visible board state. A game where Burn Down the House was held too long, Etali, Primal Conqueror was rushed into obvious punishment, or Chandra, Awakened Inferno was ignored as a stabilizer should be marked for review.

• Mistakes: log every pass with unused mana when a legal stabilizing or pressure action existed. Also flag attacks that exposed key ramp creatures, blocks that wasted Goldhound, Poison Dart Frog, Writhing Chrysalis, or Spinewoods Armadillo, and target choices made without checking public graveyards, exile, stack, and commander tax.

• Stranded cards: identify cards stuck in hand for multiple turns and why. Separate mana-color failures, timing failures, missing targets, and low-impact legal actions for Lukka, Coppercoat Outcast, Koth, Fire of Resistance, Raiding Schemes, Rocksteady, Crash Courser, Great Divide Guide, Intrepid Stablemaster, and Pinnacle Kill-Ship; mark Card text check required when the tactical reason depends on uncertain text.

• Sideboard: confirm that no sideboard action was attempted because the registered sideboard is empty. If the match exposed an unhandled axis, record it as a deck construction issue, not as a missed sideboard line.

Existing User Requests

No additional user reflection requests were supplied.