Editorial photograph of the Sixer matchday desk at 09:00 IST — a single editor's chair pulled up to a wooden surface stacked with the day's bound pages, a fountain pen resting on an open ledger, daylight on the newsroom.

Pages · cadence

The real impact of stale Pages on a fantasy-cricket reader — how the Sixer desk keeps 22 pages current

At 18:55 IST on a Tuesday a reader notices the desk's Pages index lists the same captain call, the same boundary map, and the same tournament window it listed the day before — and assumes nothing has moved. The misread is the story. Sixer runs a written refresh cycle across 22 working pages, and the cycle decides what the reader sees on the next visit. This explainer walks the cycle end to end: the daily sweep, the four moments a page is rewritten, the supersession rule, and the rows that are deliberately frozen.

Get Started Compare Options

22 working pages on a single published cadence

4 rewrite moments trigger a new dated edit

0 current events, live source changes or new captain calls claimed in this explainer

CA 01 · The refresh question

A reader who reopens a Sixer Page at 18:55 IST may assume nothing has moved.

The misread is the story. Sixer's 22 working pages run on a written cadence; the cadence decides what the reader sees on the next visit, what gets rewritten, and what stays put on purpose. Reading the cadence is reading the desk — a page that hasn't moved in two days isn't a dead page; it is a page that hasn't received a fresh fact the desk can name.

Why a "quiet page" is not a "dead page"

A page that has not been edited in 48 hours is not a page the desk has abandoned. Sixer's refresh cycle only writes a new dated row when a fresh, named fact has arrived. The desk does not pad a quiet day with re-stated edits; the desk leaves the page alone and lets the chronology grow in one direction.

Why a fresh-looking page is not a "fresh page"

A page that has been edited in the last four hours is not automatically a fresh page. The desk files a dated row whenever one of the four rewrite moments lands — a toss call, an XI sheet, an injury note, or a correction — and the row carries the source name on the same line as the fact. The freshness comes from the source, not from the timestamp alone.

Why the cadence matters to a reader

The cadence matters because a fantasy-cricket reader's reading time is finite. A reader who knows the daily cycle knows when the boundary map will refresh, when the captain call will update, and when the live desk is most likely to file a new edit. Reading the cadence is reading the desk's editorial schedule.

What the cadence does not claim

The cadence is bounded and evergreen. The desk does not claim a current event, a current source change, a live correction, a live score or a current captain pick in this explainer. The labelled chronology on the chapter rail is a labelled example; the cadence itself is the durable layer.

How to read the cadence without scrolling

A reader can read the cadence from the masthead alone. The masthead carries the edition stamp, the filed time in IST, and the chapter kicker. A masthead that has not changed in 48 hours is a masthead for a page the desk has deliberately left quiet; a masthead that has changed three times in a day is a masthead for a page the desk has rewritten three times.

Why the cadence is published, not implied

Sixer publishes the cadence so a reader can plan a visit. The desk could keep the cycle internal; the desk publishes the cycle because the cadence itself is part of the editorial value. A reader who knows when a page will refresh reads the desk on the reader's schedule, not the desk's.

CA 02 · The daily cycle

The day runs two editorial passes and an open inbox.

The Sixer matchday desk runs on a written two-pass cycle — a pre-toss pass at 16:00 IST and a post-toss pass at 22:00 IST — with an open inbox at [email protected] for tips and corrections between the passes. The cycle is the same on every matchday the desk covers; the cycle shortens on a quiet day but the two passes still run.

The pre-toss pass at 16:00 IST

The pre-toss pass files the morning's named facts before the toss call lands. The pass rewrites the boundary map, the captain weighting, the venue tag and the live desk timestamp. The pre-toss pass is the desk's first editorial sweep of the matchday.

The post-toss pass at 22:00 IST

The post-toss pass files the toss call, the confirmed XI sheets and any late injury notes. The pass rewrites the live desk, the teams page and the captain page. The post-toss pass is the desk's final editorial sweep of the matchday before play starts.

The open inbox between passes

Between the two passes the desk runs an open inbox at [email protected]. A correction, a tip or a source filing that lands between the two passes is read, verified against the desk's source list, and either filed as a rolling entry or queued for the next pass.

What runs on a quiet day

On a quiet day — a non-matchday, an off-season day or a rained-out day — the two passes still run, but each pass writes fewer rows. The masthead changes once, the live desk carries a single short note, and the methodology and archive pages are not touched. A quiet-day cycle is shorter, not absent.

What runs on a back-to-back day

