Throughline

The weekend strike still has not happened — and Israel is disputing it is “joint”

As of this writing no strike on Iranian energy infrastructure has occurred; a named Israeli official now disputes the premise that Israel is party to the reported plan at all.

CBS News reported late on 31 July, citing multiple American and Israeli officials, that the two governments are preparing strikes on Iranian power plants and refineries “as soon as this weekend” — potentially, per one official, concluding before financial markets open Monday². The report carries on-the-record quotes from President Trump (“We’ll be hitting them very hard… at some point they’re going to say we just can’t take it anymore”), Press Secretary Karoline Leavitt and Pentagon spokesman Sean Parnell, though the plan itself rests on unnamed officials and Trump had not given a final order as of publication. As of roughly 14:00 UTC 1 August the operation “has yet to commence on the president’s final order,” and a named Israeli official told the Washington Examiner that Israel “is unaware of a decision to restart full military operations, nor has been requested of Israel to join any military actions against Iran”⁴⁹ — a direct complication of the “US and Israel” framing most coverage, including this brief’s previous edition, has been running with. Separate the three claims now in play: the reporting on a US plan is well sourced; Israeli participation is, per a named Israeli source, not confirmed on Israel’s own side; and whether any strike happens at all remains unknowable as of writing. This brief will not manufacture a finding about a strike that has not occurred.

The reported plan would mark the war’s first sustained turn against Iran’s domestic energy grid rather than military and IRGC-linked targets, five months into a conflict that opened on 28 February with the killing of Khamenei in a joint US–Israeli operation. It would also land in the same week Iran and Oman are still negotiating over the Strait of Hormuz: Tehran has countered Oman’s Malacca-style consortium proposal with its own plan — a shipping corridor running entirely through Iranian territorial waters, with part of a second route also inside them, giving Iran oversight of both inbound and outbound traffic. Oman is reportedly weighing a three-route compromise⁵. Keep this distinct from the separate, roughly ten-day truce that mediator states floated around 20–21 July — the two proposals are not one initiative, a distinction this brief drew only after conflating them once already.

On 31 July the war’s geography widened again, and this time in two directions from two different services on the same day. The Artesh — Iran’s regular army, not the Revolutionary Guard — struck Ahmad al-Jaber air base in Kuwait, the 27th phase of what Tehran calls Operation Sa’eqeh, framed as retaliation for three civilians killed on Qeshm island, including a two-year-old, during a US strike wave on 29 July³. Separately and simultaneously, the IRGC hit Ali Al Salem air base, reportedly damaging drone hangars and a fuel depot; CENTCOM says two of the missiles aimed at Kuwait fell short or broke apart, and satellite imagery reviewed by one outlet appears to show a damaged shelter⁴. These are two bases, two services, one day — not the single event that generic headlines attributing all of it to “the IRGC” imply, an error this brief made once before and is now watching for a repeat. No Kuwaiti government statement has specifically addressed the 31 July strikes; the only on-record Kuwaiti damage acknowledgment traces to an earlier wave on 18 July and should not be read as confirming anything about this one⁶.

The IRGC’s claim of three F-35s destroyed at Jordan’s Muwaffaq Salti air base is now more firmly contradicted than merely unconfirmed. CENTCOM states explicitly that no US aircraft were destroyed or damaged in the recent Iranian attacks and that every incoming weapon was “either intercepted or failed to reach its intended target”⁵⁰; Jordan’s own armed forces confirm intercepting five missiles with “no casualties or material damage,” without directly engaging the F-35 claim; and Kuwait’s Ministry of Defense confirms it detected and destroyed hostile drones over Kuwaiti airspace on 31 July while denying any successful hit on Ahmad al-Jaber’s hangars, satellite equipment or storage facilities as the IRGC claimed⁵⁰. Three independent, non-Iranian, named sources now actively contradict the Iranian claims rather than merely failing to confirm them. Separately, the drone strike on the US-owned gas tanker Energos Winter off Damietta is now datable to 29 July, not 30th — Egypt’s cabinet has confirmed a drone caused the damage but says no party has claimed responsibility; Iran denies involvement and points instead to a possible Israeli false flag, and the Houthis separately deny it⁷. Islamic Resistance in Iraq — the umbrella for Iran-aligned militias that answered US–Saudi strikes on 28 July with drone attacks of their own — still has an unresolved deadline for Baghdad in the first days of August (sources differ on whether the Hijri conversion lands on the 6th or 7th) and says retaliation against American forces becomes “inevitable” once the Arbaeen pilgrimage concludes; nothing has happened yet, consistent with the deadline still being several days out⁸. US troop casualties across the widened war now stand at 685 wounded cumulatively, after 32 more were reported hurt on 31 July⁵⁰.

