When the Monsoon Session of Parliament opened on 21 July 2025, the political theatre on Raisina Hill was set not by a budgetary squall or a corruption ledger, but by the lingering smoke of Operation Sindoor — the precision counter-terror campaign that India had launched in May 2025 against terror infrastructure operated by the Jaish-e-Mohammed (JeM) and the Lashkar-e-Taiba (LeT) across the Line of Control (LoC) and the International Border (IB) with Pakistan. Two months on, the operation had migrated from the operational map of the Directorate General of Military Operations (DGMO) to the floor of both Houses, where it became simultaneously a doctrinal milestone, a partisan flashpoint, and a test of how mature democracies metabolise the use of armed force. The Prime Minister and the Defence Minister were scheduled to brief Members under a structured statement-and-clarification format, while the Opposition pressed for a discussion under Rule 193 in the Lok Sabha and a notice under Rule 267 in the Rajya Sabha, although the Chairman ultimately rejected the eighteen Rule 267 notices and instead admitted a Rule 167 motion to schedule a structured discussion.
The naming of the operation was itself an exercise in narrative warfare. Sindoor — the vermilion that a married Hindu woman wears in the parting of her hair — collapses into a single word the grammar of bereavement: a widow wipes it off, and so the operation’s name silently reproached the 22 April 2025 Pahalgam attack, in which gunmen targeted Hindu tourists at Baisaran meadow and killed 26 civilians, leaving a number of newly widowed wives whose images saturated the public record in the days that followed. Where Operation Vijay in 1999 invoked victory and Operation Parakram in 2001–02 invoked valour, Operation Sindoor invoked grief and the obligation to answer it. Names matter in modern conflict because they pre-frame parliamentary debate, diplomatic démarches, and television chyrons; the Government of India appears to have learned, since the Uri response of 2016 and the Pulwama response of 2019, that the symbolic envelope around a kinetic act often determines its political afterlife as much as the act itself.
This essay reads Operation Sindoor not as a single tactical act but as an inflection point: the third visible step in a doctrinal migration from strategic restraint, through punitive deterrence, towards what some Integrated Defence Staff (IDS) commentators have called active deterrence — a posture in which kinetic options across the LoC and IB are normalised, calibrated, and politically pre-authorised, rather than being treated as exceptional ruptures of an otherwise restrained grand strategy. The Parliament debate that followed in July 2025 is, in turn, a window into how Article 73 executive war powers, the Cabinet Committee on Security (CCS) deliberation under Article 74, and the legislature’s residual oversight role through briefings and discussions are negotiating a new equilibrium for the use of force short of war.

