PURSUE Changes Log

FIRST PUBLISHED 20 MAY 2026 · UPDATED 1 NOV 2026 · COUNTED FROM THE RAW CSV

What this page contains. Every change to war.gov's PURSUE CSV that we can document, from the first release on May 8 to today's 478-row file (Release 07, revised October 26). It has a row-by-row diff of Releases 03 to 07 computed from the raw CSV rows, row-by-row diffs of Release 06's September 24 amendment and Release 07's October 26 revision, a timeline of every CSV state our poller recorded, one card per release, and the original May 11 comparison (161 to 158 rows) further down. Each claim on this page is a direct count. No interpretation of war.gov's intent: we say what changed, not why. No characterizations of "renames," "consolidations," or "reclassifications" - those would be inferences and are kept off this page. Where we cannot reproduce something, the page says so.

Headline findings: (1) No row has been removed. In each of the four steps from Release 03 to Release 07, zero rows were removed. Of the 294 rows in the Release 03 CSV, 293 are in today's file with the same ID and file link; the other, DOW-UAP-D042, is there too, with a new title and file link. (2) War.gov does edit existing rows after publishing: 87 rows across those four steps. 39 had the "Featured" flag cleared, and 44 had a PDF Pairing list replaced by a tag (4 rows are in both groups). (3) War.gov revised Releases 06 and 07 after they appeared. Our poller first recorded Release 06's CSV at 446 rows in total (71 of them new), then at 447 four hours later, and at 450 six days later. The six-day step is diffed row by row: 3 transcripts added, 5 existing rows edited, none removed. Release 07's CSV was revised three days after it appeared: no row added or removed, all 478 Release Date values and 159 Incident Date values rewritten, one of them wrongly. (4) The May 11 revision, covered below, added and removed no files: zero PDFs and zero videos in either direction.

Releases 03 to 07, row by row

We compared the CSV for each release with the one before it, matching rows on their ID and file link. No row was removed in any of the four steps. Of the 294 rows in the Release 03 CSV, 293 are in today's 478-row file with the same ID and file link. The other one, DOW-UAP-D042, is there too, with a new title and file link (see the Release 07 card below). Until Release 07 this page said none of the 294 was missing, which was true of the 450-row file. What war.gov does change after publishing is specific: 87 existing rows were edited across the four steps. In 39 of them the edit includes clearing the "Featured" flag, and in 44 it replaces a PDF Pairing list with a tag.

StepRowsAddedRemovedExisting rows editedWhat the edits were
R03 to R04294 to 3344001210 had the Featured flag cleared; 1 changed Agency label from "Central Intelligence Agency" to "CIA" (CIA-UAP-D001); 1 gained a PDF Pairing (DOE-UAP-D001, now paired with DOE-UAP-D005)
R04 to R05334 to 3754101010 had the Featured flag cleared
R05 to R06375 to 45075099 had the Featured flag cleared; one of them, DOW-UAP-D098, also gained a Video Pairing (DOW-UAP-PR159) and a PDF Pairing (DOW-UAP-D103, D104, D105)
R06 to R07450 to 4782805610 had the Featured flag cleared; 44 had their PDF Pairing list replaced by the tag TAG:AAWSAP (4 rows are in both groups); 5 gained pairings (DOW-UAP-D044 and videos PR039, PR040, PR088 and PR089); 1 lost a trailing space from its Description Blurb (LLE-UAP-D001). One more row, DOW-UAP-D042, got a new title and file link, and is counted as neither added nor removed

Every added, removed and edited row, with its old and new values, is in data/release-diff.json. "Rows" are CSV rows, which is also how our file count works: 158 + 64 + 72 + 40 + 41 + 75 + 28 = 478. The R06 to R07 step uses the CSV as first recorded on October 23; the October 26 revision is diffed on its own in the Release 07 card.

Three things in the CSV itself

Every CSV state our poller recorded

This is every change to war.gov's CSV that our poller logged (row count and SHA-256), taken from our public data/poll-state.json. Times are UTC. Where we kept a copy of a state we diffed it row by row; where we did not, the last column says so and this page makes no claim about what changed. Changes to war.gov's landing-page HTML (May 10 and May 12) are left out.

