After Seven Mid-Series Axings, Salman Ali Agha's Remark Challenges the Process That Used a Captain-Less Test as Evidence — Not the Result

At Gaddafi Stadium in Lahore, the microphones were set up in the same room where, three days later, the ODI tri-series final against Sri Lanka would be played. Salman Ali Agha came as the player representative — the same man who, weeks earlier, had been removed from the national squad mid-series along with six others, and who had now been recalled. I was in London, watching the feed with a spreadsheet open in front of me holding three results. When he said that removing players mid-series is not a good thing and that he hoped it would not happen again, the question that the reporting had not asked lit up in my sheet.

The three results arrived in this order: a first Test lost by an innings and 103 runs, a second lost by 194 runs, a third lost by 8 wickets. There is nothing in that sequence that leads anywhere on its own. The real anomaly is the order. The first match was the one Babar Azam missed through injury, with Agha captaining in his place. The second was the one Babar returned for — and the margin grew from 103 to 194. The match in which the team was whole on paper produced the heavier defeat. The match in which the team was incomplete became the primary justification for removing seven players. The stand-in captain was removed. The captain whose absence contaminated the first match has said nothing publicly.

Context: three matches, seven names, one press conference

Questioning the Pakistan Cricket Board's selection process is not new. What is new is that the question came from a man who is himself a product of that process. Agha's path is on record: dropped mid-series, sent back to President's Trophy Grade-I, where he made a triple hundred and a century, then recalled for the upcoming Test series against Sri Lanka. For a selection committee this is the ideal story. Drop a player, he scores domestic runs, he comes back. The system is working. Where else would you find a cleaner example.

Agha did not tell that story in his own words. He used the same journey in the opposite direction. He never mentioned his own removal — not once in the entire press conference did he put "I" at the centre. That restraint is not accidental. A player with a concrete grievance who sets that grievance aside is not making a complaint; he is stating a principle. And the advantage of a principle is that it cannot be read as personal score-settling.

I was not in that room. I had the feed, three scorecards, and the order of the questions. That evening I put the three results into a table — opposition, captain's presence, margin, and the decision taken after the match. Four columns. In two rows the decision changes, and in the third row no decision was needed at all. A sample that small proves nothing. It does tell you how large the evidence was on which a decision that large was taken.

Core: a two-match sample and a seven-man sentence

The cleanest technical objection I have concerns the quality of the three results. Treating a defeat in which the captain was absent as proof of the squad's shallowness is an attribution the data does not support. A No. 3 changes the batting order, the field settings and the dressing-room decision. A defeat by an innings and 103 is not the product of one missing player, but neither is it a clean measurement of whether the other six are worth their places.

The second match was the cleaner evidence and received less weight. Babar returned, the team was full, and the margin grew. If the committee needed a basis for culling seven names, it should have looked at the second match. It looked at the first. The difference is that the man removed in the first was captaining — the man with decision-making responsibility, and therefore the most convenient chair for 'failure' to be pinned to. Removing seven players on a three-match sample is not just a big decision; it is the wrong decision in its shape, because the evidential load per player is less than two matches each.

This is where my own 2026 work comes back. When I weighted the runs of the 2026 England–India Test series by match-state leverage, Virat Kohli's 593 and Sam Curran's 272 collapsed onto the same scale. The point of that small blog was never that Curran was the bigger player. It was that volume and value are different things and the scorecard shows you only one of them. Selection committees always read volume — how many runs, how many wickets — and never leverage, which is to say they never ask under what conditions those runs or wickets were produced.

What happened in Pakistan is the mirror image of that error. They picked the largest margin on the card and attached the largest decision to it, without asking under what conditions that margin was produced. The first match was produced under captain-absence conditions. The second under normal ones. The two do not carry equal leverage, so pooling them into a single evidence bag and cutting seven names from it is technically immature. I know that on a three-match dataset saying this is itself an admission that I do not trust a model. So I am not talking about a model. I am saying that a decision with no more than two matches behind it should have to face the questions that live inside the process — the questions Agha asked.

