Picture a wheel of forts standing guard around Pune, and one fort sitting dead in the middle of the rim where all the spokes meet. That fort is Kondhana, the one everyone also called Sinhagad — the lion-fort. Shivaji took Rajgad and Torna first, but those were empty hilltops nobody was defending. Kondhana was different. It had a garrison, a Bijapur-appointed commander, a reputation, and a slope that made attackers sweat. It was the first fort Shivaji won that someone was actively holding.1 Whether he took it by storming the walls or by quietly bending men with words, the chronicles can't agree — and that disagreement is the whole story.2
Kondhana was not new ground when Shivaji set his eye on it. The fort had passed through hand after hand like a deed that nobody could hold for long. The Khiljis held it first. Then the Bahmani kingdom. Then it slid into the grip of the Nizam Shahi. After 1636 it landed with the Adil Shahi of Bijapur, and — this part matters — it got folded into Shahaji's jagir, the land-grant Shivaji's father held from Bijapur. The paperwork was unusually blunt about it: unlike most other forts in the grant, Kondhana was to sit under Shahaji's own representative. That was a real handhold for the Bhosle family.3
Then the handhold slipped. When Dadoji Konddev — the steward who ran Shahaji's Pune estate and tutored the young Shivaji — died, the Adil Shah moved fast. He pulled Kondhana out of Shahaji's control and installed his own man, Mian Rahim Muhammad, as the officer in charge.4 So when Shivaji reached for the fort, he wasn't grabbing some neglected ruin. He was taking back something Bijapur had just deliberately taken away from his family, and he was prying it out of the hands of a sitting commander. That is why this capture stung the Adil Shah in a way the empty forts never did.
The lion-name is older than the legend. Most people meet Sinhagad through the story of Tanaji Malusare and the night assault of 1670, and assume the fort earned its lion-name from that bloody climb. Wrong order. The two names, Kondhana and Sinhagad, were already being used interchangeably decades earlier, when Shivaji first took it around 1647.5 The lion was there before the man the legend hangs on. That small fact is a crack in the famous epic, and the crack runs deep.
Here is where the page splits into two paths, because the sources do. Two reliable chronicles of Shivaji's life tell the capture of Kondhana two different ways, and neither blinks.6
The first path is the bakhar of Sabhasad. In this telling Kondhana fell to force. Shivaji took it by assault, and once the walls were his, he did the thing that turns a raid into a holding: he planted a thana, his own military outpost, inside it.7 The thana is the tell. You don't establish a garrison post in a fort you stormed and abandoned — you establish one in a fort you intend to keep, run, and answer for. The assault story is a story about permanence.
The second path is the Jedhe Shakavali. In this telling there was no storming at all. The fort came over through diplomatic manoeuvre, worked through a local intermediary: Bapuji Mudgal Narhekar, the deshpande of Khede Bare, one of the Maval valleys.8 A deshpande was a hereditary district record-keeper and revenue man — exactly the kind of rooted local figure who knew who inside the fort could be talked to, paid, or persuaded. In this version Kondhana changes hands not by ladder and blade but by the quiet pressure a well-placed local can apply on a garrison.
Both can't be literally true as written, and the vault does not resolve them into one tidy account. What they share is more interesting than where they split: in both, Kondhana is the fort Shivaji decided was worth the risk of openly provoking Bijapur. Assault or subterfuge, the target was chosen for the same reason — its place at the dead center of the ring.
This page hands the rest of the vault a clean specimen of strategic centrality. Rajgad became the capital, Torna stood as its sentinel — but Kondhana was the lock on the whole Pune door.9 Sitting in the middle of the ring of forts, whoever held it could threaten or relieve every spoke around it. That is the transferable lesson: in a network of strongholds, the decisive node is not the tallest or the richest, it is the one whose position commands the others.
The page also feeds the vault its first crisp example of the assault-versus-subterfuge fork as a documented historiographical problem rather than a romantic flourish. It pairs directly with the mediation method used at Purandar — same campaign, same year, opposite technique — and lets the vault hold "how Shivaji took forts" as a repertoire, not a single move. And it hands the Laine-myth thread a hard, datable fact: the lion-name predates the deed the legend credits it to.
Run the four early captures side by side and Kondhana stands out like a struck nerve. Shivaji took Rajgad — empty. He took Torna — empty, and so unguarded that legend says he found buried war materials and funds lying there for the taking, which he then spent arming his Maval men and building up Rajgad.10 He took Purandar — but he took it by talking his way into a family succession dispute and walking out with the keys. None of these forced Bijapur's hand, because Shivaji and his father could keep up the polite fiction: we are merely holding these for the Sultanate, they stood abandoned, they needed order.11
Kondhana broke the fiction. It was held by a Bijapur-appointed commander, Mian Rahim Muhammad. It was a prized possession precisely because of where it sat and how steep its slopes climbed, and it carried a reputation the other three forts hadn't earned.12 So when the Adil Shah looked at the map, the empty forts told him nothing, but Kondhana asked a question he couldn't unhear: why would a loyal vassal seize the one fort I was actively garrisoning? He answered it correctly. What he was watching was not a son tidying his father's estate. It was a rebel taking his first bold steps.13
That is the case study's payload. The capture that mattered politically was not the grandest or the first — it was the one that crossed a line the others didn't. Shivaji could dress empty hilltops in the language of service. He could not dress the taking of a manned, named, reputation-heavy fort in anything but ambition. The strategic value of Kondhana and its political cost were the same thing seen from two ends.
The fork in the sources sharpens this rather than blurring it. If Sabhasad is right and it was a frontal assault, the provocation was naked. If the Jedhe Shakavali is right and it was diplomatic manoeuvre, the provocation was subtler but no less real — you do not need to storm a wall to be seen pulling a garrisoned fort out from under your overlord. Either way, the Adil Shah read the move, and the backlash followed within the same arc of events: troops dispatched against Shivaji, his father Shahaji clapped in fetters far away in the Jinji camp.14
You are standing on a height above Pune with a hand-drawn map and a short list of forts. Don't look at which is tallest. Torna towers over everything and it taught you nothing — it was empty, it cost you nothing, it bought you nothing but a base. Look instead for the fort whose position makes the others nervous. Trace the spokes. Find where the lines cross. There — the one in the middle, the one with a commander already inside and a slope that will cost you blood. That is the lock.
Now feel the second decision, the one the chronicles fight over. You have two tools in your hand. One is the ladder: storm it, plant your thana, make it permanent, accept that everyone will see exactly what you did. The other is the whisperer: find your Bapuji Mudgal Narhekar, the rooted local who knows which man inside can be turned, and take the fort without raising a single ladder. Both put the lock in your pocket. They differ only in how loud the taking is — and how fast your overlord reads it.
Here is the part you cannot dodge: taking the lock is the move that ends the pretense. The empty forts let you keep saying you serve. The garrisoned center forces a confession. So before you reach for it, count the cost of being seen. Shivaji reached anyway, and the day he did, the clock on open war started running.
You can feel this strategy go wrong in a few ways. The first is grabbing height for its own sake — collecting the tallest, most dramatic forts while the quiet middle node stays in someone else's hand. Towers impress; hinges decide. A campaign that takes Torna and leaves Kondhana has the scenery and none of the leverage.
The second failure is taking the lock without the means to keep it. A thana — a standing garrison — is what turns a capture into a holding. Storm a fort, raise no outpost, march away, and you have done a raid, not a conquest. The fort that changes hands and isn't garrisoned is a fort you'll have to take again.
The third is misjudging the noise. Whisper a fort out from under your overlord and you might buy months of useful ambiguity; storm it in daylight and the answer comes fast. The error is not choosing assault or subterfuge — it is failing to count, before you move, how loudly the taking will speak to the man you're stealing from.
The sole modern source here is Vaibhav Purandare's Shivaji: India's Great Warrior King (Juggernaut, 2022) — a narrative biography for a general readership. [POPULAR SOURCE] Purandare is reliable on the broad sequence and is unusually careful to flag where his own underlying chronicles disagree, which is itself the central evidentiary fact of this page.
The live tension is the method of capture. [SINGLE SOURCE] for each branch: the assault-plus-thana account rests on Sabhasad; the diplomatic-manoeuvre-via-Narhekar account rests on the Jedhe Shakavali. These are not reconciled, and this page deliberately does not reconcile them — preserving the contradiction is the point. Note also that Purandare himself hedges the framing as Shivaji winning the fort "by way of either assault or subterfuge," signalling he will not adjudicate between his two chronicles.15
A second, smaller tension sits in the naming. The interchangeability of "Kondhana" and "Sinhagad" is stated plainly, and it carries weight beyond geography: it dates the lion-name to before the 1670 Tanaji episode that popular memory treats as its origin.16
Open questions: Which chronicle is closer to the event, and does the answer change how we read Shivaji's early method — improviser or planner? Does the establishment of a thana in the Sabhasad account decisively favor the assault reading, since a garrison post implies a contested taking rather than a negotiated handover?
Purandare is the only modern voice on the page, so the real argument is between the source-voices he carries inside his narrative: Sabhasad's bakhar and the Jedhe Shakavali. Both are treated as reliable chronicles of Shivaji's life, and both converge on the structural facts — that Kondhana was held by a Bijapur commander, that it sat at the strategic center of the Pune ring, and that Shivaji took it early. Where they split is method: Sabhasad gives a clean military story, an assault followed by the planting of a thana, while the Jedhe Shakavali gives a political one, a fort eased over through the offices of a local deshpande, Bapuji Mudgal Narhekar. The split reveals something neither chronicle states on its own. Sabhasad, by adding the thana, is interested in legitimacy-through-permanence — Shivaji as a ruler who garrisons and holds. The Jedhe Shakavali, by foregrounding a named local intermediary, is interested in legitimacy-through-rootedness — Shivaji as a man embedded in the Maval country who works through its own hereditary officers. The same capture, read by two chroniclers, becomes two different arguments about what kind of power Shivaji was building. Purandare's restraint — refusing to pick — is the honest move, and it leaves the reader holding both portraits at once.
A fort in the center of a ring and a piece on the center of a board are the same problem wearing different clothes: positional dominance, where the value of a thing is not in the thing itself but in what its position lets it threaten.
History (strategy): Sun Tzu — Field Intelligence and Signal Reading — Sun Tzu's commander wins by reading the field before he moves, choosing the engagement where position already favors him. Kondhana is that doctrine made literal: the fort whose location commands every other fort in the ring. The structural identity is "the decisive node is positional, not intrinsic." The tension is in the reading running backward — here it is the Adil Shah who reads the signal correctly, recognizing in the capture of the one garrisoned fort a rebel's first move, while Shivaji's own pretense of loyalty is the noise meant to jam that signal. The insight neither domain gives alone: positional dominance and signal-emission are two sides of one coin. Seizing the commanding node hands you leverage and broadcasts intent in the same act — you cannot take the center quietly, because taking the center is itself a message.
History (statecraft): Arthashastra — Kingship and the Rajarshi Ideal — Kautilya's king secures the realm through forts and through the careful management of how subordinates and rivals perceive his strength. The thana Shivaji plants in the Sabhasad account is pure Arthashastra: the fort is not won until it is garrisoned and held as an instrument of rule. The parallel is "a stronghold is a tool of governance, not a trophy." The tension is in the loyalty-fiction — the Rajarshi ideal prizes a king whose conduct is transparent and dutiful, yet Shivaji's early forts depend on a professed loyalty to Bijapur that he is actively betraying. The insight: the manual's clean ideal of the dutiful king and the messy reality of a vassal building independent power under cover of service expose that fort-holding is always also perception-management. To hold a fort you must hold the story of why you hold it — and Kondhana is the fort whose story could no longer be held.
Behavioral mechanics (perception management): the loyalty-fiction Shivaji and Shahaji maintain — "we hold these forts on the Sultanate's behalf" — is a textbook framing move, controlling how an action is interpreted so the actor buys time before the true intent is read. It connects to Sun Tzu — Intelligence and the Five Spies through the shared mechanism of information control: the empty forts can be dressed in the language of service, but the garrisoned fort cannot, because the fact of the resident commander is a signal the cover story can't suppress. The insight neither domain produces alone: there is a ceiling on how long a frame can hold against a load-bearing fact. Kondhana was the fact heavy enough to break the frame. The empty forts were weightless — a story could carry them indefinitely. The garrisoned fort had mass, and mass is what cracks a cover story. The behavioral lesson runs the other way too: the man you are trying to deceive is also reading signals, and the Adil Shah read this one perfectly. Deception is never one-sided. The frame only buys time against an opponent who isn't looking; against one who is, every move you make to dress an action also tells him you have something to dress.
The Sharpest Implication
You probably remember Sinhagad through Tanaji and the night-climb of 1670, and you probably assume the lion-name was the medal pinned on that bravery. It wasn't. The lion was already on the fort decades before the deed the legend hangs on — Kondhana and Sinhagad were one and the same when Shivaji first took it. So the most destabilizing thing this page says is small and sharp: the most famous fact you "know" about this fort is the wrong way round. The legend didn't name the fort; the fort outlived the legend's account of itself. If that's true here, how many other names you take as earned were already there before the story that claims to have earned them?
Generative Questions