veles-content/strategies/commander/commander_vivi_ornitier/1/reflection.md

Reflection Template For Vivi Ornitier

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 commander access, a protected combo turn, early pressure, a stack fight, a board wipe, or a failed attempt to close with Grapeshot, Crackle with Power, Thousand-Year Storm, or Underworld Breach.
• Mulligans: note whether each keep had early blue, early red, a castable setup spell, and a credible path to Vivi Ornitier, Rhystic Study, Storm-Kiln Artist, Veyran, Voice of Duality, or another engine before the table became threatening.
• Mana: identify hands or turns where Sol Ring, Arcane Signet, Izzet Signet, Thought Vessel, lands, or treasure-like resources failed to produce the colors needed for interaction, commander deployment, or the finishing spell chain.
• Velocity: ask whether Brainstorm, Ponder, Preordain, Opt, Consider, Faithless Looting, Frantic Search, Windfall, Big Score, and Rhystic Study found action or merely cycled through low-impact cards.
• Engines: record which of Vivi Ornitier, Storm-Kiln Artist, Veyran, Voice of Duality, Harmonic Prodigy, Goblin Electromancer, Thousand-Year Storm, Ral, Crackling Wit, Will of the Jeskai, and Underworld Breach actually survived long enough to matter.
• Removal: check whether Lightning Bolt, Lightning Strike, Pongify, Into the Flood Maw, Chaos Warp, Cyclonic Rift, Vandalblast, Blasphemous Act, and Abandon Attachments answered decisive threats or were spent too early.
• Stack decisions: flag any use of Counterspell, Swan Song, Spell Pierce, Arcane Denial, Fierce Guardianship, Deflecting Swat, or Narset's Reversal on a spell that did not threaten a win, lock, commander, engine, or lethal combat step.
• Closing: identify whether the deck had enough mana, storm count, graveyard fuel, copy effects, and protection when it attempted Grapeshot, Crackle with Power, Underworld Breach, or Thousand-Year Storm.
• Role assignment: record whether the pilot correctly shifted between control, setup, pressure, and combo based on visible board state rather than defaulting to the same role every game.
• Mistakes: list missed land drops, premature wheels, unprotected engine deployment, pass decisions with live interaction, combat attacks that exposed needed blockers, and target choices that failed to advance the visible plan.
• Stranded cards: name any cards repeatedly stuck in hand, especially Crackle with Power, Overpowering Attack, Prismari, the Inspiration, Thousand-Year Storm, equipment, or narrow interaction.
• Overperformers and underperformers: record which exact cards produced wins, stabilized losses, drew removal profitably, or failed despite being cast.
• Sideboard: confirm that Sideboard (0) caused no illegal sideboard action and note whether repeated matchup failures imply a future registered sideboard or maindeck adjustment rather than runtime swaps.

Existing User Requests

No additional user reflection requests were supplied.