The war that runs on euphemisms
On February 28, 2026, the United States and Israel launched nearly 900 strikes on Iran in twelve hours. They killed the Supreme Leader, levelled military infrastructure, and triggered a regional crisis that has shut down the Strait of Hormuz, sent fuel prices spiralling, and left global supply chains in chaos. By any reasonable definition, this is a war. But listen to the people in charge, and you will hear "military operation," "major combat operations," "conflict," "campaign." The word "war" keeps slipping out and then getting walked back. The gap between what is happening and what it is called is not a quirk of messaging. It is a systems problem, and understanding it tells you something important about how modern conflicts persist.
The language game
President Trump himself gave away the logic in a press conference earlier this month. Asked why he avoids the word "war," he said, plainly, "because you're supposed to get approval." Under the U.S. Constitution, only Congress can declare war. By refusing to name it, the executive branch sidesteps the legal and political machinery that is supposed to constrain military action. This is not new. The Korean War was officially a "police action." Truman never sought congressional authorization, instead citing UN Security Council resolutions. Vietnam escalated for years through a fiction of "military advisors" before the Gulf of Tonkin Resolution gave it retroactive legal cover. In each case, the euphemism came first, and the accountability came late or never. What makes the Iran situation striking is how explicitly the language is being managed. The White House submitted a War Powers report to Congress but did not explain why it launched the strikes without prior authorization. Senate Democrats have tried three times to advance a War Powers Resolution requiring congressional approval, and Senate Republicans have blocked every attempt. The constitutional mechanism exists on paper. In practice, it is a dead letter, and the euphemism is what keeps it dead.
When you don't name it, the feedback loops break
In systems thinking, naming is not just semantics. It is a trigger for feedback loops. When a country is "at war," a predictable set of mechanisms activates: public debate intensifies, funding requires explicit congressional votes, media coverage shifts to sustained scrutiny, exit strategies become a political demand, and the human cost gets framed in terms the public can process. An unnamed war bypasses all of this. Public opinion fragments because people cannot rally for or against something that officially is not happening. Congressional oversight stalls because there is nothing formal to oversee. Media cycles move on because "ongoing operations" is not a headline. The system that is supposed to create pressure toward resolution never fully engages. The DHS shutdown is a case study in what this looks like domestically. For over 42 days, the Department of Homeland Security has been unfunded. TSA workers have gone without pay since mid-February. Security lines at airports across the country have stretched for hours, with staff handing out water bottles in Houston. Congress cannot agree on a funding deal because the shutdown is tangled up with immigration enforcement disputes, not the war. The infrastructure of daily life is degrading, but the degradation is not politically linked to the conflict that is consuming the government's attention and resources. The feedback loop is broken.
The automation layer
There is a technological dimension that makes unnamed wars easier to sustain than ever before. The U.S. military has confirmed the use of advanced AI tools in the Iran campaign. Anthropic's Claude was reportedly used to accelerate the "kill chain," the process from target identification through legal review to strike execution. The Pentagon has deployed LUCAS drones, low-cost unmanned combat systems that cost roughly $35,000 each, a fraction of the $1.3 million per Tomahawk cruise missile. The economics of war are shifting toward something that can run in the background, at lower cost per strike, with fewer human decision points. This matters for the euphemism problem because the political cost of war has always been closely tied to its human visibility. Coffins coming home, soldiers on the news, draft notices in the mail: these are the things that made past wars impossible to ignore. When strikes are launched by autonomous systems from aircraft carriers in the Arabian Sea, processed through AI pipelines, and reported in acronyms, the distance between the war and the public widens. You do not need to call it a war if it does not feel like one at home. None of this means AI-enabled warfare is inherently wrong. But the combination of low-visibility technology and linguistic evasion creates a system that can sustain military action with remarkably little democratic friction.
The view from a small state
Singapore's Foreign Minister Vivian Balakrishnan put it bluntly in a Reuters interview: "The entire global economy has been taken hostage." The closure of the Strait of Hormuz, through which 20% of the world's oil and liquefied natural gas flows, is not an abstraction for trade-dependent nations in Asia. It is an existential threat. Marine fuel prices in Singapore have risen 223% since the start of 2026. Shipping companies have incurred over €4.6 billion in additional fuel costs since the strikes began. Tanker traffic through the strait has dropped to near zero. For a country like Singapore, which sits at the intersection of global shipping lanes and has built its economy on the assumption that goods move freely, this is not a distant geopolitical event. It is a crisis arriving in real time, measured in container backlogs and fuel invoices. Balakrishnan also raised questions about the necessity and legality of the war, a notable statement from the leader of a country that has maintained close security ties with the United States. Small states do not have the luxury of euphemisms. When your economy depends on shipping lanes, you call a war a war, because you need to plan for what comes next.
Everyone sees a different war
One of the most disorienting aspects of the current moment is the fragmentation of the narrative. Social media does not produce a single story about a conflict. It produces thousands of overlapping, contradictory, algorithmically sorted stories. Your feed shows you a different war depending on who you follow, what platform you use, and what the recommendation engine thinks you want to see. This is a structural problem, not just a media criticism. In previous large-scale conflicts, shared information, even if imperfect, created shared political reality. People could argue about whether a war was justified, but they were at least arguing about the same war. Today, the information environment makes it possible for a significant portion of the public to be barely aware that a major military operation is underway, while another portion is tracking every strike in real time. The euphemism thrives in this environment. When there is no consensus on what is happening, there is no consensus demand to call it what it is. The unnamed war fits neatly into the fragmented attention economy.
Pattern recognition
The pattern is worth naming even if the war is not being named. Korea, 1950: a "police action" that killed over 36,000 Americans and millions of Koreans. Vietnam, 1960s: "military advisors" that became a decade-long war. Libya, 2011: "kinetic military action" that toppled a government. Iran, 2026: "major combat operations" that have shut down a global chokepoint, killed tens of thousands, and triggered what Singapore's foreign minister calls an Asian crisis. In each case, the euphemism served the same function: it bought time. Time before the public fully engaged, before Congress asserted authority, before the political costs caught up with the military ones. The question is always how much damage accumulates in that gap between action and accountability. One month into the Iran campaign, the costs are already staggering. CSIS estimated $16.5 billion in military spending by day twelve. The Strait of Hormuz remains effectively closed. Negotiations are stalled, with the U.S. and Iran outlining starkly different demands. And the DHS shutdown continues, a slow-motion collapse of domestic infrastructure that somehow exists in a separate political universe from the war that isn't called a war. Language is not the cause of these problems. But it is the lubricant that lets them persist. A war that nobody names does not trigger the mechanisms, democratic, institutional, economic, that are designed to force resolution. It just runs, accumulating consequences, until the gap between the word and the world becomes too large to ignore. We are not there yet. But the pattern suggests we will be.
References
- Trump avoids word 'war' to describe Iran conflict 'because you're supposed to get approval', The Hill
- 2026 Iran war, Wikipedia
- Senate Republicans again block bid to halt Iran war without authorization, The New York Times
- Does the War Powers Resolution debate take on a new context in the Iran conflict?, National Constitution Center
- International police action and the Korean War, Constitution Annotated, Congress.gov
- The Korea War Powers precedent, Lawfare
- Iran conflict costing shipping industry €340 million a day, Transport & Environment
- How the Iran war threatens the global food, energy and other supplies, The New York Times
- One month into Iran war, some Trump objectives are unfulfilled, Associated Press
- All the euphemisms we use for 'war', The Nation
- Lessons for Singapore from Trump's war in Iran, Foreign Policy