The Indore Selection Correction: Dube Out, and the Arithmetic of Pace Balance

India posted 249/5 in Ranchi and still lost, because West Indies chased 250 with Shai Hope making 102 off 45 (strike rate about 226.7) and Sherfane Rutherford 84 off 37 (strike rate about 227.0). Two batters striking at roughly 227 is not a coincidence; it is the joint signature of a flat surface and a specific death-bowling failure. For the third T20I at Holkar Stadium, Indore, India made two changes: Shivam Dube out and Nitish Kumar Reddy in, Kuldeep Yadav out and Prince Yadav in. The framing of the story as 'why is Dube not playing' misses the point; the real question is what India is correcting. The answer is the bowling resource mix, not the batting order. The series stands at 1-1 with three matches left, so this is not dead-rubber rotation. Indore is historically a high-scoring, batting-friendly venue, which raises bowling risk rather than lowering it. The Dube-for-Reddy swap is near like-for-like in role but tilts the XI toward extra pace depth. The Kuldeep-for-Prince Yadav move is more revealing: India appear willing to sacrifice a specialist wicket-taker, though Prince Yadav's exact role is unconfirmed in the source. No confirmed injury explains Dube's omission; the source frames it as a selection decision, and the 'according to reports' phrasing is a sourcing caveat. The contrarian read is that correlation is not causation: two changes after one failed defence rest on a small sample, and night-match dew in Ranchi may have been the real driver, in which case the Indore fix is cosmetic. Dropping a frontline wrist-spinner is a calculated risk that could backfire on a turning surface. Signals to track: India's death-over economy, Prince Yadav's actual role, and toss and dew conditions.