TruaceTracing the truth around AIMonday, July 13, 2026
TRV-2026-0188Certified recordPeer-reviewed

Human-AI co-creation or conflict? Mapping art students’ diverse perspectives on creative identity with genAI: A Q methodology study

Abstract Generative AI (GenAI) is rapidly transforming creative fields, raising critical questions about its impact on artistic identity and authorship, which also influence art education. While studies have explored GenAI adoption, the diversity of art students’ subjective perspectives on collaborating with these tools remains under-examined. This study uses Q methodology, a mixed-methods approach to investigating subjectivity, to explore the distinct perspectives art students hold regarding their creative iden…

Education · The Trace — both readings · certified 2026-07-13 · v1 · article view · machine-readable

Current reading — gain

Art students classified as enthusiastic explorers and human-centered directors report using generative AI as a controllable tool that enables novel expression and co-agency in creative work.

Current reading — problem

Art students classified as authorship guardians and conflicted co-creators report resistance to AI co-authorship and struggles with ownership, disclosure, authenticity, and earned pride when collaborating with generative AI.

What this doesn’t fix

Findings are based on a small Q sample of 40 students and subjective sorting, limiting generalizability beyond the studied art disciplines and academic levels.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0188, v1: “Human-AI co-creation or conflict? Mapping art students’ diverse perspectives on creative identity with genAI: A Q methodology study.” Truvace, 2026-07-13. /record/TRV-2026-0188 (accessed at citation time). sha256 425e78f9b2309e44

Calibration history

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

  1. Certifiedv1425e78f9b230

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