The desks · Maritime

Maritime desk

The Strait of Hormuz and the Gulf and Red Sea shipping routes: what happened, who reported it and when. When sources disagree, you see both.

Sources through 12 Nov

Ledger built 17 Nov 2026Newest claim 17 NovGulf and Red Sea routes

What we read for it

The notices of 3 issuing authorities for the strait, 1,170 press documents from 221 outlets, and 8 prediction-market questions. Prediction-market prices are one source we cite and grade for accuracy; we serve current state, not forecasts. The authorities’ notices · Every place on these routes

How well each of the 2,880 events in this record is supported. The ledger holds 4,622 sentences; the event rule groups the sentences that report one event, and 3,163 of them make these 2,880 events. One bar per standing; its length is the number of events.
  • Corroborated29
  • Reported by two102
  • Single source2,749

Not in the bars: 1,459 sentences the event rule could not place. Each counts on its own sources and is never folded into “Single source”.

No claim on this record sits beside a live report that gives a different answer about the same incident. That counts live claims only, after any replacement, and only pairs our test could match incident for incident. See where reports differ.

Watch this domain

GET https://api.signalbureau.ai/api/record/hormuz

{
  "schema": "sb.record.v1",
  "subject": "hormuz",
  "asOf": "2026-11-17",
  "currency": {
    "state": "not-current",
    "asOf": "2026-11-12",
    "sentence": "This record is no longer current: nothing new has been observed since 2026-11-12, 5 days ago, against its daily cadence — more than 3 times its usual gap, and 1 of its registered primary sources could not be read (Corroboration & context)."
  },
  "sections": [
    {
      "key": "definition",
      "state": "written"
    },
    {
      "key": "primaryDocuments",
      "state": "degraded"
    },
    {
      "key": "claims",
      "state": "corroborated"
    },
    {
      "key": "theRecord",
      "state": "measured"
    },
    {
      "key": "ourAttention",
      "state": "measured"
    },
    {
      "key": "marketSensor",
      "state": "priced"
    },
    {
      "key": "refereeGrades",
      "state": "tracked-but-ungraded"
    },
    {
      "key": "ourRead",
      "state": "cannot-measure"
    },
    {
      "key": "changeLog",
      "state": "recorded"
    },
    {
      "key": "limits",
      "state": "measured"
    },
    {
      "key": "verify",
      "state": "measured"
    },
    {
      "key": "provenance",
      "state": "measured"
    }
  ],
  "recordVersion": "sb.tr-af16fb5c",
  "whereFrom": {
    "level": "record",
    "label": "Where this record comes from",
    "children": [
      {
        "level": "kind",
        "label": "What is reported: 3 issuing authorities, 8 outside reports, 12 agreed claims",
        "children": {
          "count": 21,
          "unfold": "expand=+1"
        }
      },
      {
        "level": "kind",
        "label": "What we collected and how closely we watch: 1,170 documents from 221 outlets",
        "children": {
          "count": 1,
          "unfold": "expand=+1"
        }
      },
      {
        "level": "kind",
        "label": "What markets price: 8 questions, belief, not fact",
        "children": {
          "count": 8,
          "unfold": "expand=+1"
        }
      }
    ]
  }
}

The live endpoint returns the full record. Shown here: its sections and their states, its currency as served, and the where-from tree folded below the first level, computed from the same files at build.

What happened, and what was said about it

Left: what happened. Right: what people said about it. An opinion never goes in the left column.

What happened

The best-carried new claim on each of the latest days, each with its reports

  • First reported 17 Nov

    The remarks come amid continuing tensions in West Asia following the outbreak of a military conflict on February 28, when joint U.S.-Israeli strikes killed Iran's Supreme Leader Ayatollah Ali Khamenei and several senior political and military officials.

    Corroborated · 4 separate reports · 4 outlets · 4 sentences, one event

  • First reported 15 Nov

    Iran launched a drone attack against a US military base in Bahrain on Sunday, its second attempt to target the country in three days.

    Corroborated · 3 separate reports · 3 outlets · 3 sentences, one event

  • First reported 14 Nov

    The United States, in response to Tehran's choking of the strategic trade route, has imposed a naval blockade on Iranian ports and provides military support to tankers using the waterway.

    Corroborated · 3 separate reports · 3 outlets · 3 sentences, one event

  • First reported 12 Nov

    Iran responded by launching missiles and drones at countries across the region, while militant groups it backs in Lebanon, Yemen and Iraq also joined the fighting.

    Reported by two · 2 separate reports · 2 outlets · 2 sentences, one event

  • First reported 11 Nov

    The Middle East war broke out on February 28 with US-Israeli strikes that killed Iran's supreme leader, Ayatollah Ali Khamenei.

    Corroborated · 3 separate reports · 5 outlets · 2 more repeat the same words · 3 sentences, one event · last seen 16 Nov

  • First reported 10 Nov

    Iran Says Strait of Hormuz Will Stay Closed Until U.S. Meets Demands

    Corroborated · 3 separate reports · 3 outlets · 3 sentences, one event

What was said about it

The views with the most separate articles behind them. Views carry no date in the ledger.

Newest in the Hormuz ledger

The 8 most recent claims, newest first, picked by date alone. Open any one for the reports behind it, down to the article link.

  1. First reported 17 Nov

    The remarks come amid continuing tensions in West Asia following the outbreak of a military conflict on February 28, when joint U.S.-Israeli strikes killed Iran's Supreme Leader Ayatollah Ali Khamenei and several senior political and military officials.

    Corroborated · 4 separate reports · 4 outlets · 4 sentences, one event

  2. First reported 17 Nov

    Aircraft carrier USS Theodore Roosevelt has joined the American naval force in the Middle East as the third carrier strike group to operate there.

    Corroborated · 3 separate reports · 4 outlets · 5 sentences, one event

  3. First reported 17 Nov

    The arrival of the USS Theodore Roosevelt brings the number of US carrier strike groups to three, alongside more than a dozen destroyers.

    Corroborated · 3 separate reports · 4 outlets · 5 sentences, one event

  4. First reported 17 Nov

    Attacks on tankers in the strait have increased as Tehran continues to disrupt shipping in the vital waterway while Washington maintains a naval blockade on Iran in response.

    Reported by two · 2 separate reports · 2 outlets · 2 sentences, one event

