Key Events

Why it mattersThe modern Gulf state system and its oldest live dispute date from the same months. The islands question has outlasted the 1979 revolution, the Iran–Iraq war, the 2016 rupture in relations and the 2026 war, which is why this module treats the region as a structure rather than as a consequence of the present conflict.

Why it mattersIt created both the institutional structure this module authors as offices — a Supreme Leader above a president — and the adversarial relationships with the United States and Israel that have stood since. Neither began in 2026.

Why it mattersThis is the direct precedent for 2026 and not merely an analogy: attacks on merchant shipping, insurance and reflagging as instruments, and outside navies in the Gulf were all established here. The Security Council's own 2026 resolution recalls its 1984 response to it.

Why it mattersThe institution the Gulf states built for exactly the circumstances of 2026 was created in response to the last time those circumstances arose. Its Joint Defence Agreement, and the question of whether it has produced collective capability, is the through-line from this event to the present.

Why it mattersVigil authors this because the Council itself reached back to it: Resolution 2817 of March 2026 explicitly recalls Resolution 552. The 2026 maritime crisis is being answered with the legal instrument written for the 1980s one.

Why it mattersThe basing arrangements this module authors as relationships — Bahrain, Qatar, Kuwait — date from this period. It is why an external power is a core actor in Gulf security rather than a visitor to it.

Why it mattersEverything in the module's nuclear file is downstream of this instrument, including the snapback mechanism that returned United Nations sanctions in 2025 and the verification arrangements whose collapse is now the central unknown.

Why it mattersIt began the sequence that ended with the 2025 snapback, and it is the origin of the concentration of Iranian exports on a single customer that the module authors as an economic dependency.

Why it mattersThe precedent that Gulf energy infrastructure is reachable, and that a single processing node can interrupt a national export system. Abqaiq is the origin point of the east–west pipeline this module authors as the region's principal Hormuz alternative.

Why it mattersIt is why Israeli air-defence systems could be deployed to Emirati territory during a war with Iran six years later. The security relationship the module authors between the UAE and Israel begins here.

Why it mattersThe largest change in the Gulf's diplomatic architecture in a decade, and the baseline the 2026 war has tested. Neither party has announced a severance since, which is why the module records the relationship as uncertain rather than ended.

Why it mattersThe first act of a campaign that ran for almost two years and is a separate, concluded episode — not the opening of the 2026 Red Sea front, which is fought against Saudi Arabia. It established that a movement in Yemen could set the terms of passage through Bab el-Mandeb for a whole category of shipping by declaring it a target, and it is why Israel's own Red Sea port lost most of its traffic within weeks. The crew was held until 22 January 2025.

Why it mattersIt split the campaign in two. American shipping and warships left the target set; Israel-linked shipping and Israel itself stayed in it — which is why the campaign could resume against ships calling at Israeli ports two months later without breaching anything the United States had agreed, and why Eilat's exposure outlasted the American war on the movement.

Why it mattersA separate, concluded conflict — not the opening of the present one. It established direct state-on-state exchange as the pattern, and it is the point after which the International Atomic Energy Agency lost access to the sites it had been verifying.

Why it mattersA process rather than a relationship: the three states acted as a grouping convened for this mechanism, which is why the module authors no E3 actor and carries the snapback as chronology instead.

Why it mattersThe legal architecture the whole Iranian economic file now sits inside, and it entered force five months before the war began. Iran, China and Russia have described the process as legally flawed.

Why it mattersThe deepest formal security relationship between an external power and a Gulf state in the module, signed three months before the war opened. What it obliges either party to do in a regional war is what the unpublished text would settle.

Why it mattersThe declaration changed the legal and political contest over the strait. What actually stopped commercial traffic over the following week was the withdrawal of war-risk cover, which is why this module keeps legal, physical and commercial access as three separate questions.

Why it mattersThe office the module authors as Iran's head of state changed hands by violence in the middle of a war. Reporting indicates many of the senior posts vacated at the same time remain unfilled, which is a fact about the Iranian state's capacity rather than about any individual.

Why it mattersA United States-acknowledged responsibility rather than an Iranian allegation, and the module records it as such. It is the clearest single measure of the civilian cost of the opening campaign and is carried without operational or graphic detail.

Why it mattersThe physical opening of the current campaign, and the date from which every other 2026 record in this module is measured. No authorisation for the use of military force was obtained, and measures directing the removal of United States forces were rejected in both congressional chambers in March.

