The War Precedent

Obama doesn't have to ask Congress to bomb Syria. But should he?

The crisis precipitated by a Syrian attack on civilians using chemical weapons, in defiance of President Barack Obama's promise that there would be consequences for the regime if such an attack were to occur, provides a timely occasion to clear up some of the confusions that have accreted in the last 50 years around the question of the president's constitutional authority to use armed force.

The seeds of this confusion were sown in the 1960s, when President Lyndon B. Johnson sought and won the overwhelming approval of both houses of Congress for the Gulf of Tonkin Resolution supporting the administration's deepening involvement in Vietnam. Johnson did not seek that resolution on constitutional grounds, but rather because he believed President Harry Truman had been mistaken, on practical political grounds, when he relied on the U.N. Charter and Security Council authority to commit troops to the U.N. expeditionary force in Korea. As the U.S. intervention in Vietnam became more controversial, the anti-war movement and their repentant allies in Congress who had supported the resolution attempted to vitiate its legal authority by claiming that they had been swindled, and had never anticipated -- despite the clear, open-ended language of the text of the resolution -- the war that resulted.

This was given the imprimatur of history by the claim, so faithfully repeated in countless books and articles since, that the entire Tonkin incident had been concocted by the Johnson administration in order to win approval for the resolution. Although there subsequently emerged doubt as to whether the second North Vietnamese attack on a U.S. destroyer in fact occurred or was erroneously reported by the local commander (whose men mistakenly took sonar reverberations for a torpedo), there is no doubt -- and there never has been any basis for doubting -- that the first attack did indeed take place and that President Johnson was just as startled by this as anyone else.

Nevertheless, this studied warping of history had an ironic effect: it persuaded presidents and their advisors that there was little to be gained by seeking congressional authority. As Johnson himself put it, "I thought if they were with me on the take-off they'd be with me until we landed. I forgot they had parachutes."

"Case law" is the phrase lawyers use to describe the judicial precedents that create a substantive body of law; in constitutional law, these precedents are the bases for doctrinal argument. But there are also doctrinal arguments as to constitutional subjects that are not justiciable, i.e., that cannot be decided by courts. Some examples of such subjects include the grounds for impeachment, the permissible bases on which the rejection of presidential nominees can be made, the question of whether the executive may by treaty purchase land for the United States (like the Louisiana Purchase) in advance of a congressional appropriation, and, of course, the constitutional requirements the executive must satisfy in order to go to war. The difference between this sort of case law and the opinions collected in the Supreme Court Reports is that the precedents are written in history -- not in judicial decisions.

There is ample precedent in recent history -- and with precedent, the more recent, the more authoritative -- to support the view that the president does not need a joint resolution of Congress, much less a declaration of war, in order to initiate hostilities on a valid constitutional basis. The rescue of the Mayaguez (Ford), the Iran hostage rescue attempt (Carter), the invasion of Grenada (Reagan), the intervention in Lebanon (Reagan), the invasion of Panama (Bush), the air attacks on Serbia (Clinton), and the cruise missile attacks on Afghanistan and Sudan (Clinton) are all recent examples.

Beyond the presidential case law, the history and text of the Constitution support the president's authority to take unilateral military action, though that may come as a surprise to many people. The Constitutional Convention of 1787 removed the power to make war from both Article I and Article II, that is, from the executive and legislative branches, giving the president the power to command forces, and Congress the power to provide funds for those forces. The power to declare war was never considered a precondition for entering hostilities but rather, as the Supreme Court observed in 1800 in Bas v. Tingy, a matter of "perfecting" an otherwise limited war and thus conferring certain rights under international law vis-à-vis neutrals, and other parties. This explains why our first war -- the so-called quasi-war against France in the John Adams administration, when many constitutional framers were alive -- was not preceded by a declaration of war. Nor, by the way, was President Thomas Jefferson's expedition against the Barbary pirates, which also relied on statutory authority.

