PURSUE Release 01 UAP Evidence-Control Requests

Dear Mr. President,

I am asking for a public evidence-control addendum for PURSUE Release 01.

This is not a request for an endorsement of any interpretation. It is a request to make the public release auditable. Release 01 is important because it gives citizens official records, public DVIDS media, FBI/NASA/NARA/State material, and a machine-readable CSV. The current public record also contains source-control conflicts that independent reviewers cannot resolve from the released files alone.

This request treats catalog conflicts as audit issues, not as evidence of bad faith or hidden conclusions.

Please direct the responsible agencies to publish a corrected, machine-readable addendum for Release 01 that includes, for every row, the stable record ID, source URL, final URL, public prior-version URL where known, file size, SHA-256 hash, known duplicate-byte group ID, agency, record type, DVIDS ID where applicable, report/video pairing fields, conflict flags, redaction status meaning, and last-reviewed timestamp.

Please also direct the agencies to correct or explain these specific conflicts:

- State rows 29 and 30: different catalog titles and dates currently resolve to identical PDF bytes and the same SHA-256 hash.
- PR26 / D12 / D23 / PR27: Release 01 pairs D23 to both PR26 and PR27, while official PR26 DVIDS prose names DoW-UAP-D12 and describes a different still-image lane.
- PR28 and PR29: DVIDS names D7 and D8, while local content review has identified D25 and D27 candidate matches; PR29 also carries United Arab Emirates / Gulf of Oman and command-source tension.
- PR38: one CSV field says resolved as aircraft while source title fields say unresolved.
- PR49 and FBI Photo A1: both carry DVIDS ID 1006111 even though one is an Army video and the other is an FBI image.
- State Cable 5: extracted cable text identifies MRN 23 MEXICO 2544 dated September 16, 2023 while catalog fields indicate 2003.
- NASA VM1-VM6: release images need original frame IDs, unmodified source-frame links, release image modification/crop/annotation history, adjacent-frame lists, and any released analysis status.

The public deserves a release that can be checked without guesswork. A careful source-integrity addendum would help serious reviewers separate official records from catalog errors, source-reported observations from analysis, and open questions from unsupported speculation.

Respectfully,

Dear Mr. President,

I am asking for a focused, releasable evidence-context packet for the Greece/Aegean PURSUE Release 01 records D33/PR34 and D35/PR35.

These records are the most source-rich current public comparison packet for source-control review because they include official mission reports, DVIDS videos, and visible source-described display-state changes. That does not make them proof of object identity, origin, extraordinary performance, or non-human technology. It means they are a useful public test case for disciplined review.

The public record should not be asked to carry more than it can prove. The requested context is what would test the report language.

Please direct the responsible agencies to release or certify the maximum lawful, non-sensitive context for these two events:

- Native or least-compressed PR34 and PR35 video, including original container, codec, frame rate, timecode, dropped-frame metadata, and edit/excerpt history.
- Sensor-display metadata: mode, polarity, FOV, zoom, gain/level, contrast settings, reticle/tracker state, stabilization state, overlay history, and time synchronization source.
- Platform context where releasable: position, altitude, heading, speed, attitude, gimbal/sensor angles, slant range or range estimate if measured, and any object-altitude assumption used in the report.
- Environmental controls for the relevant Aegean windows: weather, sea state, clouds, AIS/vessel traffic, air traffic, drone/balloon/flare activity, satellite/reentry checks, and sun/moon geometry.
- Report/video chronology: a table tying report fields to exact video timestamps and explaining any DVIDS placeholder dates or release-index differences.

The current public record preserves reported observations, but public reviewers cannot determine whether source-reported turns, estimated speed, low-over-water description, or loss-of-track wording survive platform motion, sensor panning, background transition, compression, and environmental controls.

This request asks for the evidence needed to make the case stronger or more ordinary. Either outcome would improve public trust.

Respectfully,

Dear Mr. President,

I am asking for a public archive-provenance addendum for the FBI, NARA, NASA, and State Department materials in PURSUE Release 01.

This request is not asking the agencies to validate an anomaly conclusion. It asks them to publish the source crosswalks needed to understand what Release 01 adds to the public record and how each historical item relates to prior public holdings.

Please direct the responsible agencies to publish:

- FBI 62-HQ-83894 crosswalks: Release 01 row, section, serial, page, FBI Vault part/page, redaction-state difference, Release-01-only, prior-public-only, reordered, duplicate, or differently redacted page inventory where releasable, and declassification authority/date where releasable.
- NARA incident-summary crosswalks: record group, series, container, finding-aid reference used for the mapping, microfilm roll/frame or NAID mapping, and whether the scans duplicate Project BLUE BOOK case files, administrative files, OSI material, or another accession.
- NASA Gemini/Apollo/Skylab transcript and audio lineage: source transcript/debrief title, page, mission-elapsed-time crosswalks, adjacent transcript context, and Gemini VII audio/caption source lineage.
- NASA image/frame provenance: original frame IDs, unmodified source-frame URLs or scans, adjacent-frame lists, release image crop/annotation/modification history, original-film scan notation, and any released NASA/DOW analysis status for VM1-VM6. Apollo 12 VM2-VM5 now have candidate source-frame matches in AS12-46-6846 through AS12-46-6849; that supports source-lineage review, not visual interpretation.
- State Department cable corrections and release-history data: MRN/date/subject/post crosswalks for the five cables, State rows 29/30 duplicate-byte or intended-asset explanation, correction of Cable 5 date metadata, and any prior-public FOIA/NARA copy references.

The most important public distinction is simple: an official release is not the same thing as official validation, and a republished archival document is not automatically new or less redacted until it is compared page by page.

Publishing these crosswalks would let the public verify what is new, what is repackaged, what is corrected, and what remains unknown.

Respectfully,

Dear Mr. President,

I am asking for a non-sensitive native-context and source-control packet for the PURSUE Release 01 D23/PR27 United Arab Emirates / Arabian Gulf records.

This is not a request to validate any object identity, origin, speed, range, or extraordinary performance. It is a request to make the public record testable. PR27 is a long official DVIDS infrared video, and D23 is the public mission-report lane, but the current release does not tell reviewers how the report lines and videos fit together.

Please direct the responsible agencies to release or certify:

- Whether PR27 maps to D23 UAP line 1, D23 UAP line 2, both lines, or only the broader D23 mission.
- A correction or explanation for the D23 catalog date versus the internal D23 mission-date fields.
- A correction or explanation for the PR26 / D12 / D23 conflict, including whether PR26 should reference DoW-UAP-D12, DoW-UAP-D23, both, or neither.
- The least-compressed PR27 video available for public release, with original container, codec, frame rate, timecode, dropped-frame metadata, edit/excerpt history, and generation history for the public DVIDS rendition.
- Sensor-display metadata: mode, polarity, FOV, zoom, gain/level, contrast settings, reticle/tracker state, stabilization state, overlay history, and time synchronization source.
- Platform context where releasable: position, altitude, heading, speed, attitude, gimbal/sensor angles, line-of-sight or range assumptions, and any object-altitude assumptions used in the report.
- Environmental and traffic controls for the relevant UTC windows: weather, haze, sea state, AIS/vessel traffic, air traffic, drone/balloon activity, satellite/reentry checks, fireball checks, and any range or operational deconfliction records that can be lawfully released.

The current public video is useful, but it cannot carry measured speed, range, altitude, or identity claims without the missing source controls. Publishing this packet would let reviewers determine whether the case becomes stronger, more ordinary, or simply better bounded.

Respectfully,

Dear Mr. President,

I am asking for a public source-control and sensor-context packet for PURSUE Release 01 PR28 and PR29.

These two records are worthwhile because they preserve exactly the kinds of controls public reviewers need: sensor-modality switching in PR28 and a possible water-reflection alternative in PR29. They are not currently proof of object identity, origin, extraordinary performance, or non-human technology.

Please direct the responsible agencies to first publish the authoritative report/video pairings:

- For PR28, whether the accompanying report is DoW-UAP-D7, DoW-UAP-D25, both, or neither.
- For PR29, whether the accompanying report is DoW-UAP-D8, DoW-UAP-D27, both, or neither.
- For both records, normalized incident date, location, command/source, DVIDS date, and report-date fields.

Please also release or certify the maximum lawful, non-sensitive technical context:

- Native or least-compressed PR28 and PR29 videos, original frame rate, timecode, edit/excerpt history, and public-rendition generation history.
- Sensor modality sequence, SWIR/EO/visible calibration, polarity, FOV, zoom, gain/level, contrast settings, tracker/reticle state, stabilization state, overlay history, and mode-registration details.
- Platform context where releasable: position, altitude, heading, speed, attitude, gimbal/sensor angles, line of sight, range assumptions, and any object-altitude assumptions.
- For PR29 specifically, sea state, sun/moon geometry, viewing angle, maritime traffic, surface-vessel context, water-background controls, and the source basis for or against the water-reflection alternative.

The public record should not resolve these cases by assertion. It should expose enough source control for independent reviewers to test the report language, the sensor-mode claims, and the reflection alternative.

Respectfully,

Dear Mr. President,

I am asking for a comparative evidence-control packet for the 2020 maritime infrared and range-fouler records in PURSUE Release 01.

This is not a request to treat the 2020 records as one solved incident or as a batch of extraordinary claims. It is a request for a normalized control package across repeated maritime IR/FMV records, where water background, clouds, platform motion, range-fouler geometry, sensor settings, and possible conventional explanations matter.

Please direct the responsible agencies to publish a normalized, releasable packet for D38/PR36, D44, D56, D57, D58, D60, D61, D62, D63, D65, and the related 2020 DVIDS video records where applicable. For each event, please include:

- Corrected row, date, location, report/video pairing, DVIDS ID, source URL, final URL, file size, and SHA-256 fields.
- OCR-complete report text where the current public files are scan-only or empty in text extraction.
- Native or least-compressed video where it exists, with original frame rate, timecode, public-rendition history, and edit/excerpt history.
- Sensor mode, FOV, zoom, gain/level, contrast, polarity, reticle/tracker state, stabilization state, overlay history, and time synchronization.
- Platform position, altitude, heading, speed, attitude, gimbal/sensor angles, slant range, ground range, object-altitude assumptions, and any range-fouler geometry used in the records where releasable.
- Weather, cloud, haze, sea state, AIS/vessel traffic, aviation traffic, drone/balloon/range activity, satellite/reentry, fireball, and reflection controls.

The public release now allows reviewers to identify the right records and public videos, but it does not provide enough normalized context for kinematic conclusions. A comparative evidence-control packet would improve public trust whether the individual records become more compelling, more ordinary, or more clearly unresolved because of missing data.

Respectfully,

Dear Mr. President,

I am asking for a narrow, non-sensitive source-context packet for the FBI-USPER late-2025 record and the Western US 2023 witness-summary record in PURSUE Release 01.

This is not a request to validate witness conclusions, object identity, proximity, heat, size, speed, or extraordinary performance. These records are worthwhile because they point to possible logs, sensor inventories, interview chronology, and control checks that the public cannot see in the released PDFs.

For the FBI-USPER late-2025 record, please direct the responsible agencies to publish or certify, where lawful:

- The interview serial chain, related interview or attachment inventory, and whether any pilot, helicopter, LP/OP, JOC, FLIR, NVG, radio, or dispatch records exist.
- A non-sensitive timeline for the reported helicopter search, LP/OP reports, airspace deconfliction, refuel timeline, and five military aircraft noted in the source record.
- Sensor inventory and calibration context for FLIR/NVG observations, including whether raw imagery exists and whether the reported sightings were inside or outside the recorded camera angle.
- Weather, moon, visibility, astronomical, satellite, launch/reentry, drone, flare, pyrotechnic, range-activity, and debris/ground-search controls.

For the Western US 2023 record, please direct the responsible agencies to publish or certify:

- The exact or safely generalized two-day window, witness-interview chronology, and what records support the "independently" reported language.
- The source data and method behind any later distance or size estimates.
- An inventory of checked or available patrol logs, radio traffic, dispatch records, vehicle-location records, restricted-zone access records, fixed cameras, body or vehicle cameras, NVG model/settings, weather, wind, moon/astronomy, drone/balloon/kite/aircraft controls, satellite/reentry/fireball checks, and any technical data that exists outside the released slide deck.
- If no technical records exist beyond the released summaries, a clear public statement saying so.

The public can take witness records seriously without overstating them. The right request is for the record trail that would let reviewers separate independent observation, cross-cueing, ordinary controls, missing media, and still-open questions.

Respectfully,

Subject: Release 01 DVIDS public video metadata and rendition-lineage confirmation

Suggested route: DVIDS Press Inquiry / Media Request. Request type: Content or General Query. Unit context: All Domain Anomaly Resolution Office.

