Daily Edition No. 29Thursday, August 13, 2026 · Updated 12:00 Gulf · 𝕏 @mefilesnews · Instagram @mefiles.news · Facebook

Seven files · One region · Zero illusions
@mefilesnews @mefiles.news Facebook
Iran File — Lead

Two Governments Claim the Same Waterway and the Traffic Data Show Neither Is Moving Cargo Through It

Donald Trump posted on Wednesday that the United States has “total control” over the Strait of Hormuz. Mohsen Rezaee, the new secretary of Iran’s Supreme National Security Council, had said the day before that the strait remains closed until Washington accepts Iranian conditions. Kpler counted eight vessels in the strait on Tuesday; Lloyd’s List Intelligence counted 45 transits in the first week of August against 63 the week before. The one figure neither government disputes is how little is moving through it.

Hormuz transits, weekly
Vessel transits per week, 13 July to 9 August 2026, preliminary
33 transitsw/e 19 Jul63 transitsw/e 2 Aug45 transitsw/e 9 Aug
Lloyd's List Intelligence, Strait of Hormuz Brief, 12 August 2026
The blockade ledger, self-reported
Cumulative actions since the blockade was reimposed on 14 July 2026
55
Commercial vessels redirected
3
Non-compliant vessels disabled
2
Vessels boarded
US Central Command statement, 11 August 2026

Trump’s Truth Social post, carried verbatim by Reuters, read: “The U.S.A. has total control over the Strait of Hormuz. I THINK WE WILL KEEP IT!” He added that the naval blockade of Iranian ports is being called, by “everyone,” a “WALL OF STEEL.” Speaking to reporters at Joint Base Andrews on Tuesday evening, he told ABC News: “Iran is going fine, going just absolutely fine. We totally control the Strait of Hormuz,” and added, “I don’t trust Iran. I’m the last person to trust Iran. They’ve lied to me constantly.” The commercial data published the same day describe a waterway that almost nobody is using. Kpler logged eight vessels on Tuesday, the lowest daily total since 5 August, seven of them entering and using the Iranian route, one — a coal carrier — exiting. LSEG logged eleven transits, down from fourteen the previous day. Reuters shipping data put Monday at six vessels against a ten-day average of about eleven. Before Iran moved to close the strait after 28 February, the daily figure ran at roughly 130 to 140 ships. Two commercial providers produced two different counts for the same Tuesday, and both are an order of magnitude below the pre-war norm.

What is being demonstrated on the water is the power to stop traffic, not to move it. CENTCOM announced on Tuesday that a US Navy MH-60 helicopter fired two Hellfire missiles into the engine room of the Panama-flagged M/V Vela Nova in the Gulf of Oman, disabling its steering gear after the crew “ignored repeated warnings from American forces.” The command said the vessel “attempted to transit the Gulf of Oman and violate the US blockade against Iran” and that the blockade “remains in full effect.” No casualties were stated. CENTCOM published its own cumulative ledger since the blockade was reimposed on 14 July: 55 commercial vessels redirected, three non-compliant vessels disabled, two boarded. That is self-reported by the enforcing party; AP, via SCMP, independently characterised the Vela Nova as the third vessel forcibly halted since 14 July, which is consistent. UKMTO logged an incident in the Gulf of Oman involving “a container ship and military forces” without detail. Separately, NewsNation and a Reuters wrap placed a missile strike on a container ship “off Pakistan”; CENTCOM’s own statement says Gulf of Oman. Whether that is one incident or two is not established.

The week’s deaths came 1,500 miles south of Hormuz. Yemen’s Aden-based government says four crew and two members of the rescue force were killed and ten wounded when the Tihamah, an Egyptian-owned, Tanzania-flagged cargo ship carrying food, was struck in the Bab al-Mandeb on Tuesday, in what it described as a double-tap attack; three of the dead crew were Pakistani, one Indonesian. The Houthi-run Saba agency said the group had attacked a Saudi ship carrying military equipment, and named no vessel. The Saudi Center for International Communication did not respond to Reuters' request for comment. UKMTO logged one incident in the strait, a ship hit by an unknown projectile, with no attribution and no casualty figure. Marisks initially put the toll at three. Meanwhile the price is not behaving as the rhetoric implies: Brent October futures traded at $89.53 on Wednesday morning per Al Jazeera, closed roughly flat at $88.84 per Transport Topics, and fell toward $88 on Thursday, snapping a six-session advance. US crude inventories rose 17.4 million barrels last week, the biggest weekly build since early 2023, per the EIA.

Assessment: Both capitals are now describing the same 21 nautical miles as an asset they own, and each definition is a definition of denial. Washington’s control is measured in ships turned back; Tehran’s closure is measured in ships that do not come. Neither is a claim about commerce resuming, which is the only thing a settlement could deliver — and it is why the compensation exchange matters more than the coordinates. Distrust four things today. CENTCOM’s blockade ledger is the enforcing party auditing itself. Aden’s casualty figure rests on two coast guard sources and two military officials via Reuters, and Reuters hedged it as first-of-the-war “if confirmed.” Business Recorder’s Wednesday headline that Washington and Tehran have agreed to extend a ceasefire is explicitly a report of a report with no identifiable originating source; it is the most consequential and least confirmed line in the file. And any framing that the world is burning through stockpiles should be read next to the EIA’s 17.4-million-barrel build, published the same day.

The Cartoon — August 13
HORMUZ TOLL
Total control, and eight ships a day to prove it.”
MEFILES · the cartoon · Kpler counted eight vessels in the strait on the day Trump claimed total control; the pre-war norm was 130–140
8
Vessels tracked in the Strait of Hormuz on Tuesday, against a pre-war norm of 130–140 a day
Kpler, via Reuters, 11 August 2026
55
Commercial ships redirected since the blockade was reimposed on 14 July, self-reported by the enforcing command
US Central Command, as of 11 August 2026
45
Civilians killed in 15 drone strikes on El Obeid and its surroundings, documented in three weeks of June
OHCHR, via UN News, 4 July 2026
30+
Minnesota water systems whose operating technology was targeted in late July, with no formal attribution
Minnesota state officials, via NPR, 12 August 2026
10
Malian soldiers reported killed at San on 9 August; the army has published no toll of its own
AFP, one unnamed security source