The domestic triple hundred: an uncontrolled signal

A selection committee can present Agha's triple hundred and century in President's Trophy Grade-I as its own win. To me it is not evidence; it is an unvalidated signal. Converting domestic runs into Test runs requires a deflator — bowling quality, bounce, outfield, opposition standard. Pakistan's domestic structure does not carry that deflator, so a triple hundred is not proof of anything by itself. It becomes proof only when the same batsman reproduces it against Test bowling. The Sri Lanka series is that test, and its result is still in brackets.

This exposes a larger flaw in the selection system: its evidentiary standard runs in different directions depending on who it needs to protect. When a recalled player scores domestic runs, it is called a win for the system. When the same player fails in a Test, it is called the player's ceiling. The system survives both outcomes. A system that cannot be falsified is not a policy; it is a faith. I remember building the 2026 empty-stadium dataset — home win rates in that English summer fell from roughly 55% to 40%, with the drop concentrated in the final session of day four, historically the loudest hour. I published it as a twelve-post thread with the code attached because the sample was small and I owed the reader the limitation first. On the same principle: any defence of a seven-man cull on three matches is as weak as its refutation. Both sides are short of data. The only difference is that one side has already acted and the other is waiting to bat.

Three formats, three squads, and the question nobody answered

The reporter asked whether players are consulted before being rested. That was a procedural question. Agha answered a substantive one — that with three separate squads for three formats, the workload problem is not what it was, and three squads mean workload should not be a large issue.

Three squads lower average load. They do not lower individual peak load. A player picked across all three formats still carries a heavy calendar; a player picked in one carries a light one. The average improves, the variance widens. The freshest example of that variance was Agha himself — in a single window he played President's Trophy Grade-I, returned to the Test squad, and sat in a press conference as player representative on the eve of an ODI tri-series final. The living counterexample to the workload problem the three-squad model claims to solve was sitting on the stage.

There is an old habit visible here too — the line that things have changed, that there used to be only one team. The comparison is fair, but it is being used as proof of improvement where it is only a signal of change. Change and improvement are not the same thing. A structure changed: three squads. Whether that change built a process for deciding who rests when, who gets consulted, and who gets removed mid-series was never answered — and that is precisely the question Agha was best placed to answer, because he has been through that process. He did not. Whether that was an oversight or a deliberate hedge, I do not know.

The choice of stage: final eve, and the same opponent

The timing of the press conference was not accidental. Three conditions overlapped. The tri-series final was a day away, so media presence was at its peak. The opponent was Sri Lanka, the same side due for the next Test series, so the conversation could travel naturally to the Test squad. And Agha's standing had changed — no longer 'the dropped player' but 'the returning player'. Once you have returned, your right to speak is complete and nobody can dismiss you as aggrieved.

That is a calibrated balance of maximum reach and minimum confrontation. Said after a domestic match, the same words could have been waved away as a grumble. Said on the eve of a final, they cannot, because the camera was already there. This was not a reaction. It was a decision.

Contrarian: the bravery is also safe

Here is the part where I have to doubt my own first reading. The easiest interpretation is that a player removed unjustly came back and gave the system an earful. That reading is romantic and probably wrong.

Look at what he actually said. He never said the seven removals were wrong. He never said the selection criteria are poor, that loyalty is weighted above performance, that domestic runs must be deflated before being read as Test readiness. He selected one variable — mid-series, timing. His entire challenge rests on that single word. This is not a complaint; it is a very carefully judged softness. Challenging timing names no one, targets no one, and above all does not question the committee's intent. It says only that a certain action should have happened on a different day. It is a grievance the committee can accept without conceding that any of its decisions was wrong. The loudest voice in the whole story is a voice the other side can absorb at no cost.

