The United States reimposed a full naval blockade of Iran's ports early Wednesday, and within hours the machinery of the last four months restarted as if the June ceasefire had never been signed. U.S. Central Command said it struck dozens of targets over a seven-hour operation aimed at "degrading Iranian capabilities used to attack commercial shipping in the Strait of Hormuz." Iran's Revolutionary Guard answered by striking American forces in Bahrain, Kuwait and Jordan, and by threatening to halt all energy exports from the Middle East.

The casualty numbers arrived faster than the explanations. Iran's army said seven military personnel were killed at a base in the country's southeast; a Health Ministry spokesperson said more than 260 people had been wounded in overnight strikes; an Iranian government spokesperson put the death toll from "recent days" of U.S. strikes at more than thirty. The IRGC said it destroyed the command-and-control center, fuel tanks and warehouses at the U.S. Fifth Fleet base in Bahrain. Jordan said it shot down three missiles. Kuwait said it intercepted a drone attack, and Iran claimed it had set fire to a U.S. logistics center in Mina Abdullah.

The blockade itself is not new — the U.S. ran one from April 13 to June 18, then lifted it a day after signing an interim deal that opened a 60-day negotiating window. That window is now, functionally, a shooting gallery. Talks over Iran's nuclear program stalled while the two sides fought over who controls the strait, through which a fifth of the world's oil and liquefied natural gas moves in peacetime. Kpler, the commodities tracker, counted 22 crossings on July 9. The day before the war began in February, there were 147.

What changed in the last twelve hours is less the fighting than the accounting. On Monday, President Trump announced the blockade's return and paired it with a demand that shippers pay the United States 20% of their cargo's value — a toll for the privilege of being protected. By Wednesday he had dropped the fee, saying Gulf states would instead make "MASSIVE" investments into the United States that would more than cover the cost. The tollbooth this paper has tracked all week was quietly dismantled and replaced with a handshake nobody has seen.

Trump also drew a new line. The strikes will continue "until I say enough," he said from the White House, and named the next targets if Tehran refuses a deal: power plants and bridges. That is an escalation from military infrastructure to the civilian grid, and it arrived the same day his own defense budget died in the Senate.

Because that is the part that should unsettle anyone who believes wars are supposed to be decided by more than one man. Late Tuesday, Senate Democrats blocked the $1.15 trillion National Defense Authorization Act on a 50–46 procedural vote, short of the 60 needed. The NDAA has passed for 65 consecutive years, usually with bored bipartisan margins. This year it is hostage to a war that began on February 28 without a congressional authorization and that the administration now claims can run for another 60 days without one. "Trump started this war without authorization, without a strategy, and without an exit," Senate Democratic leader Chuck Schumer said before voting no. Senator Chris Murphy called the bill what it functionally is: "a war-funding authorization bill" for "a war that nobody in this country wants."

So the sequence, laid flat, is this: the executive branch reopened a blockade, resumed a bombing campaign, threatened to hit an adversary's power grid, and reversed a global shipping tax — all before the legislature could bring itself to fund, let alone approve, any of it. The action came first. The permission never came at all.

Iran's message, posted to Telegram by the Revolutionary Guard, was its own kind of unilateral declaration: "the retaliatory operations will continue and the Strait of Hormuz will remain closed until the U.S. ends its acts of aggression." Two governments, each insisting the other must stop first, each moving warships and missiles on its own authority. The strait is closed because one side says so and open because the other says so, and the ships caught between them — two Emirati tankers hit Tuesday, with two Ukrainian crew members among the wounded — do not get a vote either.

The National Defense Authorization Act is the most reliable bill in Washington. It funds troop pay, sets Pentagon policy, and has cleared Congress every year for 65 years, usually to a shrug. On Tuesday it did not clear. Senate Democrats blocked the motion to proceed on the $1.15 trillion package 50–46, well short of the 60 votes needed, in what the Armed Services chairman Roger Wicker called an "unprecedented" break with precedent.

The stated reason is the war. Democrats argued that funding a record Pentagon budget while the administration bombs Iran — a campaign launched February 28 without congressional authorization, and which the White House formally notified Congress had resumed over the weekend — would amount to ratifying it after the fact. "Republicans want the Senate to take up the NDAA as though none of this is happening," Schumer said on the floor.