Iran File

The regime, the IRGC, the proxies, the strait — read from the Gulf, not from Washington.
Claim Against Count

Trump Declares Total Control of Hormuz on the Day Eight Ships Crossed It

Two commercial trackers put Tuesday’s transits at eight and eleven against a pre-war norm of 130 to 140 a day. Tehran says the strait remains closed on its own terms.

Donald Trump posted on Truth Social on Wednesday 12 August that “The U.S.A. has total control over the Strait of Hormuz. I THINK WE WILL KEEP IT!”, adding that the naval blockade is being called “A WALL OF STEEL,” a phrase he attributed to “everyone.” Reuters carried the post verbatim. Speaking to reporters at Joint Base Andrews the previous evening, he told ABC News: “Iran is going fine, going just absolutely fine. We totally control the Strait of Hormuz,” then added, “I don’t trust Iran. I’m the last person to trust Iran. They’ve lied to me constantly. And at some point, maybe they’ll do something and then they get blown away.” Mohsen Rezaee, the newly appointed secretary of Iran’s Supreme National Security Council, said Tuesday the strait remains closed unless Washington changes its behaviour and accepts Iranian conditions for ending the war.

The traffic data do not settle the argument in either direction. Kpler counted eight vessels in the strait on Tuesday, the lowest daily total since 5 August, with seven of the eight entering on the Iranian route and a single coal carrier exiting. LSEG counted eleven for the same day, down from fourteen. Reuters shipping data had put Monday 10 August at six vessels against a ten-day average of about eleven. The pre-war baseline, before Iran moved to close the waterway after 28 February, was roughly 130 to 140 ships a day. Lloyd’s List Intelligence, in its Strait of Hormuz Brief of 12 August, logged 45 transits for 3–9 August against 63 the week before, and 33 in the week of 13–19 July. Iran’s foreign ministry rejected Trump’s claim on Wednesday without naming him, per CBS News.

Assessment: Control of a waterway is measurable, and both parties are describing the same near-empty channel as proof of their own position. Washington can point to a blockade that is holding; Tehran can point to a strait nobody is using. The discrepancy between Kpler’s eight and LSEG’s eleven for a single day is a reminder that even the neutral instrument here is imprecise at low volumes — with a handful of hulls, one definitional choice moves the figure by a third. Watch the weekly Lloyd’s series rather than the daily counts, and note that its own 5 August brief carried two irreconcilable numbers for the same window. Nobody has published a clean picture.

Two Ships, Two Versions

Aden Says Six Died on an Egyptian Food Carrier; the Houthis Say They Hit a Saudi Arms Ship

The Tihamah strike in Bab al-Mandeb would be the first shipping deaths of the war, but the vessel’s identity is described two incompatible ways and neither side has produced evidence.

Yemen’s Aden-based government says the Tihamah, an Egyptian-owned, Tanzania-flagged small cargo ship carrying food, was struck in the Bab al-Mandeb strait on Tuesday 11 August, killing four crew and two members of the rescue force and wounding ten. Three of the four crew killed were Pakistani nationals and one Indonesian, per CNBC citing the Transport Ministry, which says the Houthis fired three ballistic missiles and describes a second strike on responders. Reuters, carried by NBC News, framed the deaths as the first from a Houthi strike on shipping since the war began on 28 February, and hedged them as unconfirmed; its casualty figure rests on two Yemeni coast guard sources and two military officials. The Houthi-run Saba agency said the group attacked a Saudi ship carrying military equipment, and did not name the vessel. The Saudi Center for International Communication did not respond to a request for comment.

The number moved within hours. CNN’s 11 August live blog cited the marine intelligence group Marisks, “based on initial reports,” describing the ship as Saudi-owned with three dead including two Pakistanis. UKMTO, the Royal Navy-affiliated reporting body, logged one incident in the strait that day: a ship hit by an unknown projectile, no attribution, no casualties. That is the only neutral trace. Semafor’s framing — the first deadly strike in Bab al-Mandeb in a year — uses a different baseline from Reuters' since-28-February line. The Houthis declared a naval blockade against Saudi Arabia in the Red Sea last month, calling it a response to a Saudi siege; Riyadh denies besieging them. On 9 August, Houthi missiles and drones killed seven at the port of al-Makha, and CNN logged an attack on Saudi Aramco’s Jazan refinery the same day.

Assessment: The disagreement is not over whether a ship was hit but over what it was carrying, and that distinction carries the legal weight. An Egyptian-owned food carrier makes the strike an attack on civilian shipping; a Saudi military-equipment vessel makes it a belligerent act in a declared blockade. Both descriptions come from parties to the war, and neither has published manifest, imagery or hull identification. UKMTO’s projectile log confirms only the event. Treat the six-dead figure as an Aden claim relayed by Reuters through four unnamed Yemeni officials, and note how Marisks' opening estimate — Saudi-owned, three dead — was superseded within a day. Same water, same week, same pattern as the Vela Nova.

Self-Reported Enforcement

CENTCOM Puts Two Hellfires Into an Engine Room and Publishes Its Own Blockade Ledger

The M/V Vela Nova is the third vessel disabled since the blockade was reimposed on 14 July. Every figure in the tally comes from the force that produced it.

