veles-content/strategies/historic/historic_dimir_mill/1/reflection.md

Reflection Template For Dimir Mill

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.

• Result driver: Record the deciding axis before judging individual plays. Did Dimir Mill win because library pressure crossed the finish line, because Thought Collapse stopped the decisive spell, because Ashiok, Nightmare Muse stabilized, or because the opponent stumbled?

• Mulligan quality: Check whether the opening hand had early blue action, black access by the planeswalker turns, and a real path to mill volume. Flag keeps that contained only expensive payoffs such as Thassa, Deep-Dwelling, Fraying Sanity, or Ashiok, Nightmare Muse without Ruin Crab, Overwhelmed Apprentice, Glimpse the Unthinkable, Drowned Secrets, or stable mana.

• Mana execution: Review every Clearwater Pathway, Temple of Deceit, Fabled Passage, Island, and Swamp decision for color timing. Note whether Fabled Passage was saved for Ruin Crab landfall when legal, cracked too early, or held too long while Thought Collapse or double-spell turns needed mana.

• Velocity check: Count how quickly the opponent library moved from starting size to lethal range. Separate burst cards like Archive Trap, Glimpse the Unthinkable, and Maddening Cacophony from engine cards like Drowned Secrets, Fraying Sanity, Ruin Crab, and Thassa, Deep-Dwelling so tuning does not confuse setup with payoff.

• Engine performance: Ask whether Drowned Secrets, Fraying Sanity, and Thassa, Deep-Dwelling generated enough extra mill to justify their tempo cost. Mark games where these cards were stranded, removed before value, or cast into lethal pressure when immediate mill or interaction was needed.

• Interaction discipline: Audit each Thought Collapse use against the visible stack and board. The key question is whether it countered the spell that changed the clock, protected a lethal mill sequence, stopped a combo or finisher, or was spent on a lower-impact spell because no better plan existed.

• Board survival: Record whether Overwhelmed Apprentice, Ruin Crab, Ashiok token creation from Ashiok, Nightmare Muse, or legal bounce/defensive modes bought relevant turns. If creatures attacked or blocked, judge the decision from visible life totals, combat math, and library clock, not from generic aggression.

• Closing accuracy: Inspect turns involving Fraying Sanity, Archive Trap, Glimpse the Unthinkable, Maddening Cacophony, and Ruin Crab triggers for missed lethal sequencing. Ask whether a burst spell, land drop, kicked or alternate legal mode, or held trap window would have closed sooner.

• Role assignment: Label the game plan as race, control, stabilize-then-burst, or planeswalker pressure. Note mistakes where the pilot played a slow control role while the opponent library was nearly dead, or raced while visible battlefield pressure required defense.

• Stranded-card report: List cards that remained unusable for multiple turns and why. Separate color screw, too much mana cost, wrong matchup texture, no legal target or mode, and timing errors for Archive Trap, Thought Collapse, Thassa, Deep-Dwelling, Fraying Sanity, and Ashiok, Dream Render.

• Sideboard reality: Confirm that no sideboard action occurred because the registered sideboard contains zero cards. For post-board games, evaluate adaptation through mulligans, sequencing, and counterspell targets only.

• Overperformer and underperformer notes: Name the exact cards that exceeded or missed expectations in context. Useful notes include Ruin Crab producing repeated landfall, Overwhelmed Apprentice buying a turn, Ashiok, Dream Render mattering only when legal actions supported it, or Ashiok, Nightmare Muse being too slow under pressure.

Existing User Requests

No additional user reflection requests were supplied.