The July 28 operation was a limited retaliatory package, at least in its published form. U.S. and Saudi fighter aircraft struck several logistics and weapons sites in Iraq after more than 30 alleged IRGC-directed drone attacks over 72 hours. [E1] Riyadh said its forces acted with U.S. Central Command under the right of self-defense after attacks on Saudi oil facilities. [E2] Neither government disclosed aircraft types, weapons, named targets or a continuing campaign structure, leaving one joint sortie as the outer boundary of the confirmed operation. [E1][E2]
Baghdad’s response exposed the trap beneath the bomb damage. Iraq’s presidency described the PMF as part of the country’s official security institutions and called the strikes a flagrant violation of sovereignty. [E4] The National Security Council simultaneously ordered a plan to stop Iraqi territory from threatening neighboring states and declared that responding to such threats belongs exclusively to Iraq’s constitutional institutions. [E3] The PMF is therefore protected enough that foreign attacks become assaults on the state, yet autonomous enough that Baghdad must promise to stop cross-border attacks launched from the state’s own soil. [E3][E4]
The PMF reported a preliminary toll of 20 fighters killed and 32 wounded. [E5] Neither the American nor Saudi statement supplied a casualty count or answered whether the sites belonged administratively to Iraqi security institutions. [E1][E2] Baghdad and the coalition consequently assigned incompatible legal identities to the same targets: official forces in the Iraqi account, terrorist logistics and weapons sites in the strike account. [E1][E4] That collision lets each side defend its action while leaving the underlying command chain untouched. [E1][E3][E4]
July 28’s clearest novelty is public ownership. CENTCOM placed American and Saudi fighter aircraft in the same sentence, while the Saudi Defense Ministry claimed the operation under its own self-defense rationale. [E1][E2] Those documents establish overt Saudi participation in this strike package; they do not establish a first Saudi kinetic action in Iraq. [E1][E2] Public attribution still changes the political geometry because Baghdad must now answer a named Saudi combatant as well as Washington whenever Iraqi launch networks threaten the kingdom. [E2][E3]
The restrained reading deserves full weight. One strike package, an unpublished target list and no announced standing command mechanism can still amount to a punitive signal designed to force Iraqi enforcement. [E1][E2] Baghdad said it had already been engaging the relevant parties and has now ordered measures to prevent further violations from either direction. [E3] Named arrests, launcher seizures or unit-level discipline would give Riyadh grounds to stop after one acknowledged retaliation and would preserve this episode as coercive diplomacy with bombs attached. [E3]
Iran’s Foreign Ministry condemned the operation as an assault on Iraqi sovereignty and territorial integrity. [E6] The PMF’s casualty announcement supplies a domestic constituency for retaliation even before Baghdad reconciles the national toll. [E5] Those statements increase political pressure without documenting a follow-on attack or a decision by Baghdad to confront the implicated formations. [E5][E6] The next measurable break would be an armed-group claim explicitly tied to July 28, because rhetoric alone does not reveal who still controls the launch chain. [E3][E5][E6]
A second publicly acknowledged Saudi sortie inside Iraq would settle the larger question. It would show that the July 28 coordination was repeatable and that Riyadh had entered a continuing public strike chain beyond its borders. [E1][E2] Without repetition, Baghdad still has room to contain the episode through enforcement, diplomacy and its asserted monopoly over retaliation. [E3] Baghdad can denounce the bomb and promise to police the launchers; until it controls both chains, each answer exposes the other. [E3][E4]