Use file checksums to detect accidental evidence changes — what should the operator record?
A file may change during copying even when its name does not. A checksum can detect that narrow problem, but it cannot certify the truth of a public statement or continued permission to read it. Apply integrity checks to approved copies without turning them into authenticity claims.
Verify byte identity of permitted result files while keeping integrity checks separate from source truth or authorization.
Record file_path, digest_algorithm and digest_value for the exact exported bytes, not a screenshot or a subsequently reformatted table. Hashing the downloaded file before and after transfer checks the transfer path; hashing a regenerated file answers a different question about representation stability.
State that a matching digest confirms the copied bytes only. Review source availability and permission separately when sharing or reopening the file. A digest copied beside an altered file can still match that altered file, so provenance and trust in the recorded reference remain independent concerns.Choose the checked object
Record file_path, digest_algorithm and digest_value for the exact exported bytes, not a screenshot or a subsequently reformatted table. Hashing the downloaded file before and after transfer checks the transfer path; hashing a regenerated file answers a different question about representation stability.
Keep representations separate
A pretty-printed JSON file and its compact source can differ bytewise while describing the same rows; label which representation was hashed. Record whether the digest covers compressed archive bytes or extracted file bytes, since two valid archives can contain identical content with different packaging.
Exercise the failure path
Change one harmless character in a temporary permitted copy and confirm verification reports a mismatch without overwriting the original receipt. Use a disposable fixture for this test; do not mutate the only permitted source copy merely to demonstrate that the digest checker can fail.
Investigate mismatches
Compare encoding, line endings and authorized content changes before declaring corruption; create a new revision when a deliberate edit explains the difference. If a formatter changes whitespace, a byte mismatch is expected; compare parsed records separately before deciding whether the research values changed as well.
Bound the assurance
State that a matching digest confirms the copied bytes only. Review source availability and permission separately when sharing or reopening the file. A digest copied beside an altered file can still match that altered file, so provenance and trust in the recorded reference remain independent concerns.
Keep the boundaries clear.
- Verify byte identity of permitted result files while keeping integrity checks separate from source truth or authorization.
- Operational record: Choose the checked object. Context badges do not certify access.
Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.
Primary references
Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.