Then I suppose the best they can hope for are hardware packet checksums, tcp checksums, in some cases TLS will also flag corruption in transit, then it's on the

Then I suppose the best they can hope for are hardware packet checksums, tcp checksums, in some cases TLS will also flag corruption in transit, then it's on them to have a sane storage layer underneath. But for the specific scenario cited of historical archivists and preservation, I think it's reasonable to say "run zfs or a similar solution and closely monitor/replace the disks over time". That sounds more likely to work than building resilience into the equivalent of .zip and hoping those tools will recover such an error.