On a back-to-back matchday the post-toss pass of day one overlaps the pre-toss pass of day two. The desk reads both fixtures in a single sweep and files a single dated row that covers both windows. The chronology grows in one direction; back-to-back days do not collapse the chronology.

What the daily cycle does not do

The daily cycle does not run a live score wire. The desk does not auto-refresh a page from a feed; the desk reads a named source, files a dated row, and moves on. The two passes are human editorial sweeps; the desk does not replace the sweeps with automation.

Editorial photograph of a Sixer editor reading a single news edit at the desk — a printed page held at reading distance with a fountain pen held in the off hand, daylight on a wooden surface.

The four rewrite moments decide which page gets a fresh dated row — a toss call rewrites the live desk, an XI sheet rewrites the teams page, an injury note rewrites the captain page, and a correction rewrites the methodology.

CA 03 · The four rewrite moments

Four moments rewrite a page; nothing else does.

Sixer rewrites a working page only when one of four named moments lands. The four moments are: a toss call, a confirmed XI sheet, a named injury note, and a dated correction. A page that has not received any of the four is a page the desk has deliberately left untouched.

①

Moment 1 — the toss call

A toss call rewrites the live desk and the captain page. The toss call is the first named fact the desk can publish on a matchday; the post-toss pass rewrites the live desk with the toss call and the dew read on the same row. A toss that flips mid-day rewrites the live desk a second time.

②

Moment 2 — the confirmed XI sheet

A confirmed XI sheet rewrites the teams page and the captain page. The XI sheet carries the playing eleven on the same row as the role weighting; the desk cross-checks the XI sheet against the team-association press release before filing the rewrite.

③

Moment 3 — the named injury note

A named injury note rewrites the live desk and the captain page. The injury note carries the player's name, the injury nature and the source on the same row. A speculative injury note — "according to sources close to" — does not count as a named injury note; the desk waits for the named source.

④

Moment 4 — the dated correction

A dated correction rewrites the methodology page and the page that carried the wrong fact. The correction is filed on the same URL as the original page; the corrections log on every page carries the dated correction. The correction is the desk's accountability row.

⑤

What is not a rewrite moment

A social media post, a fan comment, a podcast rumour or an aggregator's headline is not a rewrite moment. The desk does not aggregate third-party copy; the desk does not run a wire service. A page that has only received those inputs is a page the desk has deliberately left untouched.

⑥

Why the four moments are named

The four moments are named so a reader can audit the desk. A reader who lands on a page and asks "why was this rewritten yesterday at 18:42 IST?" can scan the chronology for one of the four moments. The named moments are the desk's editorial contract with the reader.

CA 04 · The supersession rule

An old note gets superseded on the same URL, never redirected.

When a dated row is overtaken by a fresh, named fact, the old row is superseded on the same URL. The supersession rule is the desk's editorial position on chronology: every page carries the full dated record, and a reader who wants the older note can scroll to it. Sixer does not redirect, does not delete and does not silently rewrite history.

What supersession looks like on a page

On a rewritten page the new dated row appears at the top of the chronology. The older row stays below the new row, with a one-line note that points at the row that superseded it. A reader who scrolls down the chronology sees both rows; the older row is not deleted.

What supersession looks like in the feed

In the feed the new dated row appears as a new item with its own publication time. The older item stays in the feed with its original publication time. The feed grows in one direction; older items are not retracted.

What supersession is not

Supersession is not a redirect. The desk does not move a row from one URL to another; the desk does not rewrite a row's publication time; the desk does not change a row's headline after the row has been published. A reader who lands on the older URL still finds the older row at its original time.

Why supersession matters to a reader

Supersession matters because a reader who scrolls back through a page sees the desk's editorial history on that page. The desk does not pretend a row never happened; the desk files the supersession in the open. The chronology is the desk's accountability row.

How to read a superseded row

A superseded row carries the original headline, the original publication time and the original source. The supersession note sits below the row and points at the row that replaced it. A reader who reads the supersession note can decide which row to trust — the older row or the newer row.

When supersession does not apply

Supersession does not apply to the methodology page, the archive page, the terms page, the privacy page or the contact page. Those pages carry their own editorial stamp and are rewritten on a different cadence. Supersession is a rule for dated news rows, not for editorial reference pages.

Editorial photograph of a Sixer editor's notebook open at a calendar spread — a single week laid out with two passes marked per matchday in blue ink and three frozen rows marked in grey, daylight on a wooden surface.

A reader who reads the cadence for the first time learns which rows move daily, which move weekly, and which stay frozen — and the distinction changes which page to open at 09:00 IST versus which page to bookmark for a season.

CA 05 · What does not move

