From 89/3 to 111 in the Irani Cup: Jammu & Kashmir's Collapse and the Real Layer of Domestic Red-Ball Cricket

11:50 pm. The room in Brisbane is cold; a scorecard sits frozen on the laptop screen. On the first page of my notebook I have written 89/3, and a little below it, 111. Between the two numbers lie seven wickets and twenty-two runs. After years of watching matches I have learned that a figure like this does not speak on its own—it has to be made to speak, and that takes patience, context and quiet notes. I am an archaeologist of potential; I brush the dust off what the market overlooks. I watch for the pause that comes before the decision, not the highlight after it. Today's number is the same kind of thing—a picture of a domestic cricket culture hidden inside a collapse.

The full details of the match I am writing about are not in my hands. What I have is a result and the outline of a collapse: Rest of India won the Irani Cup, Jammu & Kashmir went from 89/3 to 111 all out, and the two agents of that fall were Mukesh Kumar and Akash Deep. No venue, no date, no innings breakdown, no individual bowling figures, no toss, no pitch character. For an archaeologist this is an incomplete dig site. But layers can still be read inside incompleteness—if we do not mix in invented facts and read only what is genuinely written.

The Irani Cup: a system inside a match

The Irani Cup is an annual fixture of India's domestic first-class calendar, run by the Board of Control for Cricket in India. Two teams meet. On one side is the Ranji Trophy champion—the best domestic side of that season; on the other is Rest of India, a composite XI drawn from across the domestic teams, usually carrying a bowling attack close to national standard. First-class cricket means multi-day, red-ball play, where sessions, follow-ons and declarations all apply. A sudden cluster of seven wickets inside one innings is therefore not an unnatural event; the very character of red-ball cricket hides this kind of rupture inside it.

Jammu & Kashmir are playing this match, which does not mean they are an ordinary side. To reach the Irani Cup as Ranji champion, a team must first put together a strong Ranji season. The collapse therefore stands on the exact opposite side of their season narrative—it is an exceptional session, the picture of a single rupture, not a verdict on the whole team's quality. Yet this is precisely where the media makes its biggest mistake: it turns seven wickets in one innings into a certificate about an entire batting culture.

The composition of Rest of India matters. It is not a franchise, nor a single state's team. It is a selected side in which the best domestic performers are gathered, and it often includes pacers hovering on the edge of the national team. The Irani Cup is thus structurally an unequal meeting: a team built over a season against a collection of stars. History leans toward Rest of India in this inequality, and that is no hidden mystery—it is the simple product of the selection process.

The result itself is therefore not surprising. The surprising part is the shape of the collapse: seven wickets, twenty-two runs. Inside that shape lie the real cricket information, the real question and the real warning.

Seven wickets for twenty-two runs: the grammar of a collapse

The first thing to hold onto is the arithmetic character of this collapse. 89/3 means three wickets down for 89; the top order was holding somewhat. Then all out for 111 means the last seven wickets fell for just twenty-two runs. In other words, across the final two-thirds of the innings the batting line-up produced virtually no resistance. This is a familiar design in red-ball cricket: the top order builds a partnership, then one wicket breaks that partnership's rhythm, and behind it the lower order falls inside twenty or twenty-five runs.

I have seen this many times: such a rupture does not happen in a single ball; it happens as one ball is added to the next. A wicket brings a new batsman in, and a new batsman means fresh time needed to settle—and that window is exactly the pacer's greatest opportunity. In red-ball cricket that window is wider, because before settling, movement off the pitch forces the batsman into self-defence. Seven wickets for twenty-two runs is no accident; it is a window in which one set of bowlers attacks together and one set of batsmen breaks together.

Two names of pace, and the makers of broken rhythm

The two names attached to this collapse—Mukesh Kumar and Akash Deep—are both pacers, and both are familiar faces of Bengal and the Indian team. One signal is clear here: this rupture did not come from the slow squeeze of spin; it came from the jolt of pace. Spin usually drains an innings slowly; pace, especially with the new ball or the second new ball, suddenly harvests wickets. Both pacers being named together suggests a paired attack—perhaps the new-ball pair, or pressure from two ends at first change.

But here I must stop, and stopping is important. The report names two pacers, but there is not a single digit about who took how many, what their economy was, how many overs they bowled. So I cannot put these bowlers' achievement into numbers; I can only say their role was at the centre of the collapse. An analyst who leaps from these two names straight to a verdict—such as 'they are ready for the national team'—is turning a partial picture of one innings into a career certificate.

A lesson from my long experience applies here. Performing well in domestic red-ball cricket and performing well at international level are separated by a quiet wall. That wall is called consistency. Dropping seven wickets in one match can be easy; holding that rhythm across five straight matches is hard. Triggering a collapse for Rest of India is admirable, but the national door opens on that consistency, not on a single day's flash.

International-standard pace against domestic batting: where the gap is

