An archetype is a starting model, not a script.

Use labels to ask better questions

An archetype label summarizes where a plan tends to place pressure, how it expects to use time, and which resources it wants to preserve. That summary helps form an opponent range and an opening hypothesis. It becomes harmful when it replaces observation: this is a control deck, so I must attack, or this is an aggressive deck, so every defensive trade is correct.

Treat the label as provisional. Compare it with revealed sequencing, resource use, and the position that actually exists. A plan built around early pressure can draw a resource-heavy hand and need to protect future capacity. A slower plan can become the active pressure player when it develops the only threat and the opponent has the stronger long horizon.

Decision Fieldbook does not list current decks inside these families. Official rules and patch context show why a live game needs time-stamped references, while this page teaches a durable classification method. If you need current lists or event preparation, use a current first-party or specialist source and verify its date separately.

Four broad plan families

A pressure-first plan converts early resources into a clock and asks the opponent to answer on constrained terms. Study how it maintains initiative, protects enough follow-up, and recognizes when further extension adds more risk than pressure. A resource-first plan absorbs or denies early pressure and expects remaining capacity to matter later. Study its safety thresholds, answer allocation, and path from stabilization to a closing plan.

An assembly-first plan needs several conditions to produce a decisive swing or finish. Study how it buys time, protects necessary pieces, and distinguishes essential components from flexible substitutes. An adaptive plan derives strength from choosing among several roles or converting flexible resources. Study the information it needs, the cost of staying flexible, and the checkpoint where ambiguity should become commitment.

These families describe emphasis, not purity. A pressure plan still manages value. A resource plan still needs initiative. An assembly plan can win through ordinary board pressure. An adaptive plan can misjudge the cost of waiting. The useful classification is the one that reveals the next tradeoff.

• Pressure-first: how does current initiative become a clock before resources run out?
• Resource-first: what must be contained, and what later capacity justifies patience?
• Assembly-first: which conditions are essential, and how is time purchased safely?
• Adaptive: what information justifies flexibility, and when must a role be chosen?

Build a plan-family worksheet

For your own list, write the primary family, a secondary family it can enter, and the evidence that triggers the change. Then identify its opening job, strongest resource phase, common bottleneck, flexible resources, and the condition that usually closes a match. This description should remain useful when individual inclusions change.

For an opponent, begin with a range of families and narrow it from observed behavior. Early development suggests pressure but does not prove it. Holding resources may indicate an answer, an assembly need, or simply a weak draw. Ask which plan best explains several observations together, and retain a fallback for the next credible branch.

Translate the worksheet into checkpoints. By the end of the opening, has either side established a clock? At the middle resource phase, who benefits from ordinary exchanges? After a defining resource is spent, did the match move from assembly to pressure or from defense to closing? Checkpoints keep the model connected to play.

Keep the model separate from the live metagame

New releases and balance changes can alter which plans are common, how quickly pressure develops, and which resources are scarce. That is why this page does not name a best archetype, supply win rates, or attach a permanent label to a current list. Such claims require current data, format, rank, region, sample method, and an explicit expiry date.

When applying the framework to current play, record your external source and access date separately. Return to the source after a patch or when your observations repeatedly conflict with the expected range. Do not edit the framework merely because one list rose or fell; revise the family description only if the underlying decision questions no longer fit.

During review, ask where the label helped and where it blinded you. If it produced a useful opening range and pivot signal, keep it. If it caused you to ignore revealed evidence, narrow or replace it. The aim is not perfect taxonomy. It is a better plan under uncertainty.