Why it mattersThe clearest marker of the Emirati shift from hedging to hardening, and it separates the UAE response from the Saudi, Qatari and Omani ones. The module records it as a suspension of relations rather than a termination.

Why it mattersATTRIBUTION IS DISPUTED AND REMAINS SO. Saudi Arabia attributed the attack to Iran; Iranian officials publicly denied targeting Gulf energy facilities. On the same day Iran's defence ministry reported attacks on Qatari facilities and the IRGC claimed a tanker strike — so Iranian messaging was internally inconsistent rather than uniformly denying. Vigil publishes the physical event and both positions and adjudicates neither.

Why it mattersAn aggregate rather than seven separate records, because the analytically significant fact is the pattern: energy and shipping infrastructure across four states, including Oman, which the Security Council resolution nine days later names among the attacked. Iran's defence ministry reported some of these attacks while Iranian officials denied targeting Gulf energy facilities.

Why it mattersThis, and not the closure declaration, is what stopped commercial traffic. The strait remained legally open and physically passable and stopped carrying trade anyway — the module's central analytical finding, and the reason it models commercial access as a question of its own.

Why it mattersIran's ultimate decision-making office changed hands nine days into a war. Accounts differ on whether he assumed office on 8 or 9 March, so the office record states the month rather than a day; this event carries the selection date the source gives, which is a different fact from the date the holding began.

Why it mattersIt is not a Chapter VII resolution and it creates no sanctions or measures of any kind — a condemnation and a set of demands. Its recall of Resolution 552 is the Council answering a 2026 maritime crisis with the instrument it wrote for the 1980s one.

Why it mattersQatar has no LNG route to market that avoids the Strait of Hormuz, so a multi-year capacity loss here cannot be routed around or replaced at short notice. It transmits as widened price spreads between the American, European and Asian gas markets rather than as physical shortage.

Why it mattersThe Council was united on condemning attacks on the Gulf states in March and split on shipping in April. It is the clearest available measure of how far the external powers diverge on this system, and the reason the module treats China and Russia as strategic actors with their own positions rather than as Iranian backers.

Why it mattersTHE CLEAREST DOCUMENTED RESTRAINT ORDER OF THE WAR, AND WHAT IT DOES AND DOES NOT SHOW. The instruction was issued in the Supreme Leader's name and addressed to every branch at once, through the national security council rather than through a military headquarters — which documents where the authority to stop the war sat, and says nothing about how the order travelled through the forces below. No separate acknowledgement by the Revolutionary Guard or the Artesh is on the record. Gulf states reported Iranian launches on the day itself; when each was fired relative to the order is not established, so they are not read as non-compliance. The pause is a separate arrangement from the memorandum of understanding signed in June, which this module records on its own date.

Why it mattersTHE ONE FOREIGN MILITARY DEPLOYMENT TO SAUDI ARABIA IN THIS WAR THAT A GOVERNMENT HAS ANNOUNCED, and it was made four months before the Makkah agreement existed, under a bilateral treaty. The ministry stated a purpose of coordination and readiness; no combat role is stated in the announcement and none is authored here. Any later claim that Pakistani forces in the kingdom demonstrate the trilateral agreement's activation has to reckon with this record first: the force was already there, and the instrument it came under was a different one.

Why it mattersA military measure, and deliberately not authored as a sanctions instrument: the restriction on who may buy Iranian oil and the physical prevention of its movement are separate mechanisms with separate remedies. The CENTCOM figures are self-reported and carried as such.

Why it mattersThe regulator's own assessment, and the point at which the access constraint became a documented humanitarian condition. Vigil publishes the mine warning as a stated condition and publishes no location, extent or clearance information of any kind.

Why it mattersTwo facts about Gulf cohesion on one day: the members meeting collectively about the war, and one of them leaving the institution that coordinates their principal export. The stated rationale was national interest and production ambition rather than the war, and the module records the coincidence of dates without asserting a causal link.

Why it mattersA change to the LEGAL contest over the strait that altered neither physical passage nor commercial access, which is exactly why the module keeps the three separate. Iran has also stated it is not party to the 1982 Law of the Sea Convention, so the dispute is not a simple division between Iran and the West: its own corridor partner rejects the claim.

Why it mattersThe disruption deepened for four months rather than being absorbed by adjustment, which is what distinguishes a structural access failure from a supply interruption. These figures measure production made unavailable — not exports, not capacity, and not a permanent loss.