A second strike on Kyiv inside 48 hours — and a correction to how this brief described the first one

Russia hit the capital again in the early hours of 1 August; Vol. I No. 3 closed before it happened and wrongly said the night had passed quietly. Behind that, Russian territorial gains remain collapsed by an order of magnitude from a year ago.

This thread opens today, and the reader should not assume familiarity with everything behind it. The war entered its fifth year in February 2022. What follows is the state of play now, not the whole history: Russia holds roughly 19–20 per cent of Ukraine, and for the first time in over a year its rate of advance has slowed to a crawl. ISW’s own count puts June 2026’s territorial gain at 30.42 sq km, against 481.25 sq km in June 2025 — a sixteenfold fall⁹. Ukraine’s independent tracker DeepState gives a different absolute number for the same month, 84 sq km against 556 sq km a year earlier, a roughly sixfold fall¹⁰. The two trackers disagree by nearly 3x on magnitude and agree entirely on direction; publish the range, not a single figure, and keep confidence at Medium rather than High for exactly this reason. For the five weeks to 28 July, ISW recorded no net Russian advance at all, against Ukrainian counterattacks pushing Russia’s 58th Combined Arms Army onto the defensive in western Zaporizhzhia. The main Russian effort remains the axis toward Kostiantynivka and Pokrovsk, with continued pressure at Kupiansk, Lyman, Vovchansk and Sumy.

That backdrop was overtaken overnight. Russia struck Kyiv again in the early hours of 1 August — the capital’s second major ballistic-missile strike in 48 hours, following the multi-city strike of 29–30 July already covered below. Kyiv’s Capital Police, via Interfax-Ukraine, put the toll as of 14:00 local time at nine killed and 33 injured, four of them minors, with 278 property-damage complaints filed across five districts — Darnytskyi worst hit, with seven dead and 14 injured, followed by Solomianskyi, Shevchenkivskyi (where a residential building partially collapsed), Dniprovskyi, Holosiivskyi and Pecherskyi⁴⁷. Early reporting in the first hour or two after the roughly 1:33am local strike understandably understated the toll (some outlets still show three or four dead, the figure current at the time they filed); the Interfax-Ukraine figure, current as of this writing, is the one to use. Kyiv Independent’s own headline — “Kyiv hammered by ballistic missiles as Russia launches 2nd major attack in 48 hours” — independently frames this the same way⁴⁷. President Zelensky said 27 ballistic missiles were fired at the capital and only one was intercepted, underscoring the same interceptor shortage detailed below⁴⁸. Russia’s Ministry of Defense, relayed via a Russian-aligned aggregator rather than a direct TASS statement this brief could independently verify, claims the targets were defence-industrial — a radio-electronics plant, a drone-parts plant, a missile-component plant, a UAV assembly site and a logistics centre — with no mention of residential damage; Moscow has made no acknowledgment of civilian casualties. ISW had not yet published an assessment of this specific strike as of this writing, consistent with its usual publication cadence roughly half a day behind. Vol. I No. 3’s claim that the night had passed with “no confirmed new mass strike” is corrected in the Ledger below.

