Shami, Shastri and the Selection Mechanism: Why 229 Test Wickets Are Priced by a Fitness Report, Not a Tribute

There are two screens on my desk in Bengaluru. On the left, Ravi Shastri's clip is running on loop — the one where he says Mohammed Shami should perhaps have been picked for the two-Test series in New Zealand. On the right, Perth, December 2026: the spell where Shami took 6 for 56. Between the two screens hangs the one question the clip does not answer — what the selection committee had written on its file that week.

The clip carries no date. No venue. No channel, no show, no broadcast day. The material I am working from confirms that Shastri said it, and confirms nothing about when, or in the context of which selection meeting. The information points do not even settle which year the tour starting November 19 belongs to. When the date goes missing, every current-age and current-ranking conclusion has to be filed under data pending verification.

Three papers were sitting on that file at once — the central contract grading, the workload window, and the medical clearance. For the selection committee this was never a talent question. It was a question of pricing availability. Shastri's remark was commentary on that price, not a revision of it.

His argument is essentially about Test-role fit, not a claim that Shami would automatically have run through New Zealand. Shami has 229 wickets in 64 Tests. That is substantial red-ball value. But the report gives no Test average, no strike rate, no New Zealand split, no workload data for the previous twelve months. The career value is clear; the immediate selection value is not.

Ajit Agarkar, the chief selector, questioned the fitness. That gets sold very easily as Shastri versus Agarkar. My method runs the other way: mechanism first, verdict second. The mechanism here is that the two men are pricing two different variables of the same cricketer. Shastri is a broadcaster now; nothing gets signed in his office. His product is experience — he can argue that a man with 229 wickets is worth the clouds in New Zealand. Agarkar's office signs the team sheet. His product is availability. Accountability sits with the man who signs the sheet. Shastri is not being dishonest; he is speaking from the one chair where accountability is zero. That is the least reported part of this whole argument.

New Zealand conditions reward an experienced seamer — cloud, seam movement, lateral movement, a fourth-stump line. All of that is inference, not assessment. There is no venue, no weather, no pitch report. Without a venue, 'New Zealand conditions' is a geographic term, not a tactical variable. And a two-Test series is a small sample. Had Shami played and taken 2 for 90, that would not prove the selection wrong. Had he taken 6 for 40, it would not prove it right. Selection policy is not audited over two matches, though it is audited on television every night, and that asymmetry is why this argument keeps coming back.

Here is the thing I keep returning to. Shami's career-best Test figures came in a match India lost. I watched that spell at 5:30 in the morning Bengaluru time, tea gone cold, watching a scoreboard that said the bowler was winning and the team was losing. Individual bowling numbers do not price team outcomes, and selection debates keep putting both into the same account. When you cite 229 wickets, you are citing a man who was one quarter of a pace group with Ishant Sharma, Jasprit Bumrah and Umesh Yadav — a system, not a person. That system no longer exists in that form. A man who was part of it gets repriced outside it, and the price is lower even when the wicket count is not.

His last Test was the 2026 World Test Championship final. Nothing since. Now there is a Test retirement, and he is available for white-ball cricket only. That is the hinge where the whole debate changes shape: from 'should he have been picked' to 'can he still deliver value with the white ball'. Those are two different questions and putting them on one table is laziness, not analysis.

At 36, the question is never pace. Pace goes last. What goes first is seam presentation — the moment the ball leaves the hand and the seam is not quite upright, and it skids instead of swinging. Then recovery between spells, those twenty minutes that decide whether the second spell looks like the first. Then the fourth-day second-innings spell, where matches are decided and where we at our desks have the least data. All three are measurable. The report contains none of the measurements. What it contains is 15 to 20 overs for Bengal. Eighteen overs in a domestic game proves you can bowl. It does not prove you can carry five days, two flights, three training sessions and a DRS review.