The next 4, newest first: show them
  1. First reported 17 Nov

    Iran continues to attack commercial shipping vessels around the strait while the United States reportedly continues to enforce a naval blockade of Iranian ports.

    Reported by two · 2 separate reports · 2 outlets · 2 sentences, one event

  2. First reported 17 Nov

    CNN has reported that United States intelligence indicates Iran is developing plans to target senior officials in President Donald Trump’s administration with a “dirty bomb” or a chemical weapon in Washington, DC.

    Reported by two · 2 separate reports · 2 outlets · 2 sentences, one event

  3. First reported 17 Nov

    Reuters reported that the crew of a tanker was reported missing in the Strait of Hormuz during the same period, and the United Kingdom Maritime Trade Operations agency said the crew of a tanker passing through the waterway was unaccounted for after being attacked north of the Omani port city of Khasab.

    Reported by two · 2 separate reports · 2 outlets · 2 sentences, one event

  4. First reported 17 Nov

    Separately, Iran's attacks on vessels in the Strait of Hormuz continued on Tuesday with a tanker’s crew being unaccounted for after the ship was struck for a second time north of Oman’s Khasab, the United Kingdom Maritime Trade Operations agency said on Tuesday.

    Reported by two · 2 separate reports · 2 outlets · 2 sentences, one event

What separate sources agree on

We count a story once, however many outlets reprint it.

  • First reported 17 Nov

    The remarks come amid continuing tensions in West Asia following the outbreak of a military conflict on February 28, when joint U.S.-Israeli strikes killed Iran's Supreme Leader Ayatollah Ali Khamenei and several senior political and military officials.

    Corroborated · 4 separate reports · 4 outlets · 4 sentences, one event

  • First reported 17 Nov

    Aircraft carrier USS Theodore Roosevelt has joined the American naval force in the Middle East as the third carrier strike group to operate there.

    Corroborated · 3 separate reports · 4 outlets · 5 sentences, one event

  • First reported 15 Nov

    Iran launched a drone attack against a US military base in Bahrain on Sunday, its second attempt to target the country in three days.

    Corroborated · 3 separate reports · 3 outlets · 3 sentences, one event

  • First reported 14 Nov

    Iran’s Islamic Revolutionary Guard Corps said two oil tankers struck naval mines in the southern part of the Strait of Hormuz, caught fire, and sank one vessel while attempting to cross via what it called an “unauthorized” route.

    Corroborated · 3 separate reports · 3 outlets · 3 sentences, one event

  • First reported 14 Nov

    The United States, in response to Tehran's choking of the strategic trade route, has imposed a naval blockade on Iranian ports and provides military support to tankers using the waterway.

    Corroborated · 3 separate reports · 3 outlets · 3 sentences, one event

Every claim in the archive (4,622 sentences): show them

Where reports differ

No claim on this record sits beside a live report that gives a different answer about the same incident. That counts live claims only, after any replacement, and only pairs our test could match incident for incident.

Headlines several outlets carried this week

Each is a publisher’s headline as its feed carried it, quoted, not a claim we extracted. “Where from” opens that headline’s own article; a row whose link is another outlet’s report says so.

12 headlines about Hormuz carried by several outlets between 11 Nov 2026 and 17 Nov 2026: 5 corroborated, 7 reported by two. This counts publishers, not truth. Many outlets repeating one official statement is still one statement.

  • First reported 12 Nov

    Headline, news.google.com: “Middle East latest: IRGC says two oil tankers caught fire after hitting sea mines in Hormuz”

    Corroborated · 7 separate reports · 10 outlets · 1 more of unknown origin, not counted

  • First reported 11 Nov

    Headline, marineinsight.com: “Oil Tanker Catches Fire After Hitting Naval Mine In Strait Of Hormuz, Iran Says”

    Corroborated · 5 separate reports · 6 outlets

  • First reported 11 Nov

    Headline, newscord.org: “IRGC Navy Says Two Oil Tankers Exploded in Strait of Hormuz After Ignoring Warnings”

    Corroborated · 4 separate reports · 4 outlets

The other 9: show them
  • First reported 14 Nov

    Headline, gulfnews.com: “UN urges US, Iran to allow fertiliser shipments through Strait of Hormuz”

    Corroborated · 4 separate reports · 4 outlets

  • First reported 15 Nov

    Headline, newscord.org: “UKMTO Reports Tanker Struck Twice in Strait of Hormuz, Crew Unaccounted for”

    Reported by two · 2 separate reports · 3 outlets · 1 more of unknown origin, not counted

  • First reported 11 Nov

    Headline, ibtimes.com.au: “Strait of Hormuz Latest: Iran Vows Waterway Will Never Return to Pre-War Status as More Tankers Hit Mines”

    Corroborated · 3 separate reports · 3 outlets

  • First reported 11 Nov

    Headline, aljazeera.com: “Iran denies talks with US, says Hormuz will stay shut until demands are met”

    Reported by two · 2 separate reports · 2 outlets

  • First reported 16 Nov

    Headline, marineinsight.com: “Supertanker With 2 Million Barrels Of Oil Sinks After Hitting Mine In Strait Of Hormuz, Iran Says”

    Reported by two · 2 separate reports · 2 outlets

  • First reported 15 Nov

    Headline, nypost.com: “Trump’s Hormuz squeeze has Iran strangled — now slam its back door, too”

    Reported by two · 2 separate reports · 2 outlets

  • First reported 11 Nov

    Headline, foxnews.com: “Iran escalates in Hormuz, claims strike on Omani island it says 'enemy' uses for US military ops”

    Reported by two · 2 separate reports · 2 outlets

  • First reported 17 Nov

    Headline, gulfnews.com: “Strait of Hormuz attack: Indian seafarer missing after second attack on tanker off Oman”

    Reported by two · 2 separate reports · 2 outlets

  • First reported 11 Nov

    Headline, euronews.com: “Oil prices rise as investors monitor shipping disruption in the Strait of Hormuz”

    Reported by two · 2 separate reports · 2 outlets

