Moderate evidence
Published recordEducationProblem Space
More
Conceptualizing "Noaiphobia": Psychophysiological stress during unaided versus AI-assisted writing in an exploratory pilot study
- Truvace record
- TRV-2026-2946raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Controlled or validated comparison
- Sources
- 1 sourcePeer-reviewed
- sha256
- 3635d5895ee6…check it
The rapid integration of generative AI into academic workflows has raised concerns about psychological dependence and about what happens when access is lost. This paper proposes "Noaiphobia" as an exploratory construct: the acute psychophysiological stress response associated with the unavailability of AI support during task execution. We tentatively frame it as arising from three processes: withdrawal-like reactions to habitual reliance, an increase in intrinsic cognitive load once an external scaffold is remov…
The problem
In a pilot study of 18 Tunisian sports science students who use AI daily, mean heart rate was 93.10 bpm writing without AI versus 77.15 bpm with it, and self-rated stress was 73.06 mm versus 28.06 mm on a 100-mm scale.
What this doesn’t fix
The unaided condition always came first, so AI availability is confounded with order and with the greater effort of unaided writing. The study had only 18 sports science students, and no measure of AI dependency was taken.
Sources
1 on file- Addictive Behaviors Reportsdoi:10.1016/j.abrep.2026.100765
Cite this record
v1Truvace Impact Record TRV-2026-2946, v1: “Conceptualizing "Noaiphobia": Psychophysiological stress during unaided versus AI-assisted writing in an exploratory pilot study.” Truvace, 2026-11-15. /record/TRV-2026-2946 (accessed on the day you copy it). sha256 3635d5895ee64474…
Change history
1 versionEvery change made to this record since it was first published, and why. Nothing has changed since it went up.
Certified into the record
Check this record hasn’t been altered
How to check it yourself, without trusting this page
Download any version from /api/record/TRV-2026-2946 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