IRAN Signal Report

Monthly Signal Analysis

1. Overview

Subject Iran

Months compared June 2026 → July 2026

Earlier-month records 216

Later-month records 275

Changes in ongoing flows 4

Newly emerging flows 2

Faded or no-longer-visible flows 1

The clearest overall change was the simultaneous expansion of the Iran–US military exchange and deterioration of the Iran–US agreement track. July also showed broader and more direct tools for controlling Strait of Hormuz shipping, while two distinct new flows formed around the Iran–Ukraine Caspian vessel dispute and repeated protest-linked executions.

2. Changes in Ongoing Flows

Iran–US Military Exchanges Expanded Across Regional Bases and Infrastructure

Signal subtype Expanded

Flow scope Iran actions directed at US military forces, bases, and associated infrastructure in the region.

Earlier-month flow June already contained an active retaliation flow against US forces. Iran recorded attacks on US bases, including the Fifth Fleet headquarters, warnings of wider strikes, and retaliatory drone strikes against US-linked targets.

Later-month flow July retained that military exchange but spread it across a wider set of locations and target types. Records referred to US military facilities and radar systems in Oman, military sites in Jordan, infrastructure in Bahrain, logistics and air-base targets in Kuwait, and US infrastructure in Erbil.

What changed The principal change was breadth. The flow moved beyond recurring attacks and threats against US bases in Gulf states to a wider regional set of military, communications, logistics, radar, technology, and infrastructure targets.

Why this is a signal The expansion appears repeatedly across July rather than in a single incident. The underlying Iran–US military flow remained the same, but its locations and target types became substantially broader.

Representative Structured Actions

Date Subject Action Keywords Entities Co-actors Row ID

---------- ------- ------- ------------------------------------------------------------- -------- --------- ------

2026-06-10 Iran attack US Navy Fifth Fleet headquarters US 60

2026-06-27 Iran launch retaliatory drone strikes; US-linked targets US 196

2026-07-13 Iran say hits US military facilities; radar systems in Oman US 82

2026-07-21 Iran target Amazon infrastructure in Bahrain; US military sites in Jordan US 155

2026-07-26 Iran destroy US infrastructure in Erbil US 213

Confidence High

Strait of Hormuz Control Expanded from Fees and Permits to Regulatory and Direct Vessel-Control Measures

Signal subtype Expanded

Earlier-month flow June showed an established effort to regulate and negotiate Strait of Hormuz access. Actions included maritime fees, transit permits, discussions with Oman, reopening arrangements, a proposed hotline, transit authorization requirements, and competing closure and reopening measures.

Later-month flow July retained the management and negotiation side of the flow while adding more direct regulatory and vessel-control actions. Iran submitted a transit regulation bill, repeatedly referred to unauthorized transit and ship interception, maintained traffic restrictions, and recorded the disabling of oil tankers. Talks with Oman and other states continued alongside these measures.

What changed The flow broadened from administrative arrangements such as fees, permits, and negotiated management to a wider set of legal, enforcement, interception, and physical vessel-control tools.

Why this is a signal July did not merely contain more Hormuz references. The types of actions used within the same shipping-control flow became more diverse and more directly connected to enforcement.

Representative Structured Actions

Date Subject Action Keywords Entities Co-actors Row ID

---------- ------- -------- -------------------------------------------------------- -------- --------- ------

2026-06-18 Iran announce maritime fees for Strait of Hormuz 121

2026-06-19 Iran begin permits to pass through Strait of Hormuz 122

2026-07-15 Iran submit Strait of Hormuz transit regulation bill 101

2026-07-27 Iran say unauthorized Strait of Hormuz transit; ship interception 229

2026-07-31 IRGC claim disabling of oil tankers in Strait of Hormuz 272

Confidence High

Iran–US Agreement Track Shifted from Deal-Building to Compliance Disputes and Conditional Re-engagement

Signal subtype Changed Direction

Earlier-month flow June contained repeated movement toward an agreement. Records included discussion of drafts and amendments, an agreement to end the war and reopen the Strait of Hormuz, a preliminary agreement signed by the Iranian president, technical talks, and a roadmap for a final deal. Signs of strain were also visible late in the month through allegations of violations and threats to halt negotiations.

