E · Optimization & Practice · §18Testing Framework

E · Optimization & Practice · §18

Testing Framework

Record more than match wins. Seven categories that turn a loss into a diagnosis rather than a feeling.

New entry

Mistake taxonomy

Stored in this browser only : no account, no backend, no upload.

From the guide . §18 Testing Framework

Match wins alone do not tell you whether the deck or the pilot is the problem. Seven categories do.

Match context

Opponent archetype, exact variant, play or draw, mulligans taken, cards bottomed, graveyard hate observed, sideboard cards observed, and your final post-board configuration.

Opening-hand structure

Classify each keep as natural combo, Frog setup, Archaeologist setup, surveil setup, fair interaction, -, or a speculative keep. Over enough games this is the single most informative field.

Combo timing

The turn the target entered the graveyard, the turn Goryo was cast, whether the target sat exposed for a full turn cycle, whether Goryo was cast in a main phase or an end step, whether priority was retained after Frog, and which piece of interaction beat or protected the line.

Atraxa output

Cards seen by type, cards actually taken, whether sorcery was missing, and whether what you took created a winning plan or only volume.

Pitch economy

What was pitched to Force, what was pitched to , whether the pitch removed the hand’s only setup, threat or protection, and whether hard-casting would have been better.

Ephemerate output

Classify each one: permanence, evoke line, Riddler permanence, Spider-Man reset, Archaeologist value, protection, or dead and stranded. The last category is the one worth counting.

Sideboard performance

Wrath value and energy paid, Clarion activations prevented, whether Clarion cost you Frog or , Consign targets, whether Riddlers were too slow or exactly right, whether Surgical had a functional target, and whether changed the stack.

Loss classification

Assign each loss one primary cause: mulligan or keep error, mana sequencing, priority or timing, target selection, sideboard construction, role assignment, graveyard-hate exposure, pitch-resource error, variance, or a fundamentally unfavourable matchup texture.

Pilot noteThis is what stops a missed Goryo mill being diagnosed as a deckbuilding problem, which is the most common way pilots ruin a good list.