What the issuing authorities publish

The authorities that issue notices for the strait itself, read by an automated daily fetch, last read Nov 17. Each row leads with what the issuer said and the date that reading speaks for.

  • 18 Oct

    UKMTO / JMIC advisory notes

    UK Maritime Trade Operations (Royal Navy) / coalition Joint Maritime Information Center (JMIC) · ~every 2–3 days

    Update 106 (18 october)

  • 17 Nov

    NAVAREA IX navigational warnings

    National Hydrographic Office, Pakistan Navy (the interior Strait’s WWNWS issuer) · daily

    Warning 445/26 (17 Nov 2026), as issued.

    show the warning as issued

    445/26 (17 Nov 2026) — LPG TANKER INVOLVED IN A SECURITY INCIDENT CAUSING FIRE STRAIT OF HORMUZ 170630 UTC NOV 2026

  • 8 May

    Corroboration & context

    US MARAD MSCI · NGA MSI · EIA · Lloyd’s JWC · periodic / event-driven

    Latest document on this channel, NAVAREA P 1540/2024, is dated May 2024.

    show the warning as issued

    NAVAREA P 1540/2024 (081538Z MAY 2024) — PERSIAN GULF. QATAR. DNC 10. SURVEY OPERATIONS 08 MAY UNTIL FURTHER NOTICE BY M/V HORIZON GEOBAY IN AREA BOUND BY 26-09.23N 051-48.00E, 26-06.54N 052-02.87E, 25-31.26N 051-56.93E, 25-33.85N 051-41.16E. WIDE BERTH REQUESTED.

    NGA issues NAVAREA IV, XII and HYDRO only; this covers the APPROACHES to the Strait, never its interior, which is NAVAREA IX (read separately above). Corroboration, not a primary tripwire.

What markets price

Belief, not fact. We quote the venues as a sensor and publish no probability of our own. How that sensor has scored.

8 market questions in all; every one, with its deadline, is under “How this record is kept”.

The conditions we follow

One report pinned per condition, with the earlier report it replaced. Each row says how far its pinned report trails the ledger’s newest claim.

The 1 conditions: show them

Source for every report, date and outlet: the Hormuz reporting ledger and the first-hand notices in the Hormuz record

The condition names, and which report is pinned to each, were chosen by hand. The layer that would group claims into conditions on its own is not built yet, so this board does not rank them.

Developers can read this record through the SigB API.

On the newest day

What changed on 17 Nov, the newest day in the ledger.

  • Claims in the Hormuz ledgerNew: 66Changed or replaced: 4first seen on 17 Nov; replaced counts claims set aside since then, each kept on file with its reason
  • Published Hormuz recordNew: 4Changed or replaced: 4claims in and out as the 7-day window moved

Source for every count: the Hormuz reporting ledger, the Hormuz record’s change log, and each place’s record

The last 76 days

Hatched bars: claims first seen that day in the Hormuz ledger. Numbered squares match the events below.
Events
Claims a day
peak 126
3 Sep: 126 claims4 Sep: 45 claims5 Sep: 42 claims6 Sep: 45 claims7 Sep: 68 claims8 Sep: 68 claims9 Sep: 105 claims10 Sep: 46 claims11 Sep: 77 claims12 Sep: 42 claims13 Sep: 33 claims14 Sep: 65 claims15 Sep: 74 claims16 Sep: 60 claims17 Sep: 43 claims18 Sep: 74 claims19 Sep: 15 claims20 Sep: 31 claims21 Sep: 75 claims22 Sep: 95 claims23 Sep: 91 claims24 Sep: 61 claims25 Sep: 68 claims26 Sep: 28 claims27 Sep: 72 claims28 Sep: 85 claims29 Sep: 72 claims30 Sep: 36 claims1 Oct: 41 claims2 Oct: 36 claims3 Oct: 20 claims4 Oct: 36 claims5 Oct: 69 claims6 Oct: 75 claims7 Oct: 53 claims8 Oct: 66 claims9 Oct: 37 claims10 Oct: 36 claims11 Oct: 27 claims12 Oct: 53 claims13 Oct: 45 claims14 Oct: 61 claims15 Oct: 52 claims16 Oct: 48 claims17 Oct: 46 claims18 Oct: 45 claims19 Oct: 73 claims20 Oct: 53 claims21 Oct: 62 claims22 Oct: 64 claims23 Oct: 61 claims24 Oct: 21 claims25 Oct: 44 claims26 Oct: 73 claims27 Oct: 51 claims28 Oct: 65 claims29 Oct: 36 claims30 Oct: 89 claims31 Oct: 59 claims1 Nov: 44 claims2 Nov: 95 claims3 Nov: 120 claims4 Nov: 55 claims5 Nov: 60 claims6 Nov: 80 claims7 Nov: 50 claims8 Nov: 84 claims9 Nov: 90 claims10 Nov: 107 claims11 Nov: 92 claims12 Nov: 53 claims13 Nov: 71 claims14 Nov: 69 claims15 Nov: 68 claims16 Nov: 79 claims17 Nov: 66 claims
The 2 numbered events: show them
  1. 1 First reported 9 Sep

    Iran said on Wednesday it had attacked 10 ships near the Strait of Hormuz after the U.S. sank five Iranian oil tankers, in the biggest declared wave of tit-for-tat attacks on shipping by both sides since the start of the six-month-old war.

    Corroborated · 4 separate reports · 5 outlets · 1 more repeats the same words · 4 sentences, one event · last seen 10 Sep

  2. 2 First reported 29 Sep

    Iran threatened to attack energy infrastructure across the Middle East if its security isn't guaranteed as it ratcheted up its rhetoric while waiting for the United States to officially respond to a plan Tehran says would reopen the Strait of Hormuz.

    Single source · last seen 30 Sep

