TruaceTracing the truth around AIWednesday, August 5, 2026
TRV-2026-0620Certified recordPeer-reviewed

From bones to bytes: anticipating and addressing the governance challenges of human digital remains and posthumous digital human twins

Abstract During the nineteenth century, advances in medical research led to grave robbing and an illicit market in human biological remains (HBR). The historical episode of grave robbing illustrates how science can upend social norms. A similar scenario could soon emerge, but this time it will not be with people's biological remains, but with people's digital remains. Artificial intelligence and extended reality now create digital representations from avatars to human digital twins. In addition to the sophistica…

Policy · The Trace — both readings · certified 2026-08-01 · v1 · article view · machine-readable

Current reading — gain

Researchers propose an HDR governance framework for AI-created human digital twins that would protect citizen autonomy after death through advance data directives and data trustees.

Current reading — problem

Human Digital Remains created by AI from personal and biometric data face existing legal and ethical gaps because neither GDPR nor the AI Act currently extends rights to the deceased.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0620, v1: “From bones to bytes: anticipating and addressing the governance challenges of human digital remains and posthumous digital human twins.” Truvace, 2026-08-01. /record/TRV-2026-0620 (accessed at citation time). sha256 1e6a12e115f39885

Calibration history

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

  1. Certifiedv11e6a12e115f3

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