Launch / Editorial note
How to read day-one performance reports
Launch-day reports are most useful when they describe the setup, the symptom and the point in time. Without those three things, a headline can outlive the issue it describes.
Look for the environment
Platform, settings and hardware context turn an isolated report into something readers can evaluate.
Separate symptom from verdict
A crash report, a lighting issue and a broad judgement about the game are not the same kind of claim.
Keep the date attached
Patches and wider samples can change the picture quickly. A careful summary should preserve when it was observed and update when the evidence moves.