US Central Command announced on social media that a US Navy MH-60 helicopter fired two Hellfire missiles into the engine room of the Panama-flagged M/V Vela Nova in the Gulf of Oman on Tuesday 11 August, disabling its steering gear. The ship, CENTCOM said, “attempted to transit the Gulf of Oman and violate the US blockade against Iran,” and its crew “ignored repeated warnings from American forces.” The statement concluded: “The ship is no longer transiting to Iran in violation of the US blockade, which remains in full effect.” Casualties were not stated and the crew’s condition has not been independently established. CENTCOM also published a cumulative tally as of 11 August: 55 commercial vessels redirected, three non-compliant vessels disabled, two boarded, since the blockade was reinstated on 14 July. AP, via SCMP, separately characterised the Vela Nova as the third vessel forcibly halted in that period, consistent with CENTCOM’s own count.

UKMTO logged an incident in the Gulf of Oman involving “a container ship and military forces,” without further detail — the only neutral marker. The geography is not clean: NewsNation headlined the same Hellfire strike as hitting a container ship “off Pakistan,” and a Reuters wrap carried by the Detroit News treated a missile attack on a container ship off Pakistan as an incident distinct from the Bab al-Mandeb strike. CENTCOM’s own statement says Gulf of Oman. On the material available, it is not established whether that is one incident described two ways or two separate events, and this desk is not merging them.

Assessment: The tally is the story. Fifty-five redirections against three disablements is a compliance rate the announcing party has every reason to publicise, and no outside body is counting. There is no independent register of vessels turned back in the Gulf of Oman, no manifest audit, and no confirmation that the Vela Nova’s crew survived a missile strike on an engine room. AP’s arithmetic matches CENTCOM’s because AP is counting the same publicly announced disablements. What the number does establish is that Washington is enforcing by publication as much as by force — each announcement is a deterrent aimed at the next charterer, which is cheaper than the next Hellfire.

Sahel Monitor

Mali, Burkina, Niger, the AES bloc, JNIM, and the Russian bargain — security as economics.
Announced or Agreed

Two Secondary Outlets Say the AES Is Harmonising Mining Law, and No Communiqué Has Surfaced

Capmad and the West African Voice Network both report that Mali, Niger and Burkina Faso are aligning mining and energy policy. Neither is a wire, and the primary text behind the reports has not been published.

The claim entered circulation inside 24 hours from two outlets, neither of them a news agency. Capmad ran “AES moves to harmonise mining policies in Mali, Niger and Burkina Faso”; the West African Voice Network ran “AES States Move to Harmonize Energy and Mining Policies” roughly a day earlier. Both are secondary. What is missing is everything that would let a reader judge the story: the primary communiqué, the venue and date of the meeting, which ministers from which of the three capitals attended, and whether what emerged is a signed instrument or a declaration of intent. The verb in both headlines — “moves to” — carries the hedge. The three states between them hold gold, uranium and lithium, which is why the distinction between an announcement and a binding common code is not a technicality.

A primary document from the same window sits unread. Bamada published the communiqué of the Malian Council of Ministers of Wednesday 12 August, held under the effective chairmanship of General of the Army Assimi Goïta, at which measures were adopted; the retrievable text is truncated and its contents are unknown. In Niamey, the state newspaper Le Sahel is serialising an interview with General Abdourahamane Tiani, with parts seven and eight appearing within 48 hours — a state organ giving its head of state length, which is positioning rather than reporting. Kaweru reported Tiani receiving youth and sports ministers meeting in Niamey on 11 August, which on its own says only that the bloc’s ministerial calendar is running.

Assessment: The incentive is legible even if the document is not. Three governments that have each been renegotiating with foreign mining operators gain leverage from being seen to set a common floor, and a harmonisation reported across three jurisdictions does some of that work whether or not anything was signed. That is precisely why the absence of a primary text matters: the announcement is the asset. Read the two reports as evidence that the AES wants this understood as policy, not as evidence that it is. Until the communiqué appears with names, a venue and a legal form attached, treat it as the fourth declaration of intent, not the first common code.

The Toll Nobody Filed

Four Days After San, the Malian Army Has Still Published No Casualty Figure of Its Own

The only number in circulation — at least ten soldiers killed — rests on a single unnamed security source quoted by AFP. Bamako’s communiqué contains no toll at all.

The Malian general staff’s communiqué on the 9 August assault at San, in the Ségou region, described “an attempted attack on the FAMa position at San this Sunday 9 August 2026 at 05:30,” reported a “vigorous FAMa response,” said “the attempt was repelled” and that “the situation is under control.” It gave no figure for losses. AFP, filing Sunday at 17:06 and updating at 19:19, reported at least ten soldiers killed on the account of a security source who also said the camp was “temporarily occupied” before the army retook it; a local source confirmed losses without a number and said troops had retaken the site. JNIM claimed the “total takeover” of the barracks. Four days on, no independent verification of the camp’s status has appeared, and no photographic evidence from either side has surfaced. The 05:30 start time remains the only detail both parties assert.

The larger number in the same AFP copy is the one that has not been contested. On 18 July, at least 50 soldiers were killed in northern Mali when an army convoy was attacked by a coalition of JNIM and the Tuareg separatists of the Front for the Liberation of Azawad — described by AFP as among the deadliest attacks the army has suffered since the conflict began. Commentary layered on the wire by the aggregator PlaneteAfrique holds that the JNIM fuel blockade targets the supply corridors from Senegal and Côte d’Ivoire, through which most of Mali’s fuel transits, and that pump prices had more than doubled by the end of 2025. That is aggregator assertion, without baseline, city or fuel grade, and this desk is not charting it.

Assessment: An army that says an attack was repelled and then declines to say what it cost has made a choice about which half of the ledger it controls. The ten is thin — one unnamed source, provisional — but the silence beside it is not a gap in the record, it is the record. The item worth tracking is not San. It is whether an al-Qaeda affiliate and a Tuareg separatist movement attacking the same convoy on 18 July was a convergence or the start of a standing arrangement. A one-off and an alliance are different wars in the north, and only recurrence will tell them apart.

Sudan Crisis Monitor

