68/100

Moderate evidence

GainPublished recordBusinessGood Space

Breaking the Single Voice: Perceived AI Plurality as an Autonomy-Supportive Architecture for Ethical Marketplace Decisions

Truvace record
TRV-2026-2594raw data (JSON)
Version
v1Published
First published
Evidence type
Controlled or validated comparison
Sources
1 sourcePeer-reviewed
sha256
545029c1a85b…check it

Artificial intelligence (AI) increasingly structures how consumers encounter, evaluate, and select marketplace options, raising fundamental questions about autonomy, empowerment, and welfare-enhancing choice environments. While prior work has focused on what algorithms recommend, less is known about how recommendation system architecture shapes the experience of choice. Across three experiments, this research examines the societal and psychological implications of perceived algorithmic plurality, defined as cons…

The gain

In three experiments, consumers who got ethical recommendations from several distinct AI agents reported more perceived autonomy, stronger self–brand connection and higher purchase intentions, with the effects strongest among low-knowledge consumers.

What this doesn’t fix

The outcomes measured are perceived autonomy, self–brand connection and purchase intentions, so the results speak to consumer perceptions and stated intentions rather than actual purchases.

Sources

1 on file
  1. Journal of Macromarketingdoi:10.1177/02761467261472111
    Peer-reviewed2026-08-10

Cite this record

v1

Truvace Impact Record TRV-2026-2594, v1: “Breaking the Single Voice: Perceived AI Plurality as an Autonomy-Supportive Architecture for Ethical Marketplace Decisions.” Truvace, 2026-11-12. /record/TRV-2026-2594 (accessed on the day you copy it). sha256 545029c1a85b51cd…

Change history

1 version

Every change made to this record since it was first published, and why. Nothing has changed since it went up.

  1. Publishedv1545029c1a85b…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-2594 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.