Rekindling Phoenix

The recursion is the whole point, and the sequencing is what makes it so annoying to answer. Killing this body does not end the threat: its death trigger leaves behind a 0/1 Elemental token that reassembles the bird on your next upkeep, and it returns the Phoenix to the battlefield rather than to hand, sidestepping the sorcery-speed bottleneck and the mana cost of a recast entirely. To actually break the loop, an opponent has to exile the bird on death, counter it, or remove the token before your upkeep begins. The subtle part is that ordinary removal never touches the token, and neither do most sweepers: the Phoenix dies first, the trigger fires afterward, and the Elemental is created into an empty board with nothing left to sweep. That timing asymmetry is why it demands a specific kind of answer rather than any answer, and why a flyer that pressures life totals while being this hard to keep dead does so much work in a fair deck. Note the restraint baked in, though. The reborn copy gains haste only the turn it returns, the token is a fragile 0/1, and nothing here generates card advantage; you are recurring the same single threat, not assembling a graveyard engine. It sits squarely in the tradition the Phoenix subtype was built to embody: evasive, cheap enough to fight over, and stubbornly recurring until something finally exiles it, one card doing one job again and again.