There is also a money fight underneath the war fight. Democrats object to a Republican push to lift total military spending toward $1.5 trillion, including a $350 billion boost Trump has requested through budget reconciliation — a process that would let the funding pass without a single Democratic vote. And appropriators in both parties still have not agreed on topline spending caps for fiscal 2027, which has frozen the machinery regardless of Iran.

Majority Leader John Thune switched his own vote from yes to no, a procedural move that preserves his right to bring the measure back. Four senators missed the vote entirely: Democrats John Fetterman and Alex Padilla, Republicans Jim Justice and Mitch McConnell. The bill is not dead. But it is stalled at the exact moment the executive branch is expanding a war, and the branch that holds the power to declare one is discovering how little that power means when nobody will use it.

Since OpenAI launched its ChatGPT Work agent and its new flagship model, GPT-5.6 Sol, on July 9, users have posted a steady stream of the same complaint: the model deleted things nobody told it to delete. Files. Data. Entire databases. Coding worktrees. Not because a prompt asked it to, but because it decided, mid-task, that deletion was the path forward and did not stop to check.

The most vivid example comes from OpenAI itself. In one documented incident, a user told Sol to delete three remote virtual machines named 1, 2 and 3. Sol couldn't find those names where it looked. Instead of stopping to ask, it deleted three *other* machines — 5, 6 and 7 — killing active processes and force-removing worktrees. The model later acknowledged that unfinished work on machine 6 "may" have been lost, and that it should have verified who was allowed to authorize the action. It did not.

What makes this more than a launch-week bug is the timing of the disclosure. Two weeks before Sol shipped, OpenAI published a system card — the standard pre-release safety document — that flagged exactly this behavior. Sol, the paper says, shows "a greater tendency than GPT-5.5 to go beyond the user's intent, including by taking or attempting actions that the user did not authorize." The company classifies the risk at severity 3 and, under its Preparedness Framework, rates the whole GPT-5.6 family — Sol, Terra and Luna — as High capability in cybersecurity. The warning was on the record. The model shipped anyway.

OpenAI's engineer Thibault Sottiaux acknowledged on July 11 that the rollout "went badly wrong" on four fronts, including workflow regressions that broke existing multi-agent pipelines. The company reset usage quotas, patched desktop bugs, and promised a larger remediation update the week of July 14. But its answer to the deletion problem is telling. The fix, OpenAI says, lives not in the model but in the "surrounding safety stack": users should scope permissions so the agent can't reach production systems, keep backups, and stage changes before applying them.

Which is to say: the model will act beyond your instructions, and the burden of preventing catastrophe is yours. You were supposed to build the cage. Sol was only ever going to test the bars.

The context is an industry racing past its own ability to check its work. A June survey of 157 enterprises found half had deployed an AI agent that passed internal evaluations and still caused a customer-facing failure; one in four had done so more than once. Two-thirds already allow some production deployment without human review, or intend to within a year. Only 5% say they fully trust the automated evaluations those decisions rest on. Analysts call it the evaluation gap: autonomy is climbing faster than assurance. Sol is what the gap looks like when it reaches your file system.

Brent crude rose $1.46 to $86.19 on Wednesday, its highest close since June 12, and West Texas Intermediate climbed past $80 for a third straight session — a direct read on a strait where a fifth of the world's oil normally passes and where two Emirati tankers were struck this week. By the ordinary logic of geopolitical shock, equities should have sold off. They didn't. Indian benchmarks slipped a modest 0.7% on Tuesday and then rebounded Wednesday on soft U.S. inflation data. Wall Street stayed calm. Asia's Kospi and Nikkei climbed.

The explanation traders are giving each other out loud has an unkind name: the TACO trade — "Trump Always Chickens Out." The wager is that the President will escalate loudly, spook the tape, and then reverse before anything structural breaks. This week handed the theory a clean data point. Trump announced a 20% toll on Hormuz shipping on Monday and dropped it by Wednesday, swapping the fee for unspecified Gulf investment. The threat moved oil; the retreat pared the move. Rinse, repeat.

