The record can prove itself.
Every photo and video on this record is fingerprinted at the moment of capture: the tool computes the file's SHA-256 hash and logs it — with Google's server clock, not a device clock — to an append-only sheet only the Accountability Partner controls. If a file were ever edited, re-shot, or swapped afterward, its fingerprint would no longer match the one logged at capture time.
Capture events are timestamped by Google's servers. The device clock — the thing a backdater would change — is never trusted.
Each session fetches a code that did not exist until seconds before recording — spoken aloud and burned into the video. Pre-recorded or replayed footage cannot contain it.
SHA-256 hashes of every file, logged at capture. The checker below recomputes a file's hash in your browser and searches the public log for it.
Pick any photo or video downloaded from this record (or from the Drive archive / YouTube download). The hash is computed locally — the file never leaves your device.
NOT FOUND is expected for files that were re-encoded after capture (YouTube re-compresses uploads; screenshots and re-saves change the bytes). Original downloads from the tool and the Drive archive match exactly. For any discrepancy: ap@michealrayberry.com.
The attestation log is public and machine-readable: download it as CSV. Columns: server timestamp, project day, event, challenge code, session kind, video and photo SHA-256 fingerprints.