SAF versus RSF, the sieges and the famine, the gold economy, and the diplomacy of press releases.
Sudanese gold sent to the UAE
Annual tonnage reported by Sudan's central bank, 2024 against 2025
Gold exports to the UAE22.2 tonnes (2024)8.2 tonnes (2025)
Bloomberg, 2 April 2026, citing data shared by the Sudanese central bank
Four Cities, No Claimant

Drones Hit Khartoum, Atbara, El Damer and El Obeid Before Dawn, and No Force Has Claimed Them

Reuters counted eight drones over El Obeid and two dead, photographed a collapsed mosque wall in Khartoum North, and said explicitly it could not verify who launched the strikes or from where.

Drones struck four army-held cities in the hours before dawn on Wednesday 12 August: an area west of Omdurman and the Bahri district of Khartoum North, Atbara and El Damer on the Nile, and El Obeid in North Kordofan. Reuters correspondents Khalid Abdelaziz and Nafisa Eltahir reported eight drones over El Obeid, army air defences engaging them, and two people killed according to medical sources. The National, published in Abu Dhabi, gave at least two killed and six injured at El Obeid, labelled the figures as media reports it could not immediately confirm, and quoted residents saying the apparent target was a base housing the army’s Fifth Infantry Division. A mosque in the El-Droshab area of Khartoum North was hit; Reuters photographer El Tayeb Siddig recorded children beside a collapsed mosque wall, and AFP photographed residents clearing debris.

AFP described the Khartoum strike as the first after months of calm; Reuters dated the last drone attack on the capital to May. What no outlet produced was a claimant. The Rapid Support Forces did not claim the attacks. The Sudanese army did not immediately comment. Reuters stated it was unable to verify who launched the drones or from where, and The National’s headline used the word “suspected.” The only named-side sourcing in the day’s copy is an unnamed army source quoted by AFP and carried by Asharq Al-Awsat, who said the RSF had attacked the capital, El Obeid, Atbara and El Damer “with a large number of drones, which our anti-aircraft defenses engaged with.” That is an interested party, speaking anonymously, describing its own adversary and its own performance in the same sentence.

Assessment: A force that habitually publicises its long-range reach has said nothing for a full day about the most geographically ambitious strike set in three months. That silence is the story’s centre of gravity, not the tally. Two readings compete. One: the RSF wants the deniability, because hitting a mosque in Bahri and a garrison town simultaneously is harder to sell to the mediators in Jeddah and Addis than to its own base. Two: the attribution is being supplied for it, by an army source whose interest is in demonstrating both aggression received and air defence delivered. Until Wednesday’s operation is claimed, treat the geography as witnessed and the authorship as asserted.

Pause, Then Resumption

The El Obeid Ground Assault Restarts After a Halt Reuters Attributes to International Pressure

Witnesses say the RSF resumed its ground attack on El Obeid on Wednesday, weeks after suspending it. Military sources tell Reuters both armies have massed fresh forces in Kordofan.

Reuters reported that the RSF renewed its ground assault on El Obeid on Wednesday, having halted the attack in recent weeks under what the Arabic wire text describes as international pressure. The same copy records military sources and witnesses saying both the army and the RSF have recently moved additional forces into Kordofan, raising the likelihood of renewed clashes. The sequencing matters: the pause followed the army’s late-July push that drove the RSF west off the 400-kilometre highway linking Khartoum to El Obeid, and Mada Masr reported on 1 August that two days of fighting inside a 300-square-kilometre triangle in North Kordofan returned five towns to the army and dismantled one of the RSF’s principal logistics corridors — the largest ground offensive, it wrote, since Khartoum was retaken last year.

After those losses, RSF commander Mohamed Hamdan Dagalo pledged his men would intensify attacks until they reached Khartoum, a vow the Council on Foreign Relations tracker logs from Sudan Tribune. Nothing in that is an operational fact. What is documented is the cost of the siege on both sides of the ledger. The office of High Commissioner Volker Türk counted 15 drone strikes on El Obeid and surrounding areas in three weeks of June, killing at least 45 civilians. On 2 August a Sudanese army drone struck a traditional court in the Ghurra Zawia area of Kabkabiya locality, North Darfur: the rights group Emergency Lawyers documented at least 37 killed, the figure OCHA cited; UN News relayed OCHA quoting international media at at least 35.

Assessment: Reuters offers two framings that pull in opposite directions and does not choose between them: a force that stopped because outsiders leaned on it, and a force that restarted because it was losing. Read the resumption as pricing rather than strategy. Massad Boulos’s proposals drew an RSF answer on 14 July accepting a three-month truce while refusing to give back captured ground; renewed pressure on El Obeid is the cheapest way to keep that asymmetry standing. The Kabkabiya figures are the discipline check on this desk’s own copy: the deadliest single documented strike of the past fortnight was flown by the army, and its casualty count is already contested by one to two dead.

The Brotherhood Brief

The organization as structure — designations, networks, finances, legal battles. Structure over slogans.
One Outlet, No Calendar

A Single Publication Reports Democrats Will Skip a Brotherhood Hearing, and the Primary Record Is Unchecked

Jewish Insider reported around 6 August that Democrats plan to boycott a Senate Judiciary subcommittee hearing on the Muslim Brotherhood’s US operations. The hearing date, chair, witness list and the on-record status of the boycott are not established in the retrievable record.

The claim entered circulation through one outlet. Jewish Insider published “Democrats plan to boycott Senate Judiciary subcommittee hearing on Muslim Brotherhood,” timestamped approximately 6 August 2026. Its trade-press precursor, Legis1’s “Senate Panel Will Examine Muslim Brotherhood’s U.S. Operations,” ran roughly two weeks earlier, in late July. Between those two lines sits everything a reader would need and does not have: the subcommittee’s name, its chair, the scheduled date, whether the hearing has in fact been held, who was called to testify, which Democrats committed to staying away, and whether any of them said so on the record or whether the boycott was described to a reporter by unnamed aides. Jewish Insider has genuine Capitol Hill sourcing and a declared editorial position on this subject. Both facts matter here, and neither substitutes for the committee’s own hearings calendar.