Some rows are deliberately frozen — the desk publishes them once and leaves them alone.

Sixer freezes a small set of rows on purpose. The frozen rows are the desk's editorial anchor: the methodology note, the corrections log, the responsible-play note, the about note, the contact mailbox, the terms page, the privacy page and the verified winners archive. The frozen rows are rewritten only when the desk's editorial position changes, not on a daily cycle.

The methodology page

The methodology page is the desk's reading rules. The page is rewritten when the desk's reading rules change — for example, when a new named source family is added or when an existing rule is retired. The page is not rewritten on a daily cycle.

The corrections log

The corrections log is the desk's accountability row. The log grows additively: each new dated correction is appended below the older corrections. The log is not edited in place; a correction is never silently removed from the log.

The responsible-play note

The responsible-play note is the desk's editorial rule on budgeting, breaks, chasing losses and the helpline. The note is rewritten only when the desk's editorial position changes — for example, when a new helpline number is published by the relevant authority. The note is not rewritten on a daily cycle.

The terms and privacy pages

The terms and privacy pages are the desk's own editorial use note and the privacy statement. The pages are not the legal pages of any third-party platform; the pages are Sixer's own use terms. The pages are rewritten when Sixer's editorial position changes; the pages are not rewritten on a daily cycle.

The verified winners archive

The verified winners archive is the desk's reader-result record. The archive grows additively: each new verified entry is appended below the older entries. The archive is not edited in place; an entry is never silently removed from the archive once published.

Why frozen rows are deliberate

Frozen rows are deliberate because the desk's editorial position should not move every matchday. A reader who lands on the methodology page expects to find the same reading rules they read the week before; a reader who lands on the responsible-play note expects to find the same helpline. Frozen rows are the desk's editorial stability row.

CA 06 · What this means for a reader on a Tuesday morning

Reading the cadence changes which page to open at 09:00 IST.

Reading the cadence changes how a reader plans a visit. A reader who knows the daily cycle knows to open the live desk at 16:00 IST for the pre-toss pass and at 22:00 IST for the post-toss pass; a reader who knows the four rewrite moments knows to skip a page that has not received any of the four; a reader who knows the supersession rule knows to scroll a page before trusting the top row. The cadence is portable to any matchday the desk covers.

①

Reading the daily cycle on a Tuesday morning

At 09:00 IST on a Tuesday a reader can predict which pages have moved and which have not. The live desk has not yet been rewritten — the pre-toss pass is seven hours away — and the methodology page has not moved in weeks. The reader who plans the visit accordingly reads the methodology note and skips the live desk until 16:00 IST.

②

Reading the four rewrite moments on a Wednesday

On a Wednesday matchday the four rewrite moments land in a predictable order. The toss call rewrites the live desk first; the XI sheet rewrites the teams page next; the injury note — if any — rewrites the captain page third; the post-match correction rewrites the methodology page last. A reader who plans around the four moments reads the desk in the order the moments arrive.

③

Reading the supersession rule on a quiet day

On a quiet day the supersession rule still applies. The most recent dated row sits at the top of the chronology; an older row, if any, sits below it. A reader who reads the supersession note on the older row can decide which row to trust — the older row or the newer row — without leaving the page.

④

Reading the frozen rows on a season view

On a season view — a reader who reads the desk across a full tournament window — the frozen rows are the desk's editorial anchor. The methodology page, the responsible-play note, the terms page and the privacy page do not move across the season; the verified winners archive grows additively. The season-view reader bookmarks the frozen rows once and revisits them when the editorial position changes.

⑤

Reading the cadence against third-party copy

A reader who reads the cadence can compare Sixer's cadence against third-party aggregator copy. The aggregator refreshes every minute from a wire feed; Sixer writes a new dated row only when a named source has filed a fact. The cadence difference is the editorial difference; a reader who reads both can decide which row to trust.

⑥

What this explainer does not promise

This explainer does not promise a particular captain call, a particular venue win-probability, a particular fantasy-points projection or a particular offer on the basis of the cadence. The cadence is the editorial schedule; the reader's matchday decision is the reader's own. The desk publishes the cadence so the reader can plan — the desk does not endorse any particular decision.

What the cadence does not do

What the cadence does not do, even on a clean read.

The cadence is the desk's editorial schedule. Sixer publishes the cadence so a reader can plan a visit; the cadence is not a recommendation and not a prediction. The desk's editorial position is plain, and the desk repeats it on every explainer it publishes. The cadence is a schedule, not a fantasy engine.

Sixer does not auto-refresh from a feed

