Four years earlier, in a tent, Shivaji had signed away twenty-three of his thirty-five forts to the Mughals.1 In the spring and summer of 1670, he took almost all of them back — not in years, not in a war of attrition, but in roughly four months.2 Purandare calls it "an almost impossible feat," and the word is exact: a stack of stone fortresses, each a separate problem, falling one after another in an avalanche of attacks.3 The blitz starts with Sinhagad and does not stop. Mughal commanders are captured, routed, killed, or flee in fright; one general loses the word "Jung" — "war" — from his own title for running away.4 And the single sharpest feature of it, the thing that made it nearly impossible to stop, was a refusal to play by the season's rules: the Marathas kept fighting through the monsoon, when every other army in the mountains was sitting still in the rain.5
The blitz only makes sense against what came before it. The Treaty of Purandar in 1666 had stripped Shivaji of twenty-three of his thirty-five forts.6 Those were not abstract losses; they were the spine of his territory, the high points from which the Maval country is held. After a three-year break from open conflict — time he spent putting his house in order and re-energizing his forces — Shivaji decided he had had enough and went back to planned aggression.7 Sinhagad fell on the night of 4–5 February 1670, and the triumph there was the match.8
Buoyed by Kondhana, the Marathas set out to recapture the rest, and the success came so swift and smooth that within a matter of only four months almost all twenty-three lost citadels were back in Shivaji's possession.9 The British at Bombay and Surat, watching the speed of it, wrote that Shivaji's "motions have ever been so quick that his designs were rarely yet anticipated," and that he "now marches not before as a thief but in gross with an army of 30,000 men, conquering as he goes."10 The man who had signed the treaty as the weaker party was now moving as the stronger one, undoing the document fort by fort.
The mechanism of the blitz is best read through the men who lost. Each name is a different kind of defeat, and together they show a system, not a streak of luck.
The conquest of the prestigious Purandar in March 1670 set the tone — the Marathas took the Mughal qiledar Raziuddin captive.11 At Nanded the faujdar Fateh Jung Khan fled in such fright that the irascible Aurangzeb stripped the word "Jung" from his title as punishment.12 Ludi Khan, the Mughal governor of Konkan, was routed twice and forced off the coast.13 At Kalyan-Bhiwandi the commander Uzbek Khan was attacked and killed by Shivaji.14 Mahuli near Thane is the fullest little tragedy: the qiledar Manohardas Gaud fought hard and well but, knowing he could not hold, sent his resignation to Muazzam at Aurangabad — and the man who replaced him, Allahvardi Khan, was killed and the fort taken anyway.15 Lohgad and Kohoj fell too, and Salher was scaled with a rope-ladder climb of the same family as Sinhagad's.16 Aurangzeb summoned heavy hitters — Daud Khan, and Diler Khan, who had given the Marathas a hard time at Purandar four years before — and their arrival "failed to stem the tide."17 Bhimsen Saxena, a historian then working with the Mughals in the Deccan, recorded the result in one bleak: "A number of Mughal officers arrived in Aurangabad in a very miserable condition."18
The internal logic underneath all these names is near-simultaneity. Purandare's read — and he flags it as inference, since only Sinhagad left records — is that Shivaji chalked out an elaborate strategy, mapped the details, and assigned specific tasks to specific teams for a push made all at once.19 You do not retake twenty-three forts in four months in sequence; you do it in parallel, with the enemy unable to reinforce one because the next is already falling.
This page hands the vault the systems layer that Sinhagad alone cannot supply. Sinhagad is one heroic night; the blitz is the proof that the night was not a fluke but the first move of a coordinated reconquest. It turns "Marathas were good at surprise" into "Shivaji ran a distributed, parallel, multi-fort operation faster than the Mughal command could respond."
It also gives the vault its clearest case of weather as a force multiplier — the monsoon as a weapon, not an obstacle. Most of the vault's strategy pages assume terrain and timing are constraints to work around. The blitz shows a commander turning the single most disruptive variable in the Deccan calendar, the rains, into an exclusive operating window. That is a transferable principle that reaches far past the seventeenth century. And the British letters embedded here give the vault a rare outside witness — not a Maratha chronicle or a Mughal one, but bewildered English traders describing the speed in real time.
Pick out the one factor Purandare singles out as the standout, and it is not surprise — surprise the Marathas always had. It is the rain.
Every army in the mountains, hills, passes, and coastal corridors was known to rest during the monsoon.20 This was not laziness; it was physics. Movement of men, animals, powder, and supply through the Sahyadris in violent rains is brutal, and the universal practice was to withdraw up the hills and winter quietly. Shivaji intelligently made an exception.21 The British officials in Bombay, writing to Surat, put it in a line that has outlived everyone in it: "Shivaji is not so slothful as the Mughal's forces, for he not only makes hay while the sun shines, but then when it is obscured by violent rains also."22
The leverage in this is enormous and worth spelling out. If your enemy stops fighting for a season, that season becomes a private corridor for you. The same British letter names the harvest: while the Mughal army had "withdrawn forces up the hill for a quiet wintering," Shivaji's men "have not been idle, but have recovered for him Lohgad, Kohoj ... and very lately made an assault again upon Mahuli."23 The forts that fell in the rain fell because no relief column was moving in the rain. The monsoon did not just hide the Marathas; it froze the Mughals.
And the cost to the other side shows up in Bhimsen Saxena's "very miserable condition."24 That phrase is doing more work than it looks. These are Mughal officers arriving back at Aurangabad not just beaten but demoralized, soaked, and stunned that the war did not pause when the rain started. The psychological damage of an enemy who will not observe the season is its own weapon — you cannot rest if the other side never does. The monsoon exception is therefore two attacks in one: it takes forts, and it breaks the assumption that there is any safe time at all.
Feel the rain first. It is the monsoon, the passes are running with water, and every instinct — yours and your enemy's — says wait. Sit with that shared instinct for a moment, because that is exactly the asset. The enemy has already gone up the hill to winter. His relief columns are not moving. His powder is stored, his horses are stabled, his attention is off. The season has done half your work: it has immobilized him for you.
Now move while he cannot. You are not fighting the weather; you are fighting through the window the weather opened. The forts are the same forts, but each one is now isolated — no reinforcement is coming through the violent rains, so every garrison fights alone. Hit them in parallel, not in line: Lohgad here, Kohoj there, Mahuli again, teams assigned, the push near-simultaneous, so that even if word travels, no help can.25
Hold the discipline of not resting. The hardest part is not the first assault in the rain; it is the second, and the tenth, the refusal to take the season off that the whole edge depends on. The moment you rest, you become the Mughal army — slothful, wintering, predictable. The principle to carry out of the wet: find the time your competition has agreed, by custom, not to compete, and work it.
The failure mode is named for you, in period English: sloth. "Shivaji is not so slothful as the Mughal's forces."26 The diagnostic sign of the failure is an army that observes the calendar more faithfully than it observes the enemy.
You can spot it by the season. When a force withdraws up the hill for a "quiet wintering" because that is what is done, while the opponent keeps moving, the withdrawing side has mistaken custom for necessity.27 The Mughals were not weak — they had Daud Khan, Diler Khan, prince Muazzam, a vast army. They lost forts because their tempo had an off-switch the Marathas did not. The second diagnostic sign is the "very miserable condition" of the returning officers: when your own commanders straggle back demoralized, it is usually because they were beaten at a time and in a way they had assumed was safe.28
There is a third, subtler failure visible in the blitz: internal conflict eating the response. The Mughal counter was hamstrung because Muazzam and Diler Khan did not trust each other — Diler feared the prince meant to imprison and kill him, the prince accused the general of dodging his court — and that mutual suspicion is its own kind of sloth, the leadership too busy watching each other to watch Shivaji.29 An army that cannot agree internally cannot move quickly externally, and the avalanche is built precisely to punish slowness.
The sole modern source is Purandare's Shivaji: India's Great Warrior King [POPULAR SOURCE].30 The strongest evidence under the blitz is unusually good for this corpus because it is external: British East India Company letters between Bombay and Surat, quoted directly, describing Shivaji's speed and the monsoon campaigning, plus the Mughal-employed historian Bhimsen Saxena and a Mughal newsletter reporting a 20,000-strong raid in Warhad taking 20 lakh rupees.31 Multiple hostile and neutral witnesses converging is far better warrant than a single Maratha chronicle.
The open question is the central one Purandare himself poses and cannot answer: how was it actually done? [SINGLE SOURCE — by absence] Barring Sinhagad, no surviving records detail how any of the other forts were won; the parallel-teams strategy is Purandare's reasonable inference from the one documented case, explicitly hedged with "must have."32 The "twenty-three forts" and "four months" figures are firm in the source but rounded — "almost all" of twenty-three.33 We should hold the mechanism of the blitz as informed reconstruction, not documented fact, while holding the outcome — the forts changed hands fast — as well-witnessed.
Purandare writes alone in 2022, but the blitz section is where his sources pull in genuinely different directions, and the tension is unusually productive. On one side are the Maratha-internal materials — Sabhasad above all — which give him exactly one fully-narrated fort, Sinhagad, and nothing for the other twenty-two.34 On the other side are the European and Mughal observers: the British factors at Bombay and Surat, the Mughal newsletter-writer, and Bhimsen Saxena, the historian embedded with the Mughal side.35 The convergence is striking and it runs across the enemy line: the British describe Shivaji's "quick motions" and monsoon hay-making with something close to admiration, while Bhimsen, working for the Mughals, records his own side's officers arriving "in a very miserable condition."36 When the hostile chronicler and the foreign trader agree that the Marathas were fast and the Mughals were beaten, the basic outcome is about as secure as Deccan history gets. The tension lives elsewhere — in the gap between this rich outside testimony to that it happened and the near-total silence on how. Purandare has to bridge that gap with inference, and he is honest about it ("All of it must have been backed up by vows, by a sense of opportunity"), which is itself a tell about the sources: the people best placed to record Maratha planning — the Marathas — left the thinnest operational record, while the outsiders who left the best contemporaneous detail could only see the results from the walls of Surat. What the split reveals about the blitz is that its very speed is part of why it is under-documented: an avalanche does not pause to write itself down, and the enemy too busy losing forts to track them is exactly the enemy you want.
The four-month blitz reaches into other domains through two shared ideas: that timing and weather are weapons rather than backdrops, and that surviving a forced humiliation can become the fuel for the comeback that erases it. One door is about when you fight; the other is about why you fight back at all.
The first handshake is with Sun Tzu — Field Intelligence and Signal Reading. Sun Tzu's whole apparatus treats weather, terrain, and timing as readable variables a commander exploits, not endures — heaven and earth as factors to be calculated. The blitz is that doctrine made literal: Shivaji reads the monsoon as an operating window the enemy has voluntarily closed, and walks through it.37 The structural parallel is that both treat the calendar as intelligence — knowing when the enemy will not move is as valuable as knowing where his army is. But there is a tension the Maratha case sharpens. Sun Tzu generally counsels the commander to fight on favorable ground and favorable conditions; Shivaji deliberately fights in the worst conditions, the violent rains, because the unfavorability is shared and his tolerance for it is higher. The insight neither domain alone produces: the decisive edge is not absolute capability but differential tolerance — you don't need good weather, you need to mind the bad weather less than the other side does. The monsoon is a force multiplier precisely because it multiplies the gap between an army that rests on custom and one that doesn't.
The second handshake is with Psychological Resilience and the Survival of Humiliation. The blitz is, emotionally, the answer to the Treaty of Purandar — the humiliation of signing away twenty-three forts in a tent, converted four years later into the satisfaction of taking every one of them back.38 The structural parallel is that resilience here is not passive endurance but a stored, delayed, organized response: Shivaji absorbs the loss, spends three years rebuilding, and then discharges the whole accumulated pressure in one four-month avalanche.39 The insight neither domain alone produces: a humiliation survived intact becomes a precise targeting map. Shivaji did not retake random forts; he retook the specific ones the treaty cost him. The wound dictated the campaign. Psychological resilience, read through the blitz, is not about forgetting the injury but about remembering it accurately enough to reverse it item by item — the survivor who can name exactly what was taken is the one positioned to take it back.
Both handshakes meet at tempo. The rains give Shivaji a window others won't use; the remembered humiliation gives him the motive to use it fully. Weather and wound, together, produce an avalanche neither could produce alone. The Sun Tzu reading explains when the blitz was possible — in the season the enemy abandoned. The resilience reading explains why it was aimed where it was — at the exact forts a remembered injury had marked. Strip out either and the campaign loses its shape: a comeback with motive but no opening stalls, and an opening with no motive gets wasted on easy targets instead of the ones that matter. The blitz works because a precisely-remembered loss met a deliberately-seized window, and the man holding both refused to wait for better weather or a kinder season to settle his account.
The Sharpest Implication. The most destabilizing thing the blitz says is that your competition has probably agreed, by custom, to stop competing during certain seasons — and that this agreement is invisible to the people inside it. The Mughals did not decide "we will lose forts in the monsoon." They decided "everyone rests in the monsoon," which felt like a law of nature, not a choice. Most of your own off-seasons are the same: not necessities but inherited customs you have mistaken for physics. If that is true, the highest-leverage move available to you is not working harder during the busy season but simply not stopping during the season everyone else does.
Generative Questions. (1) The blitz is famous as Sinhagad's sequel, yet the monsoon innovation may be the more transferable lesson — why does the single heroic night eclipse the four-month system in memory, and what does that say about how we record strategy versus drama? (2) Purandare can describe that the blitz happened but not how, because the Marathas left no operational records — what does it mean that the most effective campaigns are often the least documented, and who benefits from that silence? (3) Shivaji retook exactly the forts the treaty took from him — trace the difference between a comeback aimed at the original injury and one aimed merely at general advantage; which is more durable, and why?