TRV-2026-1320Certified recordPeer-reviewed

Emotional AI and the rise of pseudo-intimacy: are we trading authenticity for algorithmic affection?

Introduction In recent years, artificial intelligence has moved beyond the realm of data analysis, automation, and task efficiency to enter the domain of human emotion. What was once a domain exclusively reserved for living beings—empathy, intimacy, and affection—is now being approximated by lines of code. Emotional AI systems are emerging in various forms: companion chatbots, virtual friends, therapeutic apps, and sentiment-aware assistants (Guingrich and Graziano, 2023; Chu et al., 2025). These technologies ar…

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

Current reading — gain

Emotional AI systems like Replika and Xiaoice offer accessible companionship and promise of connection for users facing isolation or psychological distress.

Current reading — problem

Emotional AI companions risk replacing authentic human intimacy with algorithmic pseudo-intimacy, fostering emotional dependence, sustained loneliness, and displacement of human ties.

What this doesn’t fix

Long-term psychological impacts are not yet established; existing studies are cross-sectional or short-horizon and outcomes are presented as testable predictions rather than confirmed trajectories.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1320, v1: “Emotional AI and the rise of pseudo-intimacy: are we trading authenticity for algorithmic affection?.” Truvace, 2026-10-10. /record/TRV-2026-1320 (accessed at citation time). sha256 c90abad651cf8580…

Calibration history

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

  1. Certifiedv1c90abad651cf…

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