What happened
Starting in November 2022, CNET published 77 personal-finance explainers generated by an in-house AI tool. They ran under the byline “CNET Money Staff,” and a reader learned that automation was involved only by hovering over the byline, where a line noted the piece was produced “using automation technology.”
In January 2023 Futurism reported the practice. One explainer on compound interest stated that a $10,000 deposit earning three percent interest a year would earn $10,300 in the first year. That is wrong: the interest earned in the first year is $300, and $10,300 is the total balance, principal plus interest. That prompted an internal review. CNET’s editor-in-chief, Connie Guglielmo, said the review found that 41 of the 77 articles required correction, more than half, with some corrections described as substantial and others minor: incomplete company names, transposed numbers, vague phrasing. Some passages were also found not to be “entirely original,” raising a separate concern that the tool had reproduced text from elsewhere.
CNET paused the AI-generated program and revised how it disclosed automation. It said it intended to keep using AI tools in its work. The failure was not that a tool helped draft an article. It was that factual, money-related claims were published to the public without verification, and that the use of AI was disclosed only to readers who happened to hover.
What an auditable version would have shown
When more than half of a batch of published articles needs correction, the editorial questions are immediate: which claims were checked before publishing, and which parts were machine-generated. CNET could not answer either from the workflow itself; it had to reconstruct the position article by article after the fact. An auditable version records, for each piece, which passages were AI-generated, what factual claims and figures were checked and against what, and who signed off, captured at the time. That record turns a public audit of the whole back catalogue into a query, and it makes honest disclosure a by-product of how the work is logged rather than a separate promise.
Where the gap was
There were two gaps, and they compound. First, factual claims were published without a verification step, in a domain (personal finance) where a transposed number is a real harm to a reader. Second, authorship was not disclosed plainly, so readers could not weight the content accordingly. The controls map to each: a VerificationGate routes factual claims and figures to a trusted source before publication and holds anything that cannot be confirmed; a ConductRecord preserves what was generated, what was checked, and by whom, which is also what makes a clear AI-use disclosure possible. The drafting speed was never the problem. The unverified, undisclosed publishing was.
What governance should have looked like
The lesson is not “do not use AI in a newsroom.” It is that the line between a draft and a published claim is an editorial responsibility, and AI does not move it. Before a factual article ships, its claims are checked against sources, the use of automation is disclosed to the reader plainly rather than on hover, and there is a record of both. That is ordinary editorial diligence, applied to a faster drafting tool, and it is far cheaper than correcting forty-one articles in public.
The reference implementation of VerificationGate and ConductRecord is open source. It lives at github.com/saffronandindia/headlights-oss, Apache 2.0 licensed and free to install. The repository is public now.
Sources
- Plagued with errors: A news outlet’s decision to write stories with AI backfires (CNN Business)
- Publisher breaks news using bots to write inaccurate stories (The Register)
- CNET Is Quietly Publishing Entire Articles Generated By AI (Futurism)