Why it mattersThe parties' own term is memorandum of understanding. Vigil does not relabel it a ceasefire, an armistice or a peace agreement, because none of the sources does. Its fourteen reported points have not been read in an official text and are not authored.

Why it mattersThe memorandum collapsed six weeks before it formally expired. Recording the collapse and the expiry as separate events is what keeps the chronology honest: an arrangement that stopped operating in July and lapsed in August did two different things.

Why it mattersThe date this module's Red Sea front reopened. Everything that follows on the Saudi–Yemeni axis — the blockade declaration, the strike exchanges of August and September, the coastal advance to Bab el-Mandeb — runs from here, and it begins as a consequence of the Iranian leadership succession rather than of anything inside Yemen.

Why it mattersSaudi Arabia's east–west pipeline exists to move oil away from a contested strait and delivers it to a second one. From this point the region's principal Hormuz alternative depends on a waterway that is itself contested, which is why the module treats the two straits as one coupled system.

Why it mattersA SEPARATE ARRANGEMENT FROM THE MAKKAH AGREEMENT, declared eight days before it, with a different membership, a different geography and a named commander. Türkiye and Pakistan belong to both. The module authors the two apart because collapsing them would attribute maritime activity to a collective-defence agreement that has not been shown to have ordered any.

Why it mattersThe most significant new security arrangement a Gulf state entered during the war was made outside the Gulf Cooperation Council, in the same month the Council's own leaders called for faster military integration. TWO THINGS ARE TRUE AT ONCE AND ARE KEPT APART HERE: the three governments' own summit statement says that an armed attack against any one of the three shall be regarded as an attack against them all, so the collective-defence undertaking is official rather than secondary-only; and the agreement text itself has not been published, so what follows from that undertaking — what response is owed, by whom, decided how — is not established by any source read.

Why it mattersTWO DIFFERENT FACTS IN ONE DECREE. The appointments are personnel change: the post of chief of the General Staff had been without a published holder since its incumbent was killed on 28 February, while the Guard's commander was named the day after his predecessor's death and is here confirmed by decree. The merger instruction is institutional change: it shows that the General Staff and the Central Headquarters were still separate bodies five months into the war, and that the system's own leadership chose to alter the command structure during it. Neither the form of the merged body nor whether the integration is complete is published, and no new commander of the Central Headquarters is named.

Why it mattersAutomatic expiry rather than termination, and six weeks after the arrangement had already been declared over. From this date the module's account of the war carries no operative agreement of any kind.

Why it mattersTHE AGREEMENT ACQUIRED INSTITUTIONS BEFORE IT ACQUIRED A TESTED PROCEDURE. This is the record that makes "three leaders signed a declaration" an inadequate description of the Makkah agreement — and it is also the record that shows what the joint statement does not contain: no consultation procedure, no threshold, no command arrangement, no allocation of forces. Eight days later came the first attacks on a signatory's territory, and there was no published mechanism to run them through.

Why it mattersONE PHYSICAL EXCHANGE, MULTIPLE CONTESTED CLAIMS, and the module records them as such. The IRGC claimed aircraft destroyed and a large number of United States personnel killed in Jordan; two United States officials told Reuters that initial assessments showed no American casualties, and a United States official told Al Jazeera there were no injuries or significant damage at the Marine facility. Jordan's military stated it intercepted ten of thirteen ballistic missiles that entered its airspace, with the remainder falling on open ground. Iranian authorities reported civilian deaths from the United States strikes. Al Jazeera stated it could not verify Iranian claims. No casualty figure from any party is carried here as established.

Why it mattersTHE FIRST ARMED ATTACK ON A MAKKAH SIGNATORY'S TERRITORY SINCE THE AGREEMENT WAS SIGNED, and reported as the heaviest since this round of the Saudi–Houthi war reopened in July rather than as the heaviest of the whole war — and the occasion on which the agreement's response machinery would have been visible had any been published. What followed from the other two signatories was a Turkish condemnation that did not mention the agreement and a Pakistani statement that no military response was under discussion. The casualty figure is Saudi Arabia's own; the strike count is the Houthi movement's claim and is not established. What the continuation added is reach, not a new kind of act: fire directed at Riyadh, confirmed by the coalition as intercepted, and at Yanbu, the terminal the Hormuz alternative delivers to. Every Saudi account in the continuation is of interceptions, and no damage at Yanbu or in Riyadh has been confirmed by any party other than the movement; the movement's claims of hits are carried as claims. The Mecca account is disputed between the coalition and the movement and Vigil adopts neither version. The Medina attribution is the coalition's and the movement denies it; Vigil records both. The Riyadh fire of 3 October is a fire with a disputed claim attached, not an established strike.

