A vignette from the end of the U.S.-led global order, per Reuters:
Happy Tuesday. Why War? Why Now?by William Kristol Why did we go to war four days ago? And why are we going to continue this war, apparently for weeks or longer? The Trump administration can’t answer either question. That’s why some administration surrogates are trying to tell us we’re not at war. Yesterday Kasie Hunt of CNN posed a sensible question to Republican Sen. Markwayne Mullin, who serves on the Armed Services Committee and who has been acting as an administration surrogate over the last few days: “Did the president not run on not starting a war with Iran?” Sen. Mullin deflected: “This isn’t a war.” You know the administration’s defenders are in trouble when they resort to this kind of denial of reality. Secretary of Defense Pete Hegseth had undermined this talking point a few hours earlier, acknowledging that we are in fact at war: “We didn’t start this war, but under President Trump, we are finishing it.” So yes, we are at war. To deny this is disrespectful both to the American public, who have eyes to see what is happening, and to our servicemen and servicewomen, whom the administration has ordered into harm’s way. Will Sen. Mullin explain to the families of the service members who have died that their loved ones were not fighting in a war? Why did we go to war now? The administration hasn’t offered a coherent explanation. Over the weekend, President Trump suggested several purposes and backed away from some, leaving confusion in his wake. His aides tried to clean things up yesterday, having Trump read military “objectives” from a teleprompter at the White House. But none of the objectives—destroying Iran’s missile capabilities and its navy, ensuring Iran can’t obtain a nuclear weapon or support terrorism—explain why we had to go to war now. Nor do they explain why we are engaged in such an open-ended and massive military campaign. Yesterday, President Trump sent the formal notice to Congress required by the War Powers Act. He explained, “Despite my Administration’s repeated efforts to achieve a diplomatic solution to Iran’s malign behavior, the threat to the United States and its allies and partners became untenable.” “The threat became . . . untenable.” There’s no claim of self-defense. There’s no claim of imminent danger. Rather, the claim is that we were facing an allegedly untenable threat. But of course if the administration saw the threat becoming untenable, it could have done what the Constitution requires—gone to Congress, explained the situation, and sought authorization for going to war. Trump’s secretary of state, Marco Rubio, tried to help out his boss yesterday by arguing that the threat really was imminent, and that it required a preemptive attack:
But last June, Israel was at war with Iran for almost two weeks before the United States came in briefly to help finish the job. During that time there were major Iranian attacks against Israel—but only very minor, scattered attacks on U.S. assets in the region. Presumably the administration, which was, after all, in discussions with Iran last week, could have warned Iran not to attack our bases if Israel attacked. Iran would have had plenty of incentives to heed such a warning. Instead the administration chose a pre-emptive and unauthorized war for which it has offered no coherent rationale. And it now has no sound argument for why this war must be extended. The military objectives Trump mentioned have mostly been achieved, insofar as they can be. The human toll and the geopolitical and economic costs mount each day. And six American service members have died. Why should more be put in harm’s way? The answer is simple: Congress should not give this administration a blank and open-ended check to continue to wage a massive, risky, and unconstitutional war. If there’s ever a post-Trump repair of the guardrails around executive power, what should be done about the president’s war powers? And how did we get to where we are now? Share your thoughts in the comments. |