RIFTCOMBO

Combo · ENGINE

Ashe, Focused shows the hand and Fallen Feline names what she saw — and against an opponent who Holds nothing the banish never comes back

2 cards · order · verified

Pieces

Payoff

Banish the opponent's hand

Deck

Prerequisites

Steps

  1. Play Ashe, Focused (5 Energy + 1 Power). The chosen opponent reveals their hand; banish the card that most threatens the turn you are about to take.
  2. Read the rest of the hand while it is revealed (424.1: revealing is presenting the card to all players).
  3. Play Fallen Feline to a battlefield you control (2 Energy + 1 Power) and name the best spell still in that hand. 762 asks only that it be a legal card in the format.
  4. For as long as the Feline is at a battlefield, no copy of that spell can be played - including the copies they draw later, since the lock is on the name and 103.2.b lets them run three.
  5. The banished card returns at the start of their next turn when they Hold (315.2.b.2). If they control no battlefield, 469.2 means they never Hold and it never returns.

How it ends

engine only - one card gone for the rest of your turn and one spell name locked out for as long as the Feline stands; neither half scores

Sources

Published elsewhere

Walked here, in this project

How this entry was audited

REFUTE = a refutation pass, with its date and verdict · WOUNDED = the pass found a flaw and the entry was rewritten · BUDGETED = the pass checked the recycle-and-draw ledger · lens = the hunt that proposed it.

HAND-WALKED 2026-09-06 (docs/phase0/walks/2026-09-06-denial-lens-candidates.md), issue #100 candidate 4, REWRITTEN. The pair and the class are right and both uniqueness claims survive a full-pool grep. Two corrections. First, the duration: the issue treats Ashe's banish as lasting until the opponent's Hold as if that were a turn away, when 315.2.b.2 puts their Hold at the very start of their next turn - so the banish covers the rest of YOUR turn and nothing more, which reclassifies Ashe as a burst-turn escort. Second, the finding the issue did not have: 469.2 defines a Hold over a battlefield the player CONTROLS, so an opponent controlling none never Holds and the banish is permanent - the board a denial wall creates. Also added, because 190.6.d's second sentence is a trap this project has been caught by before: the Feline needs a battlefield you actually control, not merely one you brought. Card text verbatim from data/corpus_flat.txt. Ban check: neither code is among the 12 [BANNED] corpus lines nor in data/legality.json. Depends on no unruled reading.

Walked against Core Rules 2026-07-16

Match a deck list against the whole catalogue