Skip to content
You can now search across every topic, entity and event.What's new
European Tech Sovereignty
22SEP

The Iran war gets a new file name

2 min read
10:47UTC

Pentagon casualties are now logged under a category called Overseas Operations rather than Operation Epic Fury, three days after the Senate refused to bind the President by statute.

TechnologyDeveloping
Key takeaway

A casualty-database label now carries the argument that a second Iran war began in July.

US casualties from the Iran war are now recorded under a category called Overseas Operations rather than under Operation EPIC FURY, the name the campaign has carried since February, a change the Defense Casualty Analysis System (DCAS), the Pentagon's casualty ledger, made on 26 July1. The administration's stated position holds that EPIC FURY ended in May. On that reading the daily fighting since counts as a second conflict rather than a continuation of the first.

The War Powers Resolution of 1973 gives a president 60 days of hostilities without congressional authorisation before he must withdraw forces. A clock that expired months ago and a clock that started in July are legally different objects, and only one of them requires a vote2.

Congress tried the direct route on Thursday 23 July and lost twice: the House passed its resolution 214-208, the Senate killed its own 47-49 . Rep. Thomas Massie, a Kentucky Republican who crossed the aisle in that vote, named the mechanism plainly: "Let me explain this absurd ruse: The Pentagon is pretending there have been two Iran wars separated by a brief cease-fire"3.

That charge is Massie's, not ours, and casualty systems genuinely break. The timing can be checked, though. The category changed three days after the Senate refused to bind the President, a coincidence of timing and direction we can verify rather than a motive we can prove. Anyone who wants to litigate the point now has to argue about the start date of an administrative label rather than about the legality of a campaign, which shifts the fight from the floor of the Senate into the departmental record, where discovery runs slower and the department controls the filing.

Deep Analysis

In plain English

The War Powers Resolution is a 1973 law meant to stop presidents fighting long wars without Congress's sign-off. It gives the president 60 days to get formal approval once troops are in combat, or start pulling them out. The Pentagon just filed the Iran war under a new administrative name. If officials later argue the old operation ended in May, that filing could be read as starting the 60-day countdown all over again on 26 July, even though nothing has changed for the troops involved.

Deep Analysis
Root Causes

The Resolution's 60-day clock is meant to start when the president reports the introduction of United States Armed Forces into hostilities, a factual and legal determination, not an administrative filing choice. No court has ruled on whether renaming a tracking category can reset that clock, so the manoeuvre exploits a genuine gap: the law names the trigger, but nothing names who gets to decide when an operation has legally ended and a new one has legally begun.

Congress's two attempts to force the issue this month both failed on the same day, 23 July: the House passed H.Con.Res.89 214-208 directing troop withdrawal, and the Senate killed the binding S.J.Res.180 47-49, showing the political branches split even before the accounting change added a fresh procedural question.

What could happen next?
  • Consequence

    A restarted 60-day clock would give Congress a fresh, unambiguous deadline to vote on withdrawal, unlike the contested May end date currently in dispute.

  • Precedent

    If the rename is later accepted as legally resetting the clock, it would give any future administration a low-cost tool to manage War Powers deadlines through bookkeeping rather than battlefield facts.

First Reported In

Update #163 · Pentagon puts four dead back, renames war

ABC News· 28 Jul 2026
Read original
Different Perspectives
ESMC (TSMC-majority joint venture)
ESMC (TSMC-majority joint venture)
ESMC's president said construction remains on schedule after the Dresden fab's topping-out ceremony on 14 September, reported by Focus Taiwan with first process equipment still targeted for the second half of 2027. No first-party ESMC or TSMC statement independently confirms the claim, and the fab remains 70% TSMC-owned inside a project Europe cites as its semiconductor sovereignty case.
Civo
Civo
Civo sold out its Navigate London sovereignty conference on 22 September, drawing about 800 attendees including a sitting MP, a former defence procurement minister and sponsors led by Nokia. Companies House confirms chief executive Mark Boost as Civo's sole person with significant control, British and UK-resident, which answers the ownership question the conference itself is arguing matters.
United States Trade Representative
United States Trade Representative
USTR opened its 2027 National Trade Estimate comment window on 14 September, naming the EU among markets with restrictive technology requirements and inviting submissions on cross-border data rules. The window follows Trump's 24 July Section 301 order into EU digital rules by seven weeks, and unused comments are kept, in USTR's own wording, for future negotiations.
Cohere
Cohere
Cohere published the deal on 16 September without naming a regulator, running the merged company globally under its own brand from dual Toronto and Berlin headquarters. It pledges the combined company will deliver sovereign AI on STACKIT, the Schwarz Group's German platform, aimed at government buyers weighing that offer against Berlin's own anchor-customer signal.
Germany (Federal Government)
Germany (Federal Government)
Digital Minister Karsten Wildberger called the Cohere talks "a very strong signal" and signalled Berlin's readiness to become an anchor customer, now its main lever since equity sits with Cohere. The German side secured a co-headquarters and two Cohere C-suite seats, but the protective-rights terms it pressed for in July remain undisclosed.
Poland
Poland
Poland leads a self-announced AI Gigafactory consortium with a EUR 100 million phase-one commitment, matched by Czechia and joined by Hungary at EUR 25 million. EuroHPC has confirmed no consortium for the call closing 12 November, so the bloc exists only in national announcements so far.