Where a future date is allowed to come from.
Every date on the calendar comes from a publisher that states its own schedule. Nothing on it is worked out from how often a publisher has released in the past, because a cadence is a measurement of history and putting it on a future date turns it into a prediction.
The rule
One sentence, and the whole calendar follows from it.
Publishers that state their own future release dates, and the releases on this site's record that each one carries. A release is listed here ONLY when a publisher publishes its schedule itself. Nothing on the calendar is ever inferred from how often a publisher has released in the past: an observed cadence is a measurement of history, and putting it on a future date turns it into a prediction. See data/record-gaps.json for what is missing and why.
1 publisher carrying 1 release, and 1 probed and refused. A short list is what this rule produces, and the refusals below are the reason it is short.
The publishers that state their own dates
Each one links to the schedule page the dates are read from.
| Publisher | Release | What it carries here | Schedule |
|---|---|---|---|
| U.S. Census Bureau | Manufacturers' Shipments, Inventories and Orders, full report | US new orders, computers and electronics | the publisher’s schedule |
U.S. Census Bureau. One table, id=calendar, server rendered, one row per scheduled release for the whole calendar year. Each row carries the date twice: as prose in the visible cell and as a hidden key of the form A<YYYYMMDDHHMM>. The collector reads the key and verifies it against the prose, because two independent encodings that disagree mean the page changed shape and the parse can no longer be trusted. Licence: Public domain, U.S. federal government work.
Probed, and not used
A publisher that does state its dates, in a form this record will not read.
Federal Reserve Board
G.17 Industrial Production, the release behind IPG3344S and IPG334S Probed 2026-08-16. the source
The feed is valid RSS 1.0 and carries past releases. Future dates appear only inside the prose of an annual announcement item, as a sentence listing them. Reading dates out of a sentence is inference about what the sentence means, and one wording change would silently produce wrong dates on a calendar. Recorded as a gap rather than parsed.
What would close it. A structured schedule page or feed from the Board, or an explicit decision to hand-enter the dates from the annual announcement with its URL as the source.
This is the page working as intended. A calendar with two publishers on it and no explanation reads as a calendar nobody finished. A calendar with one publisher and a written reason for the second one’s absence is a statement about what this record will and will not do.