I am reviewing the public PURSUE Release 01 DVIDS video assets for source and media-provenance accuracy. This request concerns source provenance and public-record auditability; it does not ask for validation of object identity, origin, extraordinary performance, speed, range, altitude, sensor performance, or non-human technology.

Please provide the public DVIDS metadata or routing guidance needed to cite these assets accurately.

Primary correction/routing items:

- PR26 / DVIDS 1006063: DVIDS prose references DoW-UAP-D12 while Release 01 rows link PR26 to DoW-UAP-D23.
- PR27 / DVIDS 1006067: Release 01 links PR27 to DoW-UAP-D23, but D23 appears to include multiple UAP lines and duplicate row treatment.
- PR28 / DVIDS 1006073: DVIDS prose references DoW-UAP-D7; local source review identified DoW-UAP-D25 as a stronger content match for the January 2024 Greece/SWIR description.
- PR29 / DVIDS 1006074: DVIDS prose references DoW-UAP-D8 and NORTHCOM, while local source review identified DoW-UAP-D27 as a stronger content match for the June 2024 Gulf of Oman/water-reflection description.
- PR49 / DVIDS 1006111 and the FBI Photo A1 row in Release 01 both carry DVIDS ID 1006111; please correct or explain the shared identifier.

For the 28 Release 01 DVIDS video IDs, please also identify the authoritative public page URL, embed URL, VIRIN, DOD filename/source ID, published/update timestamps, highest public MP4 rendition, caption/transcript availability, thumbnail/poster-frame source if public, and any releasable public-rendition generation history. The IDs are: 1006119, 1006056, 1006059, 1006060, 1006062, 1006063, 1006067, 1006073, 1006074, 1006076, 1006078, 1006079, 1006080, 1006082, 1006083, 1006087, 1006088, 1006089, 1006093, 1006094, 1006097, 1006159, 1006104, 1006105, 1006106, 1006107, 1006110, and 1006111.

If DVIDS cannot answer source-upload, caption, public-rendition, or native/least-compressed-source questions, please route this to the appropriate AARO, DWIA, or originating public-affairs owner for a non-sensitive public-media lineage statement.

Subject: FOIA request: PURSUE Release 01 USCENTCOM source-control and operational-record records

To the USCENTCOM FOIA Requester Service Center:

This is a Freedom of Information Act request for existing USCENTCOM records. I request electronic copies where available. If fees will exceed $25, please notify me before incurring additional cost. If any portion is exempt, please release all reasonably segregable non-exempt portions. If another office or component maintains any responsive records, please refer that portion and let me know the referral destination.

This request concerns source provenance and public-record auditability; it does not ask USCENTCOM to conduct new analysis, create records, validate object identity, origin, extraordinary performance, speed, range, altitude, anomalous physics, or non-human technology.

Date range: January 1, 2020 through the date of search for release-control, review, correspondence, and public-release records, plus the original mission/report records for the listed Release 01 items if maintained separately.

Please search for existing releasable records or release-control records tied to PURSUE Release 01 Department of War records marked, reviewed, submitted, or source-controlled through USCENTCOM, including:

- DoW-UAP-D23 / PR26 / PR27, including the D12/D23/PR26/PR27 relationship conflict.
- DoW-UAP-D25 / PR28.
- DoW-UAP-D27 / PR29.
- DoW-UAP-D33 / PR34 and DoW-UAP-D35 / PR35.
- DoW-UAP-D38 / PR36.
- DoW-UAP-D44, D56, D57, D58, D60, D61, D62, D63, and D65.
- PR42 and PR44 where USCENTCOM has source-control, review, or release notes.

For those items, I request existing records reflecting:

- Authoritative report/video pairings and any corrected row/date/location fields.
- Report-line-to-video timestamp crosswalks where releasable.
- Public-rendition generation or release history for the public DVIDS videos where already reviewed.
- Releasable sensor-display state fields such as mode, FOV, zoom, polarity, reticle/tracker state, stabilization state, overlays, and timebase.
- Releasable platform state or geometry fields such as position, altitude, heading, speed, gimbal/sensor angles, line of sight, range assumptions, and object-altitude assumptions.
- Releasable environmental and traffic controls such as weather, clouds, haze, sea state, AIS/vessel traffic, aviation traffic, drone/balloon/range activity, satellite/reentry/fireball checks, and reflection controls.
- OCR-complete report text or a no-further-text statement for D60, D63, and D65 if USCENTCOM holds release-control records for those PDFs.

