By Riley Tanaka · Published May 13, 2026 · Updated May 13, 2026
Last reviewed: May 13, 2026.
On May 8, 2026, the Pentagon did something it had never quite done with UAP material before. It shipped a website. Not a PDF dump on a 1990s subdomain. Not a press release with a downloadable .docx. A real site, with navigation, a search bar, a sitemap, document categorization, and a positioning statement that read like a launch deck: let the public “make up their own minds.” The URL is war.gov/ufo/, and the polish is the story. [1]
I have been covering .gov releases since the JFK records drop in January, and I can tell you what a federal product launch usually looks like. It looks bad. PURSUE does not look bad. PURSUE looks productized.
Direct Answer
PURSUE is the Pentagon’s UAP Records Public Release page at war.gov/ufo/, launched May 8, 2026 by the All-domain Anomaly Resolution Office (AARO). Unlike past disclosures, it ships with consumer-grade UX: indexed documents, structured metadata, a stated framing (“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 has a title, a date, a source-office label, a file size, and a redaction status. The records are not paginated through a 1998-era CGI script. They are listed in a responsive table you can sort. The PDFs are individually hyperlinked. The hyperlinks resolve. [2]
If you have ever tried to find a specific page inside the CIA CREST reading room, or hunted through the FBI Vault for the Hottel memo, you know how unusual this is. 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 contains historical AARO holdings, declassified imagery, internal memoranda from predecessor offices, and a curated set of pilot incident files. The site sorts these into categories users can filter by. AARO’s existing reporting form, the one accessible at aaro.mil, is linked from the masthead. The “About PURSUE” page explains the office’s authorities under the FY2024 NDAA. The tone is bureaucratic but legible. [3]
“Make Up Their Own Minds” Is Positioning Copy
Read the framing line carefully. “We want the public to be able to make up their own minds.” That is not a neutral statement. That is positioning. [4]
Compare it to past .gov disclosure language. The 1995 CIA “Family Jewels” release was filed under a tone of grim compliance. The 2017 New York Times UAP videos surfaced through a journalist, not a portal. The 2021 ODNI Preliminary Assessment on UAP arrived as a 9-page PDF with a press call. 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 UX comparison is the National Archives release of the final JFK assassination records in January 2026 at archives.gov/research/jfk. That site indexes more than 80,000 documents, supports full-text search, and follows the U.S. Web Design System. It is a strong baseline. PURSUE is lighter on document volume but uses the same design vocabulary: the same typography, the same blue-and-white masthead, the same accordion-style filters. The DNA traces back to the 18F and U.S. Digital Service work that started under the Obama administration and survived under successor offices at GSA. [5]
In other words: PURSUE was not built in a vacuum. It was built by people who have been quietly upgrading federal web property for a decade. That competence is now pointed at UAP.
Discoverability Mechanics: How a .gov Release Becomes Findable
A site that ships without discoverability mechanics may as well not ship. PURSUE shipped with all of them. I checked. [6]
- A sitemap.xml at war.gov/sitemap.xml lists the new /ufo/ tree, which means crawlers picked it up within hours.
- The page renders server-side. SEO descriptions and Open Graph tags are populated. Title tags read cleanly in search results.
- The Wayback Machine took its first snapshot on launch day. Archive.today snapshots followed within hours, then mirrors of the individual PDFs. The crowd does this work fast when it notices.
- Press distribution was coordinated. The May 8 Pentagon press briefing put the URL on the lectern and gave reporters embargoed access the night before.
By Saturday morning, you could find PURSUE through a generic Google query, a DuckDuckGo query, a Reddit thread, a YouTube video essay, and three different Substack newsletters. 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. If you look at the PDFs inside PURSUE, the file names follow a pattern: office-of-origin, document-type, date, sequence number, redaction status. That schema reveals more about the underlying records system than any press release will. It implies a master index. It implies a permanent record locator. It implies that future releases will slot into the same taxonomy without renaming the existing files. [7]
Redaction overlays follow standard FOIA exemption codes, mostly (b)(1) national defense and (b)(3) statutory, with the exemption cited on the redacted page itself. That is the same overlay the National Archives uses. It tells you that someone made the call to be auditable rather than artistic with the black bars.
What is not hyperlinked is also a tell. The site does not deep-link from a memo to the underlying source documents the memo cites. That is a Release 02 problem. For now, the linking graph 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]
- A GitHub repository appeared mirroring every PDF with OCR text extraction.
- A subreddit thread aggregating “first reads” reached the front page of r/UFOs and r/conspiracy.
- YouTube reaction-video creators posted side-by-side screen recordings of themselves scrolling the portal.
- A Substack ran a 4,000-word post comparing PURSUE to the AARO Historical Record Report Volume I from 2024.
- An archive.today mirror of war.gov/ufo/ went up before noon on May 9.
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 held a press briefing on May 8, 2026 to announce PURSUE. 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 implies more is coming without committing to a date. 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 Marcus Halloway’s record-by-record analysis. 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 from an office whose authorities are still being negotiated in Congress. The structure is real. The selection is the question.
PURSUE is also not a one-time event. Release 01 is in the URL. That is a product roadmap. Release 02 will arrive on a schedule that the office controls. Each subsequent release will be measured against the launch. The bar has been set unusually high for a federal disclosure, and the office will now have to clear it twice a year, or whatever cadence they commit to.
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) satisfy a statutory transparency obligation, (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. For the political-coalition story behind how this site got built and shipped, see Augustus Kane’s analysis. For the record-by-record audit of what is actually inside, see Marcus Halloway’s piece. For the product launch as product launch, you are reading it.
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 file naming convention frozen in time at 3:14pm Eastern on May 8, 2026: those are the primary sources for what the Pentagon did. The screenshots are dated. The threads are archived. The launch happened.
