Strategic information infrastructure
A FOIA response is not the finish line. It is evidence that tells you what to ask next.
fuckthe.press preserves the request, the response, the exact source identity, the unresolved gap, and the next bounded records move so an investigation gets narrower and stronger instead of starting over.
RES-009 verified source-pair target complete
The evidentiary chain reaction
The useful outcome is not merely receiving documents. It is building the documentary path required to make the government define its answer through its own records.
That creates an appeal question: what enforcement proceeding is being protected, and when does the basis expire?
That creates a more precise request for the records system, fields, exports, or search results the agency just identified.
That creates a bounded request for communications, attachments, or routing records tied to a known person and time window.
Every answer should reduce uncertainty—or create the next defensible branch.
Immutable source identity
Source identity is proven from the actual objects. A summary, OCR layer, agency index page, or released-record bundle cannot silently substitute for the requester submission or the requester-facing response.
The request side must be the actual submission, not an agency description of it.
The response side must be the agency letter sent to the requester, not just the produced records.
Each side is hashed so the evidence can be rechecked against the exact bytes later.
The public proof can show that verification happened without publishing requester-identifying material.
Verification architecture
A pair can finish acquisition, duplicate screening, qualification, two independent reviews, and adjudication and still remain outside the public corpus. The target count never gets to decide the evidence.
Golden cases
The test is not whether police records can prove an extraterrestrial explanation. The test is what LVMPD recorded, retained, redacted, released, and identified as responsive.
Reinstated/narrowed request for Watch Commander logs, PIO metadata, inter-agency notification metadata, evidence/property ledger metadata, and retention notices tied to the April 30–May 1, 2023 backyard/UAP call.
Requested dispatch logs, radio transmissions, 911 recordings, incident/case files, investigative notes, internal memoranda, intelligence records, and other records generated by the response.
Requested all BWC footage from every responding officer and supervisor, recording metadata, event identifiers, subsequent-response footage, and a legal basis for every withholding or redaction.
Source: LVMPD Public Records Request Archive and current LVMPD portal correspondence. Agency-created BWC routing IDs are preserved as linked references and are not counted as new independently filed requests.
The test is not to collapse every sighting into one phenomenon. It is to reconstruct what each agency knew, when it knew it, and which records supported later public conclusions.
Public-safe research ledger
The public layer exposes verified milestones, counts, and research state. Private acquisition material, requester identity, raw reviewer output, and sealed evidence remain outside the public surface.
The canonical public corpus cannot regress below the latest verified snapshot simply because an older feed row is still cached upstream.
P279 closed RES-009 at 120/120: 90 promotions, 277 canonical bindings, checkpoint 90 passed, 8 source families, 67 pairs outside FTC/HHS, and zero remaining. No P280 is assigned unless the completed scope is explicitly expanded.
THE PRODUCT IS NOT A BIGGER PILE OF DOCUMENTS.
Public-record pipeline
These requests exist to resolve specific evidence gaps. The ledger shows the question, agency, scope, and public status without publishing requester identity, contact information, signatures, private receipts, raw source material, or sealed review evidence.
Detection systems, federal investigative leads, and the FAA security-partner requests behind the New Jersey Temporary Flight Restrictions.
Bounded exact-term searches designed to establish whether “Project Twilight” appears in existing federal records.
Eight independently filed LVMPD requests covering CAD, emergency communications, body-worn camera, redaction provenance, post-incident surveillance, the broader investigative file, and two September 22 BWC follow-ups. Related agency-created routing IDs are shown inside the affected requests.
Records concerning deployment, operation, detections, analytical results, unresolved detections, interagency coordination, and after-action assessment of advanced drone/UAS detection technology used during the late-2024 New Jersey incidents.
Status: Acknowledged September 11, 2026 · DHS tracking 2026-HQFO-03767
Records documenting the federal-security-partner requests behind 22 drone Temporary Flight Restrictions issued over New Jersey critical infrastructure on December 19, 2024, and the FAA decision process that produced them.
Status: Acknowledged by FAA · request 2026-05635
Records concerning how the FBI evaluated more than 5,000 reported drone-sighting tips, generated approximately 100 investigative leads, and categorized, resolved, or left unresolved those reports.
Status: FBI eFOIA request received · an eFOIA file is now available for this request
An exact-term records request to determine whether “Project Twilight,” “PROJECT TWILIGHT,” or “Twilight Project” appears in DIA records.
The request asks DIA to search existing electronic systems for correspondence, memoranda, reports, briefings, program indexes, project listings, contract records, budget records, tasking documents, presentations, and records-management indexes containing those exact terms.
Status: Receipt confirmed by DIA FOIA Service Center
The same bounded exact-term search was submitted to the Department of the Air Force to identify records using “Project Twilight,” “PROJECT TWILIGHT,” or “Twilight Project.”
The request covers existing correspondence, memoranda, reports, briefings, program indexes, project listings, contract records, budget records, tasking documents, presentations, and records-management indexes containing the specified terms.
Status: Received · Air Force case 2026-07789-F
Complete existing Computer Aided Dispatch record for the May 1, 2023 backyard incident, bounded to event LLV230500000097.
Status: Submitted · Media Request · LVMPD X017511-091826
Communications recordings associated with the event from initial reporting and dispatch through officer radio traffic and final disposition.
Status: Redirected by LVMPD to the Communications Research Office workflow for 911 calls, Communications Record Reports, and phone/radio search and reproduction · original reference X017512-091826
All existing BWC recordings for every officer who responded to, investigated, assisted with, or otherwise participated in the May 1, 2023 event.
Status: Response received September 22, 2026 · two BWC items produced through Evidence.com/Axon · follow-up X017739-092226 filed for native/additional BWC · LVMPD X017513-091826
Existing records documenting review, redaction, obscuring, withholding, or release processing of body-worn-camera footage associated with the event.
Status: Completed September 24, 2026 · requester inspection found the two Evidence.com items were the same two previously produced redacted BWC recordings, with the backyard portions obscured · no separate redaction/audit records were identified in this production · LVMPD X017514-091826
Records concerning LVMPD's reported placement, installation, operation, or proposed placement of surveillance cameras at the residence following the May 1, 2023 incident.
Status: Processing · LVMPD reports active research/correspondence with appropriate units · earliest expected availability, if any, close of business October 16, 2026 · related agency-created BWC routing ID X017995-092426 · original reference X017515-091826 remains active
The broader investigative record associated with the backyard incident and any cross-referenced identifiers tied to the same event.
Status: Processing · LVMPD reports active research/correspondence with appropriate units · earliest expected availability, if any, close of business October 16, 2026 · related agency-created BWC routing ID X017996-092426 · original reference X017517-091826 remains active
Follow-up to X017513-091826 seeking the original/native source versions of the two produced recordings and every additional BWC recording associated with the event.
Status: Submitted · Body Worn Camera Request · LVMPD X017739-092226
Separate document request for the Axon/evidence-system paper trail surrounding the BWC associated with the event.
Status: Submitted · General Police Records Request X017742-092226 · related agency-created BWC routing ID X017999-092426 submitted September 24, 2026
Agency acknowledgements, tracking numbers, productions, referrals, denials, and appeals are added as the record develops.
The public trail shows the research process without publishing the researcher.Contributor intake · engine-building corpus
A denial, appeal, fee letter, no-record response, clarification request, portal export, or released record may contain the exact procedural clue that helps somebody else's investigation. Contribution intake is being built as part of the engine-development phase.
Personal or requester-identifying data is not a commodity for the project.
Exact source files can be retained for provenance verification while a separate public-safe derivative is used publicly.
Submitting material does not mean the original document, your identity, contact details, signatures, or private portal information will be published.
Requester-identifying information can be removed before public use, while hashes and provenance preserve the evidentiary chain.
What helps most
How usefulness is judged
Submission portal
The public site will not pretend an upload path exists before the privacy, provenance, duplicate-checking, and public-safe review pipeline is ready. Until then, this page defines exactly what the contribution system is being built to accept and protect.
Follow development progress →