Concepts

How a program hides in the budget

The documented ways US defense money reaches programs Congress can't see in detail, separated from UAP Gerb's claims about what that money funds. The mechanisms are real and legal; whether any fund UAP work is the open question.

Ties

ToRoleYearsVerdictSource
UAP Gerbsource of the UAP-specific claimsConcept
Report 01 - UAP program recordsthe 'programs' FOIA clusterConcept
Harry Reidasked for a restricted SAP for AATIP (2009)2009Documented · occurred

Tied from

FromRoleYearsVerdictSource
UAP Gerbmain research areaConcept
SAP loopholes (UAP Gerb Vol 2)extends it—
UFO secrecy architecture (UAP Gerb Vol 1)the SAP and DOE layers—verified/occurred

Links

Documented mechanisms (real, legal)

Mechanism How it works Status
Classified line items Budget books list lines like Air Force RDT&E 'Classified Programs', one of the biggest single lines in the defense budget, with no detail {{verified}}
Air Force 'pass-through' (non-blue) budget Money in the Air Force top line that the Air Force never sees or controls. About $38B/yr recently; $52.3B requested for FY2027. Never itemized. A 2013 RAND report said it funds the National Intelligence Program (mostly satellites), special operations and the Defense Health Program Air & Space Forces; RAND
Special Access Programs (SAPs) Access beyond Top Secret; three kinds: acknowledged, unacknowledged (USAP), and waived DoD 5205.07
Waived SAPs 10 USC 119: the Secretary 'may waive any requirement' to report details if disclosure 'would adversely affect the national security', and must then brief only 'the chairman and ranking minority member of each of the defense committees' (roughly 8 people). The least-overseen legal category Statute text
Vague program-element names Budget lines ('program elements') with generic titles ('Advanced Technology Development', 'Special Programs') that can hold classified sub-efforts Practice
Contractor IRAD Contractors do 'independent R&D' and recover it as overhead on other contracts (FAR 31.205-18). The work isn't a line item Congress votes on Mechanism
DOE 'Restricted Data' Under the Atomic Energy Act, nuclear-weapons information is 'born classified' and handled outside DoD's SAP system; 'Transclassified Foreign Nuclear Information' is a real related category Law

Added from Gerb Vol. 2 (see SAP loopholes (UAP Gerb Vol 2))

Mechanism Status
Unacknowledged SAP security = 3–10% of operating cost (one estimate 40%) JSC 1994
'Content-only' SAP: information only, no program budget line AFI 16-701 text; the claim that it removes reporting is inference
Sub-compartments/projects need only service-level SAP office approval; congressional notice is specified at the SAP level AFI 16-701 §4.3–4.5
'Non-covert action' White House SAP falls between 50 USC 3093 and 10 USC 119 Grusch's claim; plausible gap

UAP Gerb's claims about what the mechanisms hide (as reported; to be sourced episode by episode)

Claim Status What would test it
Lockheed funds UAP reverse-engineering through IRAD ('generic aerospace research') {{unproven}} IRAD disclosures to DCAA; contractor project titles; whistleblower testimony
The NRO holds 'carryover' funds for legacy UAP programs {{unproven}} NRO budget justifications; IG reports on unobligated balances
DOE runs crash retrieval via NEST; material held as Restricted Data {{unproven}} DOE classification guides; NEST mission documents
Cheney was a 'principal advocate' for DOE-routed funding {{unproven}} Primary source needed
Paul Kaminski (Under Secretary for Acquisition 1994–97) formalized the structure that keeps programs from GAO audit {{unproven}} SAP policy changes 1994–97; Kaminski's own statements

Supporting context (documented, UAP-adjacent)

How to use this with E

For each claim E brings: (1) the budget document or program-element number, (2) the fiscal year, (3) what the line says vs. what's alleged. Log it in the table above and link the source episode on UAP Gerb.