30/100

Emerging evidence

Published recordMedia & ArtsGeneral

A capitalist contest: the AI industry v. the creative industries

Truvace record
TRV-2026-1240raw data (JSON)
Version
v2Revised
First published
Evidence type
Commentary, opinion, or narrative review
Sources
1 sourcePeer-reviewed
sha256
fd7692f34632…check it

This paper examines whether artificial intelligence industry developers of large language models should be permitted to use copyrighted works to train their models without permission and compensation to creative industries rightsholders. This is examined in the UK context by contrasting a dominant social imaginary that prioritises market driven-growth of generative artificial intelligence applications that require text and data mining, and an alternative imaginary emphasising equity and non-market values. Policy…

The problem

AI developers training large language models on copyrighted works without permission or compensation risks exploiting creative labor and privileging Big Tech profit over creator rights.

What this doesn’t fix

Analysis is bounded to the UK policy context and to conceptual imaginaries rather than empirical measurement of economic impacts.

Sources

1 on file
  1. Journal of the British Academydoi:10.5871/jba/013.a38
    Peer-reviewed2025-09-18

Cite this record

v2

Truvace Impact Record TRV-2026-1240, v2: “A capitalist contest: the AI industry v. the creative industries.” Truvace, 2026-11-04. /record/TRV-2026-1240 (accessed on the day you copy it). sha256 fd7692f3463239ee…

Change history

2 versions

Every change made to this record since it was first published, and why.

  1. Revisedv2fd7692f34632…

    Editorial pass: sharper headline; filed as context: no real AI gain or problem (gain absent, problem unsupported).

  2. Publishedv17e396100614e…

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