---
title: "Compare claimed source metadata with the file actually produced"
url: "https://ailawframework.com/obligations/incoming-evidence-deepfakes-and-synthetic-documents/compare-claimed-source-metadata-with-the-file-actually-produced/united-states"
type: "task_jurisdiction_version"
site: "AI Law Framework"
id: "A44-A20260923-1-US"
practice_area: "Incoming evidence — deepfakes & synthetic documents"
tier: "yellow"
lawyer_review: "required"
jurisdictions: ["US"]
last_reviewed: "2026-10-22"
---

# Compare claimed source metadata with the file actually produced

> Put the filename, hash, capture time, device, and sender claimed in the cover sheet beside the same fields read from the file. Flag every field that does not match. Do not decide whether the exhibit is authentic.

Canonical page: https://ailawframework.com/obligations/incoming-evidence-deepfakes-and-synthetic-documents/compare-claimed-source-metadata-with-the-file-actually-produced/united-states  
Last reviewed: 2026-10-22

Site index for agents: https://ailawframework.com/llms.txt

## Key facts

| Fact | Value |
| --- | --- |
| Practice area | [Incoming evidence — deepfakes & synthetic documents](https://ailawframework.com/obligations/incoming-evidence-deepfakes-and-synthetic-documents.md) |
| Human involvement | Yellow: Lawyer and AI draft together |
| How AI is used | Put the filename, hash, capture time, device, and sender claimed in the cover sheet beside the same fields read from the file. Flag every field that does not match. Do not decide whether the exhibit is authentic. |
| What the lawyer must review | Authenticity is Federal Rule of Evidence 901(a): evidence sufficient to support a finding that the item is what the proponent claims. A certification under Rule 902(13) or 902(14) still needs a qualified person and the Rule 902(11) notice. Open the file itself. Formal Opinion 512 requires you to review tool output before anyone relies on it. |
| Written for | United States |
| Applies to | [Compare claimed source metadata with the file actually produced](https://ailawframework.com/obligations/incoming-evidence-deepfakes-and-synthetic-documents/compare-claimed-source-metadata-with-the-file-actually-produced.md) |

## Checking plan

- What the AI does: Put the filename, hash, capture time, device, and sender claimed in the cover sheet beside the same fields read from the file. Flag every field that does not match. Do not decide whether the exhibit is authentic.
- Basis: Checked against the linked sources on 22 October 2026. Confirm the current instrument before reliance.

## Notes

- Rule 902(13) and 902(14) certify process or copying. They do not prove the depicted events happened.
- The 17 May 2026 Evidence Rules report did not put a machine-generated-evidence rule into force. Use 901 and 902.

## Sources

- [Federal Rule of Evidence 901, Authenticating or Identifying Evidence](https://www.law.cornell.edu/rules/fre/rule_901) (checked 2026-10-22)
- [Federal Rule of Evidence 902, Evidence That Is Self-Authenticating](https://www.law.cornell.edu/rules/fre/rule_902) (checked 2026-10-22)
- [ABA Formal Opinion 512, Generative Artificial Intelligence Tools (29 July 2024)](https://www.americanbar.org/content/dam/aba/administrative/professional_responsibility/ethics-opinions/aba-formal-opinion-512.pdf) (checked 2026-10-22)

## Forms and precedents for this task

| Form or precedent | Kind | AI level | Summary |
| --- | --- | --- | --- |
| [Metadata comparison schedule for a digital file](https://ailawframework.com/precedents/incoming-evidence-deepfakes-and-synthetic-documents/metadata-comparison-schedule.md) | Form | Yellow | Schedule comparing what a party claims about a digital file with the properties of the file actually held: names, times, hashes, device fields and software marks, for a lawyer to read before any… |
| [Production-set log for candidate synthetic or altered media](https://ailawframework.com/precedents/incoming-evidence-deepfakes-and-synthetic-documents/production-synthetic-media-log.md) | Form | Yellow | Log for marking items in a production, brief or client upload that need a lawyer's eye: missing native files, platform AI labels, inconsistent metadata, or a witness account that does not match the… |
| [Protocol for exchange of native electronic files where authenticity is in issue](https://ailawframework.com/precedents/incoming-evidence-deepfakes-and-synthetic-documents/native-file-exchange-protocol.md) | Agreement | Red | Short protocol the parties can adopt for a file whose authenticity, identity or provenance is disputed: native file, hash, metadata export, no public AI, and a timetable for a s 167 request. |

Signed-in accounts can read the full text of each one.

*Practice guidance for planning and review. Confirm current primary sources and the requirements of the actual matter. This is general information, not legal advice.*