And one plain cricket explanation, forced in so my own framework cannot fool me: perhaps Shami simply was not bowling well enough at that moment. The least dramatic explanation is the least saleable one. But if the structural argument cannot beat it on evidence, the structural argument is worthless. I think here it can — because the selectors had information from outside the ground and Shastri had information from inside a tape, and fitness does not show up on tape.

The more reviews I watched, the less I believed in the technology and the more in the theatre. I first wrote that about DRS, then about VAR, and now it fits Indian selection almost exactly, because of the way the word 'fitness' becomes public. It is a category, not a measurement. Agarkar said there was a fitness question. That is a claim with no number attached — no test, no score, no scan, no percentage of workload completed. Shastri said he should have played. Also a claim, also with no number. Where there is no measurement, the argument collapses into personality, which is why every fitness dispute in Indian cricket becomes a story about who said what to whom.

Here is the inverted point that seems to me the newest thing in this whole debate. Cricket built a tradition of publishing the measurement in DRS by showing ball-tracking; football buried the same measurement in VAR and turned it into rumour. Indian selection found a third route: where the measurement exists, hide it; where it does not exist, announce the category. Medical files are more sensitive than ball-tracking, granted. But if you justify a selection publicly with the word fitness, the word needs a public definition, or the selection is a performance.

I borrow systems from other sports and then test whether the transplant survives contact with a Ranji schedule or an IPL auction, and I say so when it does not. NBA load management: 82 games, a fifteen-man bench, substitutions every three minutes, and the ability to sit a man for a night at zero structural cost. Put that on Test cricket. Eleven players, no substitutions beyond concussion, and a fast bowler who breaks down in the second innings costs you that match and the next one. The transplant fails here not on medicine but on series length. Resting a man for one Test is an NBA protocol; in a two-Test series it means sitting out half the series, with no third Test to come back into.

Formula 1's pit window — tyre degradation, safety car, track position — has a cricket analogue in the contract cycle, the auction cycle and the World Cup cycle. The analogy breaks on pit-stop frequency. A race gives you three stops; a career gives you three or four decision points. F1's model lets you correct fifty times. Cricket's lets you correct four times, in front of everyone.

Follow the money. Shastri's 2027 World Cup pathway rests on three conditions: fitness, IPL form, and an injury vacancy. Two of those are outside the player's control. It is a route driven by vacancies rather than performance, and vacancy-led selection is always weak selection, because you are waiting on your own luck. IPL form is an input, not proof. T20 tests four-over matchup bowling and death overs; ODI cricket asks for ten-over spells, new-ball wickets in the powerplay and phase control in the middle. The IPL can raise a 36-year-old's visibility; it cannot establish his ODI readiness. For that you need a controlled 50-over sample — three or four games where you can see what his ball is doing in the sixth and ninth overs.

Auction arithmetic is its own market. A franchise does not pay for 229 Test wickets. It prices a four-over bowler who is 36, whose workload is unknown, and who has not bowled in a competitive 50-over game in two years. That profile earns a risk discount, not an experience premium. Test legacy and auction price are different markets.

Where could I be wrong? First, by treating Shastri as blameless. He has a microphone, and microphones reward the line that sounds brave. Saying Shami should have played costs nothing and cannot be disproved, because the match was never played. If I question the DRS graphics, I have to question the studio's brave lines too, or my scepticism is selective. Second, by over-theorising. Perhaps Shami was simply out of rhythm. Third, if he had played and gone wicketless, the same studio would have called it a reputation pick.

And the fourth doubt is the one that stings: this debate may be a way of not asking the real question, which is why India has no published workload protocol for fast bowlers over 34. The day that protocol exists, arguments like this one end in half an hour — which may be exactly why it does not exist.

So watch the next home 50-over series. If Shami is in it, 2027 is a plan. If he is not, and the route back runs through the IPL alone, then the 2027 line is a courtesy, not a plan — no selection system stakes a World Cup on a man who has not bowled an over in that format for eighteen months. The other signal is the next central contracts list. That grading will tell you whether the system prices availability or legacy. Open it, and then tell me what happened to 229.