TRV-2026-0189Certified recordPeer-reviewed

From AI adoption to AI governance: Developing a Buddhist interpretive framework for higher education

Artificial intelligence is increasingly being adopted in higher education to support teaching, learning, administration, quality assurance, and institutional planning. However, much of the current discussion remains focused on adoption, efficiency, and technological capability, with less attention to the interpretive and governance conditions required for responsible institutional use. This article addresses that gap by developing a Buddhist interpretive framework for AI governance in higher education. Drawing o…

Policy · Problem Space — documented harm · certified 2026-07-13 · v4 · article view · machine-readable

Current reading — problem

Current discussion of AI in higher education focuses on adoption and efficiency with insufficient attention to interpretive and governance conditions needed for responsible institutional use

What this doesn’t fix

Findings are based on a small qualitative sample of 16 interview informants and 9 focus group participants with document analysis, limiting generalizability beyond studied university contexts

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0189, v4: “From AI adoption to AI governance: Developing a Buddhist interpretive framework for higher education.” Truvace, 2026-09-21. /record/TRV-2026-0189 (accessed at citation time). sha256 d7fc0f20492cc066…

Calibration history

Every change to this record since certification, in the open.

  1. Sources changedv4d7fc0f20492c…

    Source set updated

  2. Sources changedv33d42d9fb7eb4…

    Source set updated

  3. Sources changedv27039d336b823…

    Source set updated

  4. Certifiedv151fd1e1ccfd5…

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