I think the point you're making is that if someone campaigned on "no new wars," and then a shooting war with Iran breaks out, arguing that it is "not a new war" because it is a continuation, special operation, military exercise, limited conflict, or not "endless" sounds like wordplay rather than a distinction most people would accept.
In the current reporting, that is essentially the defense being offered. President Trump has argued that the Iran conflict does not violate his pledge because it is not an "endless war" and is a necessary military action rather than the kind of open-ended conflict he campaigned against.
Whether that persuades anyone depends on how they understood the original promise. Most voters hearing "no new wars" would probably interpret it in ordinary English: if U.S. forces begin fighting a country with which the U.S. was not previously at war, that is a new war. Under that common-sense definition, the distinction between "war," "military exercise," "operation," "campaign," or "not endless" is largely semantic.
Politicians of all stripes often do this. History is full of "police actions," "special military operations," "kinetic actions," and other labels that avoid the word war while troops are shooting at one another. The public then decides whether the label matches reality.
So your two-word reply, "Not new," captures the core disagreement rather neatly: the argument isn't really about what is happening; it's about what to call it. If ships are being attacked in Hormuz, missiles are flying, and American and Iranian forces are exchanging fire, many people will conclude that whatever name is chosen, it looks an awful lot like a war.
That's a fair linguistic observation.
A police action, military operation, campaign, intervention, expedition, limited war, special military operation—these are not opposites of war. They are either euphemisms for war, subsets of war, or labels describing a particular kind of war.
The dispute is often less about the underlying reality than about the political and legal implications of the word war. In ordinary English, if organized armed forces of two states are fighting one another, most people would call it a war regardless of the official terminology.
Historically, governments have frequently avoided the term. The United States fought in Korea under the label "police action." The Soviet Union spoke of "international assistance" in Afghanistan. Russia officially called its invasion of Ukraine a "special military operation." Yet historians routinely classify all of these as wars.
The word war itself is surprisingly broad. We can speak of total war, limited war, civil war, guerrilla war, cold war, trade war, religious war, and so on. Once people are arguing that a conflict is merely a "military operation" or "campaign," they are usually arguing about scope, justification, legality, or political optics—not whether organized armed conflict is occurring.
In that sense, saying "it's not a war, it's a military operation" is a bit like saying "it's not a dog, it's a terrier." A terrier is a kind of dog. Likewise, many of these alternative terms denote particular forms of war rather than something fundamentally different.
Yes—and that’s the clean, attractive part of moral thinking: some acts really do look wrong in themselves, regardless of context.
The complication is that armed conflict is one of those rare domains where multiple wrongs can coexist without cancelling each other out. So you can have:
-
A party doing something that is plainly wrongful (for example, endangering civilians by placing military assets among them), and
-
A responding party still being constrained by rules about discrimination and proportionality in force.
That doesn’t “balance the books.” It just means the moral structure doesn’t behave like arithmetic. One violation doesn’t grant a license for unlimited response.
Where your statement is especially strong is at the level of intent. Deliberately using protected people or places as cover treats those civilians not as incidental victims but as part of the protection mechanism. That’s why it has always been singled out in law and ethics as particularly serious: it weaponizes vulnerability.
At the same time, “if something is wrong it is wrong” runs into a persistent difficulty in war: decisions are often made under uncertainty, time pressure, and incomplete knowledge. So actors don’t always know whether they are responding to a genuine military objective, a deception, or a mixture. The moral clarity of the principle doesn’t always translate into clarity in execution.
There’s also a psychological twist worth noticing. In war, people tend to move from “what is the right rule?” to “who is responsible for forcing my hand?” That shift is exactly where moral reasoning starts to degrade, because responsibility becomes redistributed through retaliation.
So I’d put it this way: you’re right that some actions can be judged as wrong in themselves. The hard part is that war is a system designed to ensure those wrongs don’t stay isolated—they propagate, and then everyone involved starts making second-order decisions under conditions created by the first violation.
Yes—this is one of the more interesting civilizing constraints we’ve invented.
Designations like UNESCO World Heritage Sites are basically an attempt to create shared “no-go” zones of value: places where, regardless of who controls them, there is supposed to be a stronger presumption against military use or destruction.
They help in a few real ways.
First, they create a common language of restraint. Even enemies can agree that certain sites—ancient cities, temples, historic centers, unique natural landmarks—are not just “property,” but part of a shared human inheritance. That shared label can influence decision-making, public opinion, and post-conflict accountability.
Second, they provide a reference point for accountability after the fact. Damage to a protected site is not just “damage to infrastructure,” but something that can be documented, attributed, and politically and legally contested. That matters in modern conflicts where information is persistent and globally visible.
Third, they can have a modest deterrent effect at the margins. Commanders may hesitate if striking or operating in such areas carries higher diplomatic cost, especially when alternatives exist.
But there are limits, and they are important.
These protections are not physically enforceable in the way a wall or a weapon is. They depend entirely on the behavior of actors under stress. And in conflicts where one side believes the other is using protected status to shield military assets, the designation can lose its restraining power precisely when it is most needed.
There is also a broader tension you’ve already been circling: modern war increasingly blurs the line between civilian infrastructure and military utility. A communications hub, power station, refinery, or transport node may be simultaneously civilian-essential and militarily relevant. World Heritage status protects cultural value, but most of the modern strategic infrastructure that matters in war was never designed to be “heritage.”
So I’d put it like this: these institutions don’t eliminate the dilemmas you’ve been discussing, but they do something subtle and important—they carve out islands of heightened moral consensus inside an otherwise adversarial system. And in a domain like war, even partial consensus on “what must not be touched” is surprisingly valuable.
In that sense, your instinct is right: they are not just symbolic. They are one of the few tools that tries to push war—however imperfectly—away from totalization.
Yes—and that’s actually where the idea is strongest.
The UNESCO World Heritage system isn’t really a “war institution” at its core. Its primary purpose is cultural and environmental: to identify places that matter to humanity as a whole, regardless of national ownership.
Outside warfare, the benefits are quite concrete.
One is cultural continuity. These sites often preserve architecture, landscapes, or archaeological layers that can’t really be rebuilt once lost. The designation helps slow down irreversible change—whether from development, neglect, tourism pressure, or simple modernization.
Another is shared identity at a global level. It’s one of the few frameworks where countries regularly agree, in a formal way, that something in another country is “part of our common inheritance.” That sounds abstract, but it has real effects on diplomacy and cultural respect.
There’s also a tourism and economic dimension, which is more pragmatic than romantic. Heritage status often brings visibility, funding incentives, and conservation expertise. In many places it becomes a lever for preserving sites that might otherwise be financially vulnerable to redevelopment.
And interestingly, it creates a kind of non-market valuation system. Not everything is judged by profitability or immediate utility. A centuries-old temple, cave system, or historic city district can be treated as valuable even if it is economically “inefficient” in the short term. That’s a counterweight to purely development-driven thinking.
You can even think of it as a kind of “memory infrastructure”: societies tend to preserve what they repeatedly designate as meaningful. Without that, a lot of human history would just quietly get overwritten by newer, more profitable uses of land.
So yes—its role in war is almost a secondary effect. The deeper achievement is that it gives humanity a formal mechanism for saying: some things are worth protecting simply because they exist and carry meaning across time.
No comments:
Post a Comment