The legislative backdrop is documented. Two bills seeking a blanket organisational designation remain pending in the 119th Congress: S.2293, the Muslim Brotherhood Terrorist Designation Act of 2025, and H.R.3883, the Muslim Brotherhood Is a Terrorist Organization Act of 2025, both retrievable on Congress.gov. Neither has become law. The executive branch, meanwhile, has already acted on narrower ground. Executive Order 14362, signed in November 2025, designates certain Brotherhood chapters — not the organisation — and on 13 January 2026 the State Department and Treasury designated the Lebanese, Jordanian and Egyptian chapters, according to the Counter Extremism Project’s tracker and the two departments' own releases. A hearing on “US operations” would sit in the gap between those two approaches: chapters abroad already named, a domestic organisational designation still unwritten.

Assessment: The value of a boycott, to whoever chose it, is that it removes the cross-examination without removing the transcript. A hearing with no minority witnesses produces a clean record for the pending bills and nothing to cite against them. That is an argument for treating the boycott claim as consequential and for refusing to treat it as confirmed on one outlet’s word. The test is cheap and public: the committee’s calendar and webcast. Until someone checks it, this is a story about how a Hill event becomes a fact in circulation before it becomes a fact in the record — the same mechanism that carried this week’s Michigan item.

Chapters Abroad, Groups Inside

Washington Designated Three Foreign Chapters While Texas and Florida Move Against Organisations at Home

The federal architecture names Brotherhood chapters overseas. The litigation that will decide what the word covers inside the United States is running in state courts, and the load-bearing documents are still unread.

Executive Order 14362, signed in November 2025, is written against chapters rather than against the Muslim Brotherhood as a single entity — a choice recorded in its own title, “Designation of Certain Muslim Brotherhood Chapters as Foreign Terrorist Organizations and Specially Designated Global Terrorists,” and read the same way by the compliance trackers that law firms publish for clients. Execution came about seven weeks later. On 13 January 2026, according to the Counter Extremism Project’s tracker and the State and Treasury releases of that date, the Lebanese, Jordanian and Egyptian chapters were designated, with State also naming the Lebanese chapter’s leader. The chapter count and the entity count are not the same number, and the second one is not yet established here. A separate Treasury action in late July, “Treasury Disrupts Muslim Brotherhood and Hamas Financial Networks,” carries the individuals, jurisdictions and authorities that would fix it.

The domestic fight is a different instrument. Texas Attorney General Ken Paxton announced suit against the Muslim Brotherhood and the Council on American-Islamic Relations on 5 February 2026, seeking to stop both from operating in the state, following an earlier action involving CAIR announced on 23 December 2025. The state’s petition is public as a PDF on the Attorney General’s own site; its specific factual allegations connecting CAIR to the Brotherhood are the evidentiary spine of every US chapter-mapping claim, and this desk has not read them. In Florida, the ACLU announced on 4 July 2026 that Muslim civil rights nonprofits had sued state officials to prevent a designation the plaintiffs describe as threatening their existence. That characterisation comes from a party to the case. Florida’s own designation order — its scope, its authority, the number of entities it reaches — has not been located.

Governor Ron DeSantis welcomed an earlier lawsuit challenging CAIR’s designation, Florida Phoenix reported on 9 December 2025. The Knight First Amendment Institute set out the constitutional objection on 2 February 2026 under the heading “Red State Governors Are Designating Civil Rights Groups as Terrorists.” What nobody in the retrievable record supplies is a count: how many US states have now issued Brotherhood- or CAIR-related designations, and under which statutory authority each was issued. Without that number, the shape of the domestic campaign is being described from its two loudest cases.

Assessment: Note which venue is doing the legal work. The executive order buys foreign-policy effect at the price of narrowness; it reaches chapters in Beirut, Amman and Cairo and says nothing operative about an American nonprofit. State attorneys general have the opposite trade: no foreign-policy standing, direct reach into domestic organisations, and a much weaker evidentiary threshold to clear before a press release. That asymmetry is why the pending federal bills matter to the litigants and why the Texas petition, not the executive order, is the document to read. Distrust both sides' framing of Florida until the state’s order itself is in hand; right now it is known only through the people suing over it.

Western Media Watch

How NYT, WaPo, FT, BBC and the wires frame the region — what is emphasized, what is omitted, and what the gap reveals.
Hedge Migration

Nine Headlines Describe One Helicopter Strike and Not One of Them Names the Ship

A US MH-60 fired Hellfire missiles at a commercial vessel said to be running the blockade of Iranian ports on or about 11 August. What the US confirmed was the firing; what travelled downstream, unhedged, was the vessel’s intent.

The same reported event arrives in eight or nine different states of attribution. Al Jazeera carries it as “US military fires on cargo vessel it said sought to break Iran blockade” — two hedges, with agency for the claim left with the Pentagon. Yahoo runs that identical wording word for word, indicating a shared wire feed, and then carries two further versions: “US says helicopter fired missiles to disable ship breaking Iran blockade,” in which the hedge has migrated off the contested claim and onto the uncontested one, and “US Military Fires on Ship Attempting to Run Iran Blockade,” in which the hedge is gone and intent is asserted outright. The Hill goes furthest, describing a vessel “in violation of blockade” — an unattributed legal conclusion in the headline. Arutz Sheva, a partisan Israeli outlet, and the trade title Army Recognition both state the breaking of the blockade as fact; Army Recognition adds that this was the third cargo ship disabled.

No outlet in the captured set names the vessel, and the descriptions do not reconcile. The Hill has a Panama-flagged tanker in the Strait of Hormuz. NewsNation has a container ship off Pakistan. NBC News places the US strike in the Gulf of Oman. Either separate incidents are being conflated or outlets are filling in the blanks; a named ship with an IMO number can be checked against transponder data, an unnamed one cannot. The asymmetry also runs inside single mastheads. Al Jazeera’s news article hedges while its own live-blog slug for the following day reads “us-fires-missiles-at-cargo-ship-violating-iran-blockade.” France 24’s displayed headline that day is about Lebanon while its URL asserts “us-military-strikes-ship-violating-blockade-of-iranian-ports.” Live-blog furniture is written fast and edited least, and it is where the Pentagon’s characterisation survives unqualified.