Why it mattersTHE FILE HAS MOVED FROM A TECHNICAL BODY TO A POLITICAL ONE, AND THAT IS THE WHOLE OF WHAT HAPPENED. A referral changes the forum, not the facts: the Agency's position on 9 September is the same position it held on 4 June, and nothing in the resolution restores access, obtains an inspection or establishes anything about the programme. It matters for two reasons that have nothing to do with enrichment. First, it exhausts the Agency's own escalation ladder — after a referral the Board has no further step, so the question of what to do about Iranian non-cooperation now belongs to a Council on which two permanent members can veto any measure, which is why the move is widely read as declaratory. Second, it removes the last procedural reason for Tehran to keep the Agency's file open as a bargaining position, and the module's nuclear observable — an inspection actually carried out at a declared site other than Bushehr — becomes harder to meet, not easier. What this record does not do is grade Iran's conduct. The absence of verification establishes neither that enrichment continued nor that it stopped, in this week as in every week since February, and the referral does not change that symmetry.

Why it mattersTHE HORMUZ ALTERNATIVE ITSELF WAS ATTACKED, on the same morning the port at the head of the Red Sea outlet it delivers to changed hands. The pipeline exists to move Saudi crude away from one contested strait; within forty-eight hours the route was under pressure at its middle and at its mouth. This was also the first attack on Saudi territory in this war launched from Iraq, and Riyadh's decision not to respond is a fact about Saudi choice, not about Saudi capability. The shutdown is what the Ministry of Energy announced; how long the line stays down, and what was actually damaged, are not established here.

Why it mattersPHYSICAL ACCESS TO THE STRAIT CHANGED HANDS; PASSAGE THROUGH IT DID NOT CLOSE, and this module keeps the two apart. Bab el-Mandeb has the Djiboutian and Eritrean shores opposite, and the wider of its two channels lies west of Perim. What the advance establishes is presence on the Yemeni side of the outlet that Saudi Arabia's east–west pipeline delivers to. What it does not establish is interdiction: no independently observed interference with non-Saudi shipping from the new positions has been read, and reporting of a sharp fall in transits on 10 September is a change in what shipowners chose to do, not evidence of an act against a vessel. FOUR THINGS STAY APART IN THIS RECORD: a stated intention to retake the ground, which government field commanders have expressed; operational preparation, which the vice chairman's regroup order is; a counteroffensive, which has not been reported; and a territorial reversal, of which none is established.

Why it mattersTHE 13 SEPTEMBER BRIEF NAMED THIS MEETING AS THE LIVE TEST OF THE COMMERCIAL CONDITION, AND THE TEST DID NOT RUN. That is the finding, and it is worth more than a communiqué would have been, because the reason for the postponement is itself the substance: the obstacle is not whether ships can pass but whose legal account of the water an instrument would endorse. A bilateral corridor scheme registered at the IMO would be the first document since March to describe how the strait is used, and a Gulf state that did not draft it reads that as a status quo being written down. What the module records is therefore a stage not reached, not a process failing — a postponement with no date is not a collapse, and Iran's own statement that this would not reopen the strait removes the reading that the meeting was about restoring traffic in the first place. Nothing here touches the commercial condition: no cover was written, no rate was taken up, and the observable remains what it was.

Why it mattersA CONGRESSIONAL NOTIFICATION IS THE BEGINNING OF A PROCESS, NOT A SALE, and the distinction decides what this record can carry. What is established is that the executive has committed itself publicly to a transfer no Arab state has been offered before, in the week after an attack on Saudi territory that no security arrangement answered — which is a statement about the direction of the defence relationship whatever Congress does next. What is not established is that Saudi Arabia will receive the aircraft: the review period is real, the qualitative-military-edge finding is a statutory requirement, and sales of this class have been notified and then not completed before. The module keeps this apart from the Makkah Agreement deliberately. One is a bilateral supply relationship with the state that has underwritten Gulf security for fifty years; the other is a collective-defence undertaking outside it. A week that produced movement on the first and none on the second is evidence about which of the two is load-bearing, and that is the only inference drawn here.

