TruaceTracing the truth around AIWednesday, August 26, 2026
TRV-2026-0818Certified recordPeer-reviewed

Exploring fashion designers' acceptance of AIGC: A dual-pathway analysis from the stimulus-organism-response perspective

Artificial Intelligence Generated Content (AIGC) is increasingly used in creative design. Understanding fashion designers' willingness to adopt these tools has therefore become important for both research and practice. Drawing on the Stimulus-Organism-Response (SOR) model, this study integrates Self-Determination Theory (SDT) with perceived risk, social influence, and facilitating conditions. It examines how these contextual stimuli shape designers' basic psychological need satisfaction and behavioral intention.…

Lifestyle · The Trace — both readings · certified 2026-08-18 · v1 · article view · machine-readable

Current reading — gain

Among Chinese fashion-design practitioners, satisfaction of basic psychological needs, especially competence, increased behavioral intention to adopt AIGC tools.

Current reading — problem

Perceived risk around AIGC reduced fashion designers' feelings of autonomy, competence and relatedness, undermining psychological conditions for adoption.

What this doesn’t fix

Findings are based on self-reported intentions from a single-country sample of 318 Chinese practitioners with complete data for 21 items, limiting generalizability beyond that population and to actual adoption behavior.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0818, v1: “Exploring fashion designers' acceptance of AIGC: A dual-pathway analysis from the stimulus-organism-response perspective.” Truvace, 2026-08-18. /record/TRV-2026-0818 (accessed at citation time). sha256 a03b97a71cc0da89

Calibration history

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

  1. Certifiedv1a03b97a71cc0

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