<?xml version="1.0" encoding="UTF-8"?>
<mods xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.loc.gov/mods/v3" version="3.1" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-1.xsd">
  <titleInfo>
    <title>Application of operational art in operation SINDOOR</title>
  </titleInfo>
  <name type="personal">
    <namePart>Asthana, S.B.</namePart>
    <role>
      <roleTerm authority="marcrelator" type="text">creator</roleTerm>
    </role>
  </name>
  <typeOfResource>text</typeOfResource>
  <originInfo>
    <place>
      <placeTerm type="text">U.S.I. Journal</placeTerm>
    </place>
    <issuance>monographic</issuance>
  </originInfo>
  <language>
    <languageTerm authority="iso639-2b" type="code">eng</languageTerm>
  </language>
  <physicalDescription>
    <form authority="marcform">print</form>
    <extent>155(641), Jul-Sep, 2025: p.409-420</extent>
  </physicalDescription>
  <abstract>Operation Sindoor marked a watershed in India’s strategic doctrine, launched after the Pakistansponsored Pahalgam terror attack of Apr 2025. It showcased India’s shift from restraint to calibrated offensive action to integrated military precision strikes with diplomatic, economic, and informational tools. By degrading terror infrastructure, suspending the Indus Water Treaty, and leveraging indigenous technologies like Akashteer and Système de Croisière Autonome à Longue Portée (SCALP) [Long Range Autonomous Cruise Missile], India demonstrated comprehensive national power and atmanirbhar (self-reliance) capability. By carefully applying principles of operational art—clear endstate, centre of gravity identification, surprise, deception, and escalation control—India executed multi-domain precision strikes while avoiding a fullscale war. The operation exposed gaps in information warfare, reaffirmed the role of drones, and tri-service integration, while establishing a new deterrence doctrine: terrorism will be treated as an act of war.-Reproduced 

https://usiofindia.org/pdf/USI_Journal_July_Sept_2025_Issue.pdf
</abstract>
  <relatedItem type="host">
    <name>
      <namePart>U.S.I. Journal  </namePart>
    </name>
  </relatedItem>
  <recordInfo>
    <recordCreationDate encoding="marc">251209</recordCreationDate>
  </recordInfo>
</mods>
