IMF PortWatch has a Hormuz disruption page. The fetched page body did not have Hormuz data. It had the familiar modern compromise: metadata and a JavaScript shell, with the numbers living behind the application. [1]

That is why this brief belongs beside the paper's earlier insistence that EIA source discipline move past This Week in Petroleum. The same rule governs PortWatch. If the body cannot be reproduced, screenshots and search snippets cannot become a table. The Hormuz protocol story is already too dependent on assertions.

The backup source is not useless. IER's summary of EIA material gives context for flows and replacement routing. [2] But it does not turn the PortWatch dashboard into a cited dataset, and it does not answer which vessels, dates or definitions the dashboard uses.

Source discipline is not anti-data. It is the only way to keep data from becoming theater. Hormuz may be moving through dashboards. Readers still need an export, an API, or a page body the paper can quote.

-- HENDRIK VAN DER BERG, Brussels