Please treat this as a narrow records request for auditability and conventional controls, not as a request for conclusions about the events.

Subject: Reference inquiry: RG 615 and UAP holdings mapping for PURSUE Release 01 incident summaries

To the National Archives reference staff:

I am reviewing public PURSUE Release 01 UAP-related records and trying to cite the National Archives record context accurately. This is a reference inquiry, not a media inquiry and not a request for NARA to validate any UAP claim.

Please point me to existing public finding aids, NAIDs, record groups, series, containers, microfilm references, catalog entries, or reference pages that would help map the Release 01 incident-summary PDFs and related historical summaries to NARA holdings.

The specific records are:

- 38_143685_box7_Incident_Summaries_1-100
- 38_143685_box_Incident_Summaries_101-172
- 38_143685_box_Incident_Summaries_173-233

The source-control mapping needed is:

- Whether any Release 01 incident-summary PDFs appear to map to Record Group 615, Project BLUE BOOK case files, Project BLUE BOOK administrative files, OSI material, microfilm, or another accession.
- Whether there are existing NAIDs or catalog entries that should be cited for the incident summaries, textual/microfilm records, moving-image records, photographs, or presidential-library UAP-related holdings.
- Whether NARA has public guidance for distinguishing newly accessioned RG 615 material from older UFO/UAP-related holdings in other record groups.
- Whether a researcher should cite a specific collection, series, container, microfilm roll/frame, or catalog URL when discussing these records.

This request concerns source provenance and public-record auditability. I am not asking NARA to create a new crosswalk, certify that any record is novel or less redacted, interpret an object, or endorse any conclusion. Public pointers or recommended search terms would be helpful.

Subject: Reference inquiry: NASA source-lineage pointers for PURSUE Release 01 historical materials

To the NASA History Office:

I am reviewing public PURSUE Release 01 NASA-related historical materials and trying to cite original NASA sources accurately. This is a source-lineage/reference inquiry. It does not ask NASA to validate object identity, origin, extraordinary performance, anomalous physics, or non-human technology.

Please point me to existing public sources or reference paths for these materials:

- PURSUE Release 01 NASA rows 20-21 and 139-150.
- Gemini VII transcript, debrief, audio, and caption lineage, including mission-elapsed-time or page-span references where available.
- Apollo 12 image/frame provenance for Release 01 VM1-VM6. Local source review found candidate public-source matches for VM2-VM5 in Apollo 12 Image Library frames AS12-46-6846 through AS12-46-6849, within the AS12-46-6845 through AS12-46-6852 sequence. These are candidate source-lineage leads only, not image-content claims.
- Any original frame IDs, unmodified source-frame URLs, adjacent-frame lists, scan/film notations, or public image-modification/crop/annotation history that would keep these citations accurate.
- Apollo 17, Skylab, or related NASA transcript/image/audio materials included in Release 01, if NASA History has a better public citation path than the Release 01 file alone.

If this requires a formal FOIA request or another NASA office rather than a History Office reference response, please let me know the right routing. I am only trying to separate public source provenance from interpretation.

Subject: FOIA request: PURSUE Release 01 State cable release-history and provenance records

To the Department of State Information Access Programs Directorate:

This is a Freedom of Information Act request for existing Department of State records. I request electronic copies where available. If fees will exceed $25, please notify me before incurring additional cost. If any portion is exempt, please release all reasonably segregable non-exempt portions. If any responsive record is already publicly available, a citation or URL is sufficient.

This request concerns source provenance and public-record auditability; it does not ask the Department to validate any UAP claim, object identity, origin, extraordinary performance, or non-human technology.

Date range: the source cable dates listed below and any release-processing, FOIA, MDR, accession, or public-reading-room records through the date of search.

I am reviewing Department of State records included in PURSUE Release 01 and request existing records reflecting:

- MRN/date/post/subject crosswalks for Release 01 rows 151-155 / MRNs 85 PORT MORESBY 199, 94 DUSHANBE 259, 01 MOSCOW 13169, 04 ASHGABAT 1028, and 23 MEXICO 2544.
- Release-history references for Release 01 rows 29-30, identified in Release 01 as 59_214434_SP 16 [7.18.1963] and 59_64634_711.5612[7-2852].
- Any prior-public FOIA, FOIA Library, NARA, or reading-room references for the same cables.
- Any release-history, accession, declassification, or redaction-status references that can be released.
- Records reflecting whether Release 01 State rows 29 and 30 are intended to reference the same PDF asset or whether one row points to an incorrect asset.
- Records reflecting whether the cable identified in extracted text as MRN 23 MEXICO 2544 should be dated September 16, 2023 rather than the 2003 date shown in Release 01 catalog fields.

The purpose is to cite the cables accurately and distinguish release metadata from event interpretation.

Subject: PURSUE Release 01 public metadata correction and routing request

Suggested route: Department of War Website Technical Support. Use the question text below in the form; it is designed to stay under the 1000-character question limit.

Question:

I am reviewing PURSUE Release 01 public War.gov materials and trying to cite them accurately. Please route this to the office that can correct or explain public CSV/page metadata conflicts: State rows 29/30 duplicate PDF; PR26/D12/D23/PR27 pairing; PR28 D7 vs D25; PR29 D8/NORTHCOM vs D27/Gulf of Oman; PR38 unresolved vs aircraft; PR49 and FBI Photo A1 sharing DVIDS ID 1006111; State Cable 5 2003 vs MRN 23 MEXICO 2544 dated 2023; NASA VM1-VM6 source-frame/annotation lineage. I am asking only for routing or a corrected machine-readable addendum, not validation of object identity, origin, performance, anomaly status, or non-human technology. Evidence-control page: https://virtualrealityaistudio.com/uap/evidence-control-requests/

If routed to postal public communications instead of the web form, include the same public evidence-control URL and the DOW IQA evidence appendix for the longer issue list. Do not use this route for disclosure demands, native sensor files, or event validation.

Subject: Request for Correction under DOW Information Quality Guidance: PURSUE Release 01 public metadata/source-control conflicts

Mail to: DOW Public Affairs/Information Quality Act, 1400 Defense Pentagon, Washington, DC 20301-1400.

Do not send until the owner contact block below is completed and the evidence appendix is attached or included.

This is a Request for Correction of information submitted under DOW's Information Quality Guidance.

Requester contact information:

- Name: [OWNER FULL NAME]
- Mailing address: [OWNER MAILING ADDRESS]
- Telephone: [OWNER PHONE]
- Email: [OWNER EMAIL]
- Organization affiliation, if any: [OWNER ORGANIZATION OR NONE]

Information to be corrected:

PURSUE Release 01 public materials, including the War.gov PURSUE public page, Release 01 public CSV/data product, public media links, and related public source metadata for the affected rows listed in the appendix.

This request concerns source provenance and public-record auditability; it does not ask for validation of object identity, origin, extraordinary performance, speed, range, altitude, anomalous physics, sensor truth, or non-human technology.

Explanation of correction requested:

Please correct or publicly explain specific public metadata/source-control conflicts in PURSUE Release 01. The requested correction is a public, machine-readable addendum or corrected CSV that identifies stable row IDs, source URLs, final URLs, file size or hash fields where available, duplicate-byte group where applicable, agency, record type, DVIDS ID, report/video pairing fields, redaction/status definitions, conflict flags, and last-reviewed timestamp where available.

Impact:

The current conflicts make it difficult for public researchers to cite Release 01 accurately, distinguish public source metadata from local inference, and avoid linking unrelated records through duplicated identifiers. Corrected public metadata would improve accuracy, clarity, completeness, utility, and integrity of the disseminated public data product.

Requested corrections or explanations:

- State rows 29 and 30: correct or explain whether two differently titled/dated catalog rows intentionally point to the same PDF asset.
- PR26 / D12 / D23 / PR27: correct or explain whether PR26 should reference DoW-UAP-D12, DoW-UAP-D23, both, or neither, and how D23 maps to PR26/PR27 if applicable.
- PR28: correct or explain whether PR28 is paired to DoW-UAP-D7, DoW-UAP-D25, both, or neither.
- PR29: correct or explain whether PR29 is paired to DoW-UAP-D8, DoW-UAP-D27, both, or neither, and reconcile public United Arab Emirates / Gulf of Oman / source-command fields if they remain conflicted.
- PR38: correct or explain the conflict between unresolved title language and any field that says resolved as aircraft.
- PR49 / FBI Photo A1: correct or explain why an Army video row and an FBI image row both carry DVIDS ID 1006111.
- State Cable 5: correct or explain whether the cable identified in extracted text as MRN 23 MEXICO 2544 should be dated September 16, 2023 rather than the 2003 date shown in Release 01 catalog fields.
- NASA VM1-VM6: provide or route public source-lineage fields for original frame IDs, unmodified source-frame links or scans, adjacent-frame lists, and release-image modification/crop/annotation history where already public or releasable.