Perhaps the most important arguments in this area are not doctrinal, historical, or textual, but prudential. In the current strategic context, does it make practical sense to require a joint resolution of Congress before the president can act? For example, with respect to extended deterrence -- the vow to treat an attack on our allies as an attack on ourselves -- I would think the answer is clearly no. A treaty -- which must win the consent of the Senate -- would suffice (as it did in Korea). How about the rescue of American nationals when force is required? Again, my sense is no: that the statutes providing such capabilities, and the extensive hearings about these contingencies which precede the adoption of those statutes by Congress, are sufficient. (This is in accord with the Adams precedent, by the way, which used three acts of Congress that appropriated funds as the basis for prosecuting the war.) What about an attack on a nascent nuclear capability sought by a hostile state? This is more doubtful, but I would be inclined to conclude that the Congress that appropriated funds, after extensive hearings over several years, for "bunker-busting" munitions could hardly claim to have been surprised when those weapons were used in the very contexts discussed at the time of the authorization and appropriations process.

These examples all have in common a certain urgency and the necessity for stealth. When there is time, the prudential calculus changes. Little is lost and much is gained by a fresh congressional debate over Syria, where there are no good tactical options that would be jeopardized by such a debate, and where the public has yet to be satisfied that the administration has good reasons for its decision.

President Obama's situation in some respects resembles that of President George H. W. Bush in the run-up to the first Gulf War. Overruling his national security advisor, Bush went to Congress for a joint resolution authorizing the U.S. invasion of Iraq. It was a daring gamble that the president finessed by announcing that he believed he had the authority to proceed in any case. This tactic seems to have narrowly won the day, with the consequence that -- although the victory in the Senate was razor-thin -- there was eventually broad public support. On Saturday, the president took a roughly similar position, saying, "while I believe I have the authority to carry out this military action without specific congressional authorization, I know that the country will be stronger if we take this course, and our actions will be even more effective."

As to whether the president is correct in his assessment that he does not, as a constitutional matter, need further congressional authorization, I am as yet undecided. The constitutional arguments for presidential intervention in Syria, absent either a North Atlantic Council endorsement or perhaps a vote by the members of the Arab League (for whose security Congress has provided extensive military assistance), are weaker than some recent precedents. In any case, I doubt it matters now. It is most unlikely that the president will use force in the face of an explicit congressional rejection of his request for authorization to use force. He carefully announced on Saturday that he had "decided that the United States should take military action against Syrian regime targets" -- not that he will.

But the really important points are that the president be seen as following the law and that we try to reform the law to reflect the changing strategic context. With regard to the first of these imperatives, I do not believe the president's position will create case law that compromises the powers of the executive any more than the actions of presidents who have reported to Congress "in accordance with" rather than "pursuant to" the War Powers Resolution that they rightly believe to be unconstitutional.

With respect to the second imperative, we must recognize that the 21st-century wars against terror are still fundamentally wars, so far as the rule of law. These wars will be waged in three domains: the campaigns against global, networked terrorists like al Qaeda and their associated allies; the attempt to prevent, and where that is not possible, to mitigate the effects of civilian catastrophes, including genocide, ethnic cleansing, and the mass killing of citizens by their own states; and the struggle to preclude the proliferation of weapons of mass destruction for the purpose of compellance rather than deterrence. President Obama recognized these three arenas when he referred on Saturday to the implications of this crisis for "governments who would choose to build nuclear arms ... terrorists who would spread biological weapons ... armies who carry out genocide."

In Syria, all three of these arenas are in play. And in Syria -- as is the case generally -- progress in one arena often means a worsening of the situation in another. This is the tragic condition of the wars of the 21st century. It may be that a national debate will enable us to appreciate this complexity.

Pete Souza/White House via Flickr


Showdowns and Shutdowns

Why the Syria debate on Capitol Hill could get tripped up over partisan fiscal battles.

In his quite stunning speech on Saturday afternoon, the president was right about the letter of the law and the spirit of the Constitution. The War Powers Act does not require the president to get congressional permission before launching cruise missiles at Syria -- but if we are still engaged in military action 60 days later, it is another matter. Yet the fact remains that the spirit of the Constitution would be violated if the president acted unilaterally at a time when there is no urgency or emergency. War powers are deeply entangled between and among the branches, even if America has had a slew of conflicts and long-lasting, all-out wars that never got a declaration of war from Congress. In that sense, it is better, in the long run, to assert appropriate presidential prerogatives and still bow in the direction of the legislative branch.

