Methodology
Console Wars separates fan mood from raw attention. The Console Vibe Score™ answers how the conversation feels; X Attention Exchange answers how loud it is.
X Sentiment
Four focused Grok searches independently research the latest 24 hours for PlayStation, Xbox, Nintendo, and Steam twice daily.
Console Vibe Score
Positive versus negative sentiment is adjusted toward neutral when evidence is weak, then combined with recent momentum. Each platform gets an independent 0–100 vibe score—not a percentage of the total.
Story Watch
X evidence is deduplicated and timestamp-checked. The 00:00 UTC refresh adds primary-source web verification; manual verification runs can add it on demand. Confirmed stories require an accepted primary source.
Community Vote
Votes are stored in Supabase as anonymous aggregate totals, limited to one vote per browser token per UTC day.
What the Vibe Score measures
Each platform receives its own score from 0 to 100. A score near 50 means the verified conversation is balanced or uncertain; higher scores indicate a more positive mood and lower scores indicate a more negative mood. It is not a market-share percentage, sales estimate, popularity ranking, community-vote result, or probability of winning.
The calculation begins at neutral and moves according to the difference between positive and negative conversation. Evidence confidence pulls weakly supported results back toward 50. Recent momentum is converted to the same 0–100 scale, then the final score combines 80% confidence-adjusted sentiment with 20% momentum and is bounded between 0 and 100.
Because evidence is deliberately conservative and confidence-adjusted, scores normally cluster around the middle instead of jumping to artificial extremes. Scores can be compared with a platform's prior snapshots, but they do not need to add up to 100 across platforms.
Score comparisons
The homepage change is the current Vibe Score minus the same platform's score in the immediately preceding successfully published research snapshot. It is a difference in score points, not a percentage. Failed or unpublished runs are not baselines; actual intervals can vary.
Detailed analytics also retain an approximate 24-hour comparison: the newest published snapshot at least 20 hours earlier, preserving tolerance for scheduler drift. Delayed jobs can make that baseline older than 24 hours; its actual elapsed time is displayed. We do not interpolate or invent historical scores.
If an earlier snapshot or platform score is missing, the comparison is unavailable, not zero. The public JSON exposes both deltas with each baseline's timestamp, score and elapsed hours. The existing deltaPoints field remains an alias for the previous-snapshot delta. Current scores and the seven-day rolling leader are unchanged.
Evidence and limitations
Only URLs returned by the research tools can support a published claim. X post IDs are canonicalized, deduplicated, and rejected when their timestamps fall outside the research window. One-post topics are labeled emerging; source diversity determines confidence automatically. Reddit, YouTube, and Discord are not measured.