Why it mattersTHE BYPASS ARITHMETIC INVERTED. For six months the honest answer to "what happens if Hormuz stays shut" was that Saudi crude has a pipeline to the Red Sea; since 10 September the answer has been that it does not, and the substitute is the strait itself. That is not a reopening and it must not be read as one — the commercial market that closed the strait in March has not moved, no war-risk cover is being written on terms charterers take up, and what is moving is state crude on escorted short legs with a warship alongside, which is the opposite of a market judgment about safety. Three things follow and are worth keeping apart. A bypass that can be interrupted is a thinner thing than a route, and this is what that looks like in practice. A route that depends on a foreign navy's escort is a route with a political dependency written into it, and the module has no basis for saying how long that escort holds. And a seventy per cent fall in total exports says that most of what the pipeline carried has not been rerouted at all but shut in — which is the number that matters and the one nobody publishes.

Why it mattersTHE BYPASS IS BACK IN SERVICE AT A RATE NOBODY HAS STATED. Twelve days after the Hormuz alternative was cut at its middle, oil is reported moving west again, and the first Yanbu cargo since the attack is scheduled — which reopens, at the margin, the Red Sea route this module treats as the strait's principal alternative. Three things are not established and are held apart here. The rate: "low" is the only description from the sources, and the percentages and timetables are estimates by people who did not operate the line. The export volume: even before the attack, terminal throughput at Yanbu and domestic refinery offtake, not the pipeline, set how much could load, and a partial restart leaves both constraints where they were. And the durability: the restart moved nothing on the other side of the ledger — Yanbu remained a declared Houthi target through the same week, with every Saudi account of those attacks one of interception. What changed is that the escorted Hormuz route is no longer the only way out for Saudi crude; what did not change is that no operator has said anything at all.

Why it mattersTHE FIRST CONSULTATION HELD UNDER THE AGREEMENT, AND IT IS A CONSULTATION, NOT AN ACTIVATION. For seven weeks the Makkah Agreement had a published undertaking and institutions on paper, and through the heaviest attacks on Saudi territory of this round it produced statements of commitment only; on 16 September Turkish and Pakistani officials said no Saudi request had been received. This week it produced its first act in its own name: the three chiefs met, in the capital of the state under attack, expressly to examine assistance under the agreement, and a Secretary General was named. That is real movement on the ladder from undertaking to mechanism and it is recorded as such. What it is not is the collective-defence clause operating. The ministers grounded Saudi action in Article 51, which is a state's own right rather than the agreement's; the chiefs named areas of cooperation, not a contribution; and nothing published says what response the agreement owes, who decides it or on what threshold. Pakistani reporting that lists possible next steps — early warning, air-defence specialists, liaison officers, joint planning cells — is analysis, not an agreed programme. The observable that separates a forum from a mechanism is unchanged: a contribution named as made under the agreement, or a formal invocation.

Why it mattersPLANNING BECAME AN ACKNOWLEDGED OPERATION, AND THE SHORE IS CONTESTED, NOT RETAKEN. On 2 October the module recorded a Saudi offensive reported in planning, with no date, and kept planning apart from a campaign. That line is now crossed: a party announced the operation with a stated objective, and the coalition acknowledged an air campaign in support and named the strait as a task. This is the first time since the July blockade that the shore Saudi Arabia's Red Sea outlet depends on is being contested by force rather than absorbed. What the record does not establish is the result. Every territorial claim is a party's, the movement denies them, and the government's own sources said on 10 October that the waterway was not secured. Target counts are the coalition's and are not established. The offensive is an air and ground operation on the shore, not a naval operation in the strait's approaches, and no interference with shipping in either direction is recorded here.

Why it mattersTHE FIRST DECISION TAKEN IN THE AGREEMENT'S OWN NAME, AND IT IS A DECISION, NOT A DEMONSTRATED CONTRIBUTION. Until 5 October the agreement had produced statements, institutions on paper and one consultation of chiefs of staff. This statement commits the three governments, under the agreement, to provide forces and capabilities for rapid deployment in the kingdom, and refers to approved arrangements for doing so. What it does not do is name a force, a size, a mission, a command or a date, cite an invocation of the collective-defence clause, or publish the arrangements it refers to. Pakistani forces were in the kingdom before the agreement existed, under the 2025 bilateral instrument, so their presence alone does not show a contribution under this one. No source read attributes a specific deployment to the decision.