Racing & sim — lap telemetry, fuel strategy and stint simulation
The racing desk covers sim racing and arcade-circuit brackets. The desk reads laps through per-team telemetry, fuel strategy through verified stint models, and braking points through publisher-published track guides.
Two racing brackets on the desk this season
Sim Racing
Lap-by-lap telemetry, fuel strategy, stint simulation. Quarterly updates with the desk's full stint profile published within 24h of any Tier-A race.
Arcade Circuit
Track mastery, nitro timing, brake-point reads. Quarterly patches with the desk's per-track braking analysis filed under the standing editorial.
How the racing desk reads a stint
A stint is fuel, tyre, pace. The desk reads three artefacts per stint: the fuel-burn profile, the tyre-degradation curve, the pace window. Where a publisher publishes a stint chart, the desk reproduces the chart; where a team publishes a pit decision, the desk files the quote under the editorial stamp.
Fuel-burn profile
Reproduce the fuel-burn profile from the publisher's per-lap telemetry. Where the telemetry omits a stint, mark the read as Tier-C.
Tyre-degradation
Track tyre-degradation curves by stint and by compound. Cross-stamp with the team's own published charts.
Pace window
Note the pace window, the undercut window and the overcut window. Editorial flag if the pit deviates from the team's stated target lap.
Brake point
Default reads: per-corner brake-point, entry speed, trail-brake zone. Edit only when the publisher's track guide corroborates the read.
Editor stamp
Tier-A lock where the publisher telemetry and the team's own chart agree. Tier-C where one disagrees.
Archive
Filed under the racing chapter archive with the publisher telemetry URL, the team's chart URL and the editorial stamp.
How a racing patch moves through the desk
Racing patches tend to be balance updates and physics changes rather than full resets. The desk files a balance log, a meta-shift editorial, and a context document for every Tier-A racing patch.
Balance log — verbatim reproduction
The balance log is the publisher's own patch notes reproduced verbatim in the newsroom. Where the publisher publishes a physics or handling change, the desk reproduces the table as-is with the publisher's own citations.
Meta-shift editorial
The meta-shift editorial is the desk's read of how the patch changes the competitive meta. The editorial is filed within 24 hours of the patch drop. The editorial is Tier-C and is explicitly flagged EDITOR'S READ.
Context document
The context document is the desk's editorial composite of the patch through the season's broadcast footage. The document is published 7 to 14 days after the meta-shift, once the first regional race has produced enough broadcast footage.
What the desk does not publish for a racing patch
The desk does not publish mid-week balance speculation. The desk does not publish private developer comments.