The binding constraint on Ukraine’s air defence is not money but a finite supply of interceptors. Roughly 95 per cent of Ukraine’s Patriot/PAC-3 stock arrives through NATO’s PURL pipeline, funded to $6.7bn by 29 countries¹⁶; on standard doctrine of roughly two interceptors per incoming ballistic missile, a wave of 70 ballistic missiles requires on the order of 140 rounds. Licensed Ukrainian production, now under signed agreements with both Raytheon and a separate MBDA/Aster-30 route, is running 24–30 months out — longer than the 18–24 months first reported — with first domestic units not expected before late 2027¹⁵. On the US side, $400m in further support is authorised but unobligated, against a Pentagon fiscal-year obligation deadline of 30 September 2026.

Overnight 29–30 July, Russia answered a Ukrainian deep strike on its refineries and a Black Sea Fleet base with a mass strike of 358 targets — 284 drones and 74 missiles, of which ISW’s own breakdown counts only 9 as true ballistic weapons against 61 cruise missiles¹¹. NPR and Kyiv Independent both headlined this a “ballistic missile attack”; on the numbers, ballistic weapons were 9 of 358 munitions, or 12 per cent of the missile mix — the framing overstates the ballistic share, even though the single deadliest hit, a household in Radushne initially reported as six confirmed dead with up to five more feared, was in fact an Iskander ballistic strike¹³. That toll has since resolved, not risen: RFE/RL’s more recent and more authoritative reporting names the family (Voronov) and gives six of ten members killed, four surviving — no one still missing, which reads as better than the “five more feared” framing implied⁵¹. The nationwide death toll for that 29–30 July strike is best supported at eight; NPR’s own article text says “at least eight,” matching ISW and Kyiv Independent, and a “ten” figure circulating in some headlines appears to conflate deaths with the number of regions struck¹². An object that entered Polish airspace near Tarnawa-Kolonia that same night, initially reported only as “probably” a Kh-101, was formally confirmed as one by Poland’s Deputy Defence Minister on 31 July¹⁴: a crater roughly ten metres across, some 95km inside the border, out of about 20 of the night’s roughly 70 missiles tracked heading toward Poland. Moscow has made no public comment on the incursion.

On diplomacy: the 28 July Oval Office meeting between Zelenskyy and Trump ran roughly an hour and covered Patriot co-production licences, joint drone production and reviving talks — no ceasefire, no deadline. A partial “air ceasefire” drafted by US and Ukrainian officials for possible transmission to Moscow remains reported only on unnamed sources via Kyiv Independent; Peskov dismissed it on 27 July as “newspaper reports and nothing more,” and no named official on either side has corroborated it since¹⁷. Adjacent but distinct: Witkoff and Kushner are reportedly expected in Kyiv in the second half of August, possibly around Independence Day on the 24th, for what would be their first visit — but Ukraine’s own ambassador to Washington, Olha Stefanishyna, cautions that “whether the visit ultimately takes place remains to be seen,” so this is scheduling chatter, not ceasefire corroboration. Domestically, Ukraine is still absorbing a defence-ministry rupture this brief had not previously covered: Fedorov was fired as defence minister on 15 July; Yevhen Khmara remains acting minister, with a confirmation vote not expected before mid-August, and has since been relieved of his separate acting-SBU-chief role, now held by Oleksandr Poklad¹⁸. Serhii Koretskyi remains prime minister.

A second resolution nobody is talking about sits in committee

The Senate is in recess until Monday; behind the settled headline vote sits an unresolved second concurrent resolution and 74 nominations still not actually confirmed.

The Senate rejected a discharge motion on S.J.Res. 181 by 49–50 on 30 July (Roll Call 216, 12:28pm), with Collins, Murkowski and Paul voting to discharge and Fetterman against¹⁹. Senator Cassidy voted no this time after backing H.Con.Res. 86 in June, so Republican crossovers shrank from four to three — the opposite of momentum, whatever a narrowing margin might suggest at a glance. H.Con.Res. 86 itself stands as adopted by both chambers with no motion to reconsider²⁰.

