The Red Thread Files
UFO / UAP · Consciousness
1945–2026621 entities437 of 1390 connections sourced138 documents held
The Red Thread Files
Government / Military

PURSUE

2026-05-08what this date marks is not recorded

Presidential Unsealing and Reporting System for UAP Encounters - the US Department of War website at war.gov/ufo, launched 8 May 2026 to publish declassified UAP records, described in the launch announcement as an interagency effort with the White House, ODNI, the Department of Energy, AARO, NASA, the FBI and other intelligence community components. FIVE RELEASES ARE LISTED THERE: 8 May, 22 May, 12 June, 10 July and 7 August 2026, each with a document bundle and a video bundle. This project holds an announcement page for the first three only, each issued by Sean Parnell in near-identical terms; Releases 04 and 05 are attested by the war.gov/ufo listing page itself and by the bundles, not by an announcement held here. NONE OF THE ANNOUNCEMENTS STATES HOW MANY FILES ITS RELEASE CONTAINS - all three were fetched on 4 September 2026 and checked for a count, and any per-release file count would have to come from somewhere this project does not hold. The third announcement states that war.gov/ufo "has received over 1.7 billion hits worldwide" since launching. WHAT THIS PROJECT HOLDS: all five document bundles, downloaded by the operator and supplied 4 September 2026 - 241 files and about 2.54 GB unzipped, being 130 files in Release 01, 6 in Release 02, 63 in Release 03, 17 in Release 04 and 25 in Release 05. NINETEEN DOCUMENTS ON THIS MAP CAME OUT OF PURSUE, and holding a file is not reading it: 222 of the 241 are held and unregistered.

In the UAP recordRuled into the unidentified-phenomena thread on 2 September 2026 from this entity's own name and role text, which contain: "uap". An editorial classification of what thread this entity belongs to; it rests on no page and does not claim to. Neighbours were not used - see apply-subjects-2026-09-02.mjs for why.

14 of 25 connections resolve to a document you can open.

2 notes on how this record was made

Documents8 behind these connections1 more that names it

Documents behind these connections

Also named in documents we hold

This entity's name appears in the 1 document below. That is the entire claim. Nothing here is evidence for anything on this map, no connection rests on it, and it says nothing about what the document is about. It is a place to look next.

Presidential Unsealing and Reporting System for UAP Encounters (PURSUE)
named in the title

25 connections

ColourWhistleblowersIncidentsScientistsGovernmentCongressOrganizations

Notes on this record

What this is

Classified `form: person` by the August 2026 pass and corrected on 23 August 2026. PURSUE is a Department of Defense records-release system, not a person. Filed as a programme, following MK-ULTRA. Note the consequence on the front door: the timeline colours government bodies and programmes in the right-hand column and leaves government PEOPLE uncoloured, so this correction makes PURSUE print in the gov colour at 2026 - which is what that rule is for.

This description, checked against the record

REWRITTEN 4 September 2026. The previous text claimed "a second release of 222 files" and "a third release of 72 files". Both official announcements were fetched that day and neither states a count; the numbers were not traceable to anything held here and were removed rather than left reading as fact. It also called PURSUE a Department of Defense website - the announcements and the site itself say Department of War. The previous text is kept here: "Presidential Unsealing and Reporting System for UAP Encounters - the Department of Defense website launched May 8, 2026 to release declassified UAP records, part of a Trump-directed transparency initiative involving the Pentagon, DOE, ODNI, NASA, and FBI. Its first release spanned documents from 1944 to the present; a second release of 222 files followed May 22, 2026; a third release of 72 files followed June 12, 2026. Despite officials promising further tranches \"every few weeks,\" no additional public release had followed as of early July 2026." CORRECTED AGAIN 4 September 2026, after the operator supplied all five bundles and asked what had been read. Two claims in the text written earlier that same day were wrong. It said "Three releases are published there: 8 May, 22 May and 12 June 2026" while this same file already held a Release 04 container row pointing at a 10 July URL - the file contradicted itself, and war.gov/ufo lists five. And it said "EIGHT DOCUMENTS ON THIS MAP CAME OUT OF PURSUE" when Release 02 had added six the day before, making fourteen; that sentence was not updated when the documents were. Both were counting errors in a paragraph whose whole job is to count, so check-releases.mjs was added the same day to refuse a release count or a document count in this text that disagrees with the rows the file actually holds. Corrected a third time later the same day, this time BY THE GATE rather than by hand: five Release 03 documents were registered an hour after the paragraph was rewritten, and check-releases.mjs refused the build until the sentence caught up.