Streaming access note added to viewing matrix

The first habit is to verify the operator help page on the same day as the streaming access update. The desk verified the operator help page at 17:14 UTC. The editorial practice is to verify any source change on a Tier-1 page on the same day the change is filed, on the basis that immediate verification gives the desk enough certainty to publish a confirmed entry.

The second habit is to log the verification timestamps on the dispatch. The dispatch line names the source the desk consulted and the date the desk verified the source. The practice protects the reader from seeing a date-less dispatch line and protects the desk from a corrections cycle that is harder than the original publication. The verification timestamps are also useful internally when the desk re-reads the operator help page on the next weekday morning.

The third habit is to treat viewing-matrix updates as routine, not as events. The matrix is rebuilt from operator pages each weekday morning; updates are posted on the dispatch stream when an operator page changes the access tier of an existing row or adds a new region row. The editorial practice is to publish the matrix update in the dispatch stream rather than as a standalone post, so the matrix and the dispatch stream stay consistent.

Where the desk diverges from coverage that mirrors trade-press reads is on the routine-event distinction. Trade press will sometimes publish a viewing-matrix update as a standalone post. The desk does not. The desk publishes the matrix update as a dispatch stream entry and updates the matrix itself, keeping the two channels consistent. The discipline is sometimes slower to operate; it is always more honest to read.

The desk also treats the streaming access update as a working document. Rows move up the access-ladder as sources confirm; rows that fall off the publisher or operator page get removed, not retained as a footnote. The access is rebuilt from publisher and operator pages only. A row the desk kept for "tracking purposes" is a row the reader cannot verify, so the desk removes rather than retains. This is sometimes the slower choice; it is always the more honest choice.

Editorial cycle: weekday-morning source-scan, weekday-afternoon narrative-edit, weekly patch workshop. Verification timestamps on the dispatch stream.

A worked example of the viewing-matrix update in practice. The desk verified the operator help page at 17:14 UTC. The new row reflects the access tier the operator named on the help page: an open live stream on Partner B, a sub-only replay, with the access tier listed as 'open with sign-up'. The desk updated the viewing matrix with the new row.

Where the dispatch covers the viewing-matrix cadence. The viewing matrix is rebuilt from operator pages each weekday morning. The matrix is a working document; the desk updates the matrix when an operator page changes the access tier of an existing row or adds a new region row. The cadence is documented on /methods/.

Where the dispatch covers the next streaming access update. The desk is reading the LATAM · PT row against the new ES row to check whether the operator published those two regions together or separately. If the operator published them together, the desk will publish a tier-change dispatch if a tier differs. If separately, the desk will continue to update one row at a time.

Where the dispatch covers the editorial framing of viewing updates. The desk treats viewing-matrix updates as routine, not as events. The matrix is rebuilt from operator pages each weekday morning; updates are posted on the dispatch stream when an operator page changes the access tier of an existing row or adds a new region row. The editorial practice is to publish the matrix update in the dispatch stream rather than as a standalone post, so the matrix and the dispatch stream stay consistent.

What the desk will do if a streaming access tier changes. The desk will publish a follow-up dispatch on the dispatch stream with the tier change and the date the change was published. The desk's editorial practice is to escalate substantive changes to the dispatch stream regardless of source tier. The tier change is logged on the dispatch stream and the viewing matrix.