The Standup runs four kinds of story, and an item runs only when it forces action on a system you already run
You can read a developer news email every morning for a week and never once be asked to do anything. Everything in it is true, and none of it touches software you actually run, so the single line that did matter sits in the same list as four that never will.
The Standup is a daily wire for what you have to do something about, one email at 07:40 carrying releases, reviewed security advisories, live outages and the breaking changes inside them.
One sentence is printed on the site as the test an item has to pass: an item runs when it forces action on a system you already run, and interesting and inert does not run. Nine kinds of story have a row in the file the feed draws its labels and colours from. Four of them run.
| The kind | What it is, in the site's own words | In the file |
|---|---|---|
| ADVISORY | Reviewed CVEs, high and critical only | runs |
| STATUS | Live outages on the platforms you run on | runs |
| RELEASE | Tagged releases from the repos we track | runs |
| CHANGELOG | What vendors shipped and what it breaks, in their own words | runs |
| NEW REPO | Repos that cleared the star floor this week | archive only |
| SHOW HN | What people built and put up for review | archive only |
| DISCUSSION | The front page, above the score floor | archive only |
| PAPER | cs.AI and cs.SE preprints | archive only |
| ON X | A post on X | archive only |
One definition, two surfaces
Each kind carries one true or false beside its row, and the coverage page and the machine readable summary both build their sections by reading that field. Neither one restates the beat in its own prose. A second copy of a definition is exactly how a publication ends up describing itself two ways on two surfaces, and a reader who meets both has no way to tell which one is current.

The archive is a record, not a curated history
Everything filed under the five kinds that are off the beat stays published and stays searchable, because the site is a record of what went out rather than a curated history. The grade those items carry, the one that labels them unverified on the card, governs how the archive renders what it already holds. It does not decide what comes in.
New tool discovery is Agentwire's beat.
What a wide beat costs the person reading
An edited digest carries an item because somebody judged it interesting. That judgement reads, from the outside, exactly like coverage.
The coverage page files the five under a heading that says so in plain words, In the archive, no longer on the beat, with the reason underneath.
Every item ends on the consequence for a system you own: The Standup.
---
One shipped product, taken apart, once a month. What it does, what it cost to build, what the pipeline behind it looks like, and what the numbers did, read off the repository and the live site, not written from memory. Join the list.