public-release-20260715-005
Comparado con public-release-20260714-002.
Washington University in St. Louis public-release-20260715-005 diferencias
Comparando public-release-20260714-002 con public-release-20260715-005.
Registro de cambios
Release-to-release tracker diff history with separate policy-text, newly-extracted claim, evidence, and source snapshot categories.
Estado actual de actualización y revisión del registro público.
Washington University in St. Louis currently has 8 source-backed claim records and 6 official source attributions. Latest tracked changed date: 27 jul 2026. Latest tracker diff: 0 comparable policy-text changes, 1 newly extracted claims, 0 source snapshot changes.
Esta página combina todas las diferencias de versiones públicas para Washington University in St. Louis. Las instantáneas individuales de lanzamiento siguen disponibles desde sus URL específicas del lanzamiento.
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.
Las afirmaciones extraídas recientemente son adiciones al seguimiento y no necesariamente han sido publicadas por la universidad. Los cambios en las instantáneas de origen muestran cambios de hash para la misma URL de origen y no constituyen por sí mismos cambios en la política.
Clasificación semántica para esta diferencia de versión.
Diferencia del seguimiento unificado generada a partir de todas las instantáneas de lanzamiento público para esta universidad.
Comparando public-release-20260714-002 con public-release-20260715-005.
1 diferencia de lanzamiento público
Comparado con public-release-20260714-002.
Comparando public-release-20260714-002 con public-release-20260715-005.
8 Afirmación registros
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.
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 15 may 2026, 3:21
official_guidance Tracker checked at 15 may 2026, 3:21
official_guidance Tracker checked at 15 may 2026, 3:21
official_guidance Tracker checked at 16 jul 2026, 2:25
official_guidance Tracker checked at 15 may 2026, 3:21
official_guidance Tracker checked at 15 may 2026, 3:21