Lighthouse AdvisorySLED AI Adoption Intelligence
← Back to results

From the Public Safety edition of October 7, 2026

Standards or public-body guidanceEmergingRecent

Federal evidence rules committee heads into Oct. 15 with AI Rule 707 withdrawn for revision and the draft deepfake Rule 901(c) still unapproved, as DOJ calls 901(c) not ready

Advisory Committee on Evidence Rules, Judicial Conference of the United States · Courts / federal evidence rulemaking · United States (federal courts)

Publisher
U.S. Courts (uscourts.gov)
Original publication
Agenda book for the Oct. 15, 2026 meeting (file dated Sept. 23, 2026)
Source retrieved
2026-10-08
Event date
2026-10-15
Read original source

What happened

The agenda book for the Oct. 15, 2026 Advisory Committee on Evidence Rules meeting states that the committee, after two hearings and more than 70 written comments, voted at its last meeting to withdraw proposed Rule 707 (machine-generated evidence offered without an expert) as published and submit a modified proposal for further study. It has also prepared but not finally approved a new Rule 901(c), under which an opponent must first produce evidence sufficient to support a finding that an item is a deepfake, after which the proponent must show it is more likely than not authentic. The committee will hear expert panels on both topics on Oct. 15. Draft May 2026 minutes reproduced in the book record DOJ's view that 901(c) is not ready for publication, that its notice provision would routinely be excused for criminal defendants, and that existing rules are adequate for deepfake claims.

Why it matters

Directly affects how police-generated AI outputs (transcripts, enhancements, analytics) and alleged deepfakes are admitted in criminal trials; state courts often follow federal evidence rule changes.

Evidence and measured results

Primary judicial rulemaking document: meeting agenda, reporter's memoranda and draft minutes. It records committee status and positions, not outcomes; the Oct. 15 decisions are not yet known.

Limitations and uncertainty

Status as of the agenda book; the committee may change direction on Oct. 15. The DOJ position comes from draft minutes of the prior meeting. Publication date inferred from the file name. Federal rules do not bind state courts.

Put this evidence to work

Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-08; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.

Sales

Role takeaway
Customer problem
Agencies increasingly offer AI-processed evidence and face deepfake claims without a settled federal rule.
Stakeholders
  • Prosecutors' offices
  • Public defenders
  • Police evidence and digital forensics units
  • Court administrators
  • State evidence rule committees
Discovery questions
  • Which evidence types are processed by AI before trial?
  • Are originals and processing logs preserved?
  • Have deepfake authenticity challenges arisen?
  • Who tracks federal and state evidence rule changes?
Value hypothesis
Provenance and documentation practices reduce the risk of exclusion regardless of how Rules 707 and 901(c) end up.
Potential engagement
Evidence-provenance readiness review and foundation templates for one AI-processed evidence type.
Unsupported claims
  • That Rule 707 or 901(c) is in effect
  • Outcome of the Oct. 15 meeting
  • That detection tools settle authenticity
  • That state courts will adopt the rules

Pre-sales engineering

Role takeaway
Fit
Applies to any agency producing transcripts, enhancements, analytics or other machine outputs used as evidence.
Architecture and integration
Capture devices, evidence management platforms and AI processing tools must preserve originals, hashes and transformation logs through to discovery.
Prerequisites
  • Hashing at ingest
  • Versioned AI processing logs
  • Retention of originals
  • Discovery export capability
Constraints
  • No AI-specific federal rule in force
  • State rules vary
  • Vendor tools may not expose model details
  • Defense access to methods
Security
Protect chain of custody with hashing and access logs; record who ran which model on which file.
Proof of value
  • Assemble a mock reliability foundation for an AI transcript
  • Verify hashes match from capture to export
  • Confirm originals are retained for all AI-processed files
  • Test whether vendor can provide method documentation

Delivery

Role takeaway
Work
Build foundation templates and provenance practices for AI-processed evidence and a deepfake-challenge playbook.
Dependencies
  • Vendor documentation
  • Evidence platform logging
  • Prosecutor input
  • Oct. 15 committee outcome
Ownership
Prosecutors' offices and agency evidence units, with court liaison tracking rulemaking.
Skills and adoption
Attorneys and analysts need training on reliability foundations and authenticity disputes.
Governance checkpoints
  • Review after Oct. 15 meeting
  • Policy on retaining originals
  • Annual review of rule changes
Acceptance criteria
  • Proposed: foundation template ready for each AI-processed evidence type
  • Proposed: 100% of AI-processed files retain original and hash
  • Proposed: playbook updated within 60 days of committee action
Risks
  • Rules change after templates are built
  • Vendors cannot document methods
  • Defense resource gaps
  • Loss of original media

Implementation considerations

Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.

Architecture and integration

What must connect, and where does the AI sit in the workflow?

Agencies that produce machine-generated evidence should expect expert-reliability scrutiny and should preserve inputs, model versions and processing logs to support it.

Governance

Who approves, reviews and stays accountable for outcomes?

Rulemaking is deliberately slow: no AI-specific federal rule is in force, and courts continue to apply existing authentication and expert rules case by case.

Security and privacy

What data, permissions and controls need testing?

Deepfake challenges put a premium on chain of custody and provenance records for body-camera, CCTV and digital evidence.

Accessibility and workforce

Who is affected, and what skills or accommodations follow?

Prosecutors, defenders and lab analysts need training on AI evidence foundations; public defenders may lack forensic authentication resources.

Procurement

What should contracts, pricing and exit terms secure?

Evidence tools that alter or analyze media should document methods and keep originals, because admissibility may hinge on explaining the process.

Operating model

Which teams own the service once it runs?

Agencies and prosecutors should plan for case-by-case reliability hearings rather than a bright-line rule in the near term.

Publication history

  1. 2026-10-07Public Safety · Issue 316 resources
Read preserved resource versions (JSON)

Stable resource ID: federal-evidence-committee-rule-707-901c-ai-oct15-20261007