Emerging evidence
Published recordEducationGeneral
More
The Transformation of Epistemic Agency and Governance in Higher Education Through Large Language Models: Toward a future of organized immaturity
- Truvace record
- TRV-2026-1191raw data (JSON)
- Version
- v3Revised
- First published
- Evidence type
- Commentary, opinion, or narrative review
- Sources
- 1 sourcePeer-reviewed
- sha256
- 795d4b2d44a3…check it
Why and how does the use of large language models (LLMs) transform epistemic agency and epistemic governance in higher education (HE), and why can this transformation usher organized immaturity as a new organizing principle for HE? Asking these questions now matters because (i) the profound impact of LLMs on epistemic agency and governance in HE has not been adequately scrutinized by theorists of organizations and HE to date and (ii) LLMs represent an epistemic technology that fundamentally alters who produces k…
The problem
Widespread adoption and legitimization of LLMs in higher education research and education rewrites epistemic governance to favor Big EdTech, turning epistemic agents into epistemic consumers and undermining academic freedom and holistic knowledge needed for democratic deliberation.
Sources
1 on file- Organization Studiesdoi:10.1177/01708406251392002
Cite this record
v3Truvace Impact Record TRV-2026-1191, v3: “The Transformation of Epistemic Agency and Governance in Higher Education Through Large Language Models: Toward a future of organized immaturity.” Truvace, 2026-11-05. /record/TRV-2026-1191 (accessed on the day you copy it). sha256 795d4b2d44a390ad…
Change history
3 versionsEvery change made to this record since it was first published, and why.
Voice pass: plainer wording and study attribution; no facts or figures changed.
Editorial pass: sharper headline; filed as context: no real AI gain or problem (gain absent, problem unsupported).
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-1191 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