Assessment: The mechanism here is ordinary and therefore worth naming: a wire supplies a hedged line, and every subsequent rewrite for length or punch removes the hedge, because “it said sought to” is four words that a headline slot does not want. The desk could not confirm whether the originating wire is AP or Reuters, and that check matters more than any adjective in the copy. Treat “in violation of” as a claim by a blockading power about a ship it stopped, not a finding. The tell to watch is silent correction: if the tanker becomes a container ship, or Hormuz becomes the Arabian Sea, note whether anyone says so.

Two Registers

Iran’s Six Conditions Become a Long List While Trump’s Compensation Becomes a Term

The same speech act — one state setting a price for negotiation — is rendered as a demand when Tehran makes it and as a condition or a term when Washington does.

The Iranian position on reopening the Strait of Hormuz, transmitted through Omani mediation, is reported as six items. NOTUS titled its origin piece “Iran Releases Set of Demands to Reopen the Strait of Hormuz.” Forbes went to “Iran Issues Trump Long List Of Demands Over Strait Of Hormuz Reopening” — “long list” doing work no numeral does. TIME, on 11 August, made Washington the grammatical subject: “Trump Responds as Iran Says U.S. Must Meet These Six Demands If Strait of Hormuz Is to Reopen.” The Hill the same day chose symmetry, “Trump clashes with Iran over Strait of Hormuz reopening terms,” in which neither party is demanding anything of the other. The Times of Israel live blog on 12 August was alone in granting Tehran the reply position: “Responding to Trump’s claims of control, Iran says Hormuz won’t open until its conditions met.”

Trump’s own precondition — compensation from Iran before talks — appears in this set as a response, a clash or a term, not as a demand. That is the asymmetry: a state requiring payment from a country whose ports it is blockading is described in the register of negotiation; a state requiring conditions before reopening a waterway is described in the register of unreasonableness. Note also what none of these headlines contains: the text. Six items are counted, characterised as long, and responded to, but the captured record shows no outlet reproducing them. Gulf News, reporting from Dubai, supplies the verb the Western set avoids — “Tehran’s oil lifeline chokes” — while covering four further vessels redirected near Hormuz.

Assessment: Lexical asymmetry of this kind is rarely a decision anyone makes; it is inherited from whose statement the desk is standing next to. The practical cost is that readers can now recite that Iran has six demands without having read one of them, which makes the package impossible to judge as reasonable or otherwise — convenient for both capitals. Watch for the first outlet to print the six in full, and note whether the characterisations survive contact with the text. The Gulf News verb is a reminder that regional desks are describing an economic siege while Washington desks describe a stalled deal.

Where the Dead Sit

Six Seafarers Die in the Red Sea and One Desk Files Them Behind Trump’s Rhetoric

Four crew and two rescuers were killed near Bab el-Mandeb on or about 12 August. NBC leads with them; CNBC compresses them to a number and puts deal prospects after the comma.

NBC News ran “Four crew, two rescuers killed in Red Sea attack; U.S. strikes ship in Gulf of Oman” — the dead disaggregated by role, in the first clause, with the American strike second. CNBC ran “Houthi attack kills six in Red Sea; Trump slams Iran as hopes for Hormuz Strait deal dim,” which converts six people into a figure and then subordinates the figure to a president’s language and a negotiation’s odds. Neither headline is false. They are different answers to the question of what a death in a shipping lane is for. The desk could not establish from the captured record whether the attribution to the Houthis rests on a claim of responsibility or on inference by others, and that distinction should be treated as open. As of Thursday the six have roles but no names, no nationalities, no employer and no named vessel.

The same grammatical choice runs through the smaller items. On an Israeli strike in northern Gaza on 12 August, Al Jazeera has “Israeli air strike kills one in northern Gaza” — outcome-led. Haaretz has “IDF Says It Targeted Hamas Commander in Northern Gaza Strike” — intent-led, with the death absent from the headline entirely, and the item filed inside a live blog whose parent slug concerns Trump and Air Force One. In southern Lebanon, Anadolu, the Turkish state agency, reports that Israel “blows up school, strikes religious commemoration site” despite the truce; France 24 reports instead that “Lebanon condemns Israel’s ‘systematic destruction' in south as violation of international law,” placing the destruction inside Beirut’s quotation marks. One outlet reports a demolition; the other reports an allegation of one. The desk has not found a second, non-Turkish-state source for the school.

Assessment: The pattern to hold onto is subordination rather than omission. Gaza and Lebanon are increasingly not absent but nested — sub-entries under Iran-war live blogs, which is a countable ratio and worth tracking per outlet per day. On Lebanon, the honest position is that a single state agency plus a government condemnation is not confirmation; if no Western outlet independently verifies the school within 48 hours, that gap becomes the finding. One caution about this desk’s own work: no article bodies were retrievable in this window, so nothing above is quoted from copy, and the absence of in-window pieces from the largest US and UK mastheads is unverified rather than established.

Israel Press Review

Reading Haaretz, Times of Israel, Ynet and the Hebrew press — what Israeli media and officials are actually saying.
Channel 13 seat projection
Projected Knesset seats, poll aired 12 August 2026; 1,240 respondents, ±3.9%
Yashar (Eisenkot)23 seatsLikud21 seatsB'Yachad (Lapid/Bennett)12 seats
Channel 13, via Times of Israel, 12 August 2026
Chain of Custody

Times of Israel Leads With CIA Doubt About the Israeli Warning That Moved Trump’s Plane

