Patch brief · source: organizer feed

Patch window key dates added to the format calendar

The format calendar now folds in patch day-of. A reader can see at a glance whether a series was played before or after a major patch. The calendar is published with each cycle.

Read the format calendar Patch literacy guide

What changed

A new column in the format calendar

The format calendar used to publish stage dates, format versions and prize pools. It now also publishes a "patch day-of" marker for each stage. The marker is a single letter — B for before patch, A for after patch, X for cross-patch window. The marker is verified against the organizer feed and the patch publisher.

Before patch

The series is played before the major patch lands. The desk labels the read as "pre-patch meta". The reader should treat the read as a snapshot, not a forecast.

After patch

The series is played after the major patch lands. The desk labels the read as "post-patch meta". The reader should treat the read as a verified first read.

Cross-patch

The series spans the patch window. The desk labels the read as "cross-patch window". The reader should treat the read as a transitional meta.

No marker

The series is played outside any major patch window. The desk labels the read as "stable meta". The reader should treat the read as a baseline.

Competitive impact

How the marker changes the read

The marker is not a meta call. The marker is a verification label. The desk still labels the brief with a source class and a competitive impact note. The marker is an additional label, not a replacement.

The marker's value is in the cumulative read. A team that plays three consecutive stages in the "before patch" marker is in a different competitive posture than a team that plays three consecutive stages in the "after patch" marker. The desk has always published the underlying facts; the marker is a presentation layer that makes the facts easier to compare.

The marker is also a discipline for the desk. A marker that is not verified against the patch publisher does not get published. The desk would rather publish a stage without a marker than publish a stage with an unverified marker. The marker inherits the desk's editorial standard: the strongest source class wins, and the calendar is updated in place when a correction lands.

The marker is published at the same cadence as the format calendar. The marker is updated in place when the patch publisher publishes a revised patch window. A correction is published as a stand-alone note if the marker is reversed. The reader can compare two calendars without re-reading the stage brief.

Stages touched

The first cycle under the marker

Stage 1

Marked as "before patch". The stage is played before the major patch lands. The desk publishes the read as a pre-patch meta snapshot. The next public patch window is expected before the next stage.

Stage 2

Marked as "cross-patch". The stage spans the patch window. The desk publishes the read as a transitional meta. The reader should weigh the read against the patch publisher's revised window.

Stage 3

Marked as "after patch". The stage is played after the major patch lands. The desk publishes the read as a verified first read. The reader can use the read to anticipate the next public series.

Patch literacy

How the desk reads a patch window

A patch window is the period between the patch publisher's announcement and the first public series played under the new patch. The window can be a single day for a minor patch, or two to three weeks for a major patch.

The desk reads a patch window in three signals. First, the bootcamp signal — the period between the patch landing and the first public series. Second, the first public series signal — the first series played under the new patch, which the desk labels as a verified first read. Third, the post-match debrief signal — the period after the first public series, when the desk can compare the brief against the on-stage read.

The marker folds the bootcamp signal and the first public series signal into the calendar. The post-match debrief signal is published as a stand-alone note. The three signals are not collapsed into a single label. Each signal is published with its source class and its verification timestamp.

The reader who wants the marker can read the calendar at a glance. The reader who wants the underlying signal stack can read the patch brief for each stage. The desk publishes both — the marker for the at-a-glance read, and the brief for the signal stack.

What to watch next

Four things to verify before the next cycle

01Verify the patch publisher's revised patch window

02Verify the stage brief against the on-stage meta

03Verify the marker against the bootcamp signal

04Publish the next format calendar update

FAQ

Patch window marker, plain answers

What is a patch day-of marker?

A patch day-of marker is a single-letter label on a stage that indicates whether the series was played before, after, or across a major patch window. The marker is verified against the patch publisher.

How long does a marker stay attached?

A marker stays attached until the next patch window. A correction is published as a stand-alone note if the marker is reversed.

Does the marker predict the meta?

No. The marker is a verification artefact, not a meta call. The desk labels the brief with a source class and a competitive impact note. The reader weighs the read.

What happens if the patch publisher moves the window?

The desk publishes a correction as a stand-alone note. The calendar is updated in place with a visible "corrected" flag and a link to the correction.

How the desk verified the marker

The verification protocol for a patch day-of marker

The desk verifies a patch day-of marker against three sources. The patch publisher is the canonical source. The organizer feed is the secondary source. The team channel is the tertiary source. The desk applies the strongest source class that is available at the moment of the marker.

The patch publisher publishes the patch window as a date range. The desk reads the date range and compares it against the stage date. A stage that falls inside the date range is marked "cross-patch". A stage that falls before the date range is marked "before patch". A stage that falls after the date range is marked "after patch".

The organizer feed publishes the stage date and the stage format. The desk reads the organizer feed and confirms the stage date against the patch publisher. If the organizer feed contradicts the patch publisher, the desk publishes a correction as a stand-alone note. The desk does not silently rewrite the marker.

The team channel is read for bootcamp activity. A team channel that announces a bootcamp before the patch lands is labelled as "bootcamp confirmed". The bootcamp label is a verification artefact, not a prediction. The desk does not infer meta fit from the bootcamp label.

The three sources are not collapsed into a single label. Each source is published with its timestamp and its verification window. The marker is a presentation layer that folds the three sources into a single label. The reader can drill into the underlying sources at any time.

The desk publishes the verification protocol alongside the marker. The protocol is a stand-alone note that lists the three sources, the verification windows and the source hierarchy. The reader can compare two protocols without re-reading the underlying sources.

The marker and the patch brief

How the marker and the patch brief fit together

The marker and the patch brief are two parts of the same read. The marker is the at-a-glance label on the format calendar. The patch brief is the underlying signal stack. The desk publishes both. A reader who only has time for the at-a-glance read can read the marker. A reader who wants the signal stack can read the patch brief.

The marker and the patch brief are not duplicates. The marker is a single letter. The patch brief is three signals — bootcamp, first public series, post-match debrief. The reader who reads the marker without the patch brief gets a verified label but not the underlying signals. The reader who reads the patch brief without the marker gets the signals but not the at-a-glance label. The desk recommends both reads.

The marker is published at the same cadence as the format calendar. The patch brief is published at the same cadence as the patch window. The two cadences are not the same. The marker is updated in place when the patch publisher publishes a revised patch window. The patch brief is updated in place when the bootcamp signal or the first public series signal changes.

The desk publishes a stand-alone note when the marker and the patch brief disagree. The note lists the marker, the patch brief, the source classes and the verification timestamps. The reader can compare two notes without re-reading the underlying marker or patch brief. The desk does not silently rewrite either the marker or the patch brief.

The two-part read is the desk's commitment to the reader. The desk does not endorse a single read. The desk publishes the marker for the at-a-glance reader and the patch brief for the signal-stack reader. The reader decides which read matches the moment.