Now to the biggest lesson of this collapse: what happens when a top domestic batting line-up meets international-standard pace? Part of the answer is written in this scorecard—rupture. Jammu & Kashmir are a best-of-Ranji side; Rest of India are a gathering of stars. The gap this clash reveals is not a gap in batting talent but a gap in familiarity. The pace a batsman sees year after year in domestic cricket differs from the combination of speed, bounce and accuracy at the national edge. When that difference surfaces inside one innings, it can appear as a seven-wicket collapse.

But caution is needed here. A single innings' collapse is not proof of a domestic batting side's overall weakness. It is the story of a particular day, a particular pitch, a particular broken rhythm. An archaeologist never draws the whole animal from one bone; he says, 'at this layer this evidence was found, the rest of the dig is pending.' In the same way, from this collapse I can say—they lost one session; I cannot say—they are weak in batting.

This is where the Jammu & Kashmir story actually becomes interesting. When a side reaches the Irani Cup as Ranji champion, the highest level of examination lies before it. Failing that examination does not mean defeat; it means a measuring stick. The question is—what will they learn from this stick? Next season, against the same pace, can they stand better? That is the real question of development, and that is the real layer of domestic cricket.

How a number begins to lie

One of my biggest lessons came from football analysis, but it holds equally true in cricket. For years in football I watched a single metric—say possession, or some modern expected-goal-type measure—slowly turn into a religion. A team finishes with sixty percent possession and people think it controlled the match, when much of that possession was sideways passing that created no dangerous chance. In the same way a single expectation metric slowly becomes an excuse to 'explain' in-game decisions, a player's form, or a referee's standard—though it cannot explain them at all.

In cricket the easy form of this disease is scoreline-worship. 89/3 to 111—the number is true, but the number alone explains nothing. On what pitch, in what light, in which innings, with how much lead, which bowler bowling at which moment—without this context the number is only a shadow. A scoreline is never the grammar of an innings; it is one sentence of that grammar, and a sentence gives the wrong meaning if the rest of the page is not read.

So when reading this collapse I first ask—at how many runs did it begin? Answer: 89/3. Then I ask—for how many runs did the last seven wickets fall? Answer: twenty-two. Together these two answers give me a 'cluster', a bundle of wickets falling in pairs. In red-ball cricket this cluster is the biggest signal, because it tells where the rhythm broke. But the cluster does not say which ball broke it; that needs ball-by-ball detail, which is absent here.

The body of pace: workload and the risk of rupture

One unspoken risk of this match deserves mention. Mukesh Kumar and Akash Deep are both fast bowlers, and a fast bowler means a body sensitive to workload. India's busy calendar—domestic red ball, white-ball series, the IPL—makes an over-count a delicate balancing act for any pacer. When two pacers together bowl a side out for twenty-two runs, then alongside the praise a question is born: how much did this spell add to their season's total load?

This is not criticism; it is arithmetic. The long-running discussion about managing pacers in the international calendar becomes more relevant after a match like this. When a bowler sends down a long spell in a domestic game, those overs are deposited in his body's ledger. The question is—will that deposit return as interest in the next series, or as loss? The scorecard does not hold this answer; the workload report does, and that is absent here.

The contrarian thought: the collapse that is not the story

Now to the part where the conventional story has to be turned over. The first reaction is—'pace crushed Jammu & Kashmir.' But pause and look, and this result is in fact expected. Rest of India is a composite star side; historically such sides are ahead against the Ranji champion. So what is new here? The answer: nothing, if we look only at the result. The novelty hides elsewhere.

The real story is not this collapse; the real story is Jammu & Kashmir being there at all. When a side climbs to the summit of domestic cricket and faces the highest examination, its collapse is not a failure—it is a boundary marker. This marker shows how much distance still remains between the best domestic side and the highest standard. Measuring that distance is far more valuable than the collapse, because it shows the road ahead.

The second contrarian thought concerns these two pacers. The easy story is—'they are Rest of India's heroes.' But as a scout I know that two bowlers being named in a collapse sometimes means only that the reporter picked the two best-known names. Who actually took how many wickets, who merely built pressure—that difference cannot be read without figures. So before building heroes, waiting is a duty. This habit of reading character over the long term has taught me that a season, not a single day's flash, reveals the true bowler.

What I will watch next

I am an archaeologist of potential, so my work is to record every layer of this collapse and match it against the next layer. Three things I will watch. First, the true figures of these two pacers—who took how many, who bowled how many; only with numbers can the achievement be measured. Second, Jammu & Kashmir's next red-ball innings—whether this collapse was an exception or the start of a pattern. Third, the selection window—whether this match's performance earns a place in any national squad.

At sixty-three I have learned that silence is the most honest scout in the room. The story of a collapse does not end in seven wickets; it ends next season, when the same batsman stands before the same pace. I will wait for that moment—because the answer is written there, not in this report.