public-release-20260715-005
Compared with public-release-20260714-002.
Washington University in St. Louis 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.
Washington University in St. Louis 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, 1 newly extracted claims, 0 source snapshot changes.
This page combines all public release diffs for Washington University in St. Louis. 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
Microsoft 365 Copilot Chat is listed for Washington University in St. Louis in an official university AI tools source. Derived availability: allowed. Derived endorsement type: not specified.
WashU IT guidance says users should not enter Washington University or secure data, including deidentified healthcare data, into publicly accessible non-protected AI tools.
WashU student-facing AI guidance tells students to check the instructor and syllabus about whether and how AI tools may be used for classwork, and says that if no explicit policy is outlined, it is better to assume AI use is banned.
WashU CTL student guidance says students should not represent AI-tool output as their own work and should cite AI contributions when using AI tools.
WashU IT AI purchasing guidance says an Office of Information Security Vendor Security Review is required when an AI tool has not yet been approved and the user intends to use or purchase it.
WashU identifies specific secure AI tools as reviewed and approved for use with sensitive information, including HIPAA- or FERPA-covered data.
WashU CTL course-policy guidance presents multiple possible GenAI policy categories for instructors, including allowed without restriction, allowed with citations, partially restricted, and completely restricted.
WashU IT's DeepSeek advisory says DeepSeek is not safe for use with university non-public information.
The WashU+AI hub tells students that responsible generative-AI use includes reviewing course expectations for authorized use and seeking clarification from instructors before using generative AI tools.
6 source attributions
official_guidance Tracker checked at May 15, 2026, 3:21 AM
official_guidance Tracker checked at May 15, 2026, 3:21 AM
official_guidance Tracker checked at May 15, 2026, 3:21 AM
official_guidance Tracker checked at Jul 16, 2026, 2:25 AM
official_guidance Tracker checked at May 15, 2026, 3:21 AM
official_guidance Tracker checked at May 15, 2026, 3:21 AM