Drafted with AI assistance from the sources listed; images are AI-generated illustrations. How EsoVitae is made
On May 8, 2026, the Pentagon released UAP records in a new shape. It shipped a website built for the release. Not a PDF dump on a 1990s subdomain. Not a press release with a downloadable .docx. A real page, with its own section navigation, a sortable index of records, embedded video, and, in the Pentagon’s announcement on X, a positioning line that read like a launch deck: the public “can ultimately make up their own minds.” The URL is war.gov/ufo/, and the polish is the story. [1]
A federal product launch usually looks bad. PURSUE does not look bad. PURSUE looks productized.
Direct Answer
PURSUE, the Presidential Unsealing and Reporting System for UAP Encounters, is the Pentagon’s UAP records page at war.gov/ufo/. It launched on May 8, 2026, after a February directive from President Trump, with the Department of War overseeing a multi-agency release and the Office of the Director of National Intelligence in support. Unlike past disclosures, it ships with consumer-grade UX: a sortable index of records, structured metadata, a stated framing (the public can “make up their own minds”), and the discoverability mechanics of a real product launch.
The Site Itself Is the Story
Open war.gov/ufo/ in a clean browser. Inspect the page. The first thing you notice is that the document index is real. Each entry carries a title, an agency label, a release date, an incident date and location, and a file type, and the list can be sorted on any of those fields. Records flagged as redacted open with a note explaining what was withheld and why. Each PDF, image and video has its own link. [2]
If you have ever tried to find a specific page inside the FBI Vault, you know how unusual this is. Release 01’s own notes say one FBI case file is only “partially posted on FBI vault with more redactions and some pages missing.” Federal records portals are normally optimized for the agency, not the reader. PURSUE is optimized for the reader. That is a design decision, and design decisions at the Department of War get signed off at levels that matter.
In short: the architecture itself communicates intent. A document dump says “we complied.” A product says “we want you to find this.”
What ships at launch
Release 01, “cleared for release” on May 8, 2026, holds about 160 files from four agencies: Department of War mission reports and pilot debriefs, FBI case files on flying discs going back to 1947, NASA transcripts and photographs from the Gemini and Apollo missions, and State Department cables. The index can be sorted by agency, date, location and file type. Readers who want “other historical UAP records” are pointed to AARO.mil. The page’s “About” section rests the effort on President Trump’s directive, with the Department of War overseeing it and support from the Office of the Director of National Intelligence. The tone is bureaucratic but legible. [3]
“Make Up Their Own Minds” Is Positioning Copy
Read the framing line carefully. In a post on X announcing the release, the Pentagon said President Trump “is focused on providing maximum transparency to the public, who can ultimately make up their own minds about the information contained in these files.” That is not a neutral statement. That is positioning. [4]
Compare it to past .gov disclosure language. The CIA released its 702-page “Family Jewels” file in 2007, 15 years after the National Security Archive asked for it under the Freedom of Information Act. The 2017 UAP videos surfaced through New York Times reporting, not a portal. The 2021 ODNI Preliminary Assessment on UAP arrived as a 9-page PDF. The framing was always “we are providing information as required.”
PURSUE shifts the agency. The reader is the analyst now. That move accomplishes three things at once. It defuses accusations of suppression. It transfers interpretive burden. And it sets a baseline expectation that future releases will arrive in the same shape. You launch a product, you have a roadmap. You launch a portal called Release 01, you have committed to a Release 02.
Comparable launches: archives.gov JFK and the .gov product lineage
The closest comparison is the same administration’s release of JFK assassination records at archives.gov/research/jfk. The National Archives began it on March 18, 2025, added a further batch on January 30, 2026, and lists more than 90,000 released pages in a plain table of file names sorted by record number. It is a strong baseline for completeness, not for design. PURSUE is far lighter on volume and far heavier on presentation, and it is not a standalone build: it sits inside the Department of War’s main website, whose footer credits hosting to the Department of War Information Activity’s WEB.mil service. [5]
Discoverability Mechanics: How a .gov Release Becomes Findable
A site that ships without discoverability mechanics may as well not ship. PURSUE’s launch-day code and archive record show most of them. [6]
- The page sets its own Open Graph and Twitter card tags, with a PURSUE title, a description of the multi-agency effort and a UAP still as the share image, so links to it unfurl cleanly on social platforms. Its plain meta description, by contrast, is still the Department of War’s site-wide boilerplate.
- The records index is not baked into the HTML. The page loads it in the browser from a CSV file, which also made the full launch-day record list easy to archive.
- The Wayback Machine captured the page 22 times on May 8, the first at 8:07 a.m. Eastern, and saved the records file the same morning.
- The announcement went out as a Pentagon post on X, and the Associated Press had a story out the same day.
Within hours the release had wire coverage and dedicated forum threads. That is product distribution. The Pentagon did not just release documents. It seeded an internet ecosystem.
Metadata Politics: What the File Names Tell You
File naming conventions are policy. The file names inside PURSUE do not follow one schema. FBI material keeps its archival case-file identifiers, such as 62-HQ-83894 Section 10. The newer Department of War records carry fresh labels built from a prefix and sequence number, a document type, a place and a date, such as “DOW-UAP-D56, Range Fouler Debrief, Arabian Sea, August 2020.” NASA items follow a matching NASA-UAP pattern. The new prefixes imply a master index that later releases can extend. The archival names show that the release is stitched together from the agencies’ existing filing systems. [7]
Redactions are flagged in the index itself. About two-thirds of the launch-day records are marked as redacted, and each opens with the same note: redactions protect “the identity of eyewitnesses, the location of government facilities,” or sensitive military information not related to UAP. It tells you that someone made the call to be auditable rather than artistic with the black bars.
What is linked is also a tell. In the launch-day index, 35 entries point to a companion record, most often a mission report matched with its video. Beyond those pairings, the index does not connect one record to another, so the linking graph mostly terminates at the document level. Researchers will have to do the cross-referencing themselves, which they will, and which the Pentagon almost certainly knows they will.
The Second-Order Ecosystem
Within 48 hours of launch, the rest of the internet did what the rest of the internet does. [8]
- Metabunk, the debunking forum run by Mick West, opened a thread that morning to catalog and analyze the files. It ran to ten pages.
- The Internet Archive’s Wayback Machine saved the page and its records file again and again through launch day.
None of this is incidental. A federal release that does not generate this ecosystem is, in product terms, a launch with no downstream. PURSUE has downstream. The downstream is the point. The Pentagon transferred the work of interpretation to a distributed network of strangers, and the strangers said yes.
The communications strategy in plain English
The Pentagon announced PURSUE on May 8, 2026 with the new page and a post on X. The line that did the rhetorical work was “make up their own minds.” Read as launch copy, the sentence does the following. It positions the Department of War as a neutral provider, not an advocate. It lowers the stakes of any single document by framing the release as a collection, not a conclusion. It promises more, in tranches “every few weeks,” without committing to dates. And it pre-empts the most predictable critique, which is that the government is hiding the good stuff, by inviting the public to look. [9]
Whether the good stuff is there or not is a question for a record-by-record analysis of the contents. The product framing is its own story.
What PURSUE Is Not
PURSUE is not transparency. Transparency is a stronger word than this release earns. PURSUE is a curated, structured, and well-distributed selection of records chosen, reviewed and declassified by the agencies that hold them. The structure is real. The selection is the question.
PURSUE is also not a one-time event. “Release 01” is in the page’s own navigation. That is a product roadmap. The page promised new tranches “every few weeks,” and Release 02 followed on May 22, 2026. Each subsequent release will be measured against the launch. The bar has been set unusually high for a federal disclosure, and the department now has to clear it every few weeks.
PURSUE is, finally, not for the believer or the skeptic. It is for the researcher. The site assumes the user has a question and is willing to do the work to answer it. That is unusual. Most federal communications assume the user has a position and is looking for confirmation. PURSUE refuses to confirm. It hands you the records and steps back. That refusal is the most professional move on the page.
Why the UX Matters for the Story
If you cover this beat, the temptation is to evaluate PURSUE on what it says about UAP. That is a category error. PURSUE is a product. Products are evaluated on what they are designed to do. PURSUE is designed to (a) answer a presidential directive on UAP transparency, (b) shift interpretive labor to the public, (c) establish a baseline format for future releases, and (d) survive crawler indexing, mirror creation, and partisan re-framing without losing structural integrity.
On every one of those design criteria, the launch succeeded. Whether the contents of Release 01 advance public understanding of UAP is a separate question, and a slower one. The political coalition behind the site and the record-by-record contents are separate questions; this article covers the launch itself.
The internet has a memory, and most of what gets written about contested topics cites secondary write-ups of secondary write-ups. The original screenshot, the launch-day Wayback snapshot, the records file as it stood on the morning of May 8, 2026: those are the primary sources for what the Pentagon did. The screenshots are dated. The threads are archived. The launch happened.
Sources
- U.S. Department of War, Presidential Unsealing and Reporting System for UAP Encounters (PURSUE), war.gov/ufo, as captured on 8 May 2026. web.archive.org; Collin Binkley and Seung Min Kim, Pentagon begins releasing new files on UFOs and says the public can draw its own conclusions, Associated Press, 8 May 2026. abc7.com
- U.S. Department of War, Presidential Unsealing and Reporting System for UAP Encounters (PURSUE), war.gov/ufo, as captured on 8 May 2026. web.archive.org; U.S. Department of War, PURSUE Release 01 records index (uap-csv.csv), as captured on 8 May 2026. web.archive.org
- U.S. Department of War, Presidential Unsealing and Reporting System for UAP Encounters (PURSUE), war.gov/ufo, as captured on 8 May 2026. web.archive.org; U.S. Department of War, PURSUE Release 01 records index (uap-csv.csv), as captured on 8 May 2026. web.archive.org
- Collin Binkley and Seung Min Kim, Pentagon begins releasing new files on UFOs and says the public can draw its own conclusions, Associated Press, 8 May 2026. abc7.com; for the earlier releases compared here: Thomas Blanton (ed.), The CIA’s Family Jewels, National Security Archive Electronic Briefing Book No. 222, updated 26 June 2007. nsarchive2.gwu.edu; Office of the Director of National Intelligence, Preliminary Assessment: Unidentified Aerial Phenomena, 25 June 2021. dni.gov
- National Archives and Records Administration, JFK Assassination Records – 2025 Documents Release. archives.gov; U.S. Department of War, Presidential Unsealing and Reporting System for UAP Encounters (PURSUE), war.gov/ufo, as captured on 8 May 2026. web.archive.org
- U.S. Department of War, Presidential Unsealing and Reporting System for UAP Encounters (PURSUE), war.gov/ufo, as captured on 8 May 2026. web.archive.org; Internet Archive, Wayback Machine capture list for war.gov/ufo, 8 May 2026. web.archive.org; Collin Binkley and Seung Min Kim, Pentagon begins releasing new files on UFOs and says the public can draw its own conclusions, Associated Press, 8 May 2026. abc7.com
- U.S. Department of War, PURSUE Release 01 records index (uap-csv.csv), as captured on 8 May 2026. web.archive.org
- Mick West, War.gov/UFO – Department of War Releases UAP Files – 2026 Release 1, Metabunk forum thread, started 8 May 2026. metabunk.org; Internet Archive, Wayback Machine capture list for war.gov/ufo, 8 May 2026. web.archive.org
- U.S. Department of War, Presidential Unsealing and Reporting System for UAP Encounters (PURSUE), war.gov/ufo, as captured on 8 May 2026. web.archive.org; Collin Binkley and Seung Min Kim, Pentagon begins releasing new files on UFOs and says the public can draw its own conclusions, Associated Press, 8 May 2026. abc7.com; U.S. Department of War, PURSUE page announcing Release 02, as captured on 23 May 2026. web.archive.org