B · Engine & Sequencing · §11
Two battlefields that feed the engine and one that fixes the deck’s worst structural problem.
Conquering here burns two from the top of your deck. That is two cards off Rhasa’s cost, two more and Harrowing targets, and a point, from one action. It is the battlefield the deck most wants to be fighting over and the default first choice.
The cost is real: you are milling yourself with no selection, and the card you burn might be the Baron you wanted or the the matchup needed. Against a fast deck that is a fine trade. Against a deck you need a specific answer for, it is not free.
Conquering here discards one and draws one. Unlike it is selective: you choose what goes to the trash, which makes it the place to send a stranded before is castable, or a Rhasa you cannot afford yet.
A unit defending alone here has two less Might. This is the answer to the structural problem in §3: fourteen small units cannot beat one large defender in a straight fight, and this makes the fight not straight.
first in most matchups, because the engine and the scoring point the same way. against anything built on a single protected defender. when you need a particular card in the trash more than you need depth.
This suite has no card-draw battlefield and no protective one. That is consistent: the deck draws through selectors and protects through bounce, and a fourth effect competing for those jobs would be worse at them than the cards already doing them.