Correspondence on Certificate Cloud Backup
Someone uploads a vaccine certificate to cloud storage because losing the phone copy feels strangely plausible.
Progress Report: Certificate Cloud Backup Protocol Period Covered: November 2021 Status: Active and Expanding
Current State
Certificate cloud backup began as a private precaution with no audience. One person, one phone, one document of moderate institutional importance. The document was photographed. The photograph was uploaded to a cloud folder titled, with some optimism, "Important."
The folder already contained a photograph of a passport, a scanned lease agreement from 2019, and three screenshots of receipts for items that have since been returned. The certificate joined this collection on a Tuesday.
Adoption Pattern
It became visible enough that other people adjusted their timing and expectations around it. This was not intended. A conversation about vaccine logistics surfaced the practice, and the practice acquired a second practitioner within the same household.
Familiarity acquires authority once a workaround has been repeated in public. The second practitioner did not evaluate the original rationale. They observed that the first practitioner had done something deliberate and replicated it. The replication was treated as confirmation.
The Contradiction
The check is meant to reduce uncertainty, but repeating it often creates another reason to check. The first upload produced the question of whether the upload was current. The question of currency produced a second upload after the second dose. The second upload produced the question of whether the original upload should be deleted or archived. The archiving question remains open.
Nobody has been asked for the certificate since it was uploaded. This fact has not affected the upload schedule.
The Governing Rule
The precaution turned into a social rule whose absence is noticed faster than its presence. When a third household member received their dose and mentioned not having backed up the certificate, this was noted. The note was not unkind. It was delivered in the tone of someone sharing a procedure, not issuing a correction.
The tone is correct. The procedure is now the standard. The original uncertainty that produced it is, for most purposes, resolved.
The backups remain. New ones are added when the original feels old.