Recorded (UTC)RowsChangeSHA-256 (first 12)What it wasRow-level diff
2026-05-08161start596cc1881aa9Release 01, as first captured.May 8 vs May 11 comparison, below
2026-05-11 18:04158-3f07601ebed0fThe May 11 revision.URL-set comparison, below
2026-05-11 19:1815800d7e9ba1d51cSecond revision the same day: same row count, different hash.Copy recovered from the Internet Archive (SHA-256 matches). The 18:04 state was not kept, so what changed is not established
2026-06-09 20:28222+646be2c64e7605Release 02 CSV (its 64 rows carry Release Date 5/22/26). The first CSV hash the poller recorded after May 12.Release 02 card, below
2026-06-10 16:362220a62a76884e52Same row count, different hash.No archived copy; what changed is not established
2026-06-12 14:11294+7248db08be3960Release 03.Release 03 card, below
2026-07-10 12:00334+4013e730c18d6eRelease 04.Row by row (R03 to R04)
2026-08-07 13:17375+415f5698f13224Release 05.Row by row (R04 to R05)
2026-09-18 12:51446+718d4232f3777fRelease 06, first state the poller recorded.No archived copy of this state
2026-09-18 16:58447+119e6dd7a69d5Release 06, four hours later: one more row.Row by row against Release 05 (+72) and against the 450-row state (Release 06 card, below). Copy recovered from the Internet Archive (SHA-256 matches)
2026-09-24 21:15450+3c3f8209ef5f5Release 06 amendment.Row by row (R05 to R06, the three Release 06 states combined; and from the 447-row state)
2026-10-23 13:16478+28096ef2c0058aRelease 07.Row by row (R06 to R07; Release 07 card, below)
2026-10-26 23:15478092b3ec7dd872Release 07 revised: same row count, dates rewritten. This is the current CSV.Row by row against the October 23 state (Release 07 card, below)

Releases, newest first

🛰️ Release 07 · 28 rows added · 478 rows total · 0 removed · revised after it appeared

The Department of War published Release 07 on October 23, 2026; the poller first recorded the new CSV at 13:16 UTC that day. All 28 new rows are PDFs: 25 Department of War, 1 FBI, 1 Executive Office of the President and 1 U.S. Government. No new agency label appeared. By title, the Department of War rows are ten Air Force forms from 1952 to 1957 ("Air Intelligence Information Report" and "Flying Object Report", D155 to D164), nine records from 2008 to 2010 that carry the tag TAG:AAWSAP in the CSV (D166 to D171 and D173 to D175, among them four BAASS monthly reports and a "Utah Ranch Investigation Report"), four Catalina Island files from 1949 to 1955 (D177, D178, D179 and D181), the final personnel record of Howard M. McCoy (D180), and a 2026 "Triangular UAP AARO Memorandum for Record" (D176). The CSV pairs D176 with the FBI row, FBI-UAP-D043, an FD-302 from 2026. It also pairs the last two rows with each other: EOP-UAP-D002, a May 1963 memorandum on recovering foreign materiel, and USG-UAP-D002, interagency correspondence on space fragments from 1962 to 1964. No row in the CSV carries the ID DOW-UAP-D165 or DOW-UAP-D172; the file does not say why.

Release 07 date23 October 2026
New rows28
Combined archive478 rows
Rows removed0

Current CSV SHA-256: 92b3ec7dd87286ea7092a33b476566b4416d3bb02970b02757b237d8322fe81a, the October 26 revision. It matches the poller's record, a byte-exact copy is archived (2026-10-26-92b3ec7dd872.csv), and our pre-push check confirms that the mirror at /uap-data-csv is byte-identical to it. The CSV as first recorded on October 23 was 096ef2c0058abd412a568d630df31cb836241c1c08c4f67bdc8cdb7e5c8418b9, also archived byte-exact (2026-10-23-096ef2c0058a.csv).

Existing rows edited: 56

One row with a new title and file link: DOW-UAP-D042

