TruaceTracing the truth around AITuesday, August 25, 2026
TRV-2026-0693Certified recordPeer-reviewed

Navigating codified, tacit and novel rules: Mapping the human-AI creativity frontier

This paper examines the boundary between human and machine creativity by analysing 593 tasks across 126 occupations in the cultural and creative industries. Theoretically, we propose an evolutionary conceptualisation of creativity, structured around three rule types corresponding to retention (codified), adoption (tacit), and origination (novel) phases. Empirically, using GPT-4, we generate synthetic annotations of the semantic content of task descriptions in the Australian Skills Classification. We derive indic…

Media & Arts · The Trace — both readings · certified 2026-08-08 · v1 · article view · machine-readable

Current reading — gain

AI autonomy feasibility increases when defined cognitive rules combine with novel rule creation, supporting a predominantly hybrid human-AI configuration across creative tasks.

Current reading — problem

Tacit rules are negatively associated with AI autonomy feasibility, constraining full replacement to 2.7% of tasks and leaving 11.0% AI immune in cultural and creative occupations.

What this doesn’t fix

Findings rely on synthetic annotations generated by GPT-4 and a simulated classification of tasks rather than observed workplace deployment, limiting generalizability beyond the Australian Skills Classification task descriptions.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0693, v1: “Navigating codified, tacit and novel rules: Mapping the human-AI creativity frontier.” Truvace, 2026-08-08. /record/TRV-2026-0693 (accessed at citation time). sha256 fc8d2102cba39bc9

Calibration history

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

  1. Certifiedv1fc8d2102cba3

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