DiplomaticExternal military supportMilitary reorganisationDefence industryActive
Does the Makkah Agreement become an operational defence mechanism?
A published procedure, an activated Secretariat, or a contribution named as made under the Agreement — not a bilateral deployment or a maritime-coalition act.
- Opened
- Last reviewed
- Status as of
- Reviews
- 10 since 2026-09-12
- Confidence
- Moderate confidence
Iran and the Gulf: Maritime Access, Energy Systems and Regional Security
A Watch question is not a forecast. It names the evidence that would change an assessment and records what each review found — including the reviews that found nothing moved.
Where it stands
Standing assessment
Current assessment
Moderate confidenceAs of
A commitment with institutions, a published text and no demonstrated procedure.
The text sent to the Turkish parliament in October 2026 obliges immediate assistance against an armed attack by another country or group of countries, each party setting the extent of its support, and, once in force, remains so indefinitely. Türkiye's foreign affairs commission approved it on 27 October; its deputy foreign minister said Saudi Arabia and Pakistan had completed ratification. On 26 October the three sent a joint delegation to Tehran. No instrument, threshold, command or named contribution is public, and no signatory has invoked it.
Latest reviewAssessment changed
The condition still said no text was public, untrue since 20–21 October. Türkiye's Foreign Affairs Commission approved the approval bill on 27 October, and its deputy foreign minister said Saudi Arabia and Pakistan had completed ratification; the bill was not on the General Assembly agenda of 28 October. On 26 October the three signatories sent a joint delegation to Tehran. Not met: implementing-instrument; no invocation or named contribution.
The evidence moved Vigil’s reading. The condition line advanced on this date.
- 2026-09-12: Baseline
- 2026-09-13: No material change
- 2026-09-20: No material change
- 2026-09-27: Assessment changed
- 2026-10-04: No material change
- 2026-10-11: No material change
- 2026-10-14: Movement observed
- 2026-10-18: No material change
- 2026-10-25: Movement observed
- 2026-11-01: Assessment changed
What would change the assessment3 assessment-change conditions · qualitative, as the record states them
Publication of an implementing instrument, or a formal invocation
Assessment effectwould move the Agreement from a stated commitment to a usable procedure and make later trilateral activity attributable for the first time.
A contribution publicly named as made under the Agreement
Assessment effectis the only evidence that would separate its effect from the bilateral and maritime arrangements already operating.
A prolonged further escalation against a signatory with no Agreement act of any kind
Assessment effectwould support reading it as a deterrent statement rather than a developing mechanism.
Observables9 named · “met” describes evidence, not success
01Test
A Turkish or Pakistani contribution named as made under the Agreement
THE ATTRIBUTION IS THE OBSERVABLE. Forces, intelligence, logistics or basing publicly stated by the contributing or receiving government to be provided under the Makkah Agreement — not a deployment that could equally rest on the 2025 bilateral agreement or on maritime-coalition membership.
02Test
A signatory formally invokes the Agreement after an attack
A government stating, with the Makkah Agreement named, that it invokes the Agreement's collective-defence commitment — that an attack is being treated as an attack on all, or that assistance is requested or given under that clause. Consultation convened under the Agreement is not this: it shows the consultation mechanism working, not the commitment invoked. A condemnation, a solidarity statement or a bilateral call is not this either.
03Test
An implementing protocol or response mechanism is published
Any published instrument below the Agreement that states what a signatory owes, on what threshold, decided by whom — or publication of the Agreement text itself.
04Test
The Saudi-based Secretariat is activated
A stated seat, a staff, or a first act. The 31 August decision to establish one is the baseline, not the observable.
05Test
A Secretary General is appointed and acts publicly
The named holder of the three-year Pakistani term, and any public act in the office.
06Test
A joint command or coordination cell attributable to the Agreement
A standing body with a military function, stated by a signatory to exist under this Agreement rather than under the maritime coalition or a bilateral arrangement.
07Test
A joint exercise or operation conducted under the Agreement
Announced by a signatory as an Agreement activity, with the participants named.
08Test
A signatory defines what constitutes an armed attack for the Agreement
An official statement of the threshold, from any of the three, including one given in a parliamentary or briefing setting.
09Test
A state accedes to the Agreement
Accession completed, not interest expressed. Pakistan said on 10 September that expansion is not under discussion; that is the baseline.
Review ledger10 entries · opened · newest first, each tied to the review that made it
Assessment changed
The condition still said no text was public, untrue since 20–21 October. Türkiye's Foreign Affairs Commission approved the approval bill on 27 October, and its deputy foreign minister said Saudi Arabia and Pakistan had completed ratification; the bill was not on the General Assembly agenda of 28 October. On 26 October the three signatories sent a joint delegation to Tehran. Not met: implementing-instrument; no invocation or named contribution.
Brief item Türkiye's commission approved the Makkah Agreement, and its three signatories went to Tehran togetherReviewed in 2026-11-01
Movement observed
The text sent to the Turkish parliament with its approval bill (2/3961) was published by the press on 20 and 21 October: assistance against an armed attack by another country or group of countries, its extent set by each party; in force indefinitely once ratified. Not met: press publication is not a signatory's, and no protocol, threshold, invocation or named contribution followed. Türkiye's Defence Minister ruled out clashes with the Houthis.
Brief item The Makkah Agreement's text became public, and its trigger is an attack by another stateReviewed in 2026-10-25
No material change
No force attributed to the Agreement and no public act by the Secretary General. Found late: on 8 October Türkiye said its ratification text was ready and described its support to Saudi Arabia as defensive and technical, not under the Agreement. Pakistan's Prime Minister called the Agreement a milestone on 16 October without naming a force. Egypt, not a signatory, sought parliamentary authority on 17 October.
Brief item The Security Council affirmed Saudi Arabia's right of self-defence, and the kingdom's defenders multiplied outside any procedureReviewed in 2026-10-18
Movement observed
Found late by the 14 October maintenance review: on 5 October the committee, in emergency session in Riyadh, decided under the Agreement to implement its collective-defence commitments and provide the agreed forces and capabilities for rapid deployment in the kingdom, and appointed the Secretary General. No force, mission or invocation is named, and no deployment is attributed to the decision; no observable is marked met.
No material change
No invocation, instrument or attributed contribution found in coverage of the 4–5 October offensive or the Riyadh airport attacks. Gulf and GCC responses were statements of solidarity naming no agreement.
Brief item The offensive for the Bab el-Mandeb shore began, and the shore is claimed, not retakenReviewed in 2026-10-11
No material change
No act under the Agreement after the 25 Sep consultation. Reuters (2 Oct) reports Pakistani equipment flown to Aden and Pakistani advisers with Saudi forces, on unnamed officials, attributed to no agreement; Türkiye's Medina statement was bilateral. No invocation, instrument or named contribution.
Brief item Riyadh is reported planning to retake the Bab el-Mandeb shore, and planning is not an offensiveReviewed in 2026-10-04
Assessment changed
The condition said there was nothing public between the undertaking and the institutions, and that is no longer accurate. On 25 September the three chiefs of staff met in Riyadh, at their foreign ministers' direction of 24 September, to explore support to Saudi Arabia under the agreement, and named intelligence cooperation, military coordination and the integration of defence capabilities; on 23 September Pakistan announced the first Secretary General for a Secretariat being established in Riyadh. That is a consultation, not an activation: no invocation, implementing instrument, contribution named under the agreement, command cell or definition of armed attack. The secretary-general-named observable moved and is not met — a holder is named, and no public act in the office has been recorded.
Brief item The Makkah Agreement held its first consultation, and a consultation is not an invocationEvent The Makkah Agreement's chiefs of staff meet in Riyadh on support to Saudi ArabiaReviewed in 2026-09-27
No material change
Checked for a second consecutive window, and the finding is the same. Pakistan's Foreign Office said on 18 September that Pakistan is committed in intent and spirit to implementing the agreement. That is a statement of commitment, not an institutional act: no implementing instrument, no published procedure, no secretariat activation, no secretary-general named, no joint command cell, no exercise under the agreement, no definition of armed attack and no invocation by any signatory. The week's actual movement in Saudi defence arrangements was a bilateral United States aircraft notification, outside this agreement entirely.
Weekly Brief Iran–Gulf developments — 20 September 2026
No material change
First weekly review after the baseline, which was set on the evidence of 7–10 September. Nothing further was identified between 11 and 13 September: no agreement text, no implementing instrument, no consultation procedure and no invocation by any signatory. The absence the object records is unchanged.
Weekly Brief Iran–Gulf developments — 13 September 2026
Baseline
Opened by the Analytical Note of the same date, which established the four-layer reading — commitment, institution, mechanism, response — and found the third and fourth layers undemonstrated in public. No weekly review trail exists before this entry and nothing earlier is inferred.
Analytical Note The Makkah Agreement under pressure: what the Houthi escalation actually tests
Connected system31 canonical records this question runs through · Watch owns the edge; each record shows the question back
Parties and forces 8
Actors
- Saudi ArabiaLargest regional producer · de-escalation pole
- PakistanExtra-regional defence partner · mediation venue
- TürkiyeExtra-regional defence partner
- Houthi movementArmed movement · Bab el-Mandeb access
- United StatesBelligerent · security guarantor · basing partner
- GCCRegional institution · collective defence commitment
Means and systems 1
Ground 3
Arrangements and events 14
Relationships
Events
- A Pakistani military force arrives in Saudi Arabia under the 2025 bilateral agreement11 Apr 2026
- A Saudi-led multinational maritime defence alliance is declared in Riyadh30 Jul 2026
- Saudi Arabia, Türkiye and Pakistan sign the Makkah Joint Defence Agreement7 Aug 2026
- The Makkah Agreement's political and defence committee meets for the first time31 Aug 2026
- The heaviest Houthi attack wave against Saudi territory of this round8 Sep 2026, continuing to 3 Oct
- The Makkah Agreement's chiefs of staff meet in Riyadh on support to Saudi Arabia23 – 25 Sep 2026
- Attacks on Riyadh's airport kill civilians in the Saudi capital8 – 10 Oct 2026
- The Makkah Agreement's committee decides to implement its collective-defence commitments in Saudi Arabia5 Oct 2026
Vigil analysis 6
Watch questions
Open this question in Explore Interactive: select this record and follow what connects to it.
Assessed as of — 2026-11-01 Last reviewed — 2026-11-01 Changed in brief — 2026-11-01 · Status wording updated