Source for bars, events, dates and report counts: the Hormuz reporting ledger

Which events are listed was chosen by hand: a selection of notable claims from the ledger.

Every place on these routes

Key: record kept · not covered yet. The words in each row say the same thing.

All 12 places, with their records: show them
  • Strait of HormuzRecord: record kept, fullPublished claims: 12Runs to: 12 Nov
  • Red SeaRecord: record kept, minimalPublished claims: 2Runs to: 16 Nov
  • YemenRecord: record kept, standardPublished claims: 12Runs to: 12 Nov
  • Bab el-MandebRecord: record kept, minimalPublished claims: 0Runs to: 27 Oct
  • Gulf of OmanRecord: not covered yetPublished claims: noneRuns to: no record yet
  • Persian GulfRecord: record kept, minimalPublished claims: 0Runs to: 20 Sep
  • Kharg IslandRecord: record kept, minimalPublished claims: 0Runs to: 2 Oct
  • FujairahRecord: record kept, minimalPublished claims: 0Runs to: 20 Sep
  • YanbuRecord: record kept, minimalPublished claims: 0Runs to: 20 Sep
  • Ras TanuraRecord: record kept, minimalPublished claims: 0Runs to: 26 Oct
  • Bandar AbbasRecord: not covered yetPublished claims: noneRuns to: no record yet
  • Suez CanalRecord: record kept, minimalPublished claims: 0Runs to: 13 Oct
How this ledger counts
  • 6,538 press articles archived between 25 Aug and 17 Nov.

  • Agreement between reports is not proof. An error repeated by every outlet would still count as agreement.

  • Copies of the same story are counted once. Some reports that share a source may still be counted separately.

  • This ledger was built on 17 Nov from archived coverage. It was not kept live.

  • 92 claims were set aside because no stored article text supports them.

  • 4 claims that called themselves the latest were set aside after a later report from the same outlet replaced them.

  • 65,552 claims that called themselves the latest were set aside after a later report from the same outlet replaced them.

  • 3,319 claims were set aside because every report behind them came from outlets that do not usually cover this subject.

  • 13,963 claims were set aside because they did not match a tracked condition. Each is kept on file with its reason.

  • A claim is shown only when we hold the outlet’s link and the article’s exact words. Claims without both are kept and counted but not shown.

  • 14 claims are kept on file as set aside, each with the reason.

the Hormuz reporting ledger and the first-hand notices in the Hormuz record, their own notes on their limits

Source for records and their dates: the maintained subject recordsSource for limits and set-aside counts: the Hormuz reporting ledger

Watches on this desk

Strait of Hormuz

record kept, full · ledger built 17 Nov 2026

sentences in the ledger
4,622
attributed views
1,175
published claims
12
first-hand sources
3

Red Sea and Yemen

the other way out

Red Sea published claims
2
Yemen published claims
12
Bab el-Mandeb published claims
0

Gulf ports

smaller records

records kept
4
published claims
0

Source for every count: the Hormuz reporting ledger and the maintained subject records

How places are grouped into these three cards was chosen by hand.

Ask this desk a question · See all Watches

How this record changes and how it is kept

Change log and corrections: show them

Corrections are added and the old line stays, struck through. 14 lines in all: 5 replaced by a later report in the same thread, 9 removed because every outlet carrying them covers a different subject.

  • 17 Nov

    9 claims added · 9 aged out of the 7-day window · 4 replaced by a later report

  • 16 Nov

    10 claims added · 10 aged out of the 7-day window

  • 15 Nov

    10 claims added · 10 aged out of the 7-day window

  • 14 Nov

    11 claims added · 11 aged out of the 7-day window

  • 13 Nov

    11 claims added · 11 aged out of the 7-day window

  • 12 Nov

    16 claims added · 16 aged out of the 7-day window

  • 11 Nov

    9 claims added · 9 aged out of the 7-day window

The newest corrections

  • 17 Nov

    Old line: However, the remaining unhedged 20% is highly exposed to the jet fuel prices currently trading at about $140 per barrel, Ryanair said in its August 2026 traffic stats.

    Replaced by a later report in the same thread: “Ryanair is one of the most hedged airlines, with about 80% of fuel costs hedged at $67 per barrel.” The old line is kept and marked.

  • 17 Nov

    Old line: Iran could reopen the Strait of Hormuz to Gulf shipping within seven days if the US fulfilled Tehran's demands to ease military pressure and lift an American blockade on Iranian ports, the Iranian official said, adding that Iran had conveyed its latest proposal to Washington via mediators last week.

    Replaced by a later report in the same thread: “A senior Iranian official said Iran could reopen the Strait of Hormuz to Gulf shipping within seven days if the US fulfilled Tehran's demands to ease military pressure and lift an American blockade on Iranian ports, adding that Tehran had conveyed its latest proposal to Washington via mediators last week.” The old line is kept and marked.

  • 17 Nov

    Old line: US President Donald Trump has rejected Iran’s latest proposal to reopen the Strait of Hormuz to shipping.

    Replaced by a later report in the same thread: “US President Donald Trump has rejected an Iranian proposal to reopen the Strait of Hormuz to commercial shipping within a week.” The old line is kept and marked.

9 removed as off-topic (AP News, BiggerPockets Blog, Inman News, and others) · show
Before and after: show the comparison

The answer a machine gets, with and without this record

What keeping the layers apart changes for a machine reader. The left column is what a one-layer reader concludes; the right column is what the maintained record keeps in view. Each line is derived from the record’s own layers, the same record machines fetch. None of it comes from a staged chat.

Without the record: one layer at a time

Reading only the coverage line (coverage state, our own measurement): attention is 1% above its baseline and steady. Conclusion: “nothing is moving here.”