The two daily passes are human editorial sweeps. The desk does not replace the sweeps with automation, does not ingest a wire feed, and does not auto-publish a row from a third-party source. A page that has been edited in the last hour carries a row a human editor has signed off.

Sixer does not claim a current event

This explainer is evergreen. The desk does not claim any current event, current source change, current correction or live timestamp. The labelled chapter rail and the labelled chronology are labelled examples; the cadence itself is the durable layer.

Sixer does not rewrite a frozen row on the daily cycle

The frozen rows — methodology, corrections log, responsible-play note, about, contact, terms, privacy, verified winners archive — are not rewritten on the daily cycle. The desk rewrites a frozen row only when the desk's editorial position changes. A reader who lands on a frozen row at 09:00 IST will read the same row at 22:00 IST.

Sixer does not store a wallet

The cadence does not run contests, does not hold wallets, and does not provide financial advice. The access route is the configured first-party link; the desk is an editorial layer, not a financial intermediary. The cadence applies to editorial pages, not to financial workflows.

Sixer does not delete a page

The desk never silently deletes a page. Where a page is wrong, the desk files a dated correction on the same URL. Where a row is superseded, the desk files a row that points at the row that has superseded it. The chronology grows in one direction.

Sixer does not write a prediction

The cadence is an editorial schedule. The desk does not write a captain prediction, a venue win-probability, a fantasy-points projection or a player ranking on the basis of the cadence. The desk writes a working read; the reader's matchday decision is the reader's own.

FAQ

Reading the cadence — short answers.

Short answers to the questions the Sixer desk hears most often from readers who want to plan a visit around the editorial schedule.

How many working pages does the desk refresh each matchday?

Sixer does not commit to a fixed number. The daily cycle rewrites whichever pages receive one of the four rewrite moments — a toss call, an XI sheet, a named injury note or a dated correction. On a quiet matchday the cycle rewrites two or three pages; on a back-to-back day the cycle can rewrite most of the player chapter.

Why are some pages frozen and others rewritten daily?

The frozen rows — methodology, corrections log, responsible-play note, about, contact, terms, privacy and the verified winners archive — carry the desk's editorial position. Rewriting them every matchday would erode the reader's confidence in the position; the desk rewrites a frozen row only when the position itself changes. The daily-cycle rows — live desk, teams, captain, boundary map, news — carry per-matchday facts and are rewritten on the daily cycle.

When a row is superseded, what happens to the older row?

The older row stays on the same URL with a one-line supersession note that points at the row that replaced it. Sixer does not redirect, does not delete and does not silently rewrite the older row's publication time. A reader who scrolls down the chronology can read the older row at its original time.

Does the cadence change on a non-matchday?

The cadence runs every matchday; on a non-matchday the two passes still run, but each pass writes fewer rows. The masthead carries a single short note; the live desk is quiet; the methodology and archive pages are not touched. A non-matchday cadence is shorter, not absent.

Can a reader audit the cadence?

Yes. Every page in the Pages index carries the masthead edition stamp and the chronology. A reader who lands on any page and scrolls the chronology can read the dated rows in order, see the supersession notes, and audit which of the four rewrite moments landed on which matchday. The audit is open on every page.

Is this explainer tied to a current event?

No. The explainer is a bounded evergreen reading frame. The desk does not claim any current event, current source change, current correction or live timestamp. The labelled chapter rail and the labelled chronology are labelled examples; the cadence itself is the durable layer.

Editor's note

Sixer's editorial stance on the cadence.

Sixer is an editorial matchday-utility desk. The cadence is the desk's editorial schedule: two daily passes, four named rewrite moments, one supersession rule, and a small set of frozen rows that anchor the editorial position. A reader who reads the cadence knows which page to open at 09:00 IST and which page to bookmark for the season. The corrections log on every page is the desk's accountability row; the open inbox at [email protected] is the desk's editorial inbox.

Source-named

The desk rewrites a row only after a named source has filed the fact. The source list is published on the methodology page; a fact enters a page only after the desk can name the source. The source-named rule is the desk's editorial contract with the reader.

Cadence-named

Each page carries the masthead edition stamp and the chronology. A reader who lands on a page can see when the page was last rewritten and which of the four rewrite moments landed. The cadence-named rule is the desk's accountability row.

Schedule-first

The cadence is portable to any matchday the desk covers. The cadence is a schedule; the desk does not endorse any specific sign-up route, captain pick or offer on the basis of any specific cadence. The schedule-first rule is the desk's editorial position.

The cadence above sits between the news desk chronology and the methodology note. The Sixer Pages is the desk's reading library — 22 working pages on a single published cadence — and the two daily passes are the editorial schedule the desk operates under.