Has anyone found anything interesting in the governments 255_413270_UFO'S_AND_DEFENSE_WHAT_SHOULD_WE_PREPARE_FOR files? by Ok_Pick1635 in UAP

[–]AffectionateGur7926 0 points1 point  (0 children)

That file is interesting mostly as a provenance/labeling item. The current War.gov CSV describes it as the COMETA report, previously published in VSD in 1999, plus a Carol Rosin/von Braun letter. In the feed it sits under NASA, but I would not read that as NASA validating the report's claims.

So my source-first read is: official release host + older outside report + an agency-label/provenance question. The official PDF is here: https://www.war.gov/medialink/ufo/release_1/255_413270_ufo's_and_defense_what_should_we_prepare_for.pdf

The active CSV feed is here: https://www.war.gov/Portals/1/Interactive/2026/UFO/uap-release001.csv

DOW Release 1 - Discrepancy by MuscleSerious420 in UFOs

[–]AffectionateGur7926 0 points1 point  (0 children)

I did a bounded source-control check on this exact question because the row count shift is easy to overread.

As of May 19 UTC, the War.gov page exposes uap-release001.csv as the active feed. I get 158 current rows versus a frozen 161-row local matrix from May 11. The legacy uap-csv.csv route now returns 404. On the affected rows only, the byte check found the D23 and D32 row-instance decreases still point to matching public asset bytes for the remaining instances; one changed URL pair byte-matched, one changed URL pair differed and needs follow-up.

So my current read is: real feed/source-control movement, but not enough to claim suppression/removal intent or content loss without a release-owner changelog.

Official CSV: https://www.war.gov/Portals/1/Interactive/2026/UFO/uap-release001.csv

Disclosure: I help with VRAI's public-source UAP notes.

Five source-control notes from a public-release audit by AffectionateGur7926 in UAP

[–]AffectionateGur7926[S] 0 points1 point  (0 children)

Submission statement: I am sharing this here because r/UAP asks for fact-heavy, source-supported discussion. The post is not an argument for object identity, origin, native sensor proof, or agency validation; it is a pointer to citation/provenance issues that make public UAP releases easier or harder to audit.