Later-month flow Early July still contained technical and indirect talks, but the flow increasingly centered on alleged agreement violations, possible abandonment of the ceasefire MoU, suspension of the Islamabad MoU, rejected conditions, and proposals to resume peace talks.

What changed The dominant action pattern moved away from building and signing an agreement toward disputing compliance with that agreement and defining conditions for renewed talks. Negotiations did not disappear, but they were increasingly framed as re-engagement after breakdowns or alleged violations.

Why this is a signal The change is supported by repeated records across July and by a clear shift in action types—from signing, agreeing, and establishing a roadmap toward accusing, suspending, rejecting, and responding to proposals to resume talks. Because signs of strain had already appeared in late June, the shift was developing before July rather than beginning abruptly on July 1.

Representative Structured Actions

Date Subject Action Keywords Entities Co-actors Row ID

---------- ---------------- ---------- ------------------------------------------------------------------ -------- --------- ------

2026-06-17 Iran President sign preliminary agreement to end war US Trump 110

2026-06-22 Iran agree on roadmap for final deal; plan to end military operations in Lebanon US 141

2026-07-15 Iran accuse memorandum of understanding violation US 94

2026-07-18 Iran say Islamabad MoU suspension US 134

2026-07-26 Iran respond to Qatari-Pakistani proposal to resume peace talks US 224

Confidence Medium

Khamenei Funeral Preparations Moved into Funeral Rites and Burial

Signal subtype Became More Concrete

Earlier-month flow June records concerned funeral planning and preparations for Ayatollah Khamenei, including announcements of the planned funeral period and invitations to foreign participants.

Later-month flow July moved into execution of those preparations. Iran prepared and began mass funeral rites, received and thanked foreign delegations attending the funeral, and recorded the burial.

What changed The flow progressed from planning and invitations to the actual funeral process and burial.

Why this is a signal This is a clear stage change within one continuous event flow. The burial is also a consequential milestone that changes the status of the earlier planning flow.

Representative Structured Actions

Date Subject Action Keywords Entities Co-actors Row ID

---------- ---------------- ------ --------------------------------------------- ------------------- --------- ------

2026-06-02 Iran reveal three-day funeral plan for Ayatollah Khamenei 17

2026-06-24 Iran President invite funeral invitation for Ali Khamenei INDIA 162

2026-07-03 Iran begin mass funeral rites for Supreme Leader 24

2026-07-05 Iran thank attendance at Ali Khamenei funeral FOREIGN DELEGATIONS 35

2026-07-10 Iran bury Imam Reza shrine burial 55

Confidence High

3. Newly Emerging Flows

Iran–Ukraine Caspian Vessel Dispute Formed into a Multi-Step Flow

Emergence type Newly Formed Flow

Earlier-month baseline No meaningful Iran–Ukraine Caspian vessel dispute was visible in the June log.

Later-month flow Beginning on July 25, records repeatedly referred to an alleged Ukrainian attack on an Iranian commercial vessel in the Caspian Sea. Iran condemned the attack, summoned Ukraine, issued a threat, demanded restitution, and later raised the issue through the IMO.

What formed A single maritime incident developed into a coherent diplomatic and response flow involving condemnation, diplomatic summons, threatened action, restitution demands, and international maritime engagement.

Why this qualifies as a new flow The July actions recur across several dates and remain tied to the same vessel incident. They therefore form a connected sequence rather than an isolated first appearance.

Representative Structured Actions

Date Subject Action Keywords Entities Co-actors Row ID

---------- ------- -------- --------------------------------------------------- -------- --------- ------

2026-07-25 Iran condemn Ukrainian strike on commercial ship UKRAINE 207

2026-07-25 Iran summon Caspian Sea vessel attack UKRAINE 210

2026-07-26 Iran threaten ship attack in Caspian Sea UKRAINE 225

2026-07-29 Iran demand deadly attack on Iranian vessel; restitution demand UKRAINE 250

2026-07-30 Iran urge Ukrainian attack on Iranian vessel IMO 267

Confidence High

Repeated Protest-Linked Executions Formed a New Domestic Flow

