When Is a War Not a War?

When Is a War Not a War?

War is among the gravest actions a nation can undertake. It commits lives, treasure, and national honor in pursuit of political objectives through organized military force. Because of its enormous consequences, the framers of the U.S. Constitution deliberately divided the power over war. Article I grants Congress the authority to declare war, while Article II makes the president Commander in Chief of the armed forces. The design was intentional, so no single individual would possess unchecked authority to plunge the nation into sustained conflict.

Modern warfare, however, often unfolds too quickly for Congress to deliberate before military action becomes necessary. In response to decades of increasingly unilateral presidential military actions, Congress passed the War Powers Resolution of 1973, recognizing that presidents may have to respond immediately to emergencies while requiring them to notify Congress within 48 hours and generally obtain congressional authorization within 60 days if hostilities continue. The law attempts to preserve both executive flexibility and congressional oversight, though every president since its enactment has questioned parts of its constitutionality.

Since World War II, the United States has seldom relied on formal declarations of war. Instead, presidents have generally sought some combination of congressional authorization, treaty obligations, coalition support, or international legal legitimacy before engaging in major conflicts.

The Korean War proceeded under a United Nations Security Council resolution authorizing member states to repel North Korea’s invasion. The Vietnam War escalated after Congress passed the Gulf of Tonkin Resolution, giving President Lyndon Johnson broad authority to employ military force. The 1991 Persian Gulf War followed explicit authorization from both the United Nations and Congress before President George H. W. Bush launched Operation Desert Storm.

Following the terrorist attacks of September 11, 2001, Congress overwhelmingly passed the Authorization for Use of Military Force (AUMF) against those responsible for the attacks, providing the legal foundation for military operations in Afghanistan and numerous counterterrorism actions that followed. In 2002, Congress enacted a separate AUMF authorizing force against Iraq, which President George W. Bush relied upon when invading in 2003. Although the Iraq War remains deeply controversial, since its justification was based on faulty intelligence of weapons of mass destruction (WMD), the war’s domestic legal basis was unmistakably established through congressional authorization, and the administration spent months building an international coalition—even though the lack of a new UN Security Council authorization remained a major point of dispute.

Whether one supported or opposed these wars, successive administrations generally understood that military action benefited from broad legal and political legitimacy. Presidents sought congressional votes, coalition partners, United Nations resolutions where possible, and extensive public debate. The process recognized that military force is not merely a tactical decision but a constitutional and democratic one.

The recent U.S. military strikes against Iran present a striking contrast. The administration did not seek a new congressional authorization before conducting offensive operations, nor was there a new United Nations mandate specifically authorizing the attacks. Supporters argue that the president possessed constitutional authority to conduct limited military operations to protect American interests, while critics contend that offensive strikes against another sovereign nation, to include killing their national leaders, is precisely the kind of hostilities requiring congressional approval.   But President Trump, as he tends in all matters, did not bother with seeking any approval or legal basis for his actions in Iran; there was no legislative mandate or any type of international authorization to support what was clearly a war.

Compounding this constitutional debate has been the administration’s language. Rather than plainly describing the operation as war or armed conflict, President Donald Trump repeatedly employed softer expressions, referring at various times to actions in Iran as “a little excursion,” “a very successful mission,” “an attack,” “strikes,” “an operation,” and emphasizing that the United States was not seeking a broader war. These descriptions may have reflected an effort to reassure the public or avoid escalation, but they also sidestep the political and constitutional implications that accompany the word war.

This rhetorical strategy invites comparisons with Russian President Vladimir Putin’s insistence on calling Russia’s full-scale invasion of Ukraine a “Special Military Operation.” In Russia, you can go to jail for calling the war a war.  The scale, circumstances, and moral contexts of the war in Ukraine and war in Iran are vastly different, but both cases illustrate how governments sometimes employ euphemistic language to shape public perception and minimize the political consequences associated with acknowledging that military force has crossed the threshold into war.

Words matter. They frame public understanding, influence democratic accountability, and shape history’s judgment. If American service members are risking their lives in combat against another nation, the public deserves language that honestly reflects the reality of what they are being asked to do. Semantic gymnastics may offer short-term political advantages, but it does little to honor those in uniform or to preserve the constitutional principles that place decisions of war and peace under the purview of Congress. A government and a nation function best when they call a spade a spade, but truth-telling has never been a hallmark of Donald Trump and his administration, and so the nation suffers.

Good luck everybody!