The Gravitational Pull of War Authorizations that Never Expire
Whenever the USA carries out a bombing, drone strike, or another round of “limited” military action far from home, someone is bound to say, “Presidents always go to war.” This makes it sound like the problem is merely the personality of the individual holding the office. That story is comforting because it lets us blame one person and move on. The truth is more serious and more helpful. Modern presidents’ desire to start wars is an insufficient explanation under our constitutional system of government. Instead, it must be understood that they operate within an incentive structure that makes military action easier to rationalize than most people think and much harder to stop than most are willing to admit.
Congress has granted presidents broad, open-ended permission to use force, and presidents have become acclimated to this unwise congressional permissiveness. Thus, the main question has subtly shifted from “Should we go to war?” to “Does this action fit under what we are already allowed to do?” This isn’t a conspiracy theory; it’s the gravitational pull of pre-authorization. It’s what happens when laws are written broadly, left in place for years, and stretched by different administrations. Authorization gravity isn’t about presidents’ personalities and private desires; it’s about how the militaristic power elite works within the law and past decisions.
Most Americans believe that Congress is supposed to decide if the country goes to war, and that the president is the Commander-in-Chief of the armed forces. But here’s a basic fact that should concern everyone. Congress has formally declared war only 11 times in U.S. history, covering just a handful of major conflicts. Yet the United States has used military force abroad hundreds of times, from major battles to small deployments and show-of-force operations. This should make us ask what process is actually being used. In reality, Congress created a system of authorizations, reporting routines, and precedents that let the president take military action without the formal process most people expect when they hear the word “war.”
Even in the past, a declaration of war wasn’t always a careful decision made before fighting began. Often, it was a formal way to recognize and legalize a conflict that had already started or been forced on the United States. Presidents would ask for declarations after attacks or rising tensions, and Congress would then name the enemy and admit that a state of war existed. The declaration didn’t guarantee restraint, but it did guarantee clarity. It forced a clear choice, set off specific legal consequences, and made representatives take open responsibility for a war against a clearly named enemy.
Declarations of war used to mark the start of major, legally recognized wars with specific countries. But Congress hasn’t formally declared war since World War II. Instead, it has used Authorizations for the Use of Military Force, which allow military action without the formal step of declaring war. The process changed, even if the actions often stayed the same. We went from specific war declarations to flexible tools that can be used in many different situations.
Today’s congressional authorizations are often written broadly, sometimes without an end date, and remain in effect long after the crisis that caused them is forgotten. What used to be a specific decision about a particular enemy is now a lasting legal platform. The Gulf of Tonkin Resolution in 1964, which led to deeper U.S. involvement in Vietnam without a formal war declaration, showed this shift. Even after it was repealed, it set an example of how Congress can authorize military force without clearly recognizing and becoming accountable for the country being at war.
A key part of this system is the standing authorization. When Congress passes a broad, open-ended authorization for military force, it does more than approve one action. It creates a legal foundation for future decisions. The executive branch, with its lawyers and national security experts, learns how to fit new operations into old authorizations. Each administration gets not just a strategy, but also a set of arguments that have already been used and accepted. Every time this happens, it makes it easier to keep going down the same path.
Take the 2001 Authorization for Use of Military Force, passed right after September 11. It allowed the president to use “all necessary and appropriate force” against those responsible for the attacks or anyone who helped them. Many Americans saw this as aimed at a specific enemy and moment. But because the wording was broad and there was no end date, it didn’t expire after the first phase of fighting. Instead, it became a standing permission that later presidents have used for years in different regions, sometimes against groups only loosely linked to the original attackers.
The 2002 Authorization for Use of Military Force against Iraq worked the same way. It was passed with a specific regime and argument in mind, but it stayed in effect for over twenty years. Congress only recently repealed it, along with the 1991 Iraq authorization, during the FY2026 defense authorization process. The fact that it lasted so long shows how hard it is to get rid of these legal authorizations once they exist. They stick around, gain more meaning over time, and become part of the system that shapes both presidential power and Congress’s tendency to avoid tough choices.
Even when there’s no specific AUMF, presidents often use their claimed Article II powers as Commander in Chief to justify limited strikes or “defensive” actions. Since the country's early days, presidents have said they can respond to sudden attacks and take defensive steps without a formal declaration of war. Over time, this narrow power has grown. Each time a president acts alone or almost alone, it adds to a growing list of examples. Every time these actions go unchallenged, it becomes easier to argue that similar actions are normal. What started as limited emergency power has gradually expanded into a broader license for ongoing campaigns.
Standing permissions aren’t just found in U.S. laws. They’re also part of the international commitments the United States has made over the years. Being part of alliances like NATO creates ongoing expectations to work together and stay ready. Article 5 of the North Atlantic Treaty doesn’t automatically declare war; it asks each member to take “such action as it deems necessary,” which can include armed force but doesn’t require it. Still, this clause and the system of mutual defense create their own pressure. They influence planning, strategy, and presidential decisions, making military involvement seem like the default choice in a crisis.
These alliances create a different kind of authorization gravity. They don’t legally authorize military strikes, but they make military responses seem normal when allies are threatened or when regional stability is at risk. Ukraine isn’t a NATO member, and Article 5 doesn’t apply to it. Still, the strong U.S. and European support for Ukraine in its war with Russia is closely tied to the security system NATO has built in Europe and the expectations that come from years of working together. In politics, actions that are easier to take, justify, and continue often become the ones that actually happen.
You can see this pattern happening now. In late February 2026, the U.S. and its allies began attacking Iran without a serious national debate or a new, specific authorization. The president announced the operation, ordered major strikes, and only then went to Congress with briefings and explanations. The legal arguments for the campaign focus on familiar ideas—defending American personnel, protecting allies, and stopping an “imminent” threat—rather than on a new, specific law.
Some facts are still being debated in reports and briefings, and the public record is not yet complete, but there is no clear, Iran-specific law authorizing a broad war. Instead, the campaign is presented as a continuation of existing counterterrorism efforts, regional deployments, and alliance duties. This is exactly the kind of situation where past authorizations, alliance expectations, and broad interpretations of Article II make military action seem like business as usual rather than something that needs new, clear public approval.
When these legal and strategic arguments become routine, they make it easier for presidents to act. A president doesn’t have to ask Congress for a public, serious vote on every use of force. Instead, he can say, “We are continuing what you already authorized,” or “We are meeting our commitments to allies,” or “We are protecting our forces in a dangerous area.” The country might still debate whether the operation is wise, but that debate usually starts after the action has begun and things are already moving forward.
This is where the War Powers Resolution of 1973 comes in—not as a villain, but as a warning. Written after Vietnam, it was meant to bring Congress back into the decision-making process regarding the deployment of U.S. forces abroad. But over time, it has mostly become a system of notifications rather than real oversight. Presidents act first and report later; Congress responds, but rarely enforces the limits the law sets. Courts have mostly stayed out of these fights, so disagreements over war powers are settled politically, if they’re settled at all.
That last point is key. Writing a law is one thing; enforcing it is another. Congress can limit the president, but doing so is risky. If Congress approves force and things go badly, it gets the blame. If it refuses and something terrible happens, it’s called weak. In this situation, Congress often prefers to stay vague. It lets the president act and decides later whether to support or criticize. The system has adapted to this habit. When a president orders strikes on Iran first and explains later that’s not unusual—it’s the result of a system shaped by years of avoiding clear decisions.
Looking at all this, old declarations of war seem less like perfect safeguards and more like a way to force clarity. They didn’t always come before fighting started, but they did make Congress name the war, name the enemy, and take open responsibility for the conflict. Today’s ongoing authorizations and changing ideas of “self-defense” make it easier for everyone to believe that nothing really new is happening—that we’re just following decisions made long ago.
This is what I mean by authorization gravity. The law doesn’t force presidents to take military action, but the buildup of laws and habits makes it much harder to hold back. Every existing authorization lowers the barriers to using force, turns exceptions into routine, and teaches institutions that acting is easier than debating. Each time a big operation happens without a new, specific vote, it becomes even easier to keep going down this path.
If you want to see how this trend affects our culture, just listen to how we talk about violence today. We use terms like “limited strikes,” “targeted operations,” “kinetic actions,” and “degrading capabilities.” We talk as if these aren’t wars because they don’t have the old signs—no draft, no declaration, no clear start or finish. But just because there’s no ceremony doesn’t mean there are no consequences. It means the system has learned to act without asking the public for real consent, the way it used to.
Some people say presidents need flexibility. The world is dangerous, Congress moves slowly, and threats can appear faster than lawmakers can respond. There’s some truth to that—a country that can’t defend itself won’t last. But flexibility shouldn’t become permanent. Emergency powers aren’t supposed to become an ongoing authority that lasts long after the emergency ends. When a campaign against another country is justified by reusing the same broad reasons from past conflicts, we’ve gone too far.
Others argue that this is just how powerful countries act. Maybe so. But that’s a reason to look closely at this pattern, not just accept it. If the system makes constant military action too easy, then people who care about self-government need to ask why—and how to make it harder to act without real consent. A major operation against Iran that starts before any real debate shouldn’t feel normal. It should be a warning about how far we’ve already gone down this path.
This matters not because every use of force is wrong, but because a country that can use force easily will do it more often. And a country that does this often will start to see these actions as normal. What was once rare becomes routine, and people start to confuse action with strategy and necessity with habit.
If we really want fewer wars—or fewer actions that feel too much like wars—the solution isn’t just to elect better presidents. We need to make it harder to use force by making sure it’s politically costly, morally serious, and legally clear. Broad authorizations and alliance promises shouldn’t replace real, current democratic decisions. They should be reviewed, narrowed, renewed, or allowed to end in public view. Congress shouldn’t be allowed to hide behind vague language while the president acts alone. If lawmakers, during something like the Iran campaign, clearly authorize, limit, or refuse more force, they’re doing their job. If they just comment, they’re making it easier for the system to keep going as it is.
A country that values self-government has to push back against its own habits from time to time. Tools that are always ready to use will get used, especially if it’s easier than saying no or starting over. Authorization gravity isn’t just a catchy phrase—it’s a real problem. If we keep creating a system that makes war the easiest option, we shouldn’t be surprised when presidents keep choosing it.