Police stops flagged by AI software and Valve's new Steam disclosure policy land the same week tech's own board reading keeps sliding on its slop and gender systems.
Confirmed, not manufactured.
how tech was measured today
Counted layer · the radar, 230 of 309 sources reporting
Tech's day ran 6.6 per 100 sources; usual is 7.2
counted 17:40 UTC · per 100 reporting · against 56 stamped days
1 day 6.6 −0.23 sd 3 days 8.7 −0.74 sd 7 days 9.0 −1.26 sd 0 5 10 15 per 100 reporting · tick = a stamped day 1 day 6.6 −0.23 sd 3 days 8.7 −0.74 sd 7 days 9.0 −1.26 sd 0 5 10 15 per 100 reporting tick = a stamped day The idea Each window counts the sources a day publishing on tech, per 100 sources reporting, so a day when more sources report does not read as busier. The signed number is today’s distance from its usual, in standard deviations.
Look for The dot is today; each tick is one of the 56 stamped days before it. The band is the usual range, one standard deviation each side: 35 of 56 days fall in it. All three windows sit below their usual. The numbers -0.23 1 day, in standard deviations
6.6 sources a day per 100, today
7.2 its usual, the mean of 56 days
56 stamped days behind it
Limits It says the volume moved; it does not say why. It counts sources publishing, not a share of all talk. Under 14 stamped days a window reads early, a hollow dot; under 7 it does not print. How it is measured Per 100: sources publishing on the domain in the window, a day, over sources reporting that day, times 100. Usual: the mean of up to 56 stamped days before this sheet, one per scan, this sheet’s own scan left out; the spread is their standard deviation. Deviation: today less the usual, over the spread. src/data/cover-2026-10-29.json counted.domains, scripts/build-cover.py rep_scores.
This is the counted layer: how much the feeds we read published about tech, per source reporting, against what they usually publish. The story above is the heard layer, written from sources. They are kept apart on purpose.
See every domain on the board .