What the settled headline vote obscures is a second, distinct vehicle addressing the hostilities that resumed after Trump’s 10 July notification of a fresh 60-day War Powers clock: H.Con.Res. 89 passed the House 214–208 on 23 July and has sat in the Senate Foreign Relations Committee with no further action since²¹. It is live and unresolved, not merely superseded by H.Con.Res. 86, which addresses an earlier phase of the conflict. Separately, the Senate’s 50–47 adoption of S.Res. 817 on 30 July authorised only en bloc consideration of 74 nominations — adoption of a process, not confirmation of the nominees. The Congressional Record’s own nominations-confirmed list for that day shows routine military promotions only; the floor vote on the 74 appears to have slipped past the pre-recess window and now awaits the chamber’s return²².

The Senate adjourned at 3:50pm on 30 July and returns at 3pm Monday, 3 August — confirmed against the Congressional Record Daily Digest itself, not the published legislative calendar, which has been wrong on this point before²³. The same day, both Supreme Court applications touching the mail-voting executive order — 26A124 (Trump v. California) and 26A139 (Alabama v. California, filed by a twelve-state coalition led by Alabama) — have responses due at 4pm before Justice Jackson²⁴. Nothing in either track can move before Monday; both are carried forward unresolved rather than manufactured into a finding.

Blanche’s confirmation stalls over a settlement fund Trump won’t call dead

The filibuster push has ended in a public no from Thune; a newer, quieter fight now threatens the Attorney General nomination itself.

The push to eliminate the legislative filibuster is over in every way that matters: Majority Leader Thune has said publicly that Republicans “are not getting rid of the legislative filibuster” and that it is “not an open question,” and in a 27 July interview he put a version of the private headcount on the record himself — roughly twenty Republican senators visited his office, of whom fifteen said no²⁶. That is Thune relaying a private headcount publicly, not fifteen senators individually going on record; the underlying characterisation, that this was a private consultation rather than a public vote-counting exercise, still holds. No rules-change vote has occurred or is scheduled.

New this week: the confirmation of Todd Blanche as Attorney General is stalled over an “anti-weaponization fund” tied to an IRS-lawsuit settlement that Trump wants used to compensate people he says were “horribly treated” by government under the prior administration. Senators Cornyn and Tillis are withholding support until the Justice Department commits the fund is dead; Trump said on 31 July “I wish it weren’t [dead],” which Tillis read as evidence the fund remains alive²⁵. The White House has floated withdrawing the nomination entirely and waiting for more favourable Senate arithmetic in January 2027. The Senate Judiciary Committee has tentatively slated a possible vote for Tuesday, 5 August — but Blanche’s private offer to formally kill the fund had, as of Friday afternoon, not yet been turned into a formal Justice Department proposal Cornyn and Tillis are waiting on⁵⁴. This is worth watching as a second front on top of the filibuster fight, not a replacement for it.

On the underlying legislative and legal record: H.Con.Res. 113’s engrossed text contains zero occurrences of “election,” “voter” or “citizenship”²⁷, even though the White House’s own Statement of Administration Policy explicitly frames the resolution as enabling the SAVE America Act and “election integrity measures”²⁸ — the framing is the administration’s, sourced to that policy statement, not a provision of the resolution itself. Separately, the First Circuit’s 25 July order denied a stay pending appeal of the injunction against Executive Order 14399 (“Ensuring Citizenship Verification and Integrity in Federal Elections”), a procedural ruling, not a merits holding — and notably observed that “the Government does not defend the legality of the EO” in seeking the stay²⁹. The underlying district-court injunction binds most defendants but explicitly not the President, and reaches only the 23 plaintiff states and DC.

No new settlement exists today — and the sources disagree more, not less, about the one they have

1 August is a Saturday; Brent and WTI futures do not trade. Every “current” quote below is Friday’s session carried forward, and Friday’s own close is now disputed more sharply than 31 July’s was.

