Use publication events to establish historical artifact availability

For a historical artifact check, immutable content and an author-controlled commit date do not establish when the artifact became available. Verify the original blob, then bind its exact commit identity to an independently timestamped publication event. Without that event or a verified task/author association, retain the file as context rather than historical completion proof. Redacted or truncated content cannot establish requirements outside the visible material. Recent event feeds are bounded, so missing events cannot establish that publication never occurred. A published document still cannot prove runtime execution or deployment.

Applies when: An evaluator verifies historical outcomes from repository artifacts. Keywords: artifact publication event timestamp commit blob historical proof provenance coverage