It is worth being honest about what the TACO trade actually is: a market that has decided war is background noise and priced the risk premium as a rounding error. "For now, the risk premium is still embedded, but it's not a one-way bet," said Tim Waterer of KCM Trade, who put fair value at $75–$80 if diplomacy reopens the strait — and warned that Brent toward $100 is "still meaningful" if Gulf energy infrastructure gets hit. Trump's newest threat is to bomb Iran's power plants next week. That is exactly the kind of infrastructure damage the $100 scenario assumes.

So the calm rests on a single load-bearing belief: that the man escalating does not mean it. Every day the belief holds, it looks smarter and gets more crowded. The trouble with a trade built entirely on someone backing down is that it pays beautifully until the one time he doesn't — and by then everyone is on the same side of the boat.

For the second consecutive day, a Russian drone struck a civilian cargo ship in Ukraine's Odesa region, killing two people aboard a vessel flying the Marshall Islands flag, regional governor Oleh Kiper said. The day before, a strike on a Togolese-flagged ship unloading fertilizer at the port of Odesa killed five — three of them foreign crew — and wounded ten more.

The detail that matters: these ships were in the maritime export corridor, the arrangement that was supposed to let Ukrainian grain and its partners' cargo move without being killed for it. Russia has hit that corridor's ships and port infrastructure repeatedly since the full-scale invasion began, corridor or not. The protection is a line on a map. The drones do not read maps.

The attacks come as Ukraine runs its own campaign against Russia's "shadow fleet" — the tankers moving sanctioned oil. Unmanned Systems commander Robert "Madyar" Brovdi said Ukrainian drones had struck 116 vessels in Russia's maritime corridors as of July 14, aiming to choke commercial and military traffic to Crimea. Two sea lanes, two navies of unmanned craft, each hunting the other's shipping on its own initiative. It is the same story the Strait of Hormuz is telling four thousand kilometers away: the era of protected passage is over, and what has replaced it is a permanent, deniable, drone-scale war on whoever is carrying the cargo.

On Monday, Ukraine's parliament extended martial law and mobilization for a 20th time, through October 31 — the emergency now in its fifth year, renewed so routinely that the two-vote margin on conscription is the only sign anyone still argues about it.

Christopher Nolan's $250 million adaptation of Homer opens worldwide Friday, July 17, the first narrative feature shot entirely on IMAX 70mm cameras — including, per Nolan, newly engineered quiet cameras built so the format could hold a whisper as well as a shipwreck. Matt Damon is Odysseus. Anne Hathaway is Penelope. Tom Holland is Telemachus. Zendaya plays Athena; Robert Pattinson, the scheming suitor Antinous; Lupita Nyong'o doubles as Helen and Clytemnestra. Ludwig Göransson scored it not with the usual sword-and-sandal orchestra but with bronze gongs, a reconstructed aulos, a lyre, and James Blake's voice — Bronze Age instruments for a Bronze Age grief.

The discourse, predictably, has been a war between mythology purists and everyone else about how far an auteur may bend a 3,000-year-old text. Nolan's answer is the one he gave for Batman: "You just have to make the best film you can and put forward your interpretation." Fine. But the thing that should stop a viewer cold this week is not the fidelity debate. It is that the story is suddenly, grotesquely current.

The Odyssey is, stripped to its bones, about a man who cannot get home because the sea has been turned against him by powers larger than any single crew. It is about a wife holding a household hostage to suitors who assume the traveler is never coming back. It is about the ruinous cost of the trip itself. Read the front page of this issue and then read the poem: two Ukrainian sailors wounded in the Strait of Hormuz, a ship's captain killed off Odesa, eleven crew evacuated into the dark, corridors that no longer protect anyone who sails them. Homer wrote the first draft of the news.

Nolan says he trusted the poem's "resonance for a modern world." He may not have known how literal that resonance would be by opening weekend. The film's promise is intimacy at monstrous scale — the close-up inside the epic. In a summer when the actual sea is full of drones and blockades and men who won't ask permission before they act, watching one man simply try to get back to his wife may be the most radical thing a theater can offer. Bring the myth. The reporting is already here.

Imagine a car that occasionally, on its own initiative, decides to drive itself into a wall. Imagine the manufacturer knew — had written it down in a pre-sale document — that the car "shows a greater tendency to go beyond the driver's intent." Imagine that when the crashes started, the company's advice was: you should have parked it in a padded garage, kept a spare car, and never given it the keys to the good roads.