Because markets are closed, there is no fresh print to check — but re-checking Friday’s own close across sources shows the disagreement has widened, not narrowed. An earlier same-day snapshot from Trading Economics and OilPrice’s futures page had shown $88.49³⁰; a later Trading Economics read dates a $90.24 Brent print to the 31 July close, up 3.87 per cent⁵⁷ — two reads of the same nominal session, nearly $2 apart; Investing.com shows the same session reversing sharply to $86.90, down 5.21 per cent from a $91.68 prior close³¹. Excluding a confirmed-stale OilPrice.com print (its own contract timestamps trace to mid-June, a live example of the stale-data trap this brief watches for) and an implausible $103.72 WTI figure from Yahoo Finance, the honest band for Friday’s close is roughly $84.56–$91.68 for Brent and $82.45–$84.67 for WTI⁵⁷. No exchange settlement data is reachable for this beat in any circumstance; confidence stays Low, and today specifically, “current price” claims should be read as Friday’s carry-forward, not a same-day figure.

The Hormuz picture is more solid than the single specialist-press claim this brief flagged with caution on 31 July, though that specific claim — the IRGC halting two tankers under a US “air escort” and turning back four more — remains IRGC-sourced and still lacks CENTCOM confirmation³⁴. The underlying severity, however, is now independently corroborated: UKMTO (the UK’s official Maritime Trade Operations body) reported two further attacks near Oman on 31 July — a tanker hit by a projectile northeast of Lima with engine-room damage, and a large explosion witnessed northeast of Khasab — and gCaptain, citing Bloomberg and UKMTO, confirms the Qatari LNG carrier GasLog Shanghai was separately damaged exiting the strait⁵³. Kpler-sourced reporting via The National puts Friday’s Hormuz transit count at roughly ten vessels, against a pre-war average above 100 a day⁵³. The Saudi-led maritime alliance shows no material change since 31 July: it still does not cover the Strait of Hormuz, covering only Bab al-Mandeb, the Red Sea and the Gulf of Aden, with 14 of 51 invited parties having actually signed a non-binding framework³². Red Sea war-risk insurance likewise shows no new movement: Ascot and Navium remain positioned to withdraw cover for Saudi-linked vessels, with southern Red Sea rates above 1 per cent of hull value³³.

The July FOMC minutes are due a day later than this brief previously said

A calendar correction, a re-confirmed QT finding, and three dissenting governors explain themselves in public.

The July FOMC minutes are due 19 August 2026, not 18 August as an earlier edition stated — the Federal Reserve’s own calendar places minutes three weeks after the policy decision, and 29 July plus 21 days lands on a Wednesday, 19 August; the Fed has never released minutes on a Tuesday, which 18 August is³⁵. That correction, made in Vol. I No. 3, is now doubly confirmed: the Fed’s own August 2026 monthly calendar page states directly, “FOMC Minutes… Date: August 19… Meeting of July 28-29”⁵² — that correction was recorded as a typed Ledger entry in Vol. I No. 3 and is not repeated here. Separately, the finding that this brief’s earlier “QT is over” framing was eight months stale is reconfirmed on direct comparison: the 29 July and 29 April implementation notes are word-for-word identical on Treasury-purchase language³⁶,³⁷. Quantitative tightening in fact ended at the October 2025 FOMC meeting; nothing changed on 29 July.

Q2 GDP’s 1.5 per cent advance estimate, against a roughly 2.1 per cent consensus, has no revision yet; the Bureau of Economic Analysis’s second estimate is due 26 August, now added to the calendar³⁸. New colour rather than a correction: all three governors who dissented toward a hike on 29 July — Hammack, Kashkari and Logan — issued public statements on 31 July arguing that persistent supply-shock inflation warrants small, early moves rather than aggressive tightening now³⁹.

No new data this week; the June-payrolls correction stands

June’s weak print looks less dramatic once May’s own revision is read inside the same release.

There is no new labour-market data this week, and the correction already on record is reconfirmed against the Bureau of Labor Statistics’ own release text: June payrolls rose 57,000 against a May figure revised down, in the same release, from 172,000 to 129,000 — a fall of roughly 56 per cent, “somewhat over half,” not the two-thirds an earlier edition calculated by quoting the pre-revision May number⁴⁰. Unemployment stood at 4.2 per cent, participation down 0.3 points to 61.5 per cent. The next release, due 7 August, will show whether June itself is revised again alongside the July print; no credible consensus forecast for July exists, and none is offered here.