Reading only one reporting headline (attributed): “Brent Stuck Near $93 as Hormuz Tanker Attacks Offset Gulf Export Surge”. Conclusion: “whatever that single frame implies, with no way to see the layers that disagree with it.”

Reading only one market price (belief, not fact): “US-Iran Hormuz Agreement by December 31?” at 29%. Conclusion: “the crowd has settled it; one question’s odds stand in for the whole state of the world.”

Each single-layer read reaches a different conclusion.

With the record: every layer in view

UKMTO / JMIC advisory notes reports Update 106, dated 18 october; NAVAREA IX navigational warnings reports 445/26, dated 17 Nov 2026. Read from the issuer Nov 17, 2026. Of 12 claims about Hormuz on the record in the current window (Nov 11, 2026 – Nov 17, 2026), 5 are corroborated by three or more separate origins, 7 are reported by two separate origins and 0 rest on a single source. The strongest: “Middle East latest: IRGC says two oil tankers caught fire after hitting sea mines in Hormuz” (corroborated; carried by 10 publishers from 8 separate origins · 1 wire (Reuters), earliest Nov 12, 2026); “Oil Tanker Catches Fire After Hitting Naval Mine In Strait Of Hormuz, Iran Says” (corroborated; carried by 6 publishers from 5 separate origins, earliest Nov 11, 2026). These count claims in this window; the press archive's ladder, in the single-source line of this read, counts events over the whole archive. 2749 of the 2880 events in this record's press archive (its 4622 who/what/when/where sentences, grouped by the incident they report) rest on a single reporting chain: reported once, and not repeated by anyone who did not copy it. Another 1459 sentences the event rule could not place, so each counts on its own sources and is never folded into single source. They are held, and they are not corroboration. We could not judge whether claims on this record contradict each other: the pass that failed is the comparability pass. What this covers: 0 comparable pairs among 12 headline clusters on this record (66 pairs judged: 50 without a shared typed actor and action class, 16 sharing them over different propositions); 4 further clear clusters beyond the 12-claim cap were not judged. That is unknown, not none. No claim on this record sits beside a live report that gives a different answer about the same incident. That counts live claims only, after any replacement, and only pairs our test could match incident for incident. The record also holds 4 pairs of similar claims the disagreement test could not compare role for role; the test cannot say whether they differ. The ledger holds 6 recorded changes for Hormuz, the most recent on Nov 11, 2026. Each one is a change in how closely we are watching, written the moment we observed it, never backfilled and never edited after the fact. We do not yet diff against a previously published copy of this record; what stands is the ledger's own dated transitions. Side by side, unreconciled: a venue prices “Strait of Hormuz traffic returns to normal by November 30?” at 2.3% (polymarket, Nov 17, 2026), while our own record holds 5 claims corroborated by three or more separate origins (of 12 claims in all: 7 are reported by two separate origins and 0 rest on a single source). The price is the venue's number and we publish it as one; we do not blend it into ours, and we hold no probability of our own on this record. Earlier documents on file: Corroboration & context, latest dated May 2024 (NAVAREA P 1540/2024). The read above does not rest on them. Of the 8 parts of that read, 1 is not yet read; the rest are measurements. It is our analysis of the record’s own dated sections, attributed throughout and labeled ours. We serve current state, not forecasts.

Composed from the record’s own dated layers. The layers it holds apart: observed operational state · observed reporting · the record itself · coverage state · market expectation · our reading · reporting consensus · the recorded history.

show the machine’s judgment sentence, as servedWe keep the layers apart and do not collapse them. Our attention on Hormuz stands 1% above its baseline and is steady. That measures our coverage, not the subject. The reporting layer is attributed outside coverage, and the consensus ledger was computed 2026-11-17 over reporting through 2026-11-17. Each claim carries its date, and a dated layer is never read as today's news. The market layer prices 7 questions still open by their own deadline, beside 1 past its deadline and held as historical capture. A price is collective belief about defined outcomes, never proof. A system that read any single layer alone could answer wrongly in either direction; the maintained record keeps every layer in view. This is our judgment over the layers above, labeled as such.

Provenance of this panel: each line above is derived from the record’s own layers, not from a staged chat. The coverage numbers, the headline and the market price are fields in the same record served at GET /api/record/hormuz. The right column is composed from the record’s dated layers, with the served judgment sentence one tap away, verbatim. No transcripts were invented. The disagreement is in the data.

How this record is keptThe method in full: the record’s date, what it is, the press archive and its limits, our own coverage, every market question, and how to check it yourself.Show the method Hide the method

The record’s date

Sources through 12 Nov; the market sensor through 2 Oct.

What this record is

The Strait of Hormuz — the narrow waterway between Iran and Oman through which roughly a fifth of the world's oil passes.

Why we keep a record on it. We hold 1170 documents from 221 outlets over 43 active days. It runs through 18 coverage domains we watch, including Africa, Australia Economy, Autonomous Shipping. 32 market questions price outcomes under the event bound to it. Our first document on this subject is dated Sep 28, 2026; the count above is everything since.

What it is not. Our attention, not the world's state. Every count here is a count of what our own sweep collected about hormuz. 221 outlets in our declared source universe — not the whole internet. Market prices are the venue's number, cited and graded as an outside sensor. We publish no probability of our own on this record.

How complete this record is: full. It meets 3 of 3 conditions: a first-party issuer document read from the issuer itself; a claim carried from three or more separate origins; at least one market question bound to this record.

The press archive: scope, views and limits

Computed Nov 17; last re-checked Nov 17. Each claim below carries its own first-seen date.

Scope, first: 6538 articles archived by our sweeps between 2026-08-25 and 2026-11-17 — secondary press; this news ledger does not read primary feeds, which the record reads separately in its primary-source layer (UKMTO / JMIC advisory notes, NAVAREA IX navigational warnings) with their own dates. Everything here speaks for that archive only. A claim is scored by how many separate reports assert it; copies of one wire story count once. Agreement between reports is not proof. The “why” is a view, listed with who said it, never averaged.

