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 8 Nov 2026

The ledger holds 3,882 sentences about the strait. Grouped by the event they report, they make 2,394 events: 18 corroborated, 76 reported by two, 2,300 single source. The ledger also holds 1,267 sentences the event rule could not place; each counts on its own sources. 73 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. 4 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.

  • First reported 6 Nov

    The incident took place about 50 nautical miles north of Madinat ash Shamal at 2320 GMT on November 4, 2026, according to the United Kingdom Maritime Trade Operations (UKMTO), which said it had received a verified report.

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

  • First reported 4 Nov

    Tensions in the Middle East remained in focus after US officials reported conducting “defensive” strikes on Iran’s Qeshm Island, which targeted surface-to-air missiles.

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

  • First reported 3 Nov

    Prices initially rebounded overnight after reports of U.S. strikes on Iran's Qeshm Island, near the Strait of Hormuz, before reversing sharply Tuesday morning.

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

  • First reported 3 Nov

    According to the report, in one exchange, Iran’s Islamic Revolutionary Guard Corps fired a surface-to-air missile at a US warplane, which fired back in self-defence.

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

  • First reported 3 Nov

    At the same time, American forces continued their effective naval blockade against Iran, depriving the regime of billions of dollars in revenue.

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

  • First reported 31 Oct

    Iran's Revolutionary Guard has claimed that four oil tankers struck naval mines and caught fire in the Strait of Hormuz on Friday, according to reports by the Associated Press and Reuters.

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

  • First reported 8 Nov

    - Iran reports tanker fires: The IRGC said two oil tankers caught fire after hitting naval mines in the Strait of Hormuz.

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

  • First reported 8 Nov

    "Since the early hours of this morning, three non-compliant tankers have exploded and caught fire while they were sailing in the illegal channel in the Strait of Hormuz," the Islamic Revolutionary Guard Corps said in a statement.

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

From the live Hormuz record: on Polymarket, “Will there be between 0 and 4 average daily transits of the Strait of Hormuz on November 30?” was priced at 40% when last seen (2026-11-08). 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 8 Nov 2026 by: The United States had yet to publicly respond on Saturday after Iran offered a plan to reopen the strategic Strait of Hormuz, though reports indicated that President Donald Trump had rejected the proposal.

Why: A later report in the same thread replaced it. The first claim stays on the record, marked replaced. The ledger keeps 4 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-08T15:48:13+00:00",
    "newestSeen": "2026-11-08",
    "counts": {
      "kernel": 3882,
      "frames": 982,
      "retired": 13,
      "corroborated": 69,
      "two": 165,
      "single": 3648,
      "disputed": 0,
      "repeated": 73,
      "events": {
        "events": 2394,
        "corroborated": 18,
        "two": 76,
        "single": 2300,
        "couldNotMatch": 1267,
        "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": 3882,
      "ladder": {
        "unit": "event",
        "counted": 2394,
        "corroborated": 18,
        "reportedByTwo": 76,
        "singleSource": 2300,
        "couldNotMatch": 1267
      },
      "perSentence": {
        "unit": "sentence",
        "counted": 3882,
        "corroborated": 1,
        "reportedByTwo": 5,
        "singleSource": 3876,
        "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": "The incident took place about 50 nautical miles north of Madinat ash Shamal at 2320 GMT on November 4, 2026, according to the United Kingdom Maritime Trade Operations (UKMTO), which said it had received a verified report.",
  "status": "single-source",
  "independentChains": 1,
  "repetition": null,
  "standing": {
    "unit": "event",
    "level": "corroborated",
    "word": "Corroborated",
    "separateReports": 3,
    "outlets": 3,
    "repeated": null,
    "eventKey": "ev1:0325fd3c12ccb476",
    "sentencesInEvent": 3,
    "eventMatch": "matched"
  },
  "whereFrom": {
    "level": "where from",
    "label": "Where from",
    "relations": [
      {
        "role": "part of",
        "members": [
          "/event/strait-of-hormuz/",
          "/record/"
        ]
      }
    ],
    "children": [
      {
        "level": "report",
        "label": "Marine Insight · first seen 6 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.