UFO Disclosure Files

Briefing

PURSUE Release 01 source map

By UFO Disclosure Files Editorial Desk Published Updated Editorial analysis

The Release 01 source chain starts with war.gov/UFO, the May 8 announcement, and the individual PDFs linked from the official release path.

How the official source chain fits together

A useful Release 01 source map should show where each claim comes from. The portal establishes the program and download paths, the announcement explains the government framing and named agency participation, individual PDFs carry case-specific written evidence, and DVIDS pages carry official video metadata. Third-party posts can help discover discussion, but they are not the source of record.

Primary source layer

The strongest source layer is the official PURSUE portal and the May 8 Department of War release announcement. These establish the program name, the release date, the unresolved-case caveat, the rolling-tranche model, and the interagency frame.

  • PURSUE portal: program scope, directive text, Release 01 area, download paths, still/video references.
  • May 8 announcement: public release framing and statements from Department of War, ODNI, FBI, and NASA leadership.

Record source layer

The next layer is the individual source material: PDFs, images, and DVIDS video pages. This layer matters most for case analysis because it contains filenames, incident dates, location fields, sensor language, redactions, runtime, and companion-record references.

  • PDFs should be treated as document evidence, with redactions and missing attachments called out.
  • DVIDS video pages should be treated as official media metadata, not as complete investigations.
  • War.gov multimedia URLs and DVIDS URLs should both be preserved when available.

Reaction source layer

Public reactions from officials, researchers, journalists, skeptics, and UAP personalities can become news coverage, but they must be labeled as reaction or analysis. They should never be merged into the official record unless the official source itself supports the claim.

Source map takeaways

  • Use war.gov and DVIDS as the source of record for Release 01 pages.
  • Use third-party indexes only as discovery aids, then verify against official URLs.
  • Preserve source hierarchy so readers can see the difference between record evidence and commentary.
  • Follow the release hub into the source map, record pages, video pages, and future reaction coverage.

Source trail

The strongest reading starts with the primary record, then follows the supporting documents, dates, agency labels, and public statements around it. When commentary or reporting adds context, it is weighed against the source record instead of being treated as the record itself.

Sources