A receipt links the archived article where we read the claim, often a roundup, so a receipt’s own headline can differ from the claim it carries. All 4,622 sentences are listed under “What separate sources agree on”, folded.

Outside reporting, newest captured

The views: how different outlets explain it

Each with who said it, never averaged. The 3 with the most separate articles:

Every view (1,175): show them

  • Consensus measures reporting agreement, not reality — a uniformly repeated error passes any count.
  • Chains are collapsed by syndication tracing; residual shared-upstream risk remains.
  • Retroactive: computed 2026-11-17 over the archive, not tracked live.
  • Receipt gate: 92 extracted claim(s) excluded — no receipt whose own text supports the claim (the extractor's row binding is verified mechanically, never trusted).
  • Relative-anchor supersession: 4 claim(s) that described themselves as the most recent/last-known fact were retired because a claim from the SAME reporting thread, naming the same participants and the same measured quantity, describes a later instance of that subject — see 'retired'. Subject-matched, same-chain detection only: an anchor claim updated by a DIFFERENT outlet is not auto-retired, though its own firstSeen/lastSeen still render so a reader can judge its age.
  • Relative-anchor supersession: 65552 later same-thread claim(s) were NOT treated as replacing an anchored claim: 51617 are about different participants, a different measured quantity or a forecast, 13933 could not be read role for role or period for period, 1 compare against another time, 0 characterize or restate the same value and 1 report an earlier or the same period. A claim is replaced here only by a later report on the same participants and the same measured quantity, for a later period; every other pair keeps both claims standing.
  • Questions: 22 extracted sentence(s) were questions (a headline asking, e.g. "Trump said on Truth Social: 'Now that we have it under U.S.A. control, should we change th"), not assertions, and take no claim standing in any tier.
  • Literal-span counting (#1036): 742 extracted claim(s) were receipted by sentences that do not all assert the same proposition, and were split into 1740 separate claims, each counted only on the sources whose own sentence asserts it. Every count, disagreement and replacement here is decided on the sources' own words; the extractor's sentence is kept as a labelled paraphrase and decides nothing.
  • Domain-competence gate: 3319 kernel claim(s) and 466 frame(s) excluded — every supporting chain came from outlets confidently placed outside this subject's coverage domains (aerospace_defense, auto, energy, europe_politics, india_south_asia, iran_regime, …). An outlet counts as competent when its measured home beat intersects the domains the subject's own corpus lives in; outlets with too few observations are never branded and always count.
  • Semantic-dome membership: 13963 kernel claim(s) and 3189 frame(s) were source-faithful but failed typed-signature membership and are excluded — a claim enters this ledger only if its signature names a family entity (party, place, or authority) AND either its action class sits in the family's geopolitical profile or it names a family place outright.
  • An item is published only when it is RECEIPTED: the outlet's own source link AND the source's exact words (verbatim: a literal span of the stored document, offsets into it, content-addressed by docId). The claim text is the extracted proposition and is never a quote. Anything else is UNRECEIPTED: retained, counted here by reason, never shown; every published count is computed from receipted items only.
  • Disagreement pairing: 27 candidate pair(s) with overlapping words and different numbers were NOT shown as disagreements: 4 report separate incidents or readings (another named date or time, another vessel, or reported on another day), 19 assert different propositions (another party or quantity) and 4 could not be matched role for role. Two reports disagree here only when they give different values for the same actor, counterparty, quantity and incident: the same named date, or the same report day when no date is named.
  • Event grouping (event@2): 4622 claim(s) are source sentences; 497 were grouped into 214 multi-sentence event(s) and 2666 matched no other claim, giving 2880 event(s). 1459 claim(s) could not be matched (untyped action class, no participant read, or no report day), so their count stays per sentence: could not match is not single source. The rule is mechanical and conservative (same typed action, shared participants and wording, no different named person or market, first seen within 1 day, no conflicting date, time, vessel, means (mine, missile, drone, boarding, gunfire) or value, every member matched to one anchor), so it under-groups: it measures reporting agreement about one incident, not verification.
Withdrawn claims (14): show the record

A row that fails a later audit is withdrawn on the record (the claim as published, the reason, the date), never silently deleted.

  • Nov 17

    Withdrawn · kernel fact · as published: reported once, by one source · via Oil Price

    However, the remaining unhedged 20% is highly exposed to the jet fuel prices currently trading at about $140 per barrel, Ryanair said in its August 2026 traffic stats.

    Why: superseded: this claim anchors itself as the most recent known fact (last seen 2026-09-03), but a claim from the SAME reporting thread about the same participants and the same measured quantity, "Ryanair is one of the most hedged airlines, with about 80% of fuel costs hedged at $67 per barrel." (last seen 2026-09-03), reports a later period of the same subject, and is not a comparison, an elaboration or an earlier period. Same-chain, subject-matched only (#e02ae00b, #992, #1009); an update carried by a different outlet is not auto-detected..

  • Nov 17

    Withdrawn · kernel fact · as published: reported once, by one source · via Al-Monitor — Middle East

    Iran could reopen the Strait of Hormuz to Gulf shipping within seven days if the US fulfilled Tehran's demands to ease military pressure and lift an American blockade on Iranian ports, the Iranian official said, adding that Iran had conveyed its latest proposal to Washington via mediators last week.

    Why: superseded: this claim anchors itself as the most recent known fact (last seen 2026-09-22), but a claim from the SAME reporting thread about the same participants and the same measured quantity, "A senior Iranian official said Iran could reopen the Strait of Hormuz to Gulf shipping within seven days if the US fulfilled Tehran's demands to ease military pressure and lift an American blockade on Iranian ports, adding that Tehran had conveyed its latest proposal to Washington via mediators last week." (last seen 2026-09-23), reports a later period of the same subject, and is not a comparison, an elaboration or an earlier period. Same-chain, subject-matched only (#e02ae00b, #992, #1009); an update carried by a different outlet is not auto-detected..

  • Nov 17

    Withdrawn · kernel fact · as published: reported by two sources that did not copy each other · via France 24 - International breaking news, top stories and headlines, Al Jazeera – Breaking News, World News and Video from Al Jazeera, Al Jazeera – Breaking News, World News and Video from Al Jazeera

    US President Donald Trump has rejected Iran’s latest proposal to reopen the Strait of Hormuz to shipping.

    Why: superseded: this claim anchors itself as the most recent known fact (last seen 2026-09-27), but a claim from the SAME reporting thread about the same participants and the same measured quantity, "US President Donald Trump has rejected an Iranian proposal to reopen the Strait of Hormuz to commercial shipping within a week." (last seen 2026-09-28), reports a later period of the same subject, and is not a comparison, an elaboration or an earlier period. Same-chain, subject-matched only (#e02ae00b, #992, #1009); an update carried by a different outlet is not auto-detected..

  • Nov 17

    Withdrawn · kernel fact · as published: reported once, by one source · via Oil Price

    As of the start of October, the amount of oil in the strategic U.S. reserve stood at 331.2 million barrels, which was the lowest since 1983, following the latest release of over 9 million barrels.

    Why: superseded: this claim anchors itself as the most recent known fact (last seen 2026-10-10), but a claim from the SAME reporting thread about the same participants and the same measured quantity, "Some 4 million barrels daily of that goes south to U.S. refineries." (last seen 2026-10-13), reports a later period of the same subject, and is not a comparison, an elaboration or an earlier period. Same-chain, subject-matched only (#e02ae00b, #992, #1009); an update carried by a different outlet is not auto-detected..

  • Nov 3

    Withdrawn · kernel fact · as published: reported once, by one source · via Hindustan Times Business

    Brent futures rose 2.1 per cent to $106.49 a barrel, bringing gains so far this month to almost 18%, while US crude futures added 1.5% to $93.84 a barrel.

    Why: superseded: this claim anchors itself as the most recent known fact (last seen 2026-09-28), but a claim from the SAME reporting thread about the same participants and the same measured quantity, "Some 4 million barrels daily of that goes south to U.S. refineries." (last seen 2026-10-13), reports a later period of the same subject, and is not a comparison, an elaboration or an earlier period. Same-chain, subject-matched only (#e02ae00b, #992, #1009); an update carried by a different outlet is not auto-detected..

  • Oct 2

    Withdrawn · kernel fact · as published: reported once, by one source · via AP News

    Iraq is importing gasoline via Syrian port to bypass the closed Strait of Hormuz.

    Why: no domain-competent chain: every published chain (AP News) comes from outlets confidently placed outside this subject's coverage domains.

  • Oct 2

    Withdrawn · kernel fact · as published: reported once, by one source · via AP News

    An Iranian commercial ship was struck near Strait of Hormuz with 1 dead.

    Why: no domain-competent chain: every published chain (AP News) comes from outlets confidently placed outside this subject's coverage domains.

  • Oct 2

    Withdrawn · kernel fact · as published: reported once, by one source · via AP News

    One person was killed in a ship strike on the Strait of Hormuz.

    Why: no domain-competent chain: every published chain (AP News) comes from outlets confidently placed outside this subject's coverage domains.

  • Oct 2

    Withdrawn · kernel fact · as published: reported once, by one source · via AP News

    Iran plans to announce a new exclusion zone near the Strait of Hormuz.

    Why: no domain-competent chain: every published chain (AP News) comes from outlets confidently placed outside this subject's coverage domains.

  • Aug 29

    Withdrawn · kernel fact · as published: reported by two sources that did not copy each other · via Inman News, BiggerPockets Blog

    The U.S. and Iran signed a memorandum of understanding.

    Why: no domain-competent chain: every published chain (BiggerPockets Blog, Inman News) comes from outlets confidently placed outside this subject's coverage domains.

  • Aug 29

    Withdrawn · kernel fact · as published: reported once, by one source · via BiggerPockets Blog

    The Strait of Hormuz represents 20 percent of the world's oil.

    Why: no domain-competent chain: every published chain (BiggerPockets Blog) comes from outlets confidently placed outside this subject's coverage domains.

  • Aug 29

    Withdrawn · frame · as published: via inman

    Financial markets have reacted positively to developments in negotiations to reopen the Strait of Hormuz.

    Why: no domain-competent attribution: every attributed origin (inman) is an outlet confidently placed outside this subject's coverage domains.

  • Aug 29

    Withdrawn · frame · as published: via inman

    Investors celebrated the prospect of reopening the Strait of Hormuz.

    Why: no domain-competent attribution: every attributed origin (inman) is an outlet confidently placed outside this subject's coverage domains.

  • Aug 29

    Withdrawn · frame · as published: via realtor.com

    The oil price decline reflects the signed memorandum of understanding between the U.S. and Iran, hopefully marking the beginning of the end of the war that closed the straits of Hormuz.

    Why: no domain-competent attribution: every attributed origin (realtor.com) is an outlet confidently placed outside this subject's coverage domains.

Our coverage

What our own machinery collected and how closely it watches. These measure our attention, not the strait.

  • Documents

    1,170

    From 221 outlets. Documents arrived on 43 days between 28 Sept 2026 and 12 Nov 2026. Market questions are not counted, because a question is not reporting.

  • How closely we watch

    steady

    Our coverage of Hormuz is 1% above its 3-week baseline, sustained. This measures our attention — how much our tracked set is writing about it — not the strait's operational status.

  • Days with an attention reading

    182 days

    In the latest collection (17 Nov 2026), 170 signals in 39 of our coverage areas mention it.

  • Market questions on the event

    32

    The Strait of Hormuz event has carried 32 market questions since 24 May 2026, last priced 12 Nov 2026.

What changed, and when

The ledger holds 6 recorded changes for Hormuz, the most recent on Nov 11, 2026. Each one is a change in how closely we are watching, written the moment we observed it, never backfilled and never edited after the fact. The ledger began recording 2026-07-19; earlier states were tracked but not ledgered, and are not backfilled.

  • 6 Nov

    How closely we watch: changed from rising to too little history to judge

    observed Nov 6, 7:52 AM PT · prior state held since Oct 31, 8:48 AM PT

  • 6 Nov

    Front-page listing: changed from flagged to on watch

    observed Nov 6, 7:52 AM PT · prior state held since Oct 31, 8:48 AM PT

  • 7 Nov

    How closely we watch: changed from too little history to judge to steady

    observed Nov 7, 9:22 AM PT · prior state held since Nov 6, 7:52 AM PT

  • 7 Nov

    Front-page listing: changed from on watch to flagged

    observed Nov 7, 9:22 AM PT · prior state held since Nov 6, 7:52 AM PT

  • 9 Nov

    How closely we watch: changed from steady to rising

    observed Nov 9, 7:53 AM PT · prior state held since Nov 7, 9:22 AM PT

  • 11 Nov

    How closely we watch: changed from rising to steady

    observed Nov 11, 9:28 AM PT · prior state held since Nov 9, 7:53 AM PT

Every market question

What prediction markets price: belief, not fact, and never proof that something happened. We cite the venues as a sensor and publish no probability of our own. Our public grading of that sensor scores those prices against how reality resolved.

8 market questions ride this record, newest price stamp Nov 17, 2026: 7 still open by their own deadline, 1 past it and kept as recorded. A price is the venue's number, cited as one outside sensor and graded against how reality resolved; it is never a probability of ours.

Still open by their own deadline

Past their deadline, kept as recorded (final resolution at the venue)

Our read

  • measured

    What the issuing authorities say. UKMTO / JMIC advisory notes reports Update 106, dated 18 october; NAVAREA IX navigational warnings reports 445/26, dated 17 Nov 2026. Read from the issuer Nov 17, 2026.

  • measured

    How well the claims are supported. Of 12 claims about Hormuz on the record in the current window (Nov 11, 2026 – Nov 17, 2026), 5 are corroborated by three or more separate origins, 7 are reported by two separate origins and 0 rest on a single source. The strongest: “Middle East latest: IRGC says two oil tankers caught fire after hitting sea mines in Hormuz” (corroborated; carried by 10 publishers from 8 separate origins · 1 wire (Reuters), earliest Nov 12, 2026); “Oil Tanker Catches Fire After Hitting Naval Mine In Strait Of Hormuz, Iran Says” (corroborated; carried by 6 publishers from 5 separate origins, earliest Nov 11, 2026). These count claims in this window; the press archive's ladder, in the single-source line of this read, counts events over the whole archive.

  • measured

    What rests on one source. 2749 of the 2880 events in this record's press archive (its 4622 who/what/when/where sentences, grouped by the incident they report) rest on a single reporting chain: reported once, and not repeated by anyone who did not copy it. Another 1459 sentences the event rule could not place, so each counts on its own sources and is never folded into single source. They are held, and they are not corroboration.

  • Not yet read

    What contradicts. No claim on this record sits beside a live report that gives a different answer about the same incident. That counts live claims only, after any replacement, and only pairs our test could match incident for incident.

  • measured

    Where reports give different numbers. No claim on this record sits beside a live report that gives a different answer about the same incident. That counts live claims only, after any replacement, and only pairs our test could match incident for incident. The record also holds 4 pairs of similar claims the disagreement test could not compare role for role; the test cannot say whether they differ.

  • measured

    What changed. The ledger holds 6 recorded changes for Hormuz, the most recent on Nov 11, 2026. Each one is a change in how closely we are watching, written the moment we observed it, never backfilled and never edited after the fact. We do not yet diff against a previously published copy of this record; what stands is the ledger's own dated transitions.

  • measured

    The outside sensor, beside our record. Side by side, unreconciled: a venue prices “Strait of Hormuz traffic returns to normal by November 30?” at 2.3% (polymarket, Nov 17, 2026), while our own record holds 5 claims corroborated by three or more separate origins (of 12 claims in all: 7 are reported by two separate origins and 0 rest on a single source). The price is the venue's number and we publish it as one; we do not blend it into ours, and we hold no probability of our own on this record.

  • measured

    Earlier documents on file. Earlier documents on file: Corroboration & context, latest dated May 2024 (NAVAREA P 1540/2024). The read above does not rest on them.

What this record does not tell you

Standing limits of the method, true of every run:

  • The first-party maritime and government issuers behind this record are identified and verified — UKMTO/JMIC on a 1–3 day cadence, NAVAREA IX daily. The automated daily fetch cannot currently reach at least one source. A failed fetch moves nothing: the affected source holds its last verified reading, marked on its own row with the date it speaks for. Each row says which date it speaks for, and nothing updates silently.
  • The coverage regime measures our declared source universe (144 actively-scraped verticals — definitions on the API page), not the whole internet, and it is our attention — not the strait's status.
  • Cadence, stated plainly: the record refreshes on a daily sweep with intraday market updates. It is maintained, not instantaneous.

Verify it yourself

This page, GET /api/record/hormuz and the get_topic_record tool are assembled by one builder, so what you fetch is what you are reading. One honest distinction: get_entity("hormuz") returns the broader live entity dossier — a different, complementary object, not this record.

Served to machines as the resource sb://exhibit/hormuz, and through the API and MCP.

REST

curl -s https://api.signalbureau.ai/api/record/hormuz

MCP

curl -s https://api.signalbureau.ai/api/mcp -X POST -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_topic_record","arguments":{"subject":"hormuz"}}}'

Where this record comes from

This record reads as of 17 Nov 2026, assembled 17 Nov 2026. Its version number is sb.tr-af16fb5c, computed from the sections above, so it changes only when the record’s content changes.

Informational only, never financial, legal, or investment advice.