The paper’s 13 August liveblog opens at 06:02 with a Washington Post report that CIA analysts had “low confidence” in Israeli intelligence on an Iranian threat to Air Force One. Nobody involved has said so on the record.

The Times of Israel’s live file for Thursday leads at 06:02 with an aggregation: the Washington Post reporting that CIA analysts told the administration they had low confidence in the Israeli intelligence about an Iranian threat that led Donald Trump to switch aircraft in Turkey. CBS is cited separately as reporting that Defence Secretary Pete Hegseth and several other close aides travelled with Trump on the decoy flight. The threat claim itself entered the record a day earlier from Trump’s own mouth: Haaretz’s live file of 12 August runs under the slug “trump-says-advisers-wanted-him-off-air-force-one-in-turkey-due-to-iranian-threat.” The chain is therefore an Israeli outlet citing an American paper citing unnamed American analysts, assessing intelligence supplied by Israel, about a decision the American president has already described himself. No agency, no Israeli official and no named US official has confirmed any part of the downgrade.

The same liveblog series carries the other half of the week’s Iran file, and it splits the same way. Trump posted that the United States has “total control” over the Strait of Hormuz and that the naval blockade of Iranian ports will continue — the headline claim on the Times of Israel’s 12 August file — telling reporters on 11 August that the strait had been swept for mines. Iran’s answer, per the same file, is that the waterway stays shut until its conditions are met; Foreign Ministry spokesman Esmaeil Baqaei said Iran will not buckle under sanctions, which he said only reduce the chances of a diplomatic resolution. CNN, which counts the eighth round of US sanctions on Iran this year, reports strait traffic “subdued” over the past week and “weakened further.” Al Jazeera’s 12 August piece is built on the same falling transit figures.

Assessment: “Low confidence” is an analytic register, not a debunking; it can attach to intelligence that turns out to be correct. What is new is the placement. An Israeli outlet leading its day with an American doubt about an Israeli product treats Israeli intelligence credibility in Washington as the story, not the threat. Read both halves of the file together and the pattern is a US administration making declaratory claims — the plot, the total control — that the retrievable numbers do not yet carry. Watch for anyone going on the record. Until then this is a briefing war conducted through two capitals' newspapers.

Sixty and the Wall

The Change Bloc Hits Sixty Only With a Party That Missed the Threshold Last Week

Channel 13’s Wednesday poll puts the anti-Netanyahu bloc at 60 seats if Yoaz Hendel and Chili Tropper’s Zionist Home joins it. In the same channel’s poll a week earlier, Zionist Home did not clear the threshold at all.

Channel 13’s survey, aired on the evening of 12 August and relayed by the Times of Israel, has Gadi Eisenkot’s Yashar largest at 23 seats, Likud at 21 and the Lapid–Bennett B’Yachad list at 12, with the change bloc reaching 60 only once Zionist Home — the new right-wing party of Yoaz Hendel and Chili Tropper — is counted inside it. Sample 1,240, margin of error ±3.9 per cent. The same channel’s poll of 5–6 August, written up by Haaretz, had the opposition at 69 with Arab parties and 58 without, on the standing assumption that Jewish parties keep boycotting them; coalition 51, Arab parties 11, Yashar 23, Likud 22 — and Zionist Home below the threshold. Channel 12’s Midgam poll of 3 August had the opposition at 60, Likud and Yashar tied at 23, the coalition at 50, and Arab parties at 10.

Every one of these numbers sits inside its own error bar, and the gap that matters is not between them but between them and Channel 14. JNS notes that the pro-Netanyahu channel’s polls have shown the coalition crossing 60 and reaching as many as 65 — a spread of more than a dozen seats against the Center for Israel Education’s read of late-June and July surveys, which put the Likud, ultra-Orthodox and far-right bloc at 49 to 52, and against Reuters on 29 July reading the accumulated polling as predicting a clear Netanyahu defeat. Haaretz’s live tracker averages Channels 11, 12 and 13 and keeps 14, 15 and Maariv in separate columns. Its bloc labels now read “Netanyahu bloc / Arab parties / Eisenkot bloc.” Polling day is 27 October.

Assessment: The recurring 58-to-60 ceiling is not arithmetic, it is a convention: it exists because Jewish parties will not sit with Arab lists holding ten or eleven seats, and the tables encode that refusal as a separate column. Anyone reporting the ceiling as a mathematical fact is reporting an alliance choice. Two other things to hold onto. Zionist Home’s movement across the threshold, not any shift in Likud, is doing the work between the two Channel 13 runs — a rounding-scale party deciding a bloc. And Haaretz retitling the opposition after Eisenkot rather than Lapid or Bennett is a finding about editorial judgement, published before a vote is cast.

Digital Front Monitor

Cyber operations, information warfare and the infrastructure of control across the region.
The water attacks, by publisher
Competing counts of affected systems and states, late July to 6 August 2026
7
States targeted in one week (NBC, FBI)
12
States targeted (Axios, 4 Aug)
30+
Minnesota water systems hit (NPR)
~1,700
Population of Braham, Minnesota
NBC News (FBI-attributed), Axios, NPR citing Minnesota state officials
Attribution Gap

CISA Named Iran in April; the FBI’s Alert on the Water Attacks Names Nobody

NPR’s 12 August report puts operating technology at more than 30 Minnesota water systems inside a late-July wave and quotes officials who suspect Iran. The two federal documents behind the story do not agree on who did it.

NPR published a reported piece by Jenna McLaughlin at 05:00 on 12 August on cyberattacks against US municipal water systems. In Braham, Minnesota, a town of roughly 1,700 people, a water operator found the pump at the treatment plant had stopped; crews took the plant offline while they investigated and the city asked residents to conserve while it drew on a backup tank. Minnesota state officials told NPR the attack targeted operating technology at more than 30 water systems in the state, Plymouth among them, in late July; the photograph accompanying the piece is dated 30 July in Plymouth. State IT teams characterised the cause to Braham as a “coordinated cyberattack” against industrial technology nationwide. “It’s not Braham in particular that’s being targeted. It’s the internet access points and the vulnerable technology,” mayor Nate George told NPR. “Everything’s connected to the internet in one way or another.” Cybersecurity experts and federal officials suspect Iran, NPR reports — suspect, throughout the piece.