Given the scope of the president's proposed actions, the delay until perhaps mid-September is not apt to be particularly consequential. Contrary to what critics like Charles Krauthammer assert, international intelligence on Syria is strong enough that we can likely track any significant movement of chemical weapons or other materiel; and the ability we have to strike Syrian air bases and command-and-control facilities means that we can -- at any time -- inflict deep damage on Assad's regime and make it clear that there is a real and meaningful penalty for despicable conduct.

The risk here comes from other quarters. Let us assume the president did this both because he believes that going to Congress is the right thing to do, and because having a congressional imprimatur would not only add to the legitimacy of any action, but would also deter or at least dilute any congressional second-guessing. If that is true, there is an assumption that Congress will accept the White House resolution.

To be sure, there are solid reasons for that assumption. When forced off the sidelines, members of Congress have to move beyond easy criticism to confronting the harsh reality of the consequences of inaction for American credibility and prestige -- not just for Barack Obama. The fact that the resolution is drawn narrowly, along with the powerful case Secretary of State John Kerry made and the power of the president's pledge, make those consequences severe for Congress as well. For all its bluster, and the frequent demands by congressional leaders and members to apply the War Powers Resolution, when faced with a requirement to act, Congress has always blinked and deferred to the president.

For several reasons, however, this time is much dicier. One, Congress and the country are war weary after far more than a decade of debilitating conflicts in Iraq and Afghanistan, and skeptical, if not cynical, about any promises to keep the next one very limited. Two, there is a new and powerful bipartisan coalition developing on foreign and national security policy, pairing liberal Democrats and Tea Party Republicans who are want deep cuts in defense spending, a serious curtailment of aggressive intelligence gathering, and a retrenchment of American power and involvement abroad.

But there are two other reasons that spell even more serious trouble for the president. First is the deep and growing tribalism that has taken over American politics -- leaving foreign and national security policy practically the only areas where there is a bipartisan coalition, but in this case the wrong one. That may combine in a toxic fashion with the almost-uncontrollable desire by a large number of Republicans to oppose the president no matter what, undermine his policies, sabotage the laws enacted during his tenure, and inflict failure on him wherever possible. If that sentiment prevails for only a sliver of Republican lawmakers who otherwise might accept the resolution, it is trouble.

Then there is the overload of business on the congressional agenda when the two houses return on Sept. 9 -- with only nine legislative days scheduled for action in the month. We have serious confrontations ahead on spending bills and the debt limit, as the new fiscal year begins on Oct. 1 and the debt ceiling approaches just a week or two thereafter. Before the news that we would drop everything for an intense debate on whether to strike militarily in Syria, Congress-watchers were wondering how we could possibly deal with the intense bargaining required to avoid one or more government shutdowns and/or a real breach of the debt ceiling, with devastating consequences for American credibility and the international economy.

Beyond the deep policy and political divisions, Republican congressional leaders will likely use both a shutdown and the debt ceiling as hostages to force the president to cave on their demands for deeper spending cuts. Avoiding this end-game bargaining will require the unwavering attention of the same top leaders in the executive and legislative branches who will be deeply enmeshed in the Syria debate. The possibility -- even probability -- of disruptions caused by partial shutdowns could complicate any military actions. The possibility is also great that the rancor that will accompany the showdowns over fiscal policy will bleed over into the debate about America and Syria.

A full and robust conversation about what to do in the face of Bashar al-Assad's unspeakably evil actions -- with powerful interventions by President Obama, Vice President Biden and Secretary of State Kerry -- might instead have a positive impact, in the same way that the deeply emotional extended congressional debate during the George H.W. Bush presidency about going into the first Iraq war was a high point for the legislative branch. This president might, in fact, prevail with bipartisan support in both houses. That might even provide a modest lubricant for movement to avoid the insanity of government shutdowns or a debt ceiling breach. But the risks of more damaging outcomes are uncomfortably high.

Chip Somodevilla/Getty Images