public-release-20260715-005
Compared with public-release-20260714-002.
University of California, Riverside public-release-20260715-005 diff
Comparing public-release-20260714-002 to public-release-20260715-005.
Change log
Release-to-release tracker diff history with separate policy-text, newly-extracted claim, evidence, and source snapshot categories.
Current public record freshness and review state.
University of California, Riverside currently has 9 source-backed claim records and 6 official source attributions. Latest tracked changed date: Jul 16, 2026. Latest tracker diff: 0 comparable policy-text changes, 2 newly extracted claims, 0 source snapshot changes.
This page combines all public release diffs for University of California, Riverside. Individual release snapshots remain available from their release-specific URLs.
This tracker is not legal advice, not academic integrity advice, and not an official university statement unless a linked source is the university's own official page.
Newly extracted claims are tracker additions and are not necessarily newly published by the university. Source snapshot changes show hash changes for the same source URL and are not by themselves policy changes.
Semantic classification for this release diff.
Unified tracker diff generated from all public release snapshots for this university.
Comparing public-release-20260714-002 to public-release-20260715-005.
1 public release diff
Compared with public-release-20260714-002.
Comparing public-release-20260714-002 to public-release-20260715-005.
9 claim records
Google NotebookLM is listed for University of California, Riverside in an official university AI tools source. Derived availability: allowed. Derived endorsement type: institutionally licensed or procured.
Google Gemini is listed for University of California, Riverside in an official university AI tools source. Derived availability: allowed. Derived endorsement type: institutionally licensed or procured.
UCR's Provost guidelines state that generative AI tools that have not passed a campus security review may be used with public data only; for other data classifications, UCR points to secure tools including Google Gemini and Microsoft Copilot.
UCR's Provost generative-AI guidelines say instructional uses of generative AI by instructors or students should aim to improve student learning and align with UCR's instructional mission.
UCR ITS lists UCR-supported AI tools by role and allowed data level, including Gemini, NotebookLM, Google AI Studio, Microsoft 365 Copilot, Vertex AI, Zoom AI Companion, The Grove, and a ChatGPT EDU offering that the page says is not currently available.
UCR's student-facing AI announcement says students should discuss generative-AI expectations with professors, use AI to assist or enhance rather than replace original work, avoid generating entire deliverables, and cite AI-generated content or data when used.
UCR XCITE advises instructors to discuss when AI may be used in coursework and how it should be cited, and its sample syllabus language treats uncited AI use as a potential academic-integrity issue.
UCR's public generative-AI guidance for instructional settings places course-level use decisions with the Instructor of Record rather than setting one universal student-use rule in the evidence reviewed here.
UCR's general academic-integrity page defines academic misconduct to include using prohibited or inappropriate materials, plagiarism without appropriate credit, and unauthorized collaboration without instructor permission.
6 source attributions
official_guidance Tracker checked at May 16, 2026, 6:27 PM
official_guidance Tracker checked at May 16, 2026, 6:20 PM
official_guidance Tracker checked at May 16, 2026, 6:29 PM
official_pdf Tracker checked at May 16, 2026, 6:22 PM
official_guidance Tracker checked at Jul 16, 2026, 7:48 AM
official_guidance Tracker checked at May 16, 2026, 6:26 PM