Iran's Islamic Revolutionary Guard Corps said it fired 10 ballistic missiles at Al-Azraq air base in Jordan, a facility used by the United States. Jordan's military said its defenses intercepted eight missiles launched from Iran toward Jordanian territory; falling fragments caused no casualties or material damage. The host record confirms interception and an absence of reported harm. It does not confirm Iran's claim that Al-Azraq was hit. [1][5][6]

The distinction carries forward the discipline of Wednesday's account of renewed US strikes and Iran's 85-installation retaliation claim. That article separated Iran's total from confirmed strikes and interceptions. A companion brief made the rule plainer: a launching force's count is not a count of targets destroyed. Thursday's Jordan record supplies two of those columns: eight interceptions and no reported casualties or damage. It still does not turn Iran's ten-missile target claim into a confirmed hit.

The harder consequence lies farther east. The paper's previous report found Hormuz traffic at 34 of 83 normal daily transits, neither normally open nor wholly closed. On Thursday, QatarEnergy was reported to have paused its planned revival of liquefied-natural-gas production, kept Ras Laffan at minimum operations, and reduced expected vessel dockings after the attack on the Al Rekayyat tanker near Hormuz. The report, carried by Anadolu and attributed to Bloomberg sources, establishes an operating retreat. It does not establish a total Qatari LNG shutdown. [4]

Between the Jordan claim and the Qatari terminal sits a chain of evidence that war coverage too often collapses into a single verb. A force launches. A government detects incoming projectiles. Air defenses intercept some of them. Debris or a warhead may land. A site may be damaged. An operator may then reduce production or dockings because the surrounding route has become unsafe. Each event can be true without proving all the others.

Four different records

Jordan reported eight interceptions and no casualties or material damage. [5][6] Qatar reported incoming Iranian projectiles. [3] Kuwait reported renewed efforts to intercept hostile missile and drone attacks. [2] They concern different host governments, different defensive records, and different questions. Jordan's report supports eight interceptions, not the fate of all 10 missiles Iran claimed. Qatar's supports incoming projectiles. Kuwait's supports continued interception activity. Iran's statement supports only that the Guard claimed a ten-missile attack on the Jordanian base. [1] None proves a hit at Al-Azraq.

This is not caution for its own sake. A launch count describes the attacker's effort. An interception report describes a defender's activity. A damage report describes an effect at a particular place. The three numbers need not match. Writing "Iran struck Al-Azraq" would erase Jordan's no-damage record. Writing "all 10 missiles failed" would outrun a host statement that accounts for eight interceptions.

State-aligned X has an incentive to close that blank in Iran's favor. A named base and a precise missile count look like a receipt even when both come from the party making the claim. Rival accounts can make the opposite error, treating any interception announcement as evidence that every projectile was defeated and no operational effect followed. Mainstream live coverage, meanwhile, can relay each alert as it arrives without assembling the hierarchy of what each alert proves. The result is a battlefield made from verbs: fired, targeted, intercepted, hit. The evidence does not allow them to be used interchangeably.

Jordan's confirmation is narrower than Iran's claim. The paper can report eight intercepted missiles and the absence of reported casualties or material damage because the host record says so. [5][6] It can report Qatar's incoming-projectile notice and Kuwait's renewed interception report because those host records exist. [2][3] It cannot use any of them to establish that Al-Azraq was hit or to account for the two-missile difference between Iran's launch claim and Jordan's interception count.

The terminal supplies the physical receipt

Ras Laffan offers a different kind of evidence. QatarEnergy's reported response concerns what an operator did after a tanker attack: it paused a planned production revival, held the complex at minimum operations, and reduced expected vessel dockings. [4] Those measures do not say which missile landed where. They show how insecurity translated into output and port activity.

The wording matters. "Minimum operations" means activity continued at a reduced level. It cannot honestly be rewritten as "shut down." A paused revival means an intended increase did not proceed; it is not the same as a new fall from full production to zero. Reduced expected dockings mean fewer vessel calls were anticipated; the research does not supply a count that would justify a percentage. The Al Rekayyat attack changed operating behavior, but the available report does not quantify total output lost or declare all Qatari LNG unavailable. [4]

That bounded record is more useful than a dramatic adjective. Hormuz can carry ships while remaining far from ordinary passage. Ras Laffan can produce LNG while remaining at minimum operations. Qatar can report incoming projectiles without proving damage. Kuwait can report interceptions without proving every threat was destroyed. Jordan can report eight interceptions and no damage without proving what happened to every missile Iran claimed. The region's condition is not captured by open or closed, victory or failure. It is captured by separate operating records.

Thursday's LNG response also answers one of the questions left by the prior transit article. That piece said traffic, insurer guidance, and port notices were the test of whether the strait was recovering. A producer's decision to reduce dockings and suspend a revival is not a full transit count, an insurer notice, or a port circular. It is still a direct operational consequence on the same chain. Ships need a safe route and a working berth. An LNG train producing at minimum output cannot be treated as ordinary commerce merely because it has not reached zero.

What remains unknown

The missing entries are substantial. Jordan's record does not establish whether it detected all 10 missiles Iran said it fired, what happened to the two not covered by its interception count, or whether any reached Al-Azraq; it reports no casualties or material damage. [5][6] The record does not establish how many projectiles Qatar detected or how many Kuwait intercepted in this renewed round. It does not quantify Ras Laffan's minimum output or the number of dockings canceled or deferred.

Those blanks prevent a clean scorecard. They do not prevent a precise article. The ten-missile target claim is Iran's. The eight-interception and no-damage report is Jordan's. The incoming-projectile report is Qatar's. The renewed interception report is Kuwait's. The operating response is attributed to QatarEnergy through reporting carried by Anadolu. [1][2][3][4][5][6] The facts become more reliable, not less consequential, when kept in their proper columns.

This newspaper has spent the war refusing two seductive substitutions. The first turns diplomatic language into operating reality. The second turns a military announcement into a verified result. July 9 joins the two. Iran announced a hit in Jordan; the host record confirms eight interceptions and no reported damage instead. [5][6] Qatar's LNG system supplied an operating result that requires no claim of a missile hit at the terminal: minimum production, a paused revival, and fewer expected dockings after a tanker attack. [4]

One story has a host receipt that stops short of confirming Iran's claimed hit. The other has a dock schedule and an output setting. The Gulf can verify both bounded records without pretending either proves more than it says.

-- YOSEF STERN, Jerusalem