Reader depth
Reading the patch workshop with three passes
Three habits the desk follows when reading a patch on the day it publishes.
The first habit is to read the publisher changelog in full on the publication day. The publisher changelog is the lowest editorial lift — it is the publisher's own words describing what changed. The desk transcribes the changelog rows into the patch workshop left page and notes any items the changelog omits. The desk does not paraphrase the changelog; the workshop left page is the publisher's text.
The second habit is to read the operator stage cards on the same day. The operator publishes the stage cards that go live under the new patch. The desk transcribes the per-stage composition rules and the operator's stated match windows into the workshop right page, and notes where the operator deviates from the publisher changelog. Where the publisher and operator disagree, the desk publishes the disagreement in the workshop right page rather than pick one side.
The third habit is to read the role notebook against the patch and the operator rules on the same day. The role notebook is the desk's editorial frame for what each role is asked to do. The third pass asks: under the new patch, does the role responsibility change for any of the four roles? If yes, the desk publishes the change as a dated note on the role notebook. If no, the desk publishes a "no change observed" note on the workshop.
Where the desk diverges from coverage that mirrors trade-press reads is on the three-pass discipline. Trade press will sometimes publish a single-pass read of the patch that does not separate publisher, operator and role layers. The desk does not. The three passes are documented in the workshop and reproduced on the guides route so a reader who follows the desk for a season sees the same three-pass discipline on every patch.
The desk also treats the patch workshop as a working document. Rows move up the patch-ladder as sources confirm; rows that fall off the publisher page get removed, not retained as a footnote. The workshop 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.