# Reflection Template For Hidden Strings

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 each win or loss was caused by engine access, survival time, permission pressure, graveyard pressure, sideboard threat quality, or a visible sequencing mistake. Mark the first turn where `Lotus Field`, `Thespian's Stage`, `Hidden Strings`, or `Pore Over the Pages` became usable, and whether that turn was early enough for the matchup.

- Mulligans: note whether the kept hand had a real engine path or only selection. Track hands with `Sleight of Hand`, `Consider`, `Flow State`, or `Artist's Talent` that failed to find `Lotus Field`, `Thespian's Stage`, `Expedition Map`, or an untap chain before pressure became lethal.

- Mana: record every game where `Lotus Field` sacrificed lands before the hand could recover. Note whether `Spirebluff Canal`, `Steam Vents`, `Riverglide Pathway`, `Island`, `Otawara, Soaring City`, or `Lindblum, Industrial Regency` entered or functioned in a way that changed the combo turn; Card text check required for unfamiliar land details.

- Velocity: ask whether `Sleight of Hand`, `Consider`, `Flow State`, `Artist's Talent`, and `Pore Over the Pages` converted into engine pieces or only churned cards. If `Dig Through Time` was cast, record whether it found a decisive card, was delayed by graveyard constraints, or was stranded by visible hate.

- Engine execution: record whether `Hidden Strings` and `Pore Over the Pages` generated a continuing turn or stalled after one untap. Mark any turn where a legal `Hidden Strings` line existed but waiting, interaction, or mana constraints made another play better.

- Interaction: log whether `Into the Flood Maw`, `Divide by Zero`, and `Otawara, Soaring City` bought a full turn, answered the correct permanent or spell, or were spent on a low-impact target. Record whether holding interaction caused more damage than using it.

- Sideboard: record which sideboard cards were actually drawn, cast, or stranded. Track `Anger of the Gods`, sideboard `Divide by Zero`, `Spider-Sense`, `Lier, Disciple of the Drowned`, `Niv-Mizzet, Parun`, `Sphinx of the Final Word`, `Vivi Ornitier`, `Improvisation Capstone`, `Firebending Lesson`, `Iroh's Demonstration`, `Accumulate Wisdom`, `Boomerang Basics`, and `Quantum Riddler`; Card text check required for any sideboard card whose runtime label does not confirm its role.

- Closing: record whether the deck won by combo execution, `Wish` access, `Lier, Disciple of the Drowned` recursion, or sideboard threat pressure. Mark games where the engine produced mana and cards but no legal closer appeared.

- Role: ask whether the pilot correctly shifted between racing, stabilizing, protecting the engine, and grinding. Flag games where the pilot followed a generic combo plan despite visible pressure, open interaction, or a revealed disruptive card.

- Mistakes: identify the first legal action that likely changed the result, including land sequencing, premature `Lotus Field`, unnecessary `Into the Flood Maw`, missed `Divide by Zero`, weak selection choice, or overcommitted engine turn.

- Stranded cards: list cards left in hand at loss or game end, especially duplicate `Lotus Field`, excess `Thespian's Stage`, expensive closers, `Wish`, `Flashback`, `Dig Through Time`, or sideboard cards with unclear text.

- Overperformers and underperformers: compare card impact to opportunity cost, not just whether a card was cast. Credit cards that changed the clock, enabled a deterministic engine turn, protected the decisive turn, or solved a specific sideboard problem.

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