DOW-UAP-D042 went from "Range Fouler Debrief, Japan, 2023" to "Range Fouler Debrief, Arabian Gulf, 2023", and its link went from dow-uap-d42-range-fouler-debrief-japan-2023.pdf to DOW-UAP-D042-Range-Fouler-Debrief-Arabian-Gulf-2023.pdf in the same folder. Because we match on ID and file link, the tool reports this as a re-link: it is counted as neither added nor removed, and it is not among the 56 above. It is also the one Release 03 row that does not match today's CSV on ID and link. The row itself is still there. It also gained a Video Pairing (DOW-UAP-PR039, PR088 and PR089). Its Incident Location column read Arabian Gulf in all eight earlier CSV states we hold, back to May 8. Its title still says 2023, while its Incident Date column says August 31, 2020. We compared the old and new PDFs; the result is on /revisions. Our page for this file keeps its original address: /files/dow-uap-d042-range-fouler-debrief-japan-2023.

The October 26 revision, row by row (478 rows before and after)

Diffed from the two archived CSVs: 0 rows added, 0 removed, 0 re-linked, and all 478 edited.

This diff covers CSV rows, not the files they link to. Separately, on November 1 we re-fetched the 28 Release 07 PDFs and DOW-UAP-D042 from war.gov: all 29 match the SHA-256 values in our manifest. We did not re-hash the rest of the archive for this check. Every old and new value is under steps and revisions in data/release-diff.json.

🛰️ Release 06 · 75 rows added · 450 rows total · 0 removed · revised after it appeared

The Department of War published Release 06 on September 18, 2026. In the current CSV, 75 rows carry that Release Date: 67 under Department of War (55 PDFs, 11 videos and 1 audio file) and 8 under a new label, Local Law Enforcement (4 videos and 4 PDF transcripts, all Colorado). 44 of the Department of War rows have titles containing AAWSAP: a statement of objectives, a solicitation, five contract modifications and 37 DIRD papers (see the AAWSAP hub). The rest include the 1952 Tremonton, Utah film (DOW-UAP-PR159) with two Project Blue Book files (D102, D103), a 1952 presentation by Captain Edward J. Ruppelt (transcript D154, audio PR160), four mission reports from Iraq and the Middle East (D106 to D109), and further "Unresolved UAP Report" items.

Release 06 date18 September 2026
New rows75
Combined archive450 rows
Rows removed0

SHA-256 of the 450-row CSV, this release's last state: c3f8209ef5f53a124bf3f30c4a36106ffaa63ea9770ad2d33e2ba5c4fec347c7, from the poller's record. A byte-exact copy is archived in our repository (2026-09-24-c3f8209ef5f5.csv) and hashes to this value.

Revision history: 446 rows, then 447, then 450

The poller recorded three CSV states for this release: 446 rows at 12:51 UTC on September 18 (+71), 447 rows at 16:58 UTC the same day (+1), and 450 rows at 21:15 UTC on September 24 (+3). We have byte-exact copies of the 447-row and 450-row CSVs, but not of the 446-row one. So which of the first 72 Release 06 rows were in the 446-row state and which one was added by the 447-row state is not something we can reproduce, and this page makes no claim about it. The times above are when our poller recorded each state, not when war.gov published it. The step from 447 to 450 rows is diffed below. What the 450-row CSV shows, by direct count:

Nine existing rows were edited between Release 05 and the 450-row CSV: all nine had the Featured flag cleared (the nine rows flagged in Release 05), and DOW-UAP-D098 also gained the two pairings above. Ten Release 06 rows are flagged Featured. No row was removed. All nine edits were already in the 447-row CSV of September 18, 16:58 UTC.

The September 24 amendment, row by row (447 to 450 rows)

Diffed from the two archived CSVs, 2026-09-18-19e6dd7a69d5.csv and 2026-09-24-c3f8209ef5f5.csv: 3 rows added, 5 existing rows edited, 0 removed. All eight changed rows are Colorado rows under Local Law Enforcement.

So the 447-row CSV held four Colorado videos and one transcript, LLE-UAP-D001, paired with PR004; the 450-row CSV pairs each of the four videos with its own transcript. This diff covers CSV rows only, not the contents of the files they link to. Every old and new value is under revisions in data/release-diff.json.

🛰️ Release 05 · 41 rows added · 375 rows total · 0 removed