Quick Facts
- Operation name: Operation Sindoor
- Operation date: Launched in the early hours of 7 May 2025; nine targets struck in a single overnight wave
- Triggering event: 22 April 2025 Pahalgam terror attack on tourists in Baisaran meadow (26 civilians killed), attributed to JeM/LeT handlers based in Pakistan and Pakistan-occupied Kashmir (PoK)
- Target type: Nine terror launch pads, training camps and headquarters-linked sites across the LoC and inside Pakistani Punjab
- Means employed: Stand-off precision munitions including SCALP-EG cruise missiles and AASM Hammer bombs from IAF Rafale aircraft, BrahMos from Su-30 MKI, and Harop loitering munitions; no manned-aircraft incursion across the LoC/IB
- Parliamentary briefing: Both Houses, Monsoon Session 2025 (commenced 21 July 2025); statements by PM and Defence Minister, plus a separate all-party briefing
- Constitutional anchors: Article 73 (executive power co-extensive with Parliament’s legislative competence on Defence, List I Entry 1), Article 74 (Council of Ministers and CCS), Article 53 (supreme command vests in the President)
- Predecessors: 2016 surgical strikes (post-Uri), 2019 Balakot air strikes (post-Pulwama), 2025 Operation Sindoor (post-2025 attack)
Background and Historical Context
For nearly four decades after the 1971 Bangladesh Liberation War, India‘s response to Pakistan-sponsored terror was shaped by a doctrine that scholars such as K. Subrahmanyam and later Shivshankar Menon described as strategic restraint. The proposition was simple but unforgiving: a nuclear-armed adversary, a fragile economy, and a federal polity could not afford the escalatory ladder that any retaliatory strike risked climbing. The 1999 Kargil War reinforced rather than undermined this proposition; Indian forces did not cross the LoC even when tactically tempted, and the Vajpayee government turned that restraint into diplomatic capital with the Clinton administration. The 2001 Parliament attack and the resulting Operation Parakram mobilisation demonstrated the costs of coercive diplomacy without kinetic follow-through; nearly ten months of forward deployment yielded political fatigue rather than strategic clarity.
The 2008 Mumbai attacks by LeT operatives was the moment at which the strategic-restraint consensus began to fracture. Internal reviews — including the still-classified work of the Naresh Chandra Task Force on national security — flagged that absence of retaliation was being read by the Pakistan Army and the Inter-Services Intelligence (ISI) as permission rather than maturity. Yet the Manmohan Singh government chose diplomatic isolation and judicial pursuit through Interpol red notices rather than a military response, in part because the Indian Army‘s own assessment was that surprise was lost and escalation control was uncertain.
The September 2016 surgical strikes following the Uri attack were, in this sense, the first public departure from restraint. Indian Army special forces crossed the LoC to strike launch pads, and the then DGMO, Lt Gen Ranbir Singh, briefed the press at a joint MoD–MEA press conference on 29 September 2016 — a calibrated act of declassification. The signalling was as important as the strikes: India was now willing to acknowledge cross-LoC kinetic action publicly, breaking the older pattern in which such operations, when they occurred, were neither confirmed nor denied. The February 2019 Balakot air strikes following Pulwama escalated this signalling further. IAF Mirage 2000 aircraft struck targets deep inside Pakistani territory at Balakot in Khyber Pakhtunkhwa, marking the first cross-border use of Indian air power against Pakistan since 1971.
Operation Sindoor in May 2025 must therefore be read as the third panel in a triptych. Each panel raises the doctrinal stakes — from special-forces ingress, to manned-aircraft deep strike, to a multi-domain stand-off operation that combined cruise munitions, loitering munitions (drones) and reported electronic-warfare support. The doctrine has not been articulated in a single white paper; it has been written instead in operations.
What is Operation Sindoor — Targets and Scope
Operation Sindoor, as outlined in the DGMO briefing on 7 May 2025 and in subsequent statements by the Defence Minister, was a precision counter-terror operation carried out in a single overnight wave on the night of 6–7 May 2025, striking nine sites in all. The publicly stated targets fell into three concentric rings. The first ring comprised terror launch pads within Pakistan-occupied Kashmir, including sites at Muzaffarabad, Kotli and Bagh, and along the Neelum Valley axis from which trans-border infiltration had historically been mounted. The second ring extended to training camps and logistics nodes in the same sectors, including the Syedna Bilal complex at Muzaffarabad. The third — and politically most significant — ring extended into territory that Pakistan recognises as its own, targeting the Markaz Subhan Allah facility associated with JeM at Bahawalpur in Punjab, the Markaz Taiba complex linked to LeT at Muridke near Lahore, and additional sites at Shakar Garh and a village near Sialkot.
The means employed were notable for what they signalled about Indian capabilities. Stand-off precision munitions launched from within Indian airspace — including SCALP-EG air-to-surface cruise missiles and AASM Hammer guided bombs carried by Rafale aircraft of the IAF, alongside air-launched BrahMos variants fired from Sukhoi-30 MKI platforms — allowed India to strike targets without the manned-aircraft incursions that had complicated the Balakot aftermath, when Wing Commander Abhinandan Varthaman‘s MiG-21 was shot down and he was briefly held by Pakistan. Harop loitering munitions and indigenous tactical drones accounted for a further portion of the kill chain. The political logic of this composition was straightforward: minimise the probability of an Abhinandan moment, maximise the probability of demonstrable target damage, and compress the operation into a single news cycle.
The scope of Operation Sindoor is best understood not by what was struck but by what was deliberately not struck. The Government of India went out of its way to characterise the operation as non-escalatory, focused, and directed at terror infrastructure rather than at the Pakistan Army or civilian assets. No nuclear command nodes, no major Pakistani military bases, no civilian population centres were reportedly struck. The escalation ladder was thus consciously constrained — an exercise in what Thomas Schelling would have called the diplomacy of violence: using force precisely enough that the adversary can absorb it without political collapse, while still incurring real costs.
India’s Counter-Terror Doctrine: From Strategic Restraint to Active Deterrence
If strategic restraint was the doctrine of the Cold War generation and punitive deterrence was the doctrine of the post-Mumbai 26/11 generation, the doctrine emerging from Operation Sindoor can be provisionally labelled active deterrence. Three features distinguish it. First, the presumption of action has reversed: where earlier governments treated kinetic response as the exception that demanded justification, the new posture treats restraint as the option that demands justification. Second, the response time has compressed dramatically. The Uri-to-strikes window was about eleven days; the Pulwama-to-Balakot window was about twelve days; Operation Sindoor followed the Pahalgam attack of 22 April 2025 within fifteen days, the strikes being launched in the early hours of 7 May 2025. Third, the geographic threshold has dissolved: the LoC is no longer treated as a sanctuary line for terror infrastructure, and even the IB has, on the evidence of Sindoor, ceased to function as a doctrinal firebreak.
Underpinning this evolution is a quiet institutional revolution. The creation of the Chief of Defence Staff (CDS) post in 2019, the establishment of the Department of Military Affairs (DMA) in the Ministry of Defence, and the steady empowerment of the Strategic Forces Command (SFC) and the Integrated Defence Staff have collapsed the older silos between service headquarters. The National Security Council Secretariat (NSCS) under the National Security Adviser has emerged as a routine integrator of intelligence, diplomatic and operational planning. Operation Sindoor, by all accounts, was prepared through this jointness machinery, not through a single-service planning cell.
The doctrine is also legible as a response to Pakistan’s full-spectrum deterrence posture and its acquisition of tactical nuclear weapons (TNWs) such as the Nasr battlefield missile. Pakistan‘s strategic logic since roughly 2011 has been to lower the nuclear threshold so as to deter even limited Indian conventional retaliation. Operation Sindoor implicitly rejects this logic: it asserts that Indian conventional response can be calibrated below the nuclear threshold even when it crosses the LoC and the IB, and that the threshold itself is in part a function of how India chooses to define it. This is doctrinal language that Vipin Narang and Christopher Clary have been writing about for over a decade; Sindoor appears to have moved it from the seminar room to the operations room.
Parliament Briefing — What MPs Were Told
The Monsoon Session 2025 opened on 21 July and ran through 21 August. Government business accommodated a structured discussion on Operation Sindoor beginning on 28 July in the Lok Sabha and 29 July in the Rajya Sabha, with a combined sixteen-hour allocation across the two Houses; an all-party briefing by the Defence Minister and the service chiefs preceded the parliamentary debate, and the Prime Minister intervened in the Lok Sabha on 29 July. Members were briefed on the intelligence picture that preceded the operation, the target selection criteria, the battle damage assessment (BDA), the diplomatic outreach conducted in the days before and after the strikes, and the casualty figures on both sides — including, importantly, the absence of Indian combat casualties, which became a recurring rhetorical pivot.
What MPs were told, on the available reportage, fell into four buckets. First, an intelligence narrative linking the precipitating attack to handlers based in Bahawalpur and Muridke, drawing on signals intelligence, human intelligence, and corroborating evidence shared with partner intelligence agencies. Second, an operational narrative emphasising precision, proportionality, and the deliberate avoidance of Pakistan Army assets. Third, a diplomatic narrative describing pre-strike communication with the United States, the United Kingdom, the French Republic, the Russian Federation, and Gulf partners, and post-strike outreach to the People’s Republic of China. Fourth, a strategic narrative framing the operation as the new normal — that future terror provocations would receive comparable responses, calibrated to the provocation but not constrained by the LoC.
The Opposition’s interventions clustered around three themes. The Indian National Congress, through floor leaders in both Houses, pressed for greater specificity on intelligence failures that had allowed the precipitating attack in the first place — echoing the same questions it had raised after Pulwama. Trinamool Congress and the Dravida Munnetra Kazhagam sought clarity on the economic and diplomatic costs, including the implications of India’s decision of 23 April 2025 to hold the Indus Waters Treaty in abeyance and the further weakening of the Saarc framework, already moribund since 2016. The Samajwadi Party and the Aam Aadmi Party joined the Communist Party of India (Marxist) in arguing that operational success should not foreclose parliamentary scrutiny — including a demand, ultimately not conceded, for the constitution of a Joint Parliamentary Committee (JPC) to examine the lead-up to the precipitating attack.
Procedurally, the debate exposed a familiar fault line in Indian parliamentary practice. Rule 193 of the Rules of Procedure and Conduct of Business in the Lok Sabha permits a discussion on a matter of urgent public importance without a formal motion or vote — useful for ventilation but constitutionally toothless. Rule 267 of the Rajya Sabha, which allows suspension of listed business to take up a member’s notice, was invoked by Opposition members through eighteen separate notices on the opening day; Chairman Jagdeep Dhankhar rejected all of them and instead admitted a Rule 167 motion that yielded the structured discussion eventually held on 29 July. The substantive question — whether the Indian Parliament has, or should have, a more codified role in authorising or reviewing the use of force short of war — was raised but not resolved. Unlike the United States Congress, which has the War Powers Resolution of 1973, or the House of Commons in the United Kingdom, which has developed a convention since 2003 of seeking parliamentary approval for military action, the Indian Parliament retains only a post-hoc, oversight-by-debate function in this domain.
International Reactions — US, Russia, China, P5
The international reception of Operation Sindoor followed a pattern that has, by 2025, become recognisable. The United States position, articulated by the State Department and the National Security Council, was a careful balancing act: explicit recognition of India’s right of self-defence against terror, paired with a call for de-escalation and restraint by both parties. The Trump administration‘s second-term posture, more transactionally aligned with India through the Quad and the iCET technology partnership, gave Indian diplomats more rhetorical room than they had enjoyed in 2019.
The Russian Federation‘s Ministry of Foreign Affairs, consistent with its long-standing position on terrorism emanating from Pakistan-based groups, offered language closer to outright endorsement, framing the operation in terms compatible with UN Security Council Resolution 1373 on counter-terrorism obligations. The People’s Republic of China, predictably, urged both sides to exercise restraint, expressed concern about regional stability, and avoided language that would directly criticise Pakistan‘s posture; behind the scenes, Beijing‘s real concern was reportedly the demonstration effect of Indian stand-off precision strikes, given the implications for any future India–China contingency along the Line of Actual Control (LAC).
Among the remaining P5, the United Kingdom and France — both of whom have supplied platforms central to Indian capability, including the Rafale and previously the Mirage 2000 — issued statements that recognised India’s counter-terror imperative while urging dialogue. In the United Nations Security Council, Pakistan‘s attempt to internationalise the strikes through a closed-door consultation produced no actionable outcome; the Council‘s capacity for collective action on India–Pakistan matters has been functionally inert since 1971. Within the Organisation of Islamic Cooperation (OIC), the response was more critical of India, but key Gulf partners — the United Arab Emirates, the Kingdom of Saudi Arabia — pursued a quieter line, recognising the value of the India economic relationship and, in some cases, having been pre-briefed.

