A sourced, current record of what is happening in your domain.The same record, as data.

We show where sources agree and where they disagree, and we say what we have not read yet.

Current means maintained, not live: every record states how fresh it is, and says so when a source is behind.

Start a WatchOpen the public record

For machines: the machine front door

Get the daily brief by email.

One email each morning: what changed in the record, with sources. Free. Leave any time with one click.

On the Hormuz record, 12 of 12 published claims link straight to the source they came from, measured 24 Oct. That rate covers the record's published summary only; the reporting ledger behind it holds 2,984 sentences and is not part of this count.

Updated in batches, not live: this page was built 25 Oct from a record dated 24 Oct (newest news report 24 Oct; newest official notice 24 Oct).

Open the Hormuz record

For machines

Every page on this site has a machine form. Switch back to Person at any time.

Strait of Hormuz

From the reporting ledger · newest report 24 Oct 2026

The ledger holds 2,984 sentences about the strait. Grouped by the event they report, they make 1,853 events: 13 corroborated, 61 reported by two, 1,779 single source. The ledger also holds 968 sentences the event rule could not place; each counts on its own sources. 57 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. 2 claims were replaced by a later report since 3 Sep; they are kept, marked, and not counted here. The newest of the best-supported are below.

No new claim carried by three or more separate reports since 17 Oct.

  • First reported 17 Oct

    Ten of the attacks occurred in the Strait of Hormuz, one in the Persian Gulf and one in the Gulf of Oman.

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

  • First reported 12 Oct

    Attacks on commercial shipping are spreading across the Gulf region, with two Indian seafarers missing after a drone struck a tanker off Oman on Sunday and another tanker hit by a projectile while exiting the Strait of Hormuz.

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

  • First reported 8 Oct

    A number of casualties have been reported after a tanker sailing off the north coast of Qatar was struck by multiple projectiles, the United Kingdom Maritime Trade Operations (UKMTO) agency has announced.

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

  • First reported 8 Oct

    Iranian attacks on tankers hit their highest level last week of any week since the U.S.-Iran war began, with the increased offensive coming shortly after shipping through Hormuz briefly touched pre-war levels in September.

    Corroborated · 3 separate reports · 5 outlets · 1 more carries the same wire story · 4 sentences, one event

From the live Hormuz record: on Polymarket, “Will there be no Hormuz agreement?” was priced at 93% when last seen (2026-10-24). 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.

Open the full Hormuz Watch

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

{
  "schema": "sb.truth-record.v1",
  "slug": "hormuz",
  "currency": {
    "state": "not-reliably-current",
    "asOf": "2026-10-24"
  },
  "claims": {
    "count": 12
  },
  "primaryDocuments": {
    "count": 3
  },
  "changeLog": {
    "count": 40,
    "newest": {
      "at": "2026-10-24",
      "what": "sections changed"
    }
  },
  "marketSensor": {
    "question": "Will there be no Hormuz agreement?",
    "venue": "polymarket",
    "pricePct": 93,
    "priceSeenAt": "2026-10-24",
    "note": "cited, never a probability of ours"
  }
}

A real slice of the maintained Hormuz record, read from the same file this page was built from. The Person view's reading comes from the same record's reporting ledger.

The world today

Newly corroborated, by subject: claims that reached three or more separate reports, with how many each subject holds.

Record through 25 Oct.

Every section of today’s record

One record, open to inspection

The Hormuz record, as it stands today

The record is rebuilt from our data on every deploy. News reporting, our own coverage count and prediction-market prices are kept as separate layers, each with its source. Software reads the same record over MCP.

How long we’ve kept it

153 days

Tracked as an event since 2026-05-24

In our daily read of 2026-10-24, it came up 159 times across 41 of the subject areas we cover.

Our coverage right now

rising

Today: 20% above its 3-week baseline in how much our sources wrote about it, not whether passage is safer.

That measures our attention, meaning how much our sources write about the strait, not the strait’s condition.

Prediction markets on it

33 markets

Questions we have cited since 2026-05-24. Their prices are the markets’ own, never our estimate.

Inspect the full record: every layer, every receipt

Replaced, never erased

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

See every claim in the Hormuz record

The ledger keeps 2 replaced claims, each marked, and none is about the strait’s own reporting, so none is shown here. The record’s change log counts every replacement and shows the newest.

Built to be read by software

MCP and HTTP, versioned schema, limits published.

Machine documentation

tools/call get_topic_record {"subject":"hormuz"}

Returns the same record this page is built from: its claims, their sources and dates, and how fresh each part is.

Who it serves

Who reads it

The same record answers different questions. Three people who read the Hormuz record, and what each one asks of it:

  • 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?

AI systems & agents

Current entity and event state over MCP and REST. Every published claim names where it came from; where a direct link to the source exists, the record carries it. No key for reads.

The machine front door

Analysts & desks

Daily briefs, the wire, and grounded answers. On the Hormuz record, 12 of 12 published claims link straight to the source they came from, measured 24 Oct. That rate covers the record's published summary only; the reporting ledger behind it holds 2,984 sentences and is not part of this count.

Pick a desk · Ask a question

Operators & teams

A private desk watches the concerns your team cannot afford to stop watching, delivered into your workflow.

Check whether your system is a fit

Send your own AI to look around

Have your assistant read our machine door and tell you what we do, what it costs and whether it fits what you need. You do not need an account.

Look at SigB (Signal Bureau) for me. Start at https://sigb.ai/llms.txt, then its MCP server at https://api.signalbureau.ai/api/mcp (streamable HTTP, no key needed to read; a free key at POST /api/keys lets you ask). Call start_here first. Tell me what it does, what it costs, and whether it fits what I need.

To ask about SigB yourself, use Docking Control, our desk for questions about us.

Private Desk Pilot

$5,000: one-time · 30 days · ends with a written acceptance report

Start the pilot (opens in a new tab) · All plans and prices · Or start with a conversation

Today’s brief · Oct 24, 2026 · updated 2:42 PM PT

Today’s brief is published.

Vivek Ramaswamy: 18 reports across 9 subject areas, among them US Elections 2028, Intelligence, Uncategorised Auto Scraped Feeds. NYT: “How Vivek Ramaswamy’s Ruthless Ad in Ohio Divided Republicans” The Dispatch: “Vivek Ramaswamy’s Vicious Attack Ad May Backfire”

Read the full brief, including where the money and the news disagree · Ask about anything

We keep a source-traced record. The market prices in it are one labeled sensor: quoted as the markets’ own and graded in public against how events resolve: the calibration record.

The entity count is a published cut of the most-covered names. The full set we track is larger. The daily record lists what we read each day.

How a reading is made

  1. Sources. News, filings and official notices are read every day. See what we read.
  2. Relate. Each report is tied to who did what, where and when.
  3. The record. Each claim is kept with every source that carried it.
  4. Readings. A Watch shows the part of the record you asked about, newest first, with how well each claim is supported.
  5. Corrections. A replaced claim is marked, never erased.

The five steps in detail · The API documentation

No affiliation with Signal AI Ltd (London) or any similarly named service.