Organisation identity, written from the outside in

The team identity corridor holds the working samples. The featured main is the long-form dossier; the framed identity cards are the short-form reads. Where the roster is older than two seasons, the slot is left open and the desk says so.

The region filter is the first editorial ask. The desk reads the operator channel and the broadcast partner to record the region. Where the region is unknown, the row is marked as awaiting verification.

Organisations move. Acquisitions, rebrands, academy squads and tier shifts are part of the team story. The desk records each lifecycle event with a source date; the editorial ask is the lifecycle, not the scoreboard.

Acquisitions

Where an organisation acquires a roster slot or a regional qualifier, the desk records the source, the date and the brief contract version. Acquisitions are listed on the operator channel.

Rebrands

Where an organisation rebrands, the desk records the old name, the new name and the source date. The history is preserved in the past-edition register.

Academy squads

Academy squads are read as the developmental ladder. The desk records the academy roster as a separate line, with the source date and the operator channel.

The desk writes to the source it holds. Where the roster is publicly confirmed, the slot is named. Where the slot is open, the slot is left open. The desk never invents a roster and never borrows a roster from a different organisation.

Source tier

Tier-one source is the operator channel. Tier-two source is the licensed broadcast partner. Tier-three source is the team channel. Anything below tier three is labelled as awaiting verification.

Slot policy

A slot is named when the source is dated within the current season. A slot is left open when the source is older than two seasons. The editorial ask is the policy, not the result.

The team corridor is sourced from the operator channel first, the licensed broadcast partner second, and the team channel third. The tier-one source is the only source for the team identity.

The team corridor is one of three interconnected desks. The player role gallery reads the same roster and adds the role story. The match preview desk reads the fixture and adds the reasoning layer.

The desk writes a dossier in three passes. The first pass is the operator channel; the second pass is the licensed broadcast partner; the third pass is the team channel. The three passes are the editorial cadence.

First pass

The first pass reads the operator channel. The operator channel publishes the source date, the region, the track. The reader is invited to read the operator channel first, before the broadcast partner.

Second pass

The second pass reads the licensed broadcast partner. The broadcast partner publishes the schedule, the regional mirror, the caption feed. The reader is invited to read the broadcast partner second, while the operator channel is still fresh.

Third pass

The third pass reads the team channel. The team channel publishes the roster, the tier note, the brief statement. The reader is invited to read the team channel third, after the broadcast partner.

Three lifecycle events sit on top of the desk's editorial cadence. The first is the acquisition; the second is the rebrand; the third is the academy push. Each event is a working note, not a forecast.

Acquisition

Where an organisation acquires a roster slot or a regional qualifier, the desk records the source, the date, the brief contract version. The acquisition is one event; the desk accepts corrections and additions through the contact page.

Rebrand

Where an organisation rebrands, the desk records the old name, the new name, the source date. The rebrand is one event; the desk invites the reader to read the history before the present.

Academy push

Where an organisation publishes an academy roster, the desk records the academy roster as a separate line, with the source date, the operator channel. The academy push is one event; the desk invites the reader to read the developmental ladder.

The dossier is rebuilt for every organisation. Each row carries the organisation name, the region, the track, the last verified roster, the source date. The mechanics are simple and public: the reader is invited to verify the source and judge the slot.

Source tier

Tier-one source is the operator channel. Tier-two source is the licensed broadcast partner. Tier-three source is the team channel. Anything below tier three is labelled as awaiting verification.

Slot policy

A slot is named when the source is dated within the current season. A slot is left open when the source is older than two seasons. The editorial ask is the policy, not the result.

Lifecycle events

Lifecycle events are recorded on the past-edition register with the source date. The reader is invited to read the lifecycle before the present.

Region filter

The region filter is the first editorial ask. The desk reads the operator channel and the broadcast partner to record the region. Where the region is unknown, the row is marked as awaiting verification.

The team corridor runs on three writing rules. Rule one: a slot is named when the source is dated within the current season. Rule two: a slot is left open when the source is older than two seasons. Rule three: the editorial ask is the policy, not the result.

Rule one

A slot is named when the source is dated within the current season. The reader is invited to read the source date, then read the slot. The source is the rule; the slot is the editorial ask.

Rule two

A slot is left open when the source is older than two seasons. The reader is invited to read the source date, then read the open slot. The source is the rule; the open slot is the editorial ask.

Rule three

The editorial ask is the policy, not the result. The reader is invited to read the policy, then read the slot. The policy is the rule; the slot is the editorial ask.

Past-edition register

The past-edition register holds the historical record. The reader is invited to read the register, then read the lifecycle. The register is the source; the lifecycle is the editorial ask.

The team corridor reads regional operators as distinct editorial streams. Each region has its own operator channel; the broadcast partner publishes the regional mirror. The desk reads the operator channel first, the broadcast partner second.

EU

The European operator channel publishes the source date, the rule book version, the patch version. The broadcast partner publishes the schedule, the regional mirror, the caption feed. The reader is invited to follow the EU desk on the operator channel.

NA

The North American operator channel publishes the source date, the rule book version, the patch version. The broadcast partner publishes the schedule, the regional mirror, the caption feed. The reader is invited to follow the NA desk on the operator channel.

APAC

The Asia-Pacific operator channel publishes the source date, the rule book version, the patch version. The broadcast partner publishes the schedule, the regional mirror, the caption feed. The reader is invited to follow the APAC desk on the operator channel.

Global

The global operator channel publishes the source date, the rule book version, the patch version. The broadcast partner publishes the schedule, the regional mirror, the caption feed. The reader is invited to follow the global desk on the operator channel.

Reader questions, answered plainly