Supporting documented evidence:

Include the accompanying evidence appendix listing the affected rows, public URLs, observed conflicting fields, and local source-control notes. The appendix should not include claims about object identity, origin, performance, anomaly status, or non-human technology.

Subject: FOIA request: AARO / OSW-JS PURSUE Release 01 release-control records

To the OSW/JS FOIA Requester Service Center:

This is a Freedom of Information Act request for existing AARO-held or OSW/JS-held records. I request electronic copies where available. If fees will exceed $25, please notify me before incurring additional cost. If any portion is exempt, please release all reasonably segregable non-exempt portions. If another office or component maintains any responsive records, please refer that portion and let me know the referral destination.

This request concerns source provenance and public-record auditability; it does not ask for validation of object identity, origin, extraordinary performance, speed, range, altitude, anomalous physics, sensor truth, or non-human technology.

Date range: January 1, 2020 through the date of search.

Please search for existing AARO-held or OSW/JS-held records concerning PURSUE Release 01 release control and public crosswalks, including:

- Catalog/report/video relationship tables or source-control crosswalks.
- Release 01 public page correction tickets or coordination records.
- DVIDS upload, source-description, source-office, caption, or public-rendition coordination records.
- DOPSR or public-release package identifiers, if releasable.
- Non-sensitive release notes or public-release coordination records for PR27/D23, PR28/D7/D25, PR29/D8/D27, D33/PR34, D35/PR35, PR49/FBI Photo A1, the 2020 maritime IR records, and related Release 01 source-control conflicts.
- Referral or ownership notes identifying whether DVIDS, AARO, USCENTCOM, USEUCOM, USNORTHCOM, DOW Public Affairs, or another component owns correction of specific public metadata fields.

Please do not create a new analysis or event interpretation. If no responsive AARO/OSW-JS release-control records exist, a no-records response or referral path is sufficient.

Subject: FOIA request: existing FBI release inventory/crosswalk records for 62-HQ-83894 and Vault UFO Parts 01-16

To the FBI Record/Information Dissemination Section:

This is a Freedom of Information Act request for existing FBI records. I request electronic copies where available. If fees will exceed $25, please notify me before incurring additional cost. If any portion is exempt, please release all reasonably segregable non-exempt portions.

This request concerns source provenance and public-record auditability; it does not ask the FBI to validate object identity, origin, extraordinary performance, speed, range, altitude, anomalous physics, sensor truth, or non-human technology.

Please search for any existing FBI release inventory, processing note, public crosswalk, or other reasonably segregable record that maps FBI file 62-HQ-83894 / 65_HS1-834228961_62-HQ-83894 to the FBI Vault UFO collection, including UFO Part 01 through UFO Part 16 (Final), and to the PURSUE Release 01 section/serial PDFs released publicly on May 8, 2026.

If no crosswalk exists, please do not create one. Instead, please provide any existing Vault part/page range records, section/serial inventory records, release-processing metadata, prior-public release notes, or reading-room records that would help researchers compare page order, serial order, and redaction state without inferring that any page is new, missing, less redacted, or complete.

This request does not seek duplicate physical copies of public Vault PDFs unless those records contain separate release-processing metadata. Public citations or URLs are sufficient for records already available in the Vault.

Subject: Conditional FOIA request: referred PURSUE Release 01 Greece/Aegean/Mediterranean records

To the USEUCOM FOIA Requester Service Center:

This draft should be used only if DVIDS, USCENTCOM, OSW/JS, AARO, or a corrected public source identifies USEUCOM as the holder, submitter, release coordinator, or correction owner for a specific PURSUE Release 01 record.

This is a Freedom of Information Act request for existing USEUCOM records. I request electronic copies where available. If fees will exceed $25, please notify me before incurring additional cost. If any portion is exempt, please release all reasonably segregable non-exempt portions. If another office or component maintains any responsive records, please refer that portion and let me know the referral destination.