Significance of the Operation and the Debate
The significance of Operation Sindoor works at three levels — strategic, constitutional, and political — and the Monsoon Session 2025 debate is what aligns these levels into a single arc. Strategically, the operation reinforces a pattern that began with 2016 and accelerated with 2019: that India is willing to absorb the political costs of cross-border kinetic action when the precipitating provocation crosses an internal threshold. Constitutionally, the operation reactivates older debates about the location of war powers in the Indian Constitution — a text that, unlike the U.S. Constitution, contains no equivalent of Article I, Section 8, Clause 11 giving the legislature the power to declare war. Article 53 vests supreme command in the President; Article 73 reads executive power as co-extensive with Parliament’s legislative competence; and Article 246 read with List I, Entry 1 places Defence of India squarely in the Union List. The combined effect is that the executive can lawfully order operations short of war without prior parliamentary authorisation.
Politically, the debate matters because it is one of the rare occasions on which the Indian Parliament performs the function the framers might have hoped it would perform around the use of force: deliberation, scrutiny, and the formation of a documented public record. Operation Sindoor may have been over in hours; the Monsoon Session debate is the document that historians will read fifty years from now to understand what India said, to itself and to the world, about why it acted. The quality of that document — whether it is dominated by procedural skirmishes or whether it includes a genuine articulation of doctrine — is itself a measure of democratic maturity.
There is a further significance specific to federal politics. The state of Jammu & Kashmir, since the abrogation of Article 370 in August 2019 and the bifurcation into the Union Territories of Jammu & Kashmir and Ladakh, has been governed under direct central administration. Operation Sindoor was discussed in the Lok Sabha with the Lieutenant Governor‘s administration as the relevant local executor of post-strike security measures — a federal architecture that is structurally different from the one in which Operation Vijay was conducted in 1999. Members from Jammu & Kashmir, including those of the Jammu & Kashmir National Conference and the Peoples Democratic Party, used the debate to press for an accelerated restoration of statehood, arguing that effective counter-terror governance requires a politically accountable state government, not a Lieutenant Governor’s writ.
Detailed Analysis: Doctrine, Comparison, and Constitutional Architecture
To make sense of Operation Sindoor in the longer arc, it helps to set it side by side with its predecessors. The table below compares the 2016 surgical strikes, the 2019 Balakot air strikes, and the 2025 Operation Sindoor across five dimensions: the precipitating trigger, the target type, the means employed, the parliamentary briefing format, and the international reaction.
| Dimension | 2016 Surgical Strikes | 2019 Balakot Air Strikes | 2025 Operation Sindoor |
|---|---|---|---|
| Trigger | Uri Army camp attack, Sept 2016 (19 soldiers killed) | Pulwama CRPF convoy bombing, Feb 2019 (40 personnel killed) | Pahalgam tourist attack, 22 April 2025 (26 civilians killed) |
| Target type | Terror launch pads close to LoC in PoK | JeM training camp at Balakot, Khyber Pakhtunkhwa | Nine sites: launch pads and camps in PoK (Muzaffarabad, Kotli, Bagh) and HQ-linked sites in Pakistani Punjab (Bahawalpur, Muridke, Shakar Garh, near Sialkot) |
| Means employed | Indian Army Special Forces ground ingress across LoC | IAF Mirage 2000 manned strike with stand-off bombs | Multi-domain stand-off: SCALP-EG and AASM Hammer from Rafale, BrahMos from Su-30 MKI, Harop loitering munitions; no manned ingress across the LoC/IB |
| Parliamentary briefing | DGMO press briefing; no immediate Parliament session; later statements | Statements in Parliament; election-period political contestation | Structured Monsoon Session debate; PM and DefMin statements; all-party briefing |
| International reaction | Muted Western support; Pakistan denial of strikes | US/UK call for de-escalation; OIC critical; Abhinandan capture–release cycle | US recognition of self-defence; Russia supportive; China formulaic restraint call; UNSC inert |
Read across the columns, three trajectories become visible. The capability trajectory moves from boots-on-ground (high political risk, high deniability for the state) to manned aircraft (medium risk, medium deniability) to stand-off precision (low loss-of-life risk, low deniability — but also low need for deniability because the Government of India chose to own the operation publicly from the outset). The doctrinal trajectory moves from one-off exception to repeatable practice; 2016 was a precedent, 2019 was a confirmation, 2025 is becoming a template. The parliamentary trajectory moves from ex post facto press conference to mid-cycle political contestation to a more structured, session-based debate — but in none of the three episodes was Parliament asked, in any meaningful sense, to authorise the operation in advance.
The constitutional architecture deserves a closer reading. The Indian Constitution distributes war-power authority across Article 53 (President as supreme commander), Article 74 (binding aid and advice of the Council of Ministers), Article 73 (executive power coextensive with Parliament’s legislative competence), and the Seventh Schedule entries placing Defence in the Union List. Article 352 provides for the proclamation of a National Emergency on grounds including external aggression or armed rebellion; that proclamation must be approved by both Houses of Parliament within one month. But operations short of war — and Operation Sindoor, in the official telling, was an act of self-defence against non-state actors, not war on Pakistan — fall squarely within executive prerogative, and no Article 352 proclamation has been thought necessary for any of the three episodes.
The Cabinet Committee on Security, chaired by the Prime Minister and including the Home Minister, the Defence Minister, the External Affairs Minister and the Finance Minister, with the National Security Adviser as a permanent invitee, is the actual locus of decision in such operations. The CCS is itself a creature of executive convention rather than constitutional text; its functioning is governed by the Government of India (Transaction of Business) Rules, 1961 framed under Article 77(3). This is significant: the most consequential national-security decisions in India are taken under sub-constitutional rules of business, not under constitutional provisions specifically designed for that purpose.
International law adds another layer. The Government of India‘s legal framing of Operation Sindoor, like that of Balakot, rests on the inherent right of self-defence under Article 51 of the UN Charter, supplemented by the Caroline doctrine on anticipatory self-defence and the post-9/11 evolution of the unwilling-or-unable doctrine for cross-border action against non-state armed groups. India’s position, articulated through the Permanent Mission to the United Nations, has been that where a host state is either complicit in or unable to dismantle terror infrastructure, the victim state may take proportionate, targeted action. This is the same legal architecture invoked by the United States for action against Al-Qaeda targets and by Türkiye against PKK safe havens.

