Truace
Subscribe
TRV-2026-2067Certified recordPeer-reviewed

Corporate Accountability by Algorithm: AI and the Interpretation of Human Rights Due Diligence

Abstract As companies struggle to conduct human rights due diligence and governments attempt to monitor compliance with supply chain regulations, they are increasingly turning to digital technologies such as artificial intelligence (AI). While AI-based tools can improve supply chain visibility and assess human rights risks, they carry potential risks of marginalizing rightsholders and undermining traditional conceptions of corporate accountability. This article examines the methodologies behind these tools, the…

Business · The Trace — both readings · certified 2026-10-21 · v1 · article view · machine-readable

Current reading — gain

AI-based tools can improve supply chain visibility and help assess human rights risks for companies conducting due diligence.

Current reading — problem

Relying on technology firms to build AI due diligence tools delegates interpretive judgment of the legal norm to them, privatizes human rights and deemphasizes stakeholder engagement.

What this doesn’t fix

The source is an abstract of a qualitative, argument-driven study based on a critical analysis and interviews with selected groups, so it offers no measured outcomes on how often these effects occur.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-2067, v1: “Corporate Accountability by Algorithm: AI and the Interpretation of Human Rights Due Diligence.” Truvace, 2026-10-21. /record/TRV-2026-2067 (accessed at citation time). sha256 f773b10d1cb54729…

Calibration history

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

  1. Certifiedv1f773b10d1cb5…

    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-2067 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.