Trump Started a War but Can't Explain Why

America has been at war for nearly a week, but the president who started it can't explain why.

Either Iran's nuclear program needed destroying because Iran was "probably a week away" from bomb material, according to Trump adviser Steve Witkoff. Or Iran wasn't "enriching" uranium at all, per Secretary of State Marco Rubio. Maybe Iran threatened U.S. bases in the region, Defense Secretary Pete Hegseth suggests. One adviser told CNN there was "evidence" Iran planned to strike U.S. forces, but Rubio later called Iran an "imminent threat" because it would retaliate if Israel attacked—which isn't what "imminent threat" means.

The U.S. seeks regime change in Iran. Or maybe it doesn't. The operation will be short. Or maybe it won't. It depends who you ask and when.

A War Without a Plan

A simpler explanation emerges: the administration didn't plan before attacking another country and igniting a Middle Eastern conflagration. Nor has it planned what comes next.

The potential consequences are devastating. Beyond individual lives lost, the long-term regional implications could reshape the Middle East for decades. Given Iran's oil production and control over the Strait of Hormuz, economic aftershocks could ripple globally. The American government had no evacuation plan for its citizens in the region, let alone ideas about who'd govern Iran after deposing its leadership.

No one knows what the fallout will be. More troubling: no one in authority seems particularly concerned.

Democrats' Procedural Dance

Following Trump's unprovoked attack, many Democrats called for a war-powers resolution vote to restrict Iranian operations. It's a perennial Democratic favorite—complain about Republicans breaking rules while avoiding positions on the actual conflict that might prove unpopular if the war goes well.

The vote also papers over internal Democratic divisions between hawks sympathetic to attacking Iran and those rejecting the attack outright.

Sponsored

Advertise with Us

[email protected]

Sponsored

Yet dismissing this as typical Democratic timidity misses something crucial. Who decides when a country goes to war distinguishes republics from monarchies.

The Founders' Wisdom

The Founders' decision to give Congress war-declaring authority wasn't coincidental. It deliberately limited executives from waging war based on grudge, impulse, or personal profit. These restraints ensure that if America chooses war, it does so only after careful planning and deliberation—the opposite of what happened here.

As constitutional scholar Akhil Reed Amar writes, dividing war authority between executive and legislature was innovative because "in England, the king had power to both declare war and command troops." The king embodied the people, so his war decisions didn't require their consent. America was founded on the opposite proposition.

A young congressman named Abraham Lincoln wrote in 1848: "Kings had always been involving and impoverishing their people in wars, pretending generally that the good of the people was the object. This was understood to be the most oppressive of all Kingly oppressions and they resolved to so frame the Constitution that no one man should hold the power of bringing this oppression upon us."

Imperial Presidency's Complications

Proponents of "imperial presidency" note that requiring congressional permission for military force hit complications early. The second president, John Adams, entered the undeclared "quasi-war" with France from 1798-1800. The third, Thomas Jefferson, fought Barbary pirates without formal declaration.

But both conflicts were limited and defensive. Despite precedent, presidents from both parties have asserted unilateral authority—like Obama's Libya intervention. The Founders didn't anticipate lawmakers preferring to leave presidents holding the bag if military action proves unpopular.

Although the 1973 War Powers Resolution aimed to limit unilateral presidential war-making, presidents often ignore it and Congress frequently allows them to.

The Constitutional Crisis

Past presidents at least attempted explaining why they took the country to war, even unconvincingly. With Iran, Trump hasn't bothered. He blew past constitutional restraints preventing Americans from being drawn into unwanted military conflicts.

Yet it's happening because Congress is too weak to assert constitutional power against an unhinged executive.

The procedural objection to Trump's Iran war isn't minor or superficial. It's central to the Constitution's design for heeding governed consent: Presidents aren't allowed taking the country to war, committing its power to inevitable mass destruction of human lives, without the people's permission.