Watch

Watch your domain

Name what you need kept current. We show which topics we read, and keeping a Watch on them is free.

Watches are free. Configure, save and keep a Watch at no charge: no card, no end date. Up to 5 saved Watches per verified email or key. Need more, or something built around your own question? Ask us.

Name your domain

Say what you need kept current, in your own words. We split it into topics, then check each topic against what we actually read. You see every topic and whether we read it. A Watch on the topics we read is free.

Start a Watch

Configure any Watch and run it as often as you like, free and without a key. Watches are free. Configure, save and keep a Watch at no charge: no card, no end date. Up to 5 saved Watches per verified email or key. Need more, or something built around your own question? Ask us. A saved Watch is tied to your key and recalled from here, the REST API or MCP, with what changed since it was last delivered to you.

1. Configure (free)

Start from a sample Watch (each one reads the Strait of Hormuz record)

This Watch reads: Strait of Hormuz transit: availability, safety and cost of passage. To have us watch something else, propose a topic below.

2. Your key

A saved Watch belongs to a key. Keys are free and instant; we keep only a fingerprint of it, so copy it somewhere safe.

3. Save it (free)

Add a key first.

4. Your Watches: recall, see what changed, retire

Ask us to start keeping a topic

Need a topic we do not read yet? Commission it here, free. What happens next: we record it as a work order today; a matcher checks it daily against coverage we keep; we email you once when it's read, or with a plain status at 30 days. We give no date for coverage, because we do not have one.

Who uses a Watch

  • A maritime operator asks: Is passage through the Strait of Hormuz becoming more or less available, safe or costly, and why?
  • An energy desk asks: Is Gulf oil and gas supply at risk this month, and why?
  • An escalation analyst asks: Is the conflict between the United States and Iran escalating or easing?

A sample record: the Strait of Hormuz

This is one record we keep, shown as a sample of what a Watch reads. It is not a reading of your domain.

Agreement between publishers is not proof of the facts; a repeated error passes any count. Open “where from” on any claim to follow it to the original articles.

Strait of Hormuz

From the reporting ledger · newest report 22 Nov 2026

The ledger holds 4,998 sentences about the strait. Grouped by the event they report, they make 3,111 events: 33 corroborated, 113 reported by two, 2,965 single source. The ledger also holds 1,573 sentences the event rule could not place; each counts on its own sources. 93 of those events were carried by several reports that all ran in one outlet or in the same words; repeated is not corroborated, so each counts by its separate sources. 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. 7 claims were replaced by a later report since 3 Sep; they are kept, marked, and not counted here. 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 newest of the best-supported are below.

No new claim carried by three or more separate reports since 19 Nov.

  • First reported 19 Nov

    Tensions heightened further, the FCDO said, on Tuesday (17 November) when US forces struck an Iranian missile site on Qeshm Island in the Strait of Hormuz.

    Corroborated · 5 separate reports · 5 outlets · 6 sentences, one event

  • First reported 18 Nov

    "Earlier today, U.S. fighter aircraft used precision munitions to strike an Islamic Revolutionary Guard Corps (IRGC) missile launch site on Qeshm Island in self-defense," a U.S. official told Fox News.

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

  • First reported 18 Nov

    ADNOC L&S can confirm that one of its vessels was attacked while transiting the Strait of Hormuz on the evening of 17 November 2026.

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

  • 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

    A local Iranian official told the official IRNA news agency that the United States carried out several attacks on Iran's southern Island of Qeshm, located in the Strait of Hormuz, but "the situation is under control".

    Corroborated · 3 separate reports · 3 outlets · 3 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 21 Nov

    A commercial tanker caught fire after being struck by an unidentified projectile while travelling out of the Strait of Hormuz on Friday, Reuters reported.

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

  • First reported 20 Nov

    A Jordanian seafarer has gone missing after a tanker operated by the UAE’s Adnoc Logistics and Services (Adnoc L&S) came under attack in the Strait of Hormuz on November 17, 2026.

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

From the live Hormuz record: on Polymarket, “Will at least 10 ships transit the Strait of Hormuz on any day by November 30, 2026?” was priced at 20% when last seen (2026-11-12). That is Polymarket’s price, quoted as published. SigB publishes no probability of its own.

Set aside · 9 claims, each with why
  • Iraq is importing gasoline via Syrian port to bypass the closed Strait of Hormuz. Every report came from outlets that do not cover this subject.
  • An Iranian commercial ship was struck near Strait of Hormuz with 1 dead. Every report came from outlets that do not cover this subject.
  • One person was killed in a ship strike on the Strait of Hormuz. Every report came from outlets that do not cover this subject.

Replaced, never erased

When a later report replaces a claim, the record keeps the first one, marked, with the date and the reason.

From the Hormuz reporting ledger

Said on 27 Sept 2026: US President Donald Trump has rejected Iran’s latest proposal to reopen the Strait of Hormuz to shipping.

Replaced 22 Nov 2026 by: US President Donald Trump has rejected an Iranian proposal to reopen the Strait of Hormuz to commercial shipping within a week.

