Editorial pass: sharper headline; filed as context: no real AI gain or problem (gain absent, problem unsupported).
The exact text we saved
This is the version exactly as it was saved, character for character. The SHA-256 hash below is a 64-character code worked out from that text. Run the same text through SHA-256 and you get the same code; change a single letter and the code comes out completely different. Each version also stores the previous version’s hash, which chains them together so no version can be swapped out quietly.
TRUVACE RECORD VERSION record: TRV-2026-1240 version: 2 kind: revised reason: Editorial pass: sharper headline; filed as context: no real AI gain or problem (gain absent, problem unsupported). timestamp: 2026-11-04T09:55:39.394785Z status: published lens: general sector: entertainment headline: A capitalist contest: the AI industry v. the creative industries dek: 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… gain_title: (none) problem_title: 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. trace_subject: (none) gain_reading: (none) gain_evidence: (none) problem_reading: 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. problem_evidence: use copyrighted works to train their models without permission and compensation to creative industries rightsholders | privilege the interests of Big Tech in exploiting online data for profit quick_read: A peer-reviewed paper published 18 September 2025 examines whether developers of large language models should be allowed to train on copyrighted works without permission and compensation to rightsholders, focusing on the UK. It frames the issue as a contest between an imaginary centered on market-driven growth of generative AI and one centered on equity. The stakes are how copyright policy balances AI industry expansion against sustainability of creative industries. The paper contends debate currently favors Big Tech interests in exploiting online data, and points to licensing and other public-good oriented policies as alternatives, though it does not present new empirical data on licensing outcomes or economic effects. limitation: Analysis is bounded to the UK policy context and to conceptual imaginaries rather than empirical measurement of economic impacts. tag: Context key_points: The paper frames the conflict as between a market-driven imaginary favoring generative AI growth and an alternative imaginary emphasizing equity and non-market values. | Policy options discussed include licensing arrangements for use of copyrighted works in model training. | The analysis is situated in the UK policy context regarding text and data mining exceptions. rundown: The paper contrasts two social imaginaries: one that prioritizes market-driven growth of generative AI requiring text and data mining, and another that emphasizes equity and non-market values for creative labour. It argues current policy debates favor Big Tech exploitation of online data for profit and neglects approaches that would let both technology innovation and creative labour contribute to the public good, with licensing raised as a potential mechanism. sources: - peer_reviewed | Journal of the British Academy | https://doi.org/10.5871/jba/013.a38 | 2025-09-18 prev: 7e396100614e18ac0d5c1fc618bb6161215237e16a7ca5d98b1b760aedb89128
- SHA-256 hash
- fd7692f3463239ee0825aa218c348173c105e69caf3f841628e1226c73877cae
- Previous version’s hash
- 7e396100614e18ac0d5c1fc618bb6161215237e16a7ca5d98b1b760aedb89128
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.
ace