The Department of War published Release 05 on August 7, 2026; the poller first recorded the new CSV at 13:17 UTC that day. All 41 new rows carry Release Date 8/7/26: 19 Department of War (4 PDFs, 15 videos), 17 FBI (13 PDFs, 3 images, 1 video), 2 CIA PDFs, 2 Department of State PDFs and 1 PDF under a new label, Executive Office of the President (EOP-UAP-D001, "NASC Inquiry into Bahia, Brazil Incident, November 13, 1963"). By title, the FBI rows are "Digital Rendering" images and PDFs and FD-302 forms (for example "Dark Translucent Triangle," "Large Triangle with Red Lights" and "Multiple Red Lights," incidents dated 2002, 2011, 2023 and 2026); the State rows are two November 1963 cables from Brazil; the CIA rows are a 1965 report on an object near Puerto Rico and briefing notes for Walter Elder; the Department of War rows include an intelligence review of "Ghost Rocket" incidents (1947), an Air Materiel Command report on unidentified flying objects (1947-1948), "Film Analysis of Unidentified Objects, 1953", and videos from the Gulf of Oman (2021), the Pacific Ocean (2019) and the Middle East (2023 and 2025).

Release 05 date7 August 2026
New rows41
Combined archive375 rows
Rows removed0

CSV SHA-256: 5f5698f132245115dd9d4a5197d2748847f281e466d8b660de036aa3c4b678c7, from the poller's record. A byte-exact copy is archived in our repository (2026-08-07-5f5698f13224.csv) and hashes to the same value.

Ten existing rows were edited in this step: in all ten, the Featured flag was cleared. They are the ten rows flagged in Release 04. Nine Release 05 rows are flagged Featured.

🛰️ Release 04 · 40 rows added · 334 rows total · 0 removed

The Department of War published Release 04 on July 10, 2026; the poller first recorded the new CSV at 12:00 UTC that day. All 40 new rows carry Release Date 7/10/26: 28 Department of War (19 videos, 9 PDFs), 7 NASA (3 STS-80 images and 4 audio debriefings from Apollo 14 and Apollo 17), 2 Department of Energy PDFs (a 1949 Los Alamos conference on aerial phenomena and a 2015 Pantex incident report), 2 CIA PDFs (a 1955 memorandum and an analysis, both on "unconventional aircraft sightings") and 1 FBI PDF (correspondence relating to UFO sightings, 1967 and 1974). The Department of War PDFs include three "Range Fouler Debrief" reports (2019 and 2020), Project Blue Book correspondence and a Project Sign progress report (1948). No new agency label appeared.

Release 04 date10 July 2026
New rows40
Combined archive334 rows
Rows removed0

CSV SHA-256: 13e730c18d6ea586bcb9b58984481b093f3e4802c33b0f9281258ee786f8abd1, from the poller's record. A byte-exact copy of this CSV is archived in our repository (2026-07-10-13e730c18d6e.csv) and hashes to this value.

Twelve existing rows were edited in this step: 10 had the Featured flag cleared (the ten rows flagged in Release 03); DOE-UAP-D001 gained a PDF Pairing (DOE-UAP-D005); and CIA-UAP-D001's Agency label changed from "Central Intelligence Agency" to "CIA". Ten Release 04 rows are flagged Featured.

🛰️ Release 03 verified · CSV in hand · 294 rows confirmed · 294/294 SHA-256 verified

The U.S. Department of War published a third PURSUE release on June 12, 2026. We fetched the canonical war.gov CSV directly and verified it: SHA-256 48db08be39605efd86e1d92fe6af3cda7730e1da6a4b5741d37a30712ebf5e04, 294 data rows (158 from Release 01 + 64 from Release 02 + 72 new from Release 03). The 72 new files: 18 historical CIA records (the Scientific Advisory Panel on UFOs, a study titled "The Central Intelligence Agency and Overhead Reconnaissance," the Leon Davidson / CASE 17708 correspondence, and mid-century sighting reports), 29 FBI files (modern UAP reports including the 2022 Colorado Springs incident and Northeastern "orb" sightings), 11 NASA debriefings (Gemini 4/5/7/9, the Apollo 16 scientific debriefing, and a Gordon Cooper interview), 12 DoD files (a 1949 U.S. Army flying-saucer study and an AARO "Western United States" case), and the first intelligence-community-analysis and U.S. Government correspondence records. War.gov also added a new "Featured" column to the CSV schema and corrected three filename typos (re-slugged, not withdrawn); zero files were removed.

Release 03 date12 June 2026
Verified new files72
Combined archive294 files
CSV ingestVERIFIED 6/13