Why: A later report in the same thread replaced it. The first claim stays on the record, marked replaced. The ledger keeps 7 replaced claims this way.

See every claim in the Hormuz record

Watch

The sample record (Strait of Hormuz), as data

GET claims_hormuz.json → counts, and the state of each viewpoint's sorted reading (build time)

{
  "ledger": {
    "computedAt": "2026-11-22T03:39:34+00:00",
    "newestSeen": "2026-11-22",
    "counts": {
      "kernel": 4998,
      "frames": 1244,
      "retired": 16,
      "corroborated": 120,
      "two": 241,
      "single": 4637,
      "disputed": 0,
      "repeated": 93,
      "events": {
        "events": 3111,
        "corroborated": 33,
        "two": 113,
        "single": 2965,
        "couldNotMatch": 1573,
        "rule": "event@2"
      }
    },
    "countUnit": "event",
    "standing": {
      "unit": "event",
      "unitMeaning": "event: the sentences the ledger's event rule (named in its eventRule header) groups as reports of one incident, counted together under the origins rule",
      "rule": "event@2",
      "sentences": 4998,
      "ladder": {
        "unit": "event",
        "counted": 3111,
        "corroborated": 33,
        "reportedByTwo": 113,
        "singleSource": 2965,
        "couldNotMatch": 1573
      },
      "perSentence": {
        "unit": "sentence",
        "counted": 4998,
        "corroborated": 1,
        "reportedByTwo": 5,
        "singleSource": 4992,
        "notStated": 0
      },
      "fields": {
        "standing": "eventStatus",
        "separateReports": "eventOriginCount",
        "outlets": "eventOutletCount",
        "repetition": "eventRepetition",
        "eventKey": "eventKey",
        "sentencesInEvent": "eventSize",
        "match": "eventMatch"
      },
      "statement": "A kernel row that carries eventOriginCount is counted by its event (the rule named in the ledger's eventRule header): its standing is eventStatus and its count eventOriginCount, exactly as the page reads it. Its per-sentence status and originCount are kept beside them, unchanged. A row without the event fields is counted by its sentence: status and originCount. A row with disputedWith reads Contested whatever its count. A row whose eventMatch is could-not-match keeps its sentence count: could not match is not single source."
    }
  },
  "viewpoints": [
    {
      "viewpoint": "Maritime operator",
      "asks": "Is passage through the Strait of Hormuz becoming more or less available, safe or costly, and why?",
      "sortedReading": {
        "state": "cannot-measure",
        "reason": "Sorting for this viewpoint is not published yet. It is built every day and checked against what happens next before we publish it. Until then nothing on this page is placed for one viewpoint over another; the claims below are the same for every reader."
      }
    },
    {
      "viewpoint": "Energy desk",
      "asks": "Is Gulf oil and gas supply at risk this month, and why?",
      "sortedReading": {
        "state": "cannot-measure",
        "reason": "Sorting for this viewpoint is not published yet. It is built every day and checked against what happens next before we publish it. Until then nothing on this page is placed for one viewpoint over another; the claims below are the same for every reader."
      }
    },
    {
      "viewpoint": "Escalation analyst",
      "asks": "Is the conflict between the United States and Iran escalating or easing?",
      "sortedReading": {
        "state": "cannot-measure",
        "reason": "Sorting for this viewpoint is not published yet. It is built every day and checked against what happens next before we publish it. Until then nothing on this page is placed for one viewpoint over another; the claims below are the same for every reader."
      }
    }
  ]
}

The ledger's own counts. No viewpoint has a published sorted reading yet, and each says so instead of showing a placement.

GET claims_hormuz.json → kernel[newest corroborated] where-from, folded one level

{
  "claim": "Tensions heightened further, the FCDO said, on Tuesday (17 November) when US forces struck an Iranian missile site on Qeshm Island in the Strait of Hormuz.",
  "status": "single-source",
  "independentChains": 1,
  "repetition": null,
  "standing": {
    "unit": "event",
    "level": "corroborated",
    "word": "Corroborated",
    "separateReports": 5,
    "outlets": 5,
    "repeated": null,
    "eventKey": "ev1:420cd7458cca96d1",
    "sentencesInEvent": 6,
    "eventMatch": "matched"
  },
  "whereFrom": {
    "level": "where from",
    "label": "Where from",
    "relations": [
      {
        "role": "part of",
        "members": [
          "/event/strait-of-hormuz/",
          "/record/"
        ]
      }
    ],
    "children": [
      {
        "level": "report",
        "label": "TTG · first seen 19 Nov",
        "children": {
          "count": 1,
          "unfold": "expand=+1"
        }
      }
    ]
  }
}

The newest corroborated claim in the Hormuz reporting ledger, with its where-from tree folded below the first level. Its standing and counts are the ones this page shows, in the unit named (one sentence, or the event its sentences report); status and independentChains are the sentence's own, kept beside them. Each level names how to unfold the next, and every branch ends at a source link or a stated reason.