50/100

Moderate evidence

ProblemPublished recordLaborProblem Space

AI Identity Threat and Job Crafting Among University Teachers

Truvace record
TRV-2026-2998raw data (JSON)
Version
v1Published
First published
Evidence type
Survey
Sources
1 sourcePeer-reviewed
sha256
8edace30c3ce…check it

Generative artificial intelligence can challenge teachers’ professional self-evaluations, yet how these concerns relate to subsequent work behavior remains unclear. We examined AI identity threat, supervisor-directed feedback seeking, and individual job crafting in a three-wave study at two universities in central China (n = 563 at baseline). The behavioral measures were adapted to an AI-related work context. A multiple-indicator random-intercept cross-lagged panel model separated stable differences between teac…

The problem

In a three-wave study of 563 teachers at two central-China universities, higher-than-usual AI identity threat was followed by more requests for supervisor feedback (β = 0.428 and 0.398), showing generative AI unsettling teachers' professional self-evaluations.

What this doesn’t fix

The feedback-to-crafting coefficients differed between intervals, but unequal observation intervals and possible academic-calendar influences limit how that difference can be interpreted.

Sources

1 on file
  1. Behavioral Sciencesdoi:10.3390/bs16112166
    Peer-reviewed2026-11-16

Cite this record

v1

Truvace Impact Record TRV-2026-2998, v1: “AI Identity Threat and Job Crafting Among University Teachers.” Truvace, 2026-11-17. /record/TRV-2026-2998 (accessed on the day you copy it). sha256 8edace30c3ceebc7…

Change history

1 version

Every change made to this record since it was first published, and why. Nothing has changed since it went up.

  1. Publishedv18edace30c3ce…

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