234 incidents on record · 2026HeadlightsIncident reports by Ellie Harris · Melbourne
5 new this weekLibrary last updated 14 October 2026
← The incident library
HD-INC-206
Criminal justice · Brazil · 2026 · A police investigator produced a technical report with generative AI tools that contradicted the official forensic analysis of the same audio, and it was used to support a criminal charge and accepted by two lower courts

Brazil's Superior Court Threw Out a Police Report Made With Generative AI

By Ellie Harris · Filed Investigation of an incident in February 2025, according to Conjur; charge accepted by the trial court and upheld by the São Paulo Court of Justice before February 2026

Alleged: São Paulo state criminal investigators developed or deployed the AI system implicated in this incident. Details are drawn from public reports; parties are presumed innocent of any wrongdoing not established by an official finding.

Brazil's Superior Court Threw Out a Police Report Made With Generative AI

What happened

A criminal case in São Paulo state centred on a video recording. The question was whether an offensive word could be heard in the audio.

According to Brazil’s Superior Court of Justice (STJ), the official forensic institute, the Instituto de Criminalística, examined the recording and found no signs of speech matching the word mentioned in the charge.

According to the STJ, a police investigator then produced a second report using generative artificial intelligence tools, which the court named as Gemini and Perplexity. That report reached the opposite conclusion and said the word had been spoken.

According to Conjur, the trial court accepted the charge. The São Paulo Court of Justice found no evidence that the report had been produced unlawfully and allowed it to stay in the case file.

On 7 April 2026 the STJ’s Fifth Panel held unanimously that “the report produced by a police investigator using generative artificial intelligence tools does not have the minimum epistemic reliability to be used as evidence in criminal proceedings”. It ordered the report removed from the file and directed the trial judge to decide again, without it, whether the charge should proceed. The court announced the decision on 8 April.

What an auditable version would have shown

The STJ’s account sets out what the forensic institute did: an analysis of the audio by the established methods for examining speech. It does not say what the investigator asked the tools, which files were supplied or what answers came back.

According to the court, the tools “do not process sound waves” and were not suitable for phonetic analysis. The legal news site Migalhas reported that the defence argued the report could not be checked or reproduced independently, and that the reporting judge treated the absence of those qualities as an obstacle to relying on it.

A record of the analysis would have shown which tool was used, what material was supplied to it, what it was asked and what it returned. It would also have shown whether anyone compared those answers with the forensic institute’s finding before the report was used to support the charge.

The full judgment was not retrieved for this entry. The sources reviewed do not show who decided that the tools should be used.

Where the gap was

In this entry’s reading, the gap was that nobody established whether the tools could do the task at all before their output was used.

According to the STJ, the reporting judge said that “one of the risks inherent in the use of generative artificial intelligence is hallucination”, which is the presentation of information that is inaccurate, unreal or fabricated. The court found that the report lacked “minimum epistemic reliability” to be admitted as evidence.

According to the STJ’s summary of the decision, the court also recorded a degree of confirmation bias in the state’s conduct, in that the official forensic finding was set aside in favour of the AI analysis.

A VerificationGate is designed to route a factual claim to a trusted source, rather than accepting the model’s answer, before the claim is used.

A ConductRecord keeps the tool, the input, the prompt and the output of each analysis, so that it can be reproduced and challenged.

VerificationGate and ConductRecord are Headlights designs.

What governance should have looked like

The STJ left the decision on the charge itself to the trial judge, and has not decided whether the word was said.

Before an AI tool is used on evidence, best practice would be to check whether it is capable of doing the job, and to have a qualified expert carry out the analysis by methods that other experts can check.

If an AI report contradicts the official forensic findings, the difference should be recorded and referred back to the forensic institute. The defence should be given the details of the AI analysis, including the material supplied to the tools, the questions asked and the answers produced.

Failure Pattern: a police investigator used generative AI tools to re-analyse audio after the official forensic institute found nothing, and the resulting report, which contradicted the forensic finding, was used to support a criminal charge and accepted by two lower courts.

Governance Principle: an investigating authority should be able to show, for any analysis it puts forward as evidence, what tool produced it, whether that tool is suited to the task, and how its result can be reproduced and checked.

The reference implementation of VerificationGate and ConductRecord is open source. It lives at github.com/saffronandindia/headlights-oss, Apache 2.0 licensed and free to install. The repository is public now.

Sources

The mailing list

Fresh incident reports every week. One email to match.

We add new incidents to the library regularly, and send a single short email each week with what's new. The library stays free and open; this is just how you keep up with it.

Sent through Substack. Unsubscribe in one click.

The record

An auditable system would have produced a signed, tamper-evident record the moment this happened: what the system did, the version that did it, the basis it acted on, and the action taken, and São Paulo state criminal investigators could have produced it on demand.

This is the record the system as deployed did not produce in a signed, auditable form.

What this teaches
Capture what happened when it happens
What the system did, the version that did it, the basis it acted on, and the action taken, recorded at the moment, not reconstructed after.
Sign it, so no one has to trust the record-keeper
A tamper-evident entry. Edit it later and the signature breaks. The record does not ask for the benefit of the doubt.
Make it verifiable by anyone
A court, a regulator, a customer's lawyer can check the record themselves, without taking the company, or us, at our word.

Headlights summarises publicly reported AI incidents. All summaries are independently written, attributed to their original sources, and intended for research and educational purposes. Allegations are identified as such until established through official findings.

Last reviewed September 2026. This report is based on the sources listed above and reflects information available at the time of review; later developments may not be captured. Where a person is described as charged with or alleged to have done something, that allegation is unproven unless a conviction or a court or regulatory finding is stated. Headlights publishes journalism and commentary, not legal advice.

Want to write back?

Direct to my inbox.

ellie@useheadlights.com →