TRV-2026-2300Certified recordPeer-reviewed

From Cheating to Coaching: How Chemistry Syllabi Frame Academic Integrity in the Age of Generative AI

Abstract Generative artificial intelligence (AI) is rapidly changing expectations for academic integrity in higher education, yet it remains unclear how institutional AI governance is translated into course-level guidance. This study examines how academic integrity and generative AI are framed in chemistry course documents and institutional policy documents. Using a hybrid inductive–deductive qualitative document analysis, I analyzed 18 publicly available chemistry course documents and 17 institutional policy do…

Policy · Problem Space — documented harm · certified 2026-10-28 · v1 · article view · machine-readable

Current reading — problem

Only 2 of 18 chemistry course documents mention generative AI, while 15 of 17 institutional policies do, leaving students with little course-level guidance on acceptable AI use.

What this doesn’t fix

The analysis covers a small, publicly available document sample (18 course documents and 17 policy documents from nine institutions), and the author notes policies and syllabi will continue to evolve, so the findings are a baseline rather than a lasting measure.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-2300, v1: “From Cheating to Coaching: How Chemistry Syllabi Frame Academic Integrity in the Age of Generative AI.” Truvace, 2026-10-28. /record/TRV-2026-2300 (accessed at citation time). sha256 331f31d8adee7104…

Calibration history

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

  1. Certifiedv1331f31d8adee…

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