About this project

About & methodology

The UMN Ed Tech Transparency Project is an independent, unofficial resource that helps faculty, students, staff, and community members understand the University of Minnesota's policies on AI and technology, its contracts with educational technology companies, and how those choices compare with peer universities. It is not produced or endorsed by the University of Minnesota.

Principles

How this site was made

This site was researched, written, and built using Claude Code, Anthropic's AI coding agent — under the direction of a human maintainer, who chose every research question, set the verification standards, reviewed the findings, and decides what is published. The AI did the labor: searching the web and the indexed full text of public archives (such as UMN's Digital Conservancy and Board of Regents materials), drafting the plain-language summaries, assembling every citation, and building the site's search, monitoring, and link-checking systems. The judgment about what to investigate and what to publish is human.

Because AI research can make mistakes, the site is designed so you never have to take its word for anything:

Verification levels

Each entry carries a verification badge:

Dollar figures for contracts come from public Board of Regents docket summaries and news reporting, not from the contracts themselves, which UMN does not publish. Full contract documents can be requested under the Minnesota Government Data Practices Act ↗.

How the weekly policy check works

A scheduled job runs once a week. It fetches each page on our watchlist of official UMN policy and AI-guidance pages, reduces each page to its text content, and compares it against the previously stored snapshot. If a page changed, the job records an entry in the public change log with the date and a link to the page, and updates the "last checked" timestamp shown on the Policies page. The watchlist, snapshots, and checker code are all in this site's public repository, so the monitoring itself is auditable.

The checker detects that a page changed, not whether the change matters — a changed timestamp might be a typo fix or a major policy revision. Entries in the change log are prompts to go read the page, not summaries of what changed.

Out of respect for UMN Libraries' request that automated traffic avoid their archive systems, the automated checks never probe links to the Digital Conservancy, UMedia, or other Libraries archive sites — those citations are verified by humans only.

What this site is not

Corrections

Found an error or a missing source? Open an issue in the site's repository ↗ or contact the maintainer. Corrections are made publicly and tracked in the repository history.