Then the documents. The FBI’s 2026 alert is titled “Malicious Cyber Actors Targeting Water and Wastewater Sector Internet-Facing Programmable Logic Controllers, Causing Operational Disruptions.” It names no state. CISA advisory AA26-097A is titled “Iranian-Affiliated Cyber Actors Exploit Programmable Logic Controllers Across US Critical Infrastructure”; SecurityWeek’s write-up of it names Siemens, Schneider Electric and Rockwell Automation devices as the exposed equipment. NPR reports that the advisory first appeared in April 2026 and was updated days before the late-July attacks began; this desk has not verified that against the page’s revision history. The state count reached the wires as two figures from two publishers: NBC News, citing the FBI, reported municipal water systems in seven states targeted in a single week; Axios on 4 August put the number of states at 12. ABC News carried “at least 12” on anonymous sourcing. The incidents themselves are late July and the first days of August.

Assessment: The reporting is new; the attacks are two weeks old. What has not arrived in the interval is a formal attribution, and the vacuum is being filled backwards — an April advisory that says “Iranian-affiliated” is doing work the Bureau’s own July-August alert language declines to do. Distrust the state count as a trend: seven and twelve come from different publishers days apart, one of them anonymously sourced, and they are not a series. Distrust vendor “spike” figures absent a stated baseline. Note the incentive: a disruption wave nobody has formally owned stays available as pressure at the Oman table, and as a grievance, without either side having to defend it.

Claim Traffic

The Week’s Iranian Cyber File Is a Claim, a Press Release and a January Blackout

Most of what circulated on this beat between Monday and Thursday was an unconfirmed assertion, a vendor distribution or months old. The one non-commercial dataset published this week remains unopened here.

MEMRI’s CJLab reported on or about 7 August that a pro-Iran cyber group claims to have hacked an Israeli organisation. Two layers apply: MEMRI is a partisan outlet with a stated editorial mission, and what it carries is the group’s own claim, not a confirmed breach. On 12 August the Israeli outlet JFeed published a piece on an Iranian AI deepfake video of Donald Trump said to be circulating widely online; this desk found no second outlet carrying it, no named forensic analyst and no stated provenance for the file, and does not treat the Iranian attribution as established. Kaspersky’s 3 August finding that cyberespionage is a growing threat across the Middle East, Türkiye and Africa was distributed as a press release, without a telemetry period or sample size in the material retrieved. SOCRadar’s Iran-Israel dashboard, last updated around 8 August, aggregates claimed attacks; it is a marketing asset and evidence of nothing.

The recirculation is heavier than the news. Amnesty International’s Security Lab research on Pegasus is July 2026 and is still being carried as fresh. The Iranian national blackout cluster — The Conversation on 16 January, Euronews on 14 January, TechPolicy.Press on 5 February, and the argument over the Starlink workaround — is seven months old, and nothing found this week indicates a new shutdown event. The Israeli cyber chief’s surge figures date to 29 June; the Haaretz hack-and-leak investigations to January and May. Against all that, the Internet Society’s Pulse project published within the past week a shutdown tracker and report covering 2019 to 2025, the only non-commercial seven-year series on this beat. This desk has not read its figures and will not print one it has not opened. Also unswept: the Israeli National Cyber Directorate’s statements, Persian and Arabic regional press, Gulf CERT advisories, NetBlocks and IODA telemetry, Citizen Lab and Access Now.

Assessment: The supply problem is structural. When no government will attribute the water-sector wave, the demand for narrative is met by parties with a commercial or political interest in supplying it: security vendors selling detection, threat-intel firms selling dashboards, monitoring groups selling a thesis about Tehran. Each produces material that is publishable and unfalsifiable in the same gesture. The test to apply this week is not whether a claim is plausible but who bears the cost if it is wrong — and for a dashboard entry or a partisan translation, nobody does. The one dataset with no product attached to it is the one that went uncovered.

Watch Tomorrow — The Files' Forward Radar
  1. Iran File: Whether Business Recorder’s “US, Iran agree to extend ceasefire” headline acquires a named originating source, and whether Kpler’s and LSEG’s daily Hormuz counts converge or stay three vessels apart.
  2. Sahel Monitor: Whether a primary AES communiqué on mining and energy harmonisation surfaces naming the venue, date and ministers — and whether the Malian army finally publishes a casualty figure for San, five days on.
  3. Sudan Crisis Monitor: Whether the RSF claims Wednesday’s pre-dawn drone waves on Khartoum, Atbara, El Damer and El Obeid, a force that normally claims its long-range work.
  4. The Brotherhood Brief: Check the Senate Judiciary Committee hearings calendar and webcast for the subcommittee hearing’s date, witness list and whether any Democrat’s absence is on the record rather than sourced to aides.
  5. Western Media Watch: Whether any outlet publishes the disabled vessel’s name and IMO number, and whether the outlets that already wrote “in violation of blockade” correct the tanker-versus-container-ship and Hormuz-versus-off-Pakistan discrepancy openly or silently.
  6. Israel Press Review: Whether the Washington Post’s “low confidence” line on the Israeli threat intelligence draws an on-record response from the CIA, the White House or the Prime Minister’s Office.
  7. Digital Front Monitor: Pull the revision history of CISA advisory AA26-097A to establish whether it was genuinely updated days before the late-July water-sector attacks, and whether the FBI moves from “malicious cyber actors” to naming a state.
The Files in your inbox

Get every morning's edition — free

Seven files, one region, zero illusions. The full daily edition, delivered at dawn Gulf time. No noise. Unsubscribe anytime.

We use MailerLite to send the edition. Confirm via the email you'll receive.  ·  Browse past editions