This request concerns source provenance and public-record auditability; it does not ask for validation of object identity, origin, extraordinary performance, speed, range, altitude, anomalous physics, sensor truth, or non-human technology.

Please search for existing releasable USEUCOM records or release-control records for the referred PURSUE Release 01 Greece/Aegean/Mediterranean item(s), limited to the specific records identified in the referral.

Requested record categories:

- Authoritative report/video pairing or source-description ownership records.
- Releasable report-line-to-video timestamp crosswalks.
- Public-rendition generation or release history where already reviewed.
- Releasable sensor/display/platform/environment context if already contained in existing records.
- Referral notes identifying the originating or holding component for the specific public metadata conflict.

Please do not conduct new analysis or event interpretation. A no-records response or referral path is sufficient if USEUCOM does not maintain the records.

Subject: Conditional FOIA request: referred PURSUE Release 01 PR29 / DVIDS 1006074 records

To the USNORTHCOM FOIA Requester Service Center:

This draft should be used only if DVIDS, USCENTCOM, OSW/JS, AARO, or a corrected public source identifies USNORTHCOM as the holder, submitter, release coordinator, or correction owner for the PURSUE Release 01 PR29 / DVIDS 1006074 lane.

This is a Freedom of Information Act request for existing USNORTHCOM records. I request electronic copies where available. If fees will exceed $25, please notify me before incurring additional cost. If any portion is exempt, please release all reasonably segregable non-exempt portions. If another office or component maintains any responsive records, please refer that portion and let me know the referral destination.

This request concerns source provenance and public-record auditability; it does not ask for validation of object identity, origin, extraordinary performance, speed, range, altitude, anomalous physics, sensor truth, or non-human technology.

Please search for existing releasable USNORTHCOM records or release-control records concerning the referred PURSUE Release 01 PR29 lane, including DVIDS video 1006074, the DVIDS reference to DoW-UAP-D8, any D27/Gulf of Oman referral or correction records, source-description ownership, AARO submission coordination, public-page correction records, and releasable report/video pairing notes.

Please do not conduct new analysis or event interpretation. A no-records response or referral path is sufficient if USNORTHCOM does not maintain the records.

Subject: FOIA request: PURSUE Release 01 NASA source-lineage records

To NASA Headquarters FOIA:

This is a Freedom of Information Act request for existing NASA records. Please process this as one Headquarters-routed request because the responsive records may involve multiple NASA offices or centers. I request electronic copies where available.

Requester information to add before submission:

- Name:
- Email:
- Mailing address:
- Phone:
- Fee category:
- Maximum fee amount or fee waiver request:

This request concerns source provenance and public-record auditability. It does not ask NASA to validate object identity, origin, extraordinary performance, anomalous physics, non-human technology, or any visual interpretation.

Please search for existing records, source-lineage identifiers, or public-release records sufficient to identify the original NASA source context for the NASA materials included in Department of War PURSUE Release 01 rows 20-21 and 139-150, including:

- Gemini VII transcript, debriefing, audio, and caption lineage, including mission-elapsed-time or page-span references where available.
- Apollo 12 transcript source title, page span, mission-elapsed-time crosswalk, and adjacent transcript context for the Release 01 excerpt.
- Apollo 17, Apollo 11, and Skylab transcript/debriefing source title, page span, mission-elapsed-time crosswalk, and adjacent context for the Release 01 excerpts.
- Apollo 12 VM1-VM6 image/frame provenance, including original frame IDs, unmodified source-frame URLs or scans, adjacent-frame lists, scan/film notations, and public image modification/crop/annotation history where such records exist.
- Apollo 17 VM6 original frame ID, adjacent-frame list, source-frame URL or scan, original-film scan notation, and any existing releasable release-control or analysis-status record tied to the public Release 01 claim.

For context only, local public-source review found candidate Apollo 12 Image Library source-frame matches for VM2-VM5 in AS12-46-6846 through AS12-46-6849, within the AS12-46-6845 through AS12-46-6852 sequence. These are candidate source-lineage leads only, not image-content claims.

If NASA does not maintain responsive records, please provide a no-records response or refer the request to the appropriate NASA office or federal component. Please release all reasonably segregable non-exempt portions.