Comparative Lessons: How Other Democracies Authorise Force
Comparative perspective sharpens the Indian picture. The United States, whose Constitution places the power to declare war in Congress, has lived since the Korean War with a wide gap between formal text and operational practice — a gap the War Powers Resolution of 1973, passed over President Nixon‘s veto, attempted to bridge by requiring presidential consultation with Congress within forty-eight hours and a withdrawal of forces within sixty days absent congressional authorisation. The Authorisations for Use of Military Force (AUMFs) of 2001 and 2002 have, in turn, been criticised by scholars including Jack Goldsmith as having stretched far beyond their original anti-Al-Qaeda remit. The American lesson for India is sobering: a written war-powers role for the legislature does not, by itself, produce active legislative oversight; institutional culture matters as much as text.
The United Kingdom presents the opposite trajectory. Under the Royal Prerogative, the executive retained near-unfettered authority to commit forces. Yet since the 2003 Iraq War vote in the House of Commons, a constitutional convention has emerged that significant deployments require advance parliamentary approval. The 2013 vote against military action in Syria reinforced this convention. India’s Lok Sabha, by contrast, has not developed a comparable convention; the political culture treats the use of force as an executive question on which legislative ventilation is welcome but not required.
France sits between these poles. Article 35 of the French Constitution of 1958, as amended in 2008, requires the executive to inform Parliament within three days of any military intervention abroad and to seek authorisation if the deployment exceeds four months. Germany, under its Basic Law as interpreted by the Federal Constitutional Court, requires Bundestag approval for armed deployments — a “parliamentary army” doctrine that is unusually strong by global standards. Israel, frequently invoked in Indian commentary on counter-terror, in fact retains a strongly executive-centred war-powers model, with the Cabinet and Security Cabinet as decisional fora and the Knesset performing oversight rather than authorisation.
The Indian model is closer to the Israeli than to the German: a strongly executive-centred system with formal supreme command in the head of state, real authority in the cabinet committee, and a legislature whose role is post-hoc and discursive. Whether this model is well-adapted to the volume and frequency of sub-war kinetic operations that India may now conduct is a serious doctrinal question. The Monsoon Session 2025 debate did not resolve it, but it placed it squarely on the agenda for the Standing Committee on Defence and, possibly, for a future Law Commission reference.
Challenges and Open Questions
The challenges raised by Operation Sindoor and its parliamentary afterlife divide neatly into doctrinal, institutional, diplomatic and informational categories. Doctrinally, the most pressing question is the escalation ladder. India’s calibrated targeting may have served the immediate purpose, but each iteration of cross-border action raises the floor for the next. If 2016 made special-forces ingress normal and 2019 made manned air strikes normal, 2025 threatens to make stand-off precision strikes routine. Pakistan’s response in any future iteration may not be as restrained as in 2025, particularly under domestic political pressure on its civil-military balance. The risk of an action–reaction loop that exceeds the calibrated limits of either capital is therefore higher, not lower, after Sindoor.
Institutionally, the question is whether the architecture of joint planning and execution that performed well in Sindoor can scale to a higher operational tempo. The theatre commands reform — long under consideration, with proposed Northern, Western, Maritime and Air Defence commands replacing the existing seventeen single-service commands — has progressed unevenly. Sindoor‘s success may, paradoxically, slow that reform by suggesting that the present architecture is good enough; the more honest reading is that Sindoor was a single, well-prepared operation whose lessons have not been stress-tested against a contested electromagnetic spectrum or a degraded sensor environment.
Diplomatically, the question is whether India can sustain the international understanding it has cultivated. The P5 reception in 2025 was more favourable than in 2019, partly because the world has moved decisively against Pakistan-based terror groups since the Financial Action Task Force (FATF)‘s grey-listing cycles, and partly because India‘s economic weight and Quad partnerships have grown. But this favourable reception is not free of conditions. Future operations will be judged against Sindoor‘s standard of precision and proportionality; an operation that produces large civilian casualties, even unintentionally, would invite a much harsher international response. India’s diplomatic capital in this domain is real but exhaustible.
Informationally, the challenge is the contested space of battle damage assessment. After Balakot, the gap between Indian government claims and independent satellite imagery analysis became a long-running political controversy. Sindoor‘s public communication appears to have learned from this, with the DGMO briefing accompanied by a curated set of imagery and signals intelligence summaries. But the broader information environment — domestic television, social media, foreign analytical outlets, open-source intelligence (OSINT) communities such as Bellingcat — is now far less amenable to single-narrative control. The Press Information Bureau and the Ministry of External Affairs‘s External Publicity Division have had to operate as joint communicators in real time, a capability that did not exist with the same maturity even in 2019.
A further challenge lies in the relationship between operational success and the underlying political problem. Cross-border kinetic operations can degrade infrastructure, raise costs, and impose deterrent friction; they cannot, by themselves, solve the political question of Kashmir, the dynamics of the Pakistan military’s strategic culture, or the underlying ecosystem of radicalisation. The Monsoon Session debate’s most thoughtful interventions — including from independent members and from sections of the Bharatiya Janata Party‘s own veteran benches — were those that warned against confusing tactical success with strategic resolution. Operation Sindoor is best understood as buying time: time for diplomatic, economic, and political work that no kinetic operation can substitute for.

