The archive that keeps the original words

A research tool. Each case documents the complete alert sequence for a single incident at a single institution: the initial alert, every subsequent update, and the all-clear message. Every alert is annotated with analytical observations about language choices, timing, channel selection, and compliance with the Clery Act's requirements for timely warnings and emergency notifications.

What it is not: a news site, a vigilante crime database, a ranking, or an institutional report card. It is a primary-source archive intended for researchers, journalists, emergency-management practitioners, and the public-safety officers who write these messages.

One person, working with AI. New cases are researched, written, and validated through an AI ingestion pipeline that web-searches official archives, cross-references multiple sources, and assembles each case as a structured JSON file, all gated by a strict validator before anything is published. Every case is sourced; every source is linked.

In plain terms, this is a project the maintainer pays for and enjoys, not a business. If a feature or scope decision ever begins to feel commercial, it isn't. If that ever changes, this paragraph will say so.

This started as a way to learn to use AI well. Not to read about it, but to actually practice the harder skill: directing AI tools to pour large, sustained amounts of compute into building and steadily improving a single focused project over time. The archive is the thing being built, and the real exercise is learning how to make that building process reliable, systematic, and self-improving.

Campus emergency alerts turned out to be an ideal subject. The work is open-ended and verifiable: there is always another real incident to document, every claim can be checked against primary sources, and quality is enforced by an automated validator rather than by vibes. That makes it a project that compounds, where each new session of AI effort leaves the archive measurably larger and better than before.

The Clery Act (20 U.S.C. § 1092(f)) and its implementing regulations (34 CFR § 668.46) require all Title IV institutions to issue two distinct kinds of alerts: timely warnings for Clery Act crimes that pose a continuing threat, and emergency notifications for any significant emergency or dangerous situation on campus. The distinction matters enormously: timely warnings must reach the entire campus community, while emergency notifications can be targeted, yet institutions routinely conflate them. This archive documents the reality of how those legal obligations translate into the actual words that hit students' lock screens.

When a typo survives into a mass notification reaching thirty thousand people, it is not an error to correct in retrospect. It is an authenticity marker documenting the extreme urgency of composition under crisis conditions. Cleaning up alert text would destroy the evidence of how humans actually communicate when lives are at stake. Every typo, every dropped article, every all-caps sentence in this archive is preserved exactly as sent.

Each case carries an honest confidence rating: HIGH means the text is verbatim from an official source; MEDIUM means it's drawn from reliable secondary reporting (student newspapers, established local media); LOW means the text is partially reconstructed. When the alert text is reconstructed, the isVerbatimConfirmed field is set to false and the alert is rendered in italics with a dashed left border to make the distinction visible at a glance.

This archive actively prioritizes alerts from underrepresented institution types (HBCUs, community colleges, tribal colleges, institutions in US territories, small liberal arts colleges) because their alerts are systematically underrepresented in public archives due to archival practice, not crime rate. If your institution's alerts are missing, that is a gap to fill, not an indicator of safety.

Frequently asked

Questions readers ask