# Reflection Template For Dimir Control

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 survival, mana development, engine deployment, interaction timing, closing speed, or a single unresolved threat. Tie the answer to visible turns and exact cards such as Caustic Exhale, Dispelling Exhale, Villainous Wrath, Unholy Annex // Ritual Chamber, Draconic Fealty, Marang River Regent, Scavenger Regent, or Ugin, Eye of the Storms.

- Mulligans: note whether each opener had blue, black, castable interaction, and either a proactive engine or enough removal to survive. Flag any keep where Drowned Catacomb, Gloomlake Verge, Watery Grave, Temple of Deceit, Fountainport, Soulstone Sanctuary, or Maelstrom of the Spirit Dragon delayed Caustic Exhale, Dispelling Exhale, Nowhere to Run, Villainous Wrath, Unholy Annex // Ritual Chamber, or Ugin, Eye of the Storms.

- Mana: track every turn where a spell was stranded by color, tapped lands, conditional lands, or utility-land sequencing. Record whether Island, Swamp, Watery Grave, Gloomlake Verge, and Drowned Catacomb supported early interaction, and whether Fountainport, Soulstone Sanctuary, Temple of Deceit, or Maelstrom of the Spirit Dragon created tempo loss or meaningful late utility.

- Velocity: ask whether the deck spent mana every relevant turn without falling behind on board. Mark hands that had removal but no engine, engines but no survival tool, or too many expensive closers before the board was stable.

- Engines: evaluate whether Unholy Annex // Ritual Chamber, Draconic Fealty, Firdoch Core, Cunning Azurescale, Spirited Simulacrum, and Ugin, Eye of the Storms generated material advantage after resolving. Card text check required before attributing exact trigger, mode, or transformation value.

- Removal: review whether Caustic Exhale, Nameless Inversion, Nowhere to Run, and Villainous Wrath were spent on threats that changed the visible clock or protected a key engine. Flag any game where removal was held too long against lethal pressure or spent too early before a larger visible threat.

- Stack interaction: review every Dispelling Exhale decision for target quality. Mark whether it answered a payoff, protected a resolved engine, stopped a tempo swing, or was spent on a low-impact spell that let a later threat resolve.

- Closing: record whether Marang River Regent, Scavenger Regent, Ugin, Eye of the Storms, Soulstone Sanctuary, Fountainport, or creature pressure ended the game quickly after stabilization. Flag games where the deck stabilized but failed to convert before the opponent rebuilt.

- Role: ask whether the pilot correctly shifted between control, tap-out engine, and pressure roles. Identify turns where passing with interaction was better than committing a closer, or where waiting let the opponent gain inevitability.

- Mistakes: log visible mis-sequences, missed land-use opportunities, unnecessary life loss, weak target choices, and tap-out turns that exposed the deck to a known or strongly telegraphed play. Separate pilot errors from rules-engine uncertainty.

- Sideboard: confirm that no sideboard action was proposed or expected because the registered sideboard has 0 cards. If the match loss pattern required post-game adaptation, record the missing role rather than an illegal card movement.

- Overperformers and underperformers: list exact cards that repeatedly won games, stabilized boards, stranded in hand, or failed to answer common threats. Keep conclusions tied to logs, not assumed card text.

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