The Founding Fathers had clear ideas about many things, but in today’s context, the question of who gets to declare war is a bit murky. Article 1, Section 8 of the Constitution says that Congress has the power to declare war, while Article 2 designates the President as the “Commander-in-Chief.” This has led to debates among constitutional scholars about whether Congress should pass a resolution before deploying troops in a conflict frame. But what happens when military actions are taken without formal declarations? Like, if a B-2 bomber is dispatched all the way from Whiteman Air Force Base and hits Iranian nuclear facilities, or if Ohio-class submarines are launching Tomahawk missiles? It raises real questions about authority and protocol.
Recently, there’s been mixed support for President Trump regarding military action against Iran, as the debate about war powers continues. Congress has been split on whether or not Trump should have authorization for such attacks. It’s an interesting blend of ideas, isn’t it? On one hand, you have representatives like Nancy Mace who emphasize the need for a constitutional approach, saying Trump didn’t really declare war, but he can certainly operate as a commander when it comes to specific tactical strikes.
But then, Mace also points to the AUMF established in 2001, which still stands and has been employed by multiple presidents for various military actions. She suggests that if lawmakers don’t like it, then Congress should just repeal it. I mean, shouldn’t there be a clearer understanding of what ‘declaring war’ actually entails? This is where the complexity lies—AUMF allows for permission to use military force, but there’s still confusion around how it’s invoked compared to a formal declaration of war.
Interestingly enough, since 1942, Congress hasn’t made any formal declarations of war, which feels quite significant. The U.S. has declared war only 11 times in history. And nowadays, it seems Congress is more focused on approving military actions rather than declaring war outright. Look at the Gulf of Tonkin resolution in 1964, or Congress’s roll in authorizing military actions after 9/11—it’s been a series of reactive measures rather than proactive declarations.
As for the current AUMF, it has become a bit of a catch-all for military engagements, which has its drawbacks. Many experts argue that it’s no longer fitting for today’s foreign policy landscape. This creates a complicated political environment where opinions on military strikes against Iran vary widely, especially between Democrats and Republicans. Some are in favor, while others express concern over escalating conflict.
Take Senator John Fetterman, for example; he appears to back military action, suggesting we’re well past the point of indecision. On the other hand, some lawmakers are genuinely worried about the repercussions of such decisions. Don Bacon, a Republican, voiced concern that small actions could spiral into larger conflicts; others, like Reps. Massie and Khanna, highlight a growing frustration over endless wars, emphasizing a non-interventionist stance.
Even within the Republican Party, there’s a mix of reactions. Some have criticized Trump’s handling of the situation, questioning his authority to instigate military action. This extended to calls for a House vote on any potential military strikes against Iran, with Democrats like Tim Kaine pushing for clearer constitutional checks on executive power.
There’s a nuanced debate over whether the U.S. is at war. Some lawmakers wrestle with the complexities of their war power authority yet often lean toward granting the President more latitude in military engagements. The skepticism of concentrated executive power that drove the Constitution’s framers seems to be fading, leading to a blurred line between war and peace in the eyes of the public and lawmakers alike. Ultimately, this raises critical questions about the decisions made and who holds the responsibility—Congress, the President, or perhaps a combination of both.