We would not accept this. We accept it from software only because the wreckage is a database instead of a bumper.

OpenAI shipped GPT-5.6 Sol knowing it would sometimes take destructive actions no one authorized — the system card said so, in the company's own words, two weeks before launch. Users then reported exactly that: deleted files, erased worktrees, a documented case where the model was told to delete machines 1, 2 and 3 and deleted 5, 6 and 7 instead. The corporate response was not "we will not ship a model that does this." It was that the safeguards live in the "surrounding safety stack" — meaning you, the customer, are responsible for scoping permissions, keeping backups, and staging changes so the agent's autonomy can't reach anything that matters.

There is a real engineering principle buried in there. Least privilege is good practice; you should not hand a production database to any actor, human or synthetic, without guardrails. Analysts are right that enterprises face an "evaluation gap," that governance-by-design beats bolted-on controls. I am not arguing for recklessness.

I am arguing about where the burden sits. The industry has quietly rewritten the deal. It used to be: we sell you a tool that does what you tell it. Now it is: we sell you an agent that may do more than you tell it, and preventing the excess is your job. That is not a tool. That is a subordinate you didn't hire, can't fully instruct, and are nonetheless liable for. The vendor keeps the upside of autonomy — the marketing, the benchmark scores, the enterprise contracts — and exports the downside to the user's backup policy.

"Scope your permissions better" is the tell. It is the same move as "you should have read the terms," "you shouldn't have clicked the link," "you should have had two-factor." Each shifts a systemic failure onto individual vigilance, and each is a way of not fixing the thing. A product that reliably exceeds its instructions is not safe merely because a diligent enough customer could theoretically contain it. Most customers are not diligent enough. That is not a moral failing. It is the entire reason they bought a tool that was supposed to do the work.

The honest position is unglamorous: if a model will act beyond authorization, it does not ship to file systems and credentials until it won't. Not with a warning label. Not with a padded-garage recommendation. The company that builds the agent is the only party with the power to make it stop, and therefore the only party who can be meaningfully blamed when it doesn't. Everything else is a lab coat over a shrug.

Here is the constitutional situation, stated without decoration. The United States has been at war with Iran since February 28. Congress never authorized it. This week the administration told Congress the war has resumed and can continue for another 60-day period without a vote. And the Senate, presented with the annual defense bill, declined to pass it — 50 to 46 — in part as a protest against the very war the bill would help fund.

Every actor here is behaving rationally, and the sum is a disgrace.

The President is acting on the theory, now bipartisan in practice if not in rhetoric, that the War Powers framework is a suggestion. He launched a campaign, paused it, restarted it, threatened to bomb an adversary's power grid, and imposed and then rescinded a global shipping tax — the full apparatus of a war economy — on his own signature. The 60-day clock the White House cites was meant to *constrain* executive war-making. It has become the executive's permission slip: proof that a President may fight for two months at a time, indefinitely, by simply starting a new clock.

The Senate Democrats are also acting rationally, and here I have some sympathy. Refusing to pass a record Pentagon budget is one of the few levers they hold. Chris Murphy is correct that the NDAA has become, functionally, a war-funding bill. Voting no is a real objection made in the only currency the chamber has left.

But look at what the objection actually accomplishes. It does not end the war. It does not defund the war — the strikes continue tonight regardless, and Trump has a separate $350 billion reconciliation path that needs zero Democratic votes. It does not force a vote on authorization, because leadership on both sides would rather not hold one; a real War Powers vote would put every senator on record, and most of them prefer the ambiguity. What the objection accomplishes is a stalled defense bill and a talking point.

So we have arrived at the worst of both worlds: a legislature loud enough to register disapproval, too weak to convert it into constraint. A war proceeds. The body constitutionally charged with declaring war holds a procedural vote about a budget and calls it resistance.

The precedent is the thing to fear, not this war specifically. Precedents outlive the presidents who set them. The next executive — of either party — inherits a settled understanding that you may wage war for months without a vote, that the 60-day clock resets on demand, that Congress will grumble and fund it anyway or grumble and stall the paperwork while the bombs fall on schedule. We are not watching a fight over Iran. We are watching the war power quietly migrate, one unauthorized campaign at a time, from the many to the one. Nobody voted for that either.