Episode Details

If bombs are dropping and troops are being sent overseas, does it matter what the president decides to call it?

Today's episode continues a conversation about war powers: who actually has the constitutional authority to declare war? The answer is simple — only Congress does, not the president, who is commander in chief but was never given the power to start a war on his own. But as Brittany explains with a very relatable childhood cookie story, presidents have gotten remarkably creative at avoiding that requirement altogether, simply by refusing to call what they're doing a "war" in the first place.

Brittany opens with a confession: as a kid, she once ate a bite of cookies her mom had baked for the neighbors, then tried to talk her way out of trouble by insisting it wasn't "eating," it was "quality assurance tasting" to make sure the cookies were good enough to give away. Her mom wasn't fooled for a second — and Brittany argues the U.S. government has been running the exact same trick for the last eighty years, just with dramatically higher stakes. The last time Congress formally declared war was World War II. Every major military conflict since then — Korea, Vietnam, Libya, the War on Terror — has happened without one, because presidents simply relabeled what they were doing: "police action," "limited action," "kinetic military action." Brittany walks through each example in detail, showing how tens of thousands of American lives were lost in wars that were never technically called wars at all, and why letting the executive branch define its own limits on the power to send troops into combat sets such a dangerous precedent for the future.

• Why the Constitution gives only Congress — not the president — the power to declare war
• Brittany's childhood cookie story, and why it's the perfect analogy for government wordplay
• Why the last formally declared war was World War II, despite dozens of military conflicts since
• How President Truman avoided Congress in the Korean War by calling it a "police action"
• Why the Vietnam War was never declared, and how the Gulf of Tonkin incident helped drag the U.S. in
• How the military draft made Vietnam's undeclared-war status especially devastating for families
• Why Obama called 2011 airstrikes in Libya "kinetic military action" instead of war
• How the War on Terror became a war against an idea rather than a specific country
• Why Iraq and Afghanistan involved 20 years of conflict without ever being formally declared
• Why letting a president wage "war" against an idea, rather than a nation, removes any clear objective or endpoint
• How the mental toll on veterans is just as real in an undeclared conflict as in a formally declared one
• Why watching for this kind of relabeling matters just as much today as it did during Korea or Vietnam
• Why this pattern isn't new, isn't partisan, and spans nearly every modern president
• Why Eisenhower's warning about the "military-industrial complex" still matters when thinking about why wars keep happening
• Why a clearly declared war, like a clearly written warrant, needs defined objectives — and why undeclared wars often lack them entirely

0:00 Why Only Congress Can Declare War 0:56 The Cookie Story: Getting Sneaky With Words 3:14 How Presidents Get Around Congress 3:34 The Last Declared War Was World War II 3:55 The Korean War: "Police Action," Not War 5:31 Vietnam, the Draft, and the Gulf of Tonkin 7:48 Libya 2011: "Kinetic Military Action" 9:37 The War on Terror: A War Against an Idea 10:14 Iraq and Afghanistan: 20 Years, No Declaration 13:39 Eisenhower's Military-Industrial Complex 14:05 Wrap-Up: Why This Pattern Is So Dangerous

👍 Like this video if you've ever tried to talk your way out of trouble with clever wording 🔔 Subscribe for more stor