That has an expensive consequence. The real question — what the selection criteria are — never reached the stage. Attention was pulled to one component of the process, the 'when', while 'on what basis' sat unanswered. I think of The Oval in 2026. Pakistan made 338/4, Fakhar Zaman 114, and against Mohammad Amir's 3/16 India were bowled out for 158. Everyone around me blamed the pitch. I logged all 222 balls on the back of a match programme. The number that fell out was not the 180-run margin. It was that India's scoring rate halved the moment Amir pitched the ball fuller than six metres. The easiest question that day was about the pitch; the necessary question was about length. Here the easiest question is 'when'. The necessary question is 'on what basis', and it went unanswered.

The reporting ledger: one voice, zero replies

Only one named person speaks in this entire story. No PCB response, not a word from Babar Azam, nothing from the coaching staff, and the other six axed players entirely silent. That silence is a story in itself, but it was not reported as one. The largest sourcing defect for me is that only one of the seven names was ever identified. Without that list we cannot determine whether the cull was concentrated on one faction or spread evenly, and that single fact determines whether the decision was about form or about frustration.

The second defect is linguistic. The most quoted line in the direct-quote block is recorded in English and literally means that dropping the series is not a good thing. Cricket does not drop series; players and teams are dropped. That line is either imprecision from the speaker or distortion in translation or compression. As it stands it is not quotable in that form — and note that the core attitude of the entire press conference sits inside the least reliable sentence in it. The most-used quote is the weakest one.

The third defect is that all three scores sit under a 'Source: None' condition. Scores are easy to verify, but the absence of an official scorecard or series page citation is an editorial failure. Fourth, there is no byline, only a Lahore dateline. For an on-ground report carrying direct quotes, that is a significant traceability gap.

Two items remain on my verification list. The President's Trophy Grade-I is tagged to a 2026-27 season, which does not reconcile with the 8–9 September England tour referenced in the same report, the phrase 'recently concluded', and the 'upcoming Sri Lanka Test series'. That may be a season label, a parsing error, or an error in the original. Until it is settled it stays an open bracket. The spelling of Razaullah still needs checking against the official squad list. And most importantly — when and how Agha was told he was out, and whether he was spoken to beforehand, does not appear anywhere. Without that fact, no judgment on whether the process was sound can be completed.

Workload versus legitimacy: the framework that answers nothing

You may think this is a great deal of weight on one press conference. For me it is about a framework. Cricket now runs on two parallel systems: one that measures performance, one that measures load. The load system looks elegant because it demands no context — you can say a bowler has sent down this many deliveries in eighteen months and the number is not in dispute. But the moment that load has to become a rest decision, it needs something no dashboard contains: a conversation.

What broke in Pakistani selection was not the data; it was the communication. The process of telling a player why he is being removed, when, and on what basis is not a technical problem and no spreadsheet will fix it. It looks to me the way ACL rehabilitation looks — the scan comes back clean and the fear that keeps a player off the ground never shows up, because the system never built an instrument to measure it. The same thing happened here. The arithmetic of load exists, injury risk is being modelled, but the sentence — you are being removed, this is the basis, and if you disagree here is the process — is missing from the system. The day that sentence is added, a seven-name cull can still be contested, but nobody will call it a revolt.

What comes next: the Sri Lanka series is an audit, not a statement

Valued properly, the selection committee has created a problem whose solution it has also authored. If Agha scores against Sri Lanka, the committee will call it a win for its process — a claim in direct contradiction to his own remarks. If he does not, the mid-series cull argument returns in another form, and the answer the committee owes will be the one it is deferring today: what the standard is.

I want to avoid a prediction here, because I have a three-match sample and it will not carry one. But one thing I can say. The moment a second and third axed player speak publicly, that moment will not change this story; it will change its scale. One man's hope is one man's remark. Three men's identical hope becomes a document — not of a press conference, but of proceedings. Babar Azam remains the only silent and heaviest node in this chain. When he speaks it will not be about a net session; it will be about the distribution of power. And if the PCB chooses silence, that too is a statement, read a little later than intended.

When the numbers disagree with the crowd, I check both the query and the noise. This time the numbers are three, and they are quiet. What one man said in that room is only testimony that those three numbers produced a voice clearer than the selection committee's data.