Two hours before a Saturday afternoon ODI contest locks, a reader has the morning dew note open in a tab the reader has not looked at since breakfast. The note predicted a dry second innings and recommended two finger-spinners on the bench. The reader has already picked the XI with a wrist-spinner at number eight and a fast-bowling all-rounder at seven, and the dew note is the only place the spin-bench call is anchored. Skipping the audit leaves the bench call on a prediction the morning may have undone. Running the audit takes forty seconds and tells the reader whether the spin-bench call still earns the slot at the lock.
The reader who runs the audit on every stale note pays the audit cost on notes that have nothing to add. The reader who never runs the audit pays a different cost: a locked team built on notes the day has quietly contradicted. The piece below is the small audit the careful reader runs on a stale note before treating it as a lock-time signal. Five staleness signals, the order to read them in, the three lock-time moves a stale analysis still earns, a worked ODI-day example on a single fixture, the boundary the audit keeps in front of the rule, and one habit the audit would not recommend. The editorial standards behind every note the desk publishes are listed on the trust desk.
Working line for the impatient: a fantasy cricket news analysis carries a staleness budget that begins at publication and ends at the contest lock. The budget shrinks every minute a fresher note has not contradicted it, and it shrinks faster when the underlying picture has shifted since publication. Five signals decide whether the stale note still earns the lock or has become a fixture on the feed: timestamp drift, source still live, magnitude still applicable, fresher note settled, lock-screen call still standing. The audit runs the five in order, treats a clean sweep as a green light, treats any single fail as a flag the reader patches, and treats three or more fails as an archive. A reader who audits every anchored note an hour before the lock will lock a team whose calls are still grounded in notes that still earn the lock.
The staleness audit at a glance
The audit has four parts, and each part is short enough to run in the head while the contest clock is running. Five staleness signals every stale note carries. The order the careful reader runs the five signals in. Three lock-time moves a stale analysis still earns. One worked example on a Thursday weeknight fixture, with one note that earned the audit and one that did not.
The first part is the five staleness signals. Timestamp drift, source still live, magnitude still applicable, fresher note settled, lock-screen call still standing. Each signal answers one question the lock-screen call is asking. Timestamp drift answers how old the note is. Source still live answers whether the source still says what the note said. Magnitude still applicable answers whether the number, the swap or the venue call still fits the locked team. Fresher note settled answers whether a still-fresher note has touched the same question. Lock-screen call still standing answers whether the call the note is anchoring is the call the reader has on the lock screen.
The second part is the order. Timestamp drift is read first because timestamp drift is the cheapest signal to check and the easiest to misread. Source still live is read second because a live source is the precondition for any of the next three signals. Magnitude still applicable is read third because the magnitude is the part of the note the locked team actually uses. Fresher note settled is read fourth because fresher notes change the picture without changing the source. Lock-screen call still standing is read last because the lock-screen call is the only signal that can confirm or cancel all four earlier signals at once.
The third part is the three lock-time moves a stale analysis still earns. Confirm is the move the audit awards to a note that has passed all five signals. Patch is the move the audit awards to a note that has failed one signal but still anchors a call the reader has on the lock screen. Archive is the move the audit awards to a note that has failed two or more signals and is no longer the place the locked team should anchor a call. Only one of the three moves changes the locked team, and only one of the three moves leaves the locked team on the call the note anchored.
The fourth part is the worked example. A Thursday T20 contest that locks at 7:30 p.m. The reader has the morning's probable-XI note on the lock screen at 6:17 p.m., four hours after publication. The audit runs on the note. The audit returns one move, the reader applies the move, and the locked team is locked once.
The five staleness signals every stale note carries
Each signal answers one question the lock-screen call is asking. A stale note carries all five signals at once, and the careful reader names all five before treating the stale note as a lock-time signal. A note that fails one signal is a note that still anchors the call, but a note that fails two is a note the locked team cannot lean on at the lock.
The first signal is timestamp drift. The audit reads how old the note is, in minutes, against the contest lock. A note published ninety minutes before the lock is a note with a short drift. A note published four hours before the lock is a note with a long drift. A note published twelve hours before the lock is a note with a drift that exceeds the staleness budget on most formats. Timestamp drift is the cheapest signal to check, because the timestamp is on the note and the lock is on the lock screen, and the audit reads the two clocks together. A note with a long drift is not automatically stale; a note with a long drift is a note the audit pays more attention to on the next four signals.
The second signal is source still live. The audit reads whether the source the note cited still says what the note said. A press conference is a one-shot source. A pitch report is a same-day source. A captain distribution is a daily source. A weather feed is an hourly source. A probable XI is a morning-of source. The audit names the source type, names the source window, and asks whether the source window has closed. A press-conference source closes the moment the conference ends, and a note that cites a press conference carries a closed source window the moment a still-fresher press conference has not happened. A weather-feed source stays open until the next hourly feed, and a note that cites the noon weather feed carries an open source window until the 1:00 p.m. feed.
The third signal is magnitude still applicable. The audit reads whether the number, the swap, or the venue call the note named still fits the locked team. A note that names a probable XI change is applicable when the change is the change the locked team has acted on. A note that names a captaincy hedge is applicable when the hedge is the hedge the locked team has applied. A note that names a venue correction is applicable when the correction is the correction the locked team has integrated. A note that names a magnitude the locked team has not acted on is a note whose magnitude is no longer applicable, even when the magnitude is still correct on the source.
The fourth signal is fresher note settled. The audit reads whether a fresher note has touched the same question the stale note is asking. A fresher note can settle, nudge, or ignore the question. A fresher note that has settled the question cancels the stale note, and the audit returns archive regardless of how the stale note has done on the first three signals. A fresher note that has nudged the question without settling it leaves the stale note on patch, and the audit returns patch when the stale note has passed the first three signals. A fresher note that has not touched the question leaves the stale note on its own, and the audit reads the first three signals without the interference of the fresher note.
The fifth signal is lock-screen call still standing. The audit reads whether the call the note is anchoring is the call the reader has on the lock screen. A note on a probable XI change anchors the bowling slot the reader has filled. A note on a captaincy hedge anchors the captain pick the reader has locked. A note on a venue correction anchors the venue read the reader has integrated. A note on a different call is a note whose anchored call is no longer the call the reader has on the lock screen. The audit returns archive when the anchored call is no longer on the lock screen, regardless of how the stale note has done on the first four signals.
All five signals are read on every stale note the reader is anchoring a call on, and none of them are read on a note the reader has already archived. The staleness audit is the audit the locked team runs on the notes the locked team has chosen to anchor on, and the audit is the part of the lock-screen discipline the desk cannot run on the reader's behalf.
The order the careful reader runs the five signals in
The order matters because each signal answers a different question, and a fail on an early signal changes the cost of the later signals. The careful reader runs the signals in the order below, on every stale note the locked team is anchoring on. Reordering the signals turns the audit into a different audit.
Timestamp drift runs first. The reader names the timestamp on the note, names the lock time on the lock screen, and reads the difference. A drift under ninety minutes is a short drift the audit treats as low-priority. A drift between ninety minutes and four hours is a medium drift the audit treats as the audit's working zone. A drift over four hours is a long drift the audit treats as high-priority and reads with the next four signals applied in full. The reader who skips timestamp drift pays a different cost on every later signal: the later signals are read on a note whose drift the reader has not named, and the audit returns a move the drift would have changed.
Source still live runs second. The reader names the source type the note cited and names the source window. The reader compares the source window to the lock time. A source whose window is still open is a live source. A source whose window has closed is a stale source, regardless of how well the note has done on the first signal. The audit returns archive when the source window has closed and the magnitude has not been re-confirmed by a fresher source. The reader who skips source-still-live pays the cost of a note anchored on a source the source window has already closed.
Magnitude still applicable runs third. The reader names the magnitude the note gave, names the magnitude the locked team has acted on, and reads the difference. A magnitude the locked team has acted on is an applicable magnitude. A magnitude the locked team has not acted on is a magnitude the locked team is no longer using, and the audit returns archive on the stale note. The reader who skips magnitude-still-applicable pays the cost of a note whose magnitude is correct on the source but no longer correct on the lock screen.
Fresher note settled runs fourth. The reader names the fresher note that has touched the same question, names the move the fresher note has made, and reads whether the move has settled, nudged or ignored the question. A fresher note that has settled the question cancels the stale note. A fresher note that has nudged the question leaves the stale note on patch. A fresher note that has not touched the question leaves the stale note on its own merits. The reader who skips fresher-note-settled pays the cost of a stale note whose question a fresher note has already answered.
Lock-screen call still standing runs last. The reader names the call the stale note is anchoring, names the call the reader has on the lock screen, and reads whether the two calls are the same call. The audit confirms the stale note when the two calls match. The audit returns archive when the two calls do not match. The signal is run last because the signal is the only one that can confirm or cancel all four earlier signals at once, and the confirmation only matters when the lock-screen call has not been changed by a fresher note the audit has already read.
The five signals together take under a minute on a single stale note, and the audit runs on every stale note the locked team is anchoring on. The audit is not a re-read of the stale note. The audit is a check on whether the stale note still earns the anchor.
The three lock-time moves a stale analysis still earns
The audit returns one of three moves, and only one of the three moves changes the locked team. The other two moves leave the locked team on the call the audit has read. The locked team should know which move the audit has returned before the lock, because the move is the only thing the audit produces.
Confirm is the move the audit awards to a stale note that has passed all five signals. Confirm leaves the locked team on the call the stale note is anchoring, and confirm does not require the reader to open the stale note a second time. Confirm is the most common move on a locked team that has been disciplined through the deadline day, because most stale notes on a disciplined locked team are stale notes that have not been contradicted by a fresher note. The locked team that confirms a stale note at the lock has read the stale note's five signals and has not found a reason to change the lock-screen call.
Patch is the move the audit awards to a stale note that has failed one signal but still anchors a call the reader has on the lock screen. Patch changes the lock-screen call by the failure the audit has named, and patch leaves the rest of the call the stale note is anchoring intact. A stale note that fails timestamp drift but passes the next four signals is a note the audit patches with a one-line update the reader writes in the margin. A stale note that fails magnitude-still-applicable but passes the next four is a note the audit patches with the magnitude the locked team has actually used. Patch is the most useful move on a locked team that has changed a call since the stale note was published.
Archive is the move the audit awards to a stale note that has failed two or more of the five signals. Archive leaves the locked team on whatever call the audit has named, and archive removes the stale note from the list of notes the locked team is anchoring on. Archive is the largest move by count on most audits, because most stale notes on a busy deadline day fail at least two signals by the time the lock has arrived. The locked team that archives a stale note has read the stale note's five signals and has found two reasons the stale note no longer earns the anchor.
The three moves are not mutually exclusive. A stale note the audit archived at 6:00 p.m. may turn into a confirm at 7:00 p.m. when the fresher note the audit was waiting on does not arrive. A stale note the audit patched at 5:30 p.m. may turn into an archive at 7:00 p.m. when the fresher note the audit was ignoring finally settles the question. The three moves are decisions the audit re-runs when the lock-screen call changes, and the careful reader treats the moves as gates the audit can re-run, not as verdicts.
A worked example on a Saturday afternoon ODI
The example below follows a single locked team across a Saturday afternoon ODI, with two stale notes the reader is anchoring on and one fresh note the reader has just opened. The example is hypothetical. The example shows how the audit lands on each stale note, what move the audit returns, and what the locked team does at each move. The example is meant to be runnable in the head on the next deadline day.
The setup: a Saturday ODI that locks at 1:30 p.m., played at a coastal venue with a 2:00 p.m. start. The reader has a wrist-spinner at number eight, a fast-bowling all-rounder at seven, and a captain pick locked on the in-form opener. Two stale notes anchor calls the reader has on the lock screen: a dew note published at 8:45 a.m. predicting a dry second innings, and a captain-pool read published at 11:00 a.m. flagging the away opener as a differential. One fresh note has just landed: a 1:00 p.m. pitch update from the broadcaster. The reader runs the audit on the two stale notes at 12:50 p.m., forty minutes before the lock, before the pitch update has been read.
The dew note, 12:50 p.m. Timestamp drift is medium: the note is four hours and five minutes old, and the morning cloud cover has lifted. Source still live: the source is the venue's automated dew sensor, refreshed hourly, and the source window is still open at the next refresh. Magnitude still applicable: the magnitude is "two finger-spinners on the bench," and the reader has not acted on the bench call because the XI is locked on a wrist-spinner. Fresher note settled: no fresher note has touched the dew reading. Lock-screen call still standing: the spin-bench call the reader has not made is not a call the lock screen is anchored on. Two signals pass. Three signals fail. The audit returns archive. The reader removes the dew note from the lock-screen discipline, leaves the XI untouched, and the wrist-spinner at eight stays on the lock.
The captain-pool note, 12:50 p.m. Timestamp drift is medium: the note is one hour and fifty minutes old. Source still live: the source is the public captain distribution, refreshed every ninety minutes, and the source window is still open. Magnitude still applicable: the magnitude is the away opener as a differential captain, and the reader has not applied the differential. Fresher note settled: the morning powerplay note has nudged the captain pool without settling the differential. Lock-screen call still standing: the captain pick the reader has locked is the in-form opener, and the differential the note names is not the captain pick on the lock screen. Two signals pass. Three signals fail. The audit returns archive. The reader removes the captain-pool note from the lock-screen discipline and leaves the captain pick on the in-form opener.
The pitch update lands at 1:00 p.m., and the reader opens it after the audit on the two stale notes has returned. The pitch update is fresh, and the audit does not run on fresh notes. The reader reads the update, finds the surface has slowed since the morning, and the wrist-spinner at eight looks better against the slower track than the original XI had assumed. The reader makes a single XI swap and locks the team at 1:18 p.m. The audit on the two stale notes has already returned: archive on the dew note, archive on the captain-pool note. Neither stale note is anchoring a call on the locked team at the lock.
At 1:30 p.m. the contest locks. The locked team carries the wrist-spinner at eight with the slow-track swap the fresh note justified, the in-form opener as captain from the morning read, and the fast-bowling all-rounder at seven from the original XI. The dew note and the captain-pool note are both archived. The audit has been run on both stale notes the locked team was anchoring on, and the locked team is locked once on a fresh-note swap. The reader has audited two notes, archived both, and integrated one fresh note on the third call.
Three questions readers send in about the staleness audit
Is a stale note always worse than a fresh note?
Not always. A stale note on a question no fresher note has touched is often the strongest note the locked team is anchoring on, because the stale note has had hours of contradiction-test and no fresher note has contradicted it. A fresh note on a question a still-staler note has already settled is often the weakest note the locked team is anchoring on, because the fresh note is fresh for reasons the locked team has not tested. The audit treats staleness as a question of drift, source, magnitude, fresher note and lock-screen call, not as a question of age. A stale note that passes the audit is a stronger note than a fresh note that has failed the audit.
What happens to the audit when a fresher note lands during the audit itself?
The audit pauses on the signal it was reading when the fresher note lands, reads the fresher note on the freshness audit the desk applies to fresh notes, and re-runs the staleness audit from the signal that was paused. The fresher note changes the picture the audit was building, and the audit cannot finish on a picture the fresher note has changed. The careful reader treats the audit as a gate the fresher note can re-open, not as a verdict the fresher note has to wait for. Re-running the audit on a single stale note takes under a minute when the fresher note is short, and the audit is comfortable with the re-run being the only re-run the deadline day requires.
Does the audit apply to notes the desk has corrected?
Yes, with one extra signal the audit reads first. The audit reads the corrections trail at the top of the note before running the five staleness signals, and the audit treats a corrected note as a fresh note on the question the correction has changed. A corrected note on a question the locked team has not acted on is a note the audit returns to archive by default. A corrected note on a question the locked team has acted on is a note the audit patches with the corrected magnitude, regardless of how the corrected note has done on the five staleness signals. The corrections trail is the desk's standing record of what has changed, and the audit treats the corrections trail as a sixth signal the desk applies on the reader's behalf.
Where the staleness audit stops being a rule for the note
The staleness audit is a rule for stale notes the locked team has anchored a call on. The audit is not a rule for fresh notes the locked team has just opened, and the audit is not a rule for archived notes the locked team has already removed. The boundary below is the line the audit keeps in front of the rule.
The first boundary is the call the locked team is anchoring on. The audit runs on the call the reader has on the lock screen. The audit does not run on the call the reader has not yet locked, and the audit does not run on the call the reader has already locked and is no longer anchoring on. A stale note that anchors a call the reader has on the lock screen is a note the audit applies to. A stale note that anchors a call the reader has removed from the lock screen is a note the audit treats as archived regardless of how the stale note has done on the five signals. The call the reader has on the lock screen is the only call the audit applies to.
The second boundary is the source the stale note has cited. The audit runs on the source the stale note has named, and the audit does not run on a source the stale note has not named. A stale note that names a press conference is a note the audit reads with the press-conference window in mind. A stale note that names a public social post is a note the audit reads with the social-post window in mind. A stale note that does not name a source is a note the audit returns to archive by default, because the audit cannot read source-still-live on a source the stale note has not named. The source the stale note has cited is the only source the audit applies to.
The third boundary is the time the reader has left. The audit runs on the time the reader has before the lock. A stale note that the reader opens with five minutes left and that fails two of the five signals is a note the audit returns to archive, because the audit cannot fit a patch-and-re-read step into the five minutes the reader has. The careful reader treats the time-left as part of the audit, and the audit has a separate time check the five named signals do not cover. A reader with twenty-eight minutes and a settled captain pick runs the audit at a different speed from a reader with five minutes and an open bowling slot.
The boundaries are the part of the audit the locked team negotiates with the desk. The desk publishes the timestamp, the source, and the magnitude on every stale note. The locked team runs the audit on the note the desk has published. The seam between the two halves is the boundary, and the boundary is the part of the audit the locked team keeps in front of the rule.
One habit the audit recommends, one it does not
Two short paragraphs on the single staleness-audit habit the audit thinks will sharpen the next contest the most, and the one habit the audit would not recommend. The frame is bounded: the audit can publish on every stale note the desk has filed, but the audit cannot run the five signals on the locked team's behalf, and the audit is the part the locked team owns.
The habit the audit recommends is the pre-lock audit, run once on every stale note the locked team has anchored a call on. Before the contest locks, the reader names the timestamp on the stale note, the source the stale note cited, the magnitude the stale note gave, the fresher note that has touched the same question, and the lock-screen call the stale note is anchoring. The pre-lock audit turns a tab the reader has not looked at since breakfast into a tab the reader knows the lock-time move on. The reader who runs the pre-lock audit at forty minutes before the lock has time to patch the stale notes that need patching and archive the stale notes that have stopped earning the lock. The saving is the difference between a locked team grounded in notes the day has not contradicted and a locked team grounded in notes the day has quietly undone.
The habit the audit would not recommend is the always-re-read habit. Re-reading every stale note the desk has published, watching the captain pool move on every new timestamp, and changing a locked team on the strength of every new drift signal produces a locked team that has re-read the feed but has not played a contest. The bounded view: the locked team that audits every anchored note will out-read the locked team that re-reads every stale note, and the difference will be visible at the next deadline, not at the next season opener. The audit's only forecast is that the five signals compound, and the compounding is the only honest forecast the audit is willing to make on a locked team's staleness-audit habit.