Prelims Pointers
- Operation Sindoor — May 2025; precision counter-terror operation against JeM/LeT infrastructure across the LoC and IB
- Sindoor — vermilion symbolism; references martyrdom and widowhood
- Predecessors — 2016 Surgical Strikes (post-Uri); 2019 Balakot air strikes (post-Pulwama)
- Article 53 — Supreme command of the Defence Forces of the Union vests in the President
- Article 73 — Executive power of the Union extends to matters in the Union List
- Article 74 — Council of Ministers aids and advises the President; binding under 42nd and 44th Amendments
- Article 352 — National Emergency on grounds of external aggression / armed rebellion; parliamentary approval within one month
- Seventh Schedule, List I, Entry 1 — Defence of India; Entry 2A — Deployment of Union armed forces in any state
- Cabinet Committee on Security (CCS) — chaired by PM; includes Home, Defence, External Affairs, Finance Ministers; NSA as invitee
- Government of India (Transaction of Business) Rules, 1961 — framed under Article 77(3)
- DGMO — Directorate General of Military Operations; routine briefings during cross-border events
- Strategic Forces Command — established 2003; custodian of nuclear delivery systems
- Chief of Defence Staff — created 2019; head of Department of Military Affairs
- Rule 193, Lok Sabha — short-duration discussion without formal motion
- Rule 267, Rajya Sabha — suspension of business on a notice admitted by the Chairman
- UN Charter Article 51 — inherent right of self-defence
- UNSC Resolution 1373 (2001) — counter-terrorism obligations
- FATF — Financial Action Task Force; multiple Pakistan grey-listing cycles since 2008
- Quad — India, US, Japan, Australia; iCET technology partnership
- Theatre Commands — proposed Northern, Western, Maritime, Air Defence
- Bahawalpur — historical headquarters of JeM in Pakistani Punjab
- Muridke — historical headquarters of LeT/Jamaat-ud-Dawa near Lahore
- Indus Waters Treaty (1960) — brokered by the World Bank between Nehru and Ayub Khan
Mains Practice Questions
- “India’s counter-terror posture has migrated from strategic restraint to active deterrence.” Critically examine this proposition with reference to the 2016 surgical strikes, 2019 Balakot air strikes and 2025 Operation Sindoor. (GS-III, 250 words)
- Examine the constitutional architecture governing the use of armed force by India for operations short of war. Should Parliament have a more codified role in authorising or reviewing such operations? (GS-II, 250 words)
- “The escalation ladder is the most under-discussed element of India‘s new counter-terror doctrine.” Discuss with reference to Pakistan‘s full-spectrum deterrence posture and its tactical nuclear weapons. (GS-III, 250 words)
- Compare the war-powers models of India, the United States, the United Kingdom, France and Germany. Which features of these models are worth examining for adaptation in the Indian context? (GS-II, 250 words)
- “Operational success can buy time but cannot substitute for political resolution.” Critically evaluate this statement in the context of Operation Sindoor and the longer history of Kashmir-related counter-terror operations. (GS-III, 250 words)
Conclusion
Operation Sindoor and the Monsoon Session 2025 debate together mark a moment in which India’s grammar of force, its constitutional architecture, and its democratic culture have come into closer conversation than at any time since Kargil. The operation itself was a tightly engineered exercise in calibrated coercion: precision targeting, multi-domain assets, a clear non-escalatory frame, and a deliberate post-strike communications cadence designed to own the narrative without inflaming it. The debate that followed was, by Indian standards, a serious one — not because Parliament authorised the operation, which it did not and arguably need not have, but because the Houses became the venue in which doctrine, intelligence and diplomacy were articulated for the public record.
Yet the deeper questions remain. India is now a country that conducts cross-border kinetic operations with growing frequency and shrinking response times, against an adversary whose nuclear posture has been explicitly designed to lower the threshold for escalation. The active deterrence doctrine that Operation Sindoor embodies works only so long as both sides observe an unwritten ceiling on response. That ceiling is not guaranteed by capability, by geography or by treaty; it is guaranteed only by the political judgement of decision-makers in New Delhi and Rawalpindi, mediated through institutions and norms that are themselves under stress. The strongest argument for a more codified parliamentary role in such operations is not that the executive cannot be trusted, but that the executive’s task is hard enough to merit broader institutional ballast.
The vermilion in the operation’s name is, in the end, a reminder of the human cost on which all this strategic architecture rests. The widows of terror victims; the soldiers who do not return; the families on both sides of the LoC for whom statecraft is not an abstraction but a household reality — these are the constituencies whose grief any doctrine, however elegant, must finally answer to. Operation Sindoor answered to that grief in the only language statecraft has, the language of force calibrated and force communicated. Whether the deeper political work that grief demands — the work of normalisation, of regional architecture, of de-radicalisation — can find a comparable language in the years ahead is the question with which the Monsoon Session 2025 debate, perhaps unintentionally, has left the country.
Frequently asked questions
What was Operation Sindoor and what triggered it?
Operation Sindoor was a precision counter-terror operation launched in the early hours of 7 May 2025, in which nine sites linked to the Jaish-e-Mohammed and the Lashkar-e-Taiba were struck in a single overnight wave across the Line of Control and inside Pakistani Punjab. The stated trigger was the 22 April 2025 attack on tourists at Baisaran meadow in Pahalgam, in which 26 civilians were killed, attributed to handlers based in Pakistan and Pakistan-occupied Kashmir. Official statements described the targets in three rings: launch pads in PoK at Muzaffarabad, Kotli and Bagh; training camps and logistics nodes in the same sectors, including the Syedna Bilal complex at Muzaffarabad; and headquarters-linked sites deeper inside Pakistan at Bahawalpur, Muridke, Shakar Garh and near Sialkot. The Government of India characterised the operation as non-escalatory and directed at terror infrastructure rather than at the Pakistan Army or civilian assets.
Why was the operation named Sindoor?
Sindoor is the vermilion a married Hindu woman wears in the parting of her hair, and a widow wipes it off, so the name pointed at the newly widowed wives of those killed in the Pahalgam attack. Where Operation Vijay in 1999 invoked victory and Operation Parakram in 2001-02 invoked valour, Operation Sindoor invoked grief and the obligation to answer it. Names carry weight in modern conflict because they pre-frame parliamentary debate, diplomatic messaging and television coverage, and the symbolic envelope around a kinetic act often shapes its political afterlife as much as the act itself.
What does the shift from strategic restraint to active deterrence mean?
Strategic restraint was the older posture, associated with thinkers such as K. Subrahmanyam and Shivshankar Menon, in which India absorbed Pakistan-sponsored attacks rather than risk climbing an escalation ladder against a nuclear-armed adversary with a fragile economy behind it. The posture that some Integrated Defence Staff commentators have provisionally labelled active deterrence reverses the presumption: restraint is now the option that demands justification rather than kinetic response, and the Line of Control has stopped being treated as a sanctuary line for terror infrastructure, with the International Border also ceasing to function as a doctrinal firebreak. On the record of the three episodes, the 2016 strikes followed Uri after about eleven days, Balakot followed Pulwama after about twelve days, and Operation Sindoor followed the Pahalgam attack within fifteen days. The doctrine has never been set out in a single white paper; it has been written in operations.
How did Operation Sindoor differ from the 2016 surgical strikes and the 2019 Balakot air strikes?
The three episodes differ mainly in means, reach and how they were reported to Parliament. In 2016 Indian Army special forces crossed the Line of Control on the ground to strike launch pads after the Uri attack; in 2019 IAF Mirage 2000 aircraft carried out a manned strike on a JeM camp at Balakot in Khyber Pakhtunkhwa after Pulwama; in 2025 the package was multi-domain and stand-off, using SCALP-EG cruise missiles and AASM Hammer guided bombs from Rafale aircraft, air-launched BrahMos from Su-30 MKI platforms and Harop loitering munitions, with no manned-aircraft incursion across the LoC or the International Border. The parliamentary handling also shifted, from a DGMO press conference in 2016, to statements in Parliament amid election-period contestation in 2019, to a structured session-based discussion in 2025. In none of the three episodes was Parliament asked in any meaningful sense to authorise the operation in advance.
What were MPs told during the Operation Sindoor discussion, and what did the Opposition press for?
On the available reportage, the government’s account fell into four parts: an intelligence narrative linking the precipitating attack to handlers based in Bahawalpur and Muridke, an operational narrative emphasising precision, proportionality and the deliberate avoidance of Pakistan Army assets, a diplomatic narrative covering pre-strike communication with the United States, the United Kingdom, France, Russia and Gulf partners along with post-strike outreach to China, and a strategic narrative framing the operation as the new normal for future provocations. The Indian National Congress pressed for greater specificity on the intelligence failures that had allowed the precipitating attack. The Trinamool Congress and the DMK sought clarity on economic and diplomatic costs, including India’s decision of 23 April 2025 to hold the Indus Waters Treaty in abeyance and the further weakening of Saarc. The Samajwadi Party, the Aam Aadmi Party and the CPI(M) argued that operational success should not foreclose parliamentary scrutiny and demanded a Joint Parliamentary Committee into the lead-up to the attack, which was not conceded.
Under which parliamentary rules was Operation Sindoor discussed?
In the Lok Sabha the Opposition pressed for a discussion under Rule 193 of the Rules of Procedure and Conduct of Business, which permits a discussion on a matter of urgent public importance without a formal motion and therefore without a vote. In the Rajya Sabha, Opposition members filed eighteen separate notices under Rule 267, the provision that allows listed business to be suspended so that a member’s notice can be taken up; all eighteen were rejected, and a structured discussion was instead scheduled and held on 29 July. The structured discussion began on 28 July in the Lok Sabha and on 29 July in the Rajya Sabha, preceded by an all-party briefing by the Defence Minister and the service chiefs. The distinction matters because a discussion of this kind ventilates opinion without binding the executive, which is why the larger question of a codified parliamentary role was raised but left unresolved.
Does the Indian Constitution require Parliament to authorise military operations short of war?
No. Article 53 vests supreme command of the armed forces in the President, Article 74 makes the aid and advice of the Council of Ministers binding, Article 73 makes the Union’s executive power co-extensive with Parliament’s legislative competence, and Article 246 read with Entry 1 of the Union List places Defence of India with the Union, so the executive can lawfully order operations short of war without prior parliamentary authorisation. Article 352 does require both Houses to approve a Proclamation of Emergency within one month, but no such proclamation was thought necessary for any of the three episodes, each of which was officially framed as self-defence against non-state actors rather than war on Pakistan. The real locus of decision is the Cabinet Committee on Security, chaired by the Prime Minister and including the Home, Defence, External Affairs and Finance Ministers with the National Security Adviser as a permanent invitee, which functions under the Government of India (Transaction of Business) Rules, 1961 framed under Article 77(3) rather than under any constitutional provision written for the purpose. By contrast, the United States Congress has the War Powers Resolution of 1973 and the House of Commons has developed a convention since 2003 of seeking approval for significant deployments, while the Indian Parliament retains a post-hoc, oversight-by-debate role.
What legal basis did India cite for the strikes, and how did other countries react?
India’s legal framing rested on the inherent right of self-defence under Article 51 of the UN Charter, supplemented by the Caroline doctrine on anticipatory self-defence and the post-9/11 unwilling-or-unable doctrine for cross-border action against non-state armed groups, the position being that where a host state is complicit in or unable to dismantle terror infrastructure, the victim state may take proportionate, targeted action. The United States paired explicit recognition of India’s right of self-defence with a call for de-escalation by both parties; Russia’s Ministry of Foreign Affairs offered language closer to endorsement, framed in terms compatible with UN Security Council Resolution 1373; and China urged restraint and avoided directly criticising Pakistan’s posture. The United Kingdom and France, both suppliers of platforms central to Indian capability, recognised the counter-terror imperative while urging dialogue, and Pakistan’s attempt to internationalise the strikes through a closed-door Security Council consultation produced no actionable outcome. Response within the Organisation of Islamic Cooperation was more critical of India, though Gulf partners such as the United Arab Emirates and Saudi Arabia pursued a quieter line.
Tell Google you want more of this.
Add Anantam IAS as a preferred sourceOne tap, and this site shows up more often in your own Top Stories, AI Overviews and AI Mode. Remove it any time.