Emergence type Newly Formed Flow

Earlier-month baseline June contained individual judicial actions, including an execution for child sexual assault and a sentence involving a performance without hijab, but no coherent recurring flow of executions linked to anti-government or protest activity was visible.

Later-month flow July contained repeated actions explicitly linked to protests or protest participants, including executions over January protests, execution of a convicted protest participant, an announced execution of anti-government protesters, and a public hanging of protesters.

What formed A repeated sequence of execution-related actions tied specifically to protest activity became visible across the second half of July.

Why this qualifies as a new flow The records recur on several separate dates and concern the same specific type of domestic action. They are therefore more than unrelated executions or a single new case.

Representative Structured Actions

Date Subject Action Keywords Entities Co-actors Row ID

---------- ------- -------- ------------------------------------------------------- -------- --------- ------

2026-07-15 Iran execute execution over January protests 100

2026-07-18 Iran execute execution of convicted protest participant 132

2026-07-19 Iran announce execution of anti-government protesters 138

2026-07-28 Iran hang public execution of protesters; Isfahan Alikhani Square 239

Confidence High

4. Faded or No Longer Visible Flows

Direct Iran–Israel Military Exchange Was No Longer Meaningfully Visible

Signal subtype Disappeared

Flow scope Direct Iranian military actions against Israel, rather than broader diplomatic criticism or Israel-related security statements.

Earlier-month flow June contained a direct military sequence involving warnings directed at Israel, an Iranian retaliatory missile launch, publication of missile-launch footage, and an explicit announcement ending military operations against Israel.

Later-month visibility Israel remained present in July records, including criticism, security allegations, and warnings. However, no comparable recurring flow of direct Iranian missile or other military attacks against Israel was identified in the July log.

What changed The direct military-action branch visible in June was no longer meaningfully visible in July. Iran–Israel-related statements continued, but they did not reproduce the earlier direct attack flow.

Why this is a signal The June flow contained concrete military actions and an explicit end-of-operations milestone. July retained Israel-related records but not a comparable direct operational sequence. This describes visibility in the supplied logs only and does not establish that the underlying conflict definitively ended.

Representative Structured Actions

Date Subject Action Keywords Entities Co-actors Row ID

---------- ------- -------- ----------------------------------------------------------------- -------- --------- ------

2026-06-07 Iran launch missile attack in response to strikes; retaliatory missile launch ISRAEL 40

2026-06-08 Iran release missile launch footage ISRAEL 49

2026-06-08 Iran announce end of military operations against Israel ISRAEL 53

2026-07-02 Iran slam public threat against Ayatollah Khamenei ISRAEL 16

2026-07-30 Iran warn of false-flag operations; drone attack; Damietta Port ISRAEL 268

Confidence Medium

5. Signals at a Glance

Signal Type Change Confidence

------------------------------------ ------------- ---------------------------------------------------------------- ----------

Iran–US military exchanges Ongoing Flow Expanded across locations and target types High

Strait of Hormuz control Ongoing Flow Expanded into regulatory and direct vessel-control measures High

Iran–US agreement track Ongoing Flow Shifted toward compliance disputes and conditional re-engagement Medium

Khamenei funeral process Ongoing Flow Moved from planning to rites and burial High

Iran–Ukraine Caspian vessel dispute Emerging Flow New multi-step dispute formed High

Protest-linked executions Emerging Flow Repeated execution flow formed High

Direct Iran–Israel military exchange Faded Flow No comparable July operational flow identified Medium

6. Method and Limits

Both monthly datasets use the same format. Event flows were constructed from the combined meaning of actions, involved entities, co-actors, keywords, dates, and supporting topic context. `topic` was not treated as a fixed classification system, and signals were identified from changes in coherent event flows rather than simple topic, keyword, country, or record-count differences. Records involving the same country were separated when they concerned different issues or operational purposes. The evidence tables show structured action records rather than source-article citations.

The analysis is limited to the supplied June and July logs. Absence from a monthly log does not prove that an event or policy ended, and differences in source coverage can affect how strongly a flow is visible. Chronological sequence alone was not treated as evidence of causation.