Andrew Sullivan reports on the worst outlet for American creativity: devising new and all-but-deadly ways of torturing war-on-terror detainees. Here, “dryboarding,” practiced on Ali Saleh Kahlah al-Marri, whose detention the Fourth Circuit resoundingly rejected years ago.
Moammar Ghadafi’s death comes as just the most recent in a string of events putting the lie, conclusively, to the notion that Democrats are too weak, diplomatic, even-tempered, internationalist, or what-have-you to lead the American military. And every day the country survives without a terrorist attack counts as one more blow to the theory that Bush “kept us safe” because of, rather than in spite of, aggressive and quintessentially un-American tactics like torture. To their credit, Republicans seem to get it: throughout the series of increasingly hilarious Republican debates, I don’t think we’ve seen even one direct attack on Obama’s foreign policy from this angle — though it’s probably right to view the Palin/Romney argument that Obama doesn’t see America as an “exceptional” nation as some hybrid, taking the residuum of discredited national security talking points, mixing in a little bit of racism, and finishing it off with a layer of condescension.
Leave it to John Yoo then to explain how Obama is still — post-SEAL Team Six, the “war on pirates,” and the fall of Libya — an internationalist, UN sell-out. If only we’d attacked Libya sooner, and gone with a full-scale invasion, well the whole thing would’ve been over that much quicker!
But Obama does not get full credit, I think, because he took so long to intervene. Recall that the U.S. intervened only after the U.N. Security Council approved intervention. Obama chose to wait until Qaddafi had driven the rebels into a last holdout in Benghazi. He chose to restrain our operations along the lines set out by the Security Council, which forbade ground troops. This prolonged the ouster of Qaddafi into a full-blown civil war and resulted in more disintegration of the nation’s institutions than was necessary. To the extent that it is harder to get a new government to stand up and to collect and control Libya’s arms, part of the blame must also go to Obama’s delay because of his undue sensitivity to foreign opinion and the U.N.
It’s hard to say where Yoo’s faith in the virtue of unilateralism comes from. Certainly not results. Even accounting for the obvious reality that Libya stood in a far different state of affairs than Afghanistan or Iraq — which prevents me from arguing that Libya could’ve served as a template for those conflicts — thanks to Obama, Democrats can claim something that Republicans lack in the modern era: a foreign policy victory. True, Bush’s war toppled Saddam Hussein. But the Iraq War drained the treasury, creating the very deficit that Republicans today whine about; resulted in a new Iraq that America must either continue to prop up, or permit to implode; and its base price is measured in American lives, not missiles. In Libya, America managed to do some good, at a marginal price tag, and despite Republican opposition at every step. Call Libya a small victory, sure; but already, that’s more than Republicans can claim.
Please excuse the interrupted posting schedule — it’s like this, but probably in a good way ;). Basically, wish me luck for some things that have to happen today.
With apologies to Glenn Greenwald, I think it’s time for Democrats (and Americans, writ large) to become comfortable with targeted killing, even of a U.S. citizen. We’ve covered targeted killings here before. The power derives from the sovereign national right of self-defense, and trumps executive orders and international law “forbidding” assassinations — though to be sure, most authorities on the subject forcefully disapprove of the assassination of U.S. citizens. But, a string of Supreme Court decisions takes the legs out of Greenwald’s larger argument, that federal due process is actually violated when a citizen-belligerent is killed abroad. Although the Fifth Amendment does apply overseas, its force depends at least partially on the practicalities of the situation. Reid v. Covert, 354 U.S. 1 (1957); U.S. v. Verdugo-Urquidez, 494 U.S. 259 (1990). So under current law, whether it’s right or wrong, nothing Obama’s done is clear, black-and-white illegal, and none of it comes close to the Bush administration’s grave transgression of the effective suspension of the writ of habeas corpus over federal lands, accomplished (but ultimately halted by the Supreme Court) during the Bush years.
What we should do is set aside histrionics and ask ourselves first whether the targeted killing of men like Anwar al-Awlaki is ultimately illegal, as an improper compromise of the mediated foreign Fifth Amendment, and second, whether it should be. These are harder questions, both requiring a debate that can’t be started and ended so quickly.
Greenwald gets his quick answer by assuming al-Awlaki was killed “far from any battlefield.” But one of the things Bush got right — even if he applied it in a fundamentally flawed manner — was that the old definition of a “battlefield” doesn’t work anymore. No matter how we decide to define the term, the absence of a European line-of-battle formation, spent shell casings, or entrenchment is no longer dispositive. The enemy chose a nontraditional battlefield for us, and we cannot deny the battle.
On that basis, I would permit assassination only outside of American borders — we cannot permit the complete disintegration of the pomerium — and of American citizens only in those isolated situations where (1) the citizen’s connections to terrorism, apart from First Amendment activity, are not true subjects of debate, (2) where the citizen presents a clear and present danger to American security at home or abroad, and (3) where neutralization by other means continues to be, after reasonable investigation, impossible. If we want to consider truly routinizing this type of assassination, we might consider a warrant system, where citizens are given reasonable notice and opportunity to present themselves peaceably for trial to American authorities. There is, after all, no debate that al-Awlaki knew he was a target, but remained at large both to avoid justice and continue his fight against America.
But I suspect we don’t want to go down that road. Greenwald’s right about one thing — as a country, we’re far too good at avoiding serious moral debates. But he’s as guilty of that particular sin as the rest of us. Staking out an untenable, extreme position, one with no possibility of ever attracting serious support, hardly qualifies as constructive political participation. We need to be prepared for compromise, even ugly compromise, if we’re ever to deal appropriately with the fundamentally American questions posed by global terrorism.
A few months back, The New Yorker attempted to set out a synthesis explaining the President’s foreign policy strategy, as applied to Libya, the “Arab Spring,” and beyond. They concluded that the administration was attempting to “lead from behind” — which David Remnick corrects to “leading from behind the scenes” — by pushing for American interests without leaving American fingerprints on the matter. Notably, this strategy doesn’t spring from a lack of belief in American ideals, or even a hesitancy to apply direct power when needed. It follows from an acknowledgment that some sectors of the world may bristle at American involvement, even while embracing American values. So we act indirectly. Like Bender’s God (YouTube), “when you do things right, people won’t be sure you’ve done anything at all.”
This is good strategy — if it’s strategy at all — but it’s one for which we remain rhetorically unprepared. For the left’s part, we’re too ashamed of fighting this new war in the first place to take pride in the fact that it’s being done well. And for the right, any intervention conducted without military fanfare, celebrations on carrier hanger decks, and premature proclamations of victory approximates a betrayal “American exceptionalism,” a surrender to a post-American age, or a decision to vacate the world stage.
Let’s stop and recognize what’s being done, and why. The “war on terror” brings us into conflict with a sector of the world where, for whatever reason, we find ourselves less able to effect real change than we have been in previous conflicts. This phenomenon needn’t be explained by reference to overwrought hand-wringing and existential doubt about “American decline” — it’s just a different challenge, and one that can’t be addressed by the talents we’ve developed in waging (and winning) prior wars. We cannot, for example, rely on European allies to provide bases, intelligence, and support — and we’ve simply never tried to create an ally, much less from such foreign materials.
Considering the circumstances, we shouldn’t be ashamed of approaching a new problem with a new solution. The invention here is realizing that “American exceptionalism” — the American concept — isn’t a means, and so has nothing to do with warfare. It’s an end, and has everything to do with trading authoritarianism for self-determination. This strategy of “leading from behind the scenes,” and with modesty where the situation demands it, is leadership still, and a triumphant vindication of American exceptionalism from a President who cares more about results than swagger. It’s about time.
On this site, we’ve spent a fair bit of time arguing about whether the current military action in Libya was “authorized” (no), whether it therefore becomes unconstitutional (no), and whether it should be unconstitutional (maybe). Here’s a variant on the theme. Can the President order a cyber attack on a foreign power, despite the absence of a declared war, which results in property damage and could result in the loss of life, without consulting Congress? Does it matter if the attack must remain absolutely secret to succeed? And does it matter if, should the attack be traced to the United States, it could result in an all-out shooting war?
Admittedly, this doesn’t fall easily within the traditional definition of a “war.” But neither do targeted missile strikes. Some background first.
The facts
Really, you should read the linked article (and other takes on the same). But for your convenience, Stuxnet was an extremely sophisticated computer virus, released late in the last decade, indisputably designed to target centrifuges at Iranian nuclear facilities and to wear them out at an accelerated rate, thereby delaying Iran’s development of a nuclear warhead. The nature of the facilities targeted, and the virus’ method of transmission, mean that the virus must have been introduced by hand into the facility. And, further, it must have been designed based on extremely high-level information. The coders had to know, for example, the software used by the centrifuge control computers, the number of centrifuges, their operating frequency, and more. Suffice it to say, the developers required (and obtained) a level of information that could only have been gathered two means: (1) insider knowledge, or (2) concerted and successful espionage.
On this basis, and some other clues, we suspect (but nobody knows) that either the United States, Israel, or both developed Stuxnet, and deployed it with the goal of dealing an untraceable but severe tactical blow to Iran’s nuclear program. We also don’t know how well the program succeeded. So to get to an interesting hypothetical, we have to make some things up.
The assumptions
For the purposes of the below, let’s make four assumptions. First, assume that the United States deployed Stuxnet. Second, assume that the property damage was severe, even irreparable. Third, assume that, since we are talking about nuclear physics, the potential for loss of life was present, if not severe. Even if Stuxnet clearly doesn’t check that third box, it proves we’re not far from a world where a virus could do just that. Fourth, assume a nontrivial (but still small) risk of Iran tracing the virus back to the United States.
To summarize: on the assumed facts, for this hypothetical Stuxnet represents the targeted, state-sponsored neutralization of physical military assets under the control of a foreign power.
The morality
On these facts, I think using the virus to forestall the threat of a nuclear Iran, and the consequences that would entail, is not only a moral act, but an imperative. Even at the risk of explosions and possible death, neutralizing a real threat the national security of America and her allies, posed by an implacable foe, without any initial risk to American lives, is a net good by my conception of statesmanship. Although it risks war, Iran would not (and could not) fight on just this provocation. So, it’s essentially a costless tactical strike.
The law
As I see it, such strikes, even without express or implied Congressional approval, are not just moral, but fall squarely within the President’s commander-in-chief power. Stuxnet’s deployment clearly doesn’t qualify as anything near to a “war,” and the need for both secrecy and immediacy implicates the Federalist concern for the Executive’s “Energy.” Like Libya, no American lives are immediately risked, so the War Powers Act does not plausibly apply. And, this is the type of project we’ve typically relegated to the role of espionage. Bullets have long been traded between American and foreign agents without a declaration of war, and only on the Executive Branch’s say-so. Because Stuxnet is closer to espionage than an actual war, it’s not the type of event that even raises a War Powers Resolution issue.
The problem
But why? Notice how outdated the significant criteria listed above start to sound. We’re coming close to the day when a full, all-out “war” could be started and won inside of a day, and all electronically. Presumably a series of Stuxnet-type viruses could, triggered at once, decimate an undeclared enemy nation’s power grid. On my analysis — unless scale or likely result somehow matter to the legal analysis — the President could take that action, which would actually commit us to a war, on his own. Shouldn’t that be problematic?
Notice, too, that the President’s power to deploy a Stuxnet-type weapon feels like an easier case than Libya, and an easier case, even, than deploying Predator drones. Again — why? How different from Libya is a theoretical state-sponsored Stuxnet attack, anyways? Is it the actual death of enemy combatants in Libya that changes the character of the conflict? Or is it that missile launches look more like a traditional “war” than computer attacks? Here, too, these distinctions are decreasingly meaningful in a world where we can theoretically cripple foreign military assets without ground invasion and, now, without ever even firing a shot.
The face of warfare has changed. To a lot of us, Libya feels like a real constitutional problem; but if Stuxnet-type viruses see widespread adoption as weapons of war, the problem is going to get much worse before it gets better. To head off the developing difficulty, we should start to design a model for limiting unilateral warfare based on those values that actually matter to us. For me, at least, that means focusing on two factors: (1) the loss of American lives and, (2) the risk of large-scale geopolitical commitment.
I don’t think we can read values like this into the constitution, unless we acknowledge the the constitutional commitment of the “war” power to the legislature works only so long as “war,” as it’s commonly known, is a perfect proxy for the kind of international conflicts we want to all agree upon before starting. But I don’t think that assumption holds water anymore. What can we do about that?
A while back, I argued that because the War Powers Resolution doesn’t treat anything less than a ground war as a war, Obama’s handling of Libya is, whatever else it may be, constitutional. I still think that’s true: the legislative history plainly contemplates restricting only the President’s right to start a ground war, and the text of the statute speaks in terms of American “forces.” A missile isn’t a “force”; so this isn’t legally a “war.”
This reading of the WPR doesn’t mean that Libya isn’t a “war” within the common parlance, or that a missile strike on American soil wouldn’t be the start of a “war.” It just means that, for the purposes of the statute, “war” becomes a term of art with a specific legal meaning.
Reading the WPR in this limited way might make it an artifact of its time. The kind of power-projection we undertake today, and the strategy implicated in Libya, is of a decidedly post-Cold War vintage. In the Cold War, we worried about limiting the use of nuclear weapons (which is provided for separately), and the unilateral commencement of a ground war (covered by the WPR). Missile- and drone-strikes on non-state actors, or for the purposes of disrupting the same, are new inventions, unique to the war on terror; plainly not something the drafters of the WPR would have considered important; and so, remain unregulated.
Maybe that’s not the way it should be. Unilateral missile- and drone-strikes are quite capable of starting an all-out war, ultimately requiring the commitment of ground forces, and endangering American lives. That fear isn’t present in Libya, so “as-applied,” this limitation to the WPR makes sense. But if Congress’ goal was to restrain the President’s ability to start, on his own say-so, an all-out shooting war, it doesn’t follow that the President can order strikes on any target, on his own authority. The WPR should, if it is to have any meaning, prevent the President from ordering missile strikes on France, say, or Russia, as both countries could (and would) retaliate, leading to an all-out war that couldn’t help but endanger American lives.
What the WPR should do, then, is to speak in terms of probabilities. It already does, to a certain extent. As written, the resolution asks the President to submit to report & review where “United States Armed Forces are introduced” ”into hostilities or into situations where imminent involvement in hostilities is clearly indicated by the circumstances.” 33 U.S.C. § 1543(a)(1). To close the enforcement gap, all that’s needed is a little more generality. The WPR should regulate situations where “United States military power is expended” in furtherance of “hostilities, or in situations where involvement in hostilities is a natural, intended, or probable result.”
But as of now, it doesn’t, meaning President Obama’s actions remain on the level. Technically.
Joe Scarborough rightly tags a particularly absurd nascent media narrative: that the GOP’s opposition to President Obama’s Libya intervention constitutes “isolationism.” It doesn’t. First, to ascribe a particular ideological label to the Republican Party’s position here posits an actual, unitary, coherent worldview. Maybe that’s a reasonable assumption with other major political actors, but the Republican Party’s only worldview since 2008 has been opportunism. Functionaries perceive Obama as vulnerable on Libya, so they attack. There’s nothing more behind it, and certainly no principles in play.
Second, Joe is right that there’s substantial daylight between a principled opposition to the Libya intervention, and isolationism. But his description of a unitary “Bush-Obama style of warfare” demonstrates an unwillingness to apply that same scrutiny elsewhere. It should go without saying that beginning a small-scale intervention, without troop commitment and acting only with true international support, is distinct from the unilateral commencement of an all-out ground war (though we shouldn’t “forget Poland“). The two Presidents’ goals are similar: the reshaping of a region into something more favorable to American interests. But the difference between the means employed to that end speaks to a vast difference between the two men — one obvious anytime you look at the price tag of Bush’s adventure, both in lives and in dollars.
Libya proves that Obama shares with Bush a certain willingness to fight and, at an abstract level, comfort with deploying military force to protect American interests. But I don’t believe it speaks to any other similarity whatsoever. Not all military actions are created equal.
Set aside for a minute bizarre tea party concerns with the administrative state (a.k.a, “socialism”): agencies are here to stay. They’re valuable things, subject-matter experts with both the time and knowledge to solve problems well. But they’re not little legislatures. The Constitution vests Congress with the legislative power, and only Congress; for an agency to take even a quasi-legislative act, its power must derive from Congress’, typically through the explicit, and limited, delegation of authority.
For a delegation to be effective, Congress must tell the agency precisely what task it may accomplish. That any delegation of power requires such an “intelligible principle” is a bedrock rule of administrative law, dating to the dawn of the administrative state. The rule exists to prevent Congress from (essentially) delegating itself out of existence, an incentive legislators would otherwise face, especially on hot-button issues. To the extent that the nondelegation doctrine survives, it requires legislators to tell the recipient of delegated power generally what it wants done, and how to accomplish it. For example, it will not do for Congress to simply instruct the SEC to stabilize the capital markets; it must tell the SEC how it is to accomplish this goal.
There’s a way to look at the declaration of war as a similar administrative action. As we highlighted last week, the modern “declaration” takes the form of an “authorization for the use of military force,” which both checks the War Powers Act box, and permits, essentially, all military action the President may deem necessary to accomplish Congress’ chosen objective, subject only to external limits. Acting under an AUMF, the President “personif[ies] the federal sovereign,” and necessary military acts will only rarely be gainsaid.
Functionally, Congress delegates its warmaking power for the duration of the conflict, but the scope of the President’s delegated authority is always confined by the specific limits of Congress’ authorization. The President’s war powers are limited, in other words, by what we would call in the administrative context an intelligible principle: “win this war,” not, “make the world safe for America.”
All AUMFs in recent memory contain such a principle. The September 2011 AUMF comes the closest to a general grant of war power, but even there, the President could only take all:
necessary and appropriate force against those nations, organizations, or persons he determines planned, authorized, committed, or aided the terrorist attacks that occurred on September 11, 2001, or harbored such organizations or persons, in order to prevent any future acts of international terrorism against the United States by such nations, organizations or persons.
This is a finite grant — it outlines an achievable goal, and one we’re closer to achieving than ever. But the closer we get to achieving this narrow goal, the more it looks like just one part of a larger mission, one that verges on the impossible: the eradication of global terror.
By definition, such a war may never end, and it also may be one we’re obligated to fight. But perpetual war comes with serious practical problems — and to that we add a legal problem. I don’t see, at least as it stands, how Congress can authorize war against an unnamed, faceless, amorphous foe, without completely delegating away its constitutional duty (and responsibility) to declare war. Without an intelligible and limited principle, this delegation would (and probably should) be unconstitutional.
That’s not the end of the inquiry: if we need to fight such a war, we’ll figure out how to do it. All of the above means only that when we do, we’ll probably have to reinvent a good deal of our war powers framework. And that’s a process we’ll want to undertake carefully, with our eyes open to the risks.
Because I found myself in D.C. until late last night — for this event, which was nothing less than amazing — I lack time to write what I’ve wanted to for some time. Stay tuned!
In the alternative, don’t miss this post on Andrew Sullivan’s recently re-sited blog:
All war is unspeakable – but there is a civilized as well as a barbaric approach to it. In a civilized culture, you respect how the enemy, however we have to demonize them to kill them, is still human. And so there are limits to what will be done to them if they come into our custody. And there are laws of war to manage this. And then there are those moments, like those German POWs becoming American, when a gesture takes on a grander scale and actually heals.
Why did we treat Nazi prisoners then better than we treat Muslim prisoners now? The applicability of the Geneva Convention in World War II was crystal-clear, of course, while in the War on Terror, it’s certainly not. But I reject the notion that Americans believe our morality should ever be controlled by our minimum obligations. Is it a race issue — orientalism writ large? — or are we actually crueler now than we were then? Whatever the cause, to paraphrase Augustus, whatever our military power may be, we should always exceed all others in moral authority.
I’ve recently acquired a decent respect for Joe Scarborough. He seems, to a certain extent, to defy easy labeling as another mouth of the hydra-headed, but uniformly extreme, Republican Party (e.g.). But that respect has its limits.
In a Politico op-ed, Scarborough asks where the liberal outrage is over Libya — he apparently reads neither the influential Greenwald, nor the indignant Sullivan — and wonders how we can morally justify the Libya intervention, but not the Iraq War.
While one can make the moral argument that countries can be attacked strictly on humanitarian grounds, that argument is laughable when it comes to Libya.
How can the left call for the ouster of Muammar Qadhafi for the sin of killing hundreds of Libyans when it opposed the war waged against Saddam Hussein? During Saddam’s two decades in Iraq, he killed more Muslims than anyone in history and used chemical weapons against his own people and neighboring states. [. . .]
If Obama and his liberal supporters believed Qadhafi’s actions morally justified the Libyan invasion, why did they sit silently by for 20 years while Saddam killed hundreds of thousands?
The article pays lip service to the painfully obvious distinction — as a military action, the Libya expedition is both fundamentally different from, and substantially smaller than Iraq — but doesn’t follow the logic to its conclusion. The decision of when to use military force for humanitarian reasons depends on two very different values: what we’d like to do, and what we can do. Scarborough’s point about liberal hypocrisy only materializes if we equate the two values. That methodology of conflict would partially explain the rush to war in Iraq, but it’s an odd way to plan foreign policy. In fact, it’s cheating: the political science equivalent of assuming a frictionless vacuum. To make an equally absurd point, why did Bush invade Iraq in 2003, when he could have “just as easily” invaded China and installed an American proconsul in Hu Jintao’s place, wiping out the national debt in the process?!?
Especially in war and foreign policy, moral calculus matters. To that point, it’s material to note that the price tag on the Libya expedition comes in, so far, at just 0.07757404% of the staggering bill for Operation Iraqi Freedom. And that’s using the conservative, February estimate, valuing the Iraq War at just $709 billion. That took math: comparing the cost in American lives is a considerably easier task. For any value of “x,” 0 is precisely 0% of x.
Asking what wars an invincible, fully paid-for military would fight is just a distraction. What Scarborough should ask is, is the President doing the best work possible with the military resources available to us? That’s a tough call. But at least it’s a useful question.