TruaceTracing the truth around AIWednesday, July 22, 2026
TRV-2026-0413Certified recordPeer-reviewed

Justitia ex machina: The impact of an AI system on legal decision-making and discretionary authority

Governments increasingly use algorithms to inform or supplant decision-making. Artificial Intelligence systems in particular are considered objective, consistent and efficient decision-makers, but have also been shown to be fallible. Furthermore, the adoption of artificial intelligence (AI) in government is fraught with challenges which are only partly understood and rarely studied in practice. In this paper, we draw on science and technology studies and human computer interaction and report on a critical case s…

Policy · The Trace — both readings · certified 2026-07-20 · v1 · article view · machine-readable

Current reading — gain

AI system for traffic violation appeals at a Dutch court can best be applied in support of legal decision-making and its process design may mitigate some risks of algorithmic decision-making.

Current reading — problem

Use of the AI system for traffic violation appeals impacts decisions made by legal experts and creates tensions between street-level bureaucrats, screen-level bureaucrats and street-level algorithms.

What this doesn’t fix

Findings come from a single critical case study of traffic violation appeals at a Dutch court, limiting generalizability to other courts or case types.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0413, v1: “Justitia ex machina: The impact of an AI system on legal decision-making and discretionary authority.” Truvace, 2026-07-20. /record/TRV-2026-0413 (accessed at citation time). sha256 d3b1c3e230551dc8

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv1d3b1c3e23055

    Certified into the record

Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-0413 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.