🛰️ Release 02 verified · CSV in hand · 222 rows confirmed · ingested + SHA-256 verified

The U.S. Department of War published PURSUE Release 02 on May 22, 2026. We have fetched the canonical war.gov CSV directly (now hosted at /Portals/1/Interactive/2026/UFO/uap-data.csv, the older uap-csv.csv URL was retired and 404s) and verified its byte-identity: SHA-256 6be2c64e760534a567e13ebaac939bf2cea3bd9de4864d9ae98c5c8b5df1b963, 222 data rows. Breakdown: 158 rows from Release 01 (5/8/26) plus 64 new rows from Release 02 (5/22/26).

Release 02 date22 May 2026
Verified new rows64
Combined archive222 rows
CSV ingestFETCHED 6/9

War.gov restructured the CSV schema for Release 02 - the new file has 27 columns including Redaction, Release Date, Video Pairing, PDF Pairing, Description Blurb, DVIDS Video ID, Video Title, Agency, Incident Date, and Incident Location columns. The 64 Release-02 records include the DOW-UAP-PR050 - PR099 sensor-video series (51 entries), the 7 NASA crew audio files, and 6 documents including ODNI-UAP-D001 (a first-person narrative from a senior U.S. intelligence officer describing a one-hour multi-witness UAP encounter from a military helicopter in late 2025).

The 64 Release 02 files are indexed, scored, and live on the site. Live status JSON: data/poll-state.json.

🔬 File-integrity audit · war.gov re-processed 62 documents · verified: no content removed

Sometime between our May 8-9 capture and June 10, war.gov silently replaced the file bodies of 62 Release-01 PDFs at the same URLs - same filenames, same CSV rows, same page count. The replacement files are about half the size (the audited corpus went from 2.49 GB to 1.25 GB). Watching the CSV alone would not reveal this: the files kept the same URLs, so the change only shows up when you fetch the files themselves and compare their hashes or sizes. This was first flagged publicly by a reader hashing every file daily; we independently verified it before publishing, and credit the catch. The natural worry - "they shrank the files, are they hiding something?" - is answerable here because we keep the original bytes.

What we verified, file by file, against our archived originals (all 62):

Pages preserved62 / 62
Pages removed0
Images cropped0
OCR text added~32 scans

Conclusion: re-processing, not removal. War.gov re-compressed the raw scanned images and added searchable OCR text layers. The originals had no extractable text (they were image-only scans); the new versions are text-searchable. The files got smaller and more usable. We checked every one of the 62 changed files - page counts are identical, and the single file that showed fewer extracted characters turned out to be garbage OCR being replaced with clean text, not content loss.

Scope of this claim: we compared page counts and extractable-text layers on all 62 changed files against our SHA-256-matched originals. We did not pixel-compare every page image, so we cannot rule out a localized visual change on an individual page - but no pages were dropped, no images cropped, and OCR text was added rather than removed. The exact date of the swap is bounded by our two data points (May 8-9 and June 10); a reader with daily snapshots dates it to mid-May. Full machine-readable per-file audit (old size, old SHA-256, current size): wargov-file-integrity-audit-2026-06-10.json.

The May 11 revision (161 to 158 rows)

TL;DR (plain English)

War.gov changed how they label their UFO file list on May 11, 2026, but the files themselves are exactly the same. 130 PDFs and 28 videos exist in both versions. The row count in their published spreadsheet dropped from 161 to 158 because 9 PDFs that used to appear as one row each now appear as multiple rows (the same file referenced under different incident titles), and one PDF had its storage filename renamed. That accounts for the entire change. The data tables below show every PDF affected, with links to the actual files.

130PDFs both dates
28Videos both dates
9PDFs w/ extra rows
+12Extra row count
1PDF slug changed

The arithmetic

The row-count delta of -3 (161 May 8 rows -> 158 May 11 rows) decomposes cleanly:

May 8 CSV: 161 rows = 130 unique PDFs + 16 video rows + 15 PDF rows that were duplicates within the May 8 file = 130 PDF URLs + 28 video DVIDS IDs in the unique set May 11+ CSV: 158 rows = 130 unique PDFs + 16 video rows + 12 additional cross-reference PDF rows = 130 PDF URLs + 28 video DVIDS IDs in the unique set (same unique set after accounting for 1 PDF slug change; see Table 2 below) Net delta: -3 rows = 15 historical PDF-row duplicates - 12 new cross-reference rows = -3

The unique-file inventory between the two dates is identical. The CSV structure changed; the file set did not.

Table 1: 9 PDFs that gained extra CSV rows (12 extra rows total)

Each of these 9 PDFs had exactly 1 CSV row on May 8 and now has 2-4 CSV rows in the current CSV. The PDF file at the URL is unchanged (we have not yet re-hashed it; see "verification status" below). The new CSV rows describe what appear to be discrete incidents contained within the same PDF, but we do not assert this without diffing the PDF contents.

PDF URL (war.gov)Site detail pageCSV row titles (2026-05-11+)Rows
dow-uap-d32-mission-report,-syria-october-2024.pdf Syria, October 2024 D32, PR31, PR32, PR33 4x
dow-uap-d23-mission-report-united-arab-emirates-october-2023.pdf UAE, October 2023 D23, PR26, PR27 3x
dow-uap-d10-mission-report-middle-east-may-2022.pdf Middle East, May 2022 D10, PR19 2x
dow-uap-d14-mission-report-iraq-may-2022.pdf Iraq, May 2022 D14, PR21 2x
dow-uap-d16-mission-report-syria-july-2022.pdf Syria, July 2022 D16, PR22 2x
dow-uap-d18-mission-report-iraq-december-2022.pdf Iraq, December 2022 D18, PR23 2x
dow-uap-d33-mission-report-greece-october-2023.pdf Greece, October 2023 (1) D33, PR34 2x
dow-uap-d35-mission-report-greece-october-2023.pdf Greece, October 2023 (2) D35, PR35 2x
dow-uap-d38-range-fouler-debrief-middle-east-may-2020.pdf Middle East, May 2020 D38, PR36 2x

Table 2: PDF storage-slug changes (title unchanged)

One PDF on war.gov's storage backend had its file slug renamed between May 8 and May 11. The CSV Title and human-facing metadata are unchanged. SHA-256 verification (2026-05-23): bytes IDENTICAL. The rename was purely a storage-slug change with no underlying content modification.

Title (unchanged)Old URL (May 8)New URL (May 11+)Verification
DOW-UAP-D20, Mission Report, Iraq, 2023 .../dow-uap-d20-mission-report-southern-united-states-2023.pdf .../dow-uap-d20-mission-report-iraq-2023.pdf SHA-256 verified identical

Verification details: Both files share SHA-256 71ca8826db94d61583083ef8465a6902564532dcab7d49d0d2db3e86aaf85b2f (3,698,245 bytes). The current PDF was fetched 2026-05-23 from the new URL via curl_cffi chrome120 impersonation. The May 8 hash was recorded in our manifest at the time of initial parse. Verification methodology: sha256sum on both file bytes, byte-identical match.

Note: 2 additional URL-pair differences exist in the diff (involving FBI file series 59_64634 and 65_HS1-..._Section_6) but the data is currently ambiguous between "URL slug change" and "the old URL was withdrawn while a similarly-titled new URL was added." We are not asserting either reading until we have re-fetched both files and compared bytes. See the methodology note below.

Verification status by file class

What's verifiedHowStatus
Unique PDF URL set (May 8 vs May 11)Set diff on normalized URLsDone
Unique video DVIDS ID set (May 8 vs May 11)Set diff on DVIDS IDsDone - identical
Multi-row PDF count and identitiesCounter on URL field in the May 11 CSVDone
PDF byte equivalence on slug-changed files (D20)Re-fetch + SHA-256 compareDone 2026-05-23 - bytes identical
Multi-row PDFs - are extra rows describing the same content or distinct incidents within the PDF?PDF text extraction + comparisonPending
Resolution status changes (e.g., the "Middle East 2013" question)PDF content readPending
Rows added, removed and edited, Release 03 to 04, 04 to 05, 05 to 06, 06 to 07Row-by-row diff of the CSV, matched on ID + file link (pipeline/release_diff.py)Done 2026-10-13, extended 2026-11-01; re-runnable
293 of the 294 Release 03 rows are in the Release 07 CSV with the same ID and file link; the other, DOW-UAP-D042, has a new linkSame tool, Release 03 against Release 07. The October 26 revision added, removed and re-linked no rows, so this also holds for today's CSVDone 2026-11-01 - 1 not matched, re-linked rather than gone
Rows added and edited in Release 06's September 24 amendment (447 to 450 rows)Same tool, on the archived 447-row and 450-row CSVsDone 2026-10-19 - 3 added, 5 edited, 0 removed; re-runnable
Rows edited in Release 07's October 26 revisionSame tool, on the archived October 23 and October 26 CSVsDone 2026-11-01 - 0 added, 0 removed, 478 edited; re-runnable
DOW-UAP-D042: old PDF against new PDFEmbedded page image compared byte for byte; page rendered at 300 dpi and compared pixel by pixel; text layer and metadata comparedDone 2026-11-01 - same page image and text layer, different metadata
The 28 Release 07 PDFs and DOW-UAP-D042 still match at war.gov after the October 26 revisionRe-fetched all 29 from war.gov, compared SHA-256 with our manifestDone 2026-11-01 - 29 of 29 match
How Release 06's first 72 rows split between its 446-row and 447-row statesWould need the 446-row CSV, which was not keptNot reproducible
What changed in the two same-row-count revisions (May 11 second state, June 10)Each needs the CSVs on both sides. We hold the May 11 19:18 copy but not the 18:04 state before it, and the June 9 copy but not the June 10 state after itNot reproducible

How to verify this page yourself

Anyone can re-run the diff. The inputs are public:

  1. Current war.gov CSV: war.gov/Portals/1/Interactive/2026/UFO/uap-data.csv (warm a session at war.gov/UFO/ first or the CDN will 403)
  2. May 8 and May 11 CSVs: war.gov no longer hosts these, but copies recovered from the Internet Archive match the hashes in the timeline above: 2026-05-08-596cc1881aa9.csv and 2026-05-11-0d7e9ba1d51c.csv
  3. The diff itself: extract the PDF | Image Link column from both copies, normalize to lowercase, and set-difference them. The result will match the May 11 tables on this page.

Re-running the Release 03 to 07 diff

The row-by-row figures come from pipeline/release_diff.py. Clone the repository and run python -m pipeline.release_diff. It reads one CSV per release from data/csv-archive/, writes data/release-diff.json, and should reproduce every count above. The five copies are 2026-06-12-48db08be3960.csv (Release 03), 2026-07-10-13e730c18d6e.csv (Release 04), 2026-08-07-5f5698f13224.csv (Release 05), 2026-09-24-c3f8209ef5f5.csv (Release 06) and 2026-10-23-096ef2c0058a.csv (Release 07). Each is byte-exact: its SHA-256 matches the hash our poller recorded when war.gov served that file, and you can check that against the timeline above. The tool also diffs Release 06's 447-row state, 2026-09-18-19e6dd7a69d5.csv, against Release 05 and against the 450-row file, and Release 07's first state against its October 26 revision, 2026-10-26-92b3ec7dd872.csv; those results are under revisions in the JSON.

One limit: three CSV states our poller recorded were never kept, so nothing on this page says what changed in them: the first May 11 state (f07601ebed0f), June 10 (a62a76884e52) and Release 06 at 446 rows (8d4232f3777f). Four other states the poller first recorded by hash and row count only were later recovered from the Internet Archive, and each recovered file's SHA-256 matches the poller's record: May 8 (2026-05-08-596cc1881aa9.csv), May 11 19:18 (2026-05-11-0d7e9ba1d51c.csv), June 9 (2026-06-09-6be2c64e7605.csv) and Release 06 at 447 rows (2026-09-18-19e6dd7a69d5.csv). The tool diffs only the last of these; the May 11 tables above come from the URL-set comparison described there.

Why this page exists

An earlier version of /revisions characterized the May 11 change as including removals, additions, geographic consolidation, and reclassification. None of those characterizations are supported by the URL-set comparison. Rather than silently rewriting and pretending the mistake didn't happen, we kept the correction visible on /revisions and built this page to host the verified data tables. Per the site's editorial policy, transparency about our own errors is part of the credibility moat.

← BACK TO ALL FILES  ·  REVISIONS SUMMARY

📡 Subscribe via RSS 🔔 Watch on GitHub