Inside the Waiver: Oversight Gaps and Contractor Exposure
A Blackgrove Global Risk analytical essay for prime executives, defense investors, and oversight committees. Posture: null-first and tiered. The reverse-engineering and contractor-possession allegations are uncorroborated testimony and are held below the line. What is documented, and what this piece turns on, is the statutory secrecy machinery, which is real, on the public record, and the actual source of the exposure.
TL;DR
The structural opacity of waived unacknowledged special-access programs gives concealment allegations their force independent of whether the allegations are true, and that opacity is itself the contracting-integrity and litigation exposure for named primes. A firm cannot easily disprove a claim about a program it is legally barred from discussing.
The machinery is documented, not alleged. Under 10 U.S.C. § 119, a waived special-access program is exempt from normal congressional notification and reported only to a restricted group; the Freedom of Information Act does not reach private contractors; appropriations can be routed through obscure line items; and contractor data is shielded by trade-secret and proprietary protection. This is the real, public-record structure, and it is capable of hiding a program from most of Congress and from a firm's own auditors.
The exposure is a corroboration event, not the truth of any current allegation. The Grusch and "Immaculate Constellation" claims are uncorroborated testimony, and AARO's 2024 review found no evidence of reverse-engineering programs. The risk to a named prime is what would activate if any such claim were corroborated or a records-disclosure regime reached contractors: contracting-integrity, disclosure, litigation, and headline exposure that the opacity itself makes hard to rebut.
Key Findings
Waived SAPs are exempt from normal congressional notification by statute. Under 10 U.S.C. § 119, the Secretary of Defense may waive the requirement that certain information be included in the annual SAP report if inclusion would adversely affect national security, providing the information and the waiver justification only to the chairman and ranking member of each defense committee. Waived programs are the most sensitive tier and the least visible to the broader Congress.
The secrecy extends into the contractor and defeats external checks. The Freedom of Information Act does not apply to private corporations, contractor data is protected by trade-secret and proprietary rights, and appropriations can be distributed through obscure line items so that oversight committees see a normal item while a deeper effort remains buried. These are documented features, and together they can shield a program from most of Congress and from a firm's own auditors.
A counter-provision exists and defines the current fight. The FY2022 National Defense Authorization Act added 10 U.S.C. § 119a, barring the Secretary of Defense and the Director of National Intelligence from taking any action that would limit the defense committees' access to any classified program, and the FY2024 NDAA created a UAP records collection at the National Archives. The oversight system is actively contesting the opacity.
The allegations are uncorroborated, and the machinery is what makes them plausible-sounding. David Grusch's July 2023 sworn testimony alleged a multi-decade crash-retrieval and reverse-engineering program lodged within contractors to evade oversight; the "Immaculate Constellation" claim followed in November 2024. AARO's March 2024 review found no evidence of such programs, and named contractors have denied them. We hold the allegations below the line. Their persistence is a function of the documented secrecy structure, not of established fact.
The opacity is the exposure, whatever the truth. A prime named in a corroborated revelation, or reached by a records-disclosure mandate, faces contracting-integrity, disclosure, and litigation exposure, and the same secrecy that would shield a real program prevents the firm from cleanly rebutting an allegation about one. The reputational trap is structural.
Details
The thesis: opacity as exposure
We assess that the exposure to a named defense prime on this subject arises from the structure of classified-program secrecy rather than from the truth of any current allegation, and that the defining feature of the exposure is a firm's inability to rebut a claim about a program it cannot discuss. The concealment allegations that circulate about defense contractors draw their persistence from a documented fact: the system is capable of hiding a program from most of Congress, from the public, and from a firm's own auditors. That capability is the reason the allegations cannot be dismissed out of hand, and it is also the reason a prime is structurally exposed. When the machinery exists to hide exactly what an allegation describes, the absence of visible evidence does not refute the allegation, and the firm's denial carries less weight than it would in a transparent domain. The exposure is not that the allegations are true. It is that the opacity makes them un-rebuttable, and that a corroboration event would land on a firm that cannot easily defend itself.
The documented machinery
The secrecy structure is a matter of public record, and precision about it is what separates this analysis from both the believers and the debunkers. Under 10 U.S.C. § 119, special-access programs are subject to congressional oversight through annual reporting to the defense committees, a new-program report, and a requirement that a SAP may not be initiated until the defense committees are notified and thirty days elapse. The critical provision is the waiver. The Secretary of Defense may waive the requirement that certain information be included in the SAP report if the Secretary determines that inclusion would adversely affect national security, on a case-by-case basis, and in that event must provide the information and the justification for the waiver only to the chairman and ranking member of each defense committee. This is the statutory basis for the most sensitive tier of program, the waived unacknowledged SAP, whose reporting is restricted to a handful of members rather than the full oversight committees.
The Department's own directives describe the tiering. Acknowledged SAPs have a public existence and classified details; unacknowledged SAPs have a classified existence; waived SAPs are unacknowledged programs whose congressional reporting is further restricted. Programs can nest, with compartments, sub-compartments, and projects inside a single SAP, which multiplies the layers of access control. The point is not that any of this is improper. Stealth, cryptography, and nuclear programs require deep secrecy, and the structure exists for legitimate reasons. The point is that the structure is capable of concentrating knowledge of a program in very few hands, and that capability is what an allegation of concealment exploits.
The secrecy extends past the government and into the contractor, which is where the exposure localizes. The Freedom of Information Act does not apply to private corporations, so the transparency mechanism that reaches a government agency does not reach a prime's internal records. Contractor data is protected by trade-secret and proprietary rights, adding a commercial layer of confidentiality on top of the classification. And appropriations for sensitive work can be distributed through obscure line items, so that an oversight committee reviewing a budget sees a normal program while a deeper, contractor-held effort remains buried within it. These features are documented, and together they describe a structure in which a program can be shielded from most of Congress, from the public, and from a firm's own auditors simultaneously. That is the machinery, and it is real whether or not any particular allegation about its use is true.
The counter-provision and the current contest
The opacity is not uncontested, and the current legislative record is a live fight over it. The FY2022 National Defense Authorization Act added 10 U.S.C. § 119a, which bars the Secretary of Defense and the Director of National Intelligence from taking any action that would have the effect of limiting the defense committees' access to any classified program, defined to include special-access programs, alternative compensatory control measures, and other controlled-access programs. The FY2024 NDAA created a UAP records collection at the National Archives and directed the review of UAP-related records, though the more far-reaching records-review board and eminent-domain provisions of the proposed UAP Disclosure Act were stripped before enactment. The oversight system is asserting a right of access against the secrecy structure, and the outcome of that assertion is one of the developments most likely to change the exposure for a named prime, because expanded and enforced committee access is precisely what would surface or dispel a concealed program.
The allegations, tiered and held below the line
The specific allegations that name defense contractors are testimonial and uncorroborated, and we hold them accordingly. In July 2023, David Grusch testified under oath that individuals with firsthand knowledge had described a multi-decade crash-retrieval and reverse-engineering program lodged within defense contractors specifically to evade congressional oversight. In November 2024, a further claim described an unacknowledged program under the name "Immaculate Constellation." Against these, AARO's Historical Record Report Volume I of March 2024 found no evidence that the US government or private companies have been reverse-engineering extraterrestrial technology, and assessed that the named alleged programs either do not exist, are misidentified authentic and highly sensitive national-security programs unrelated to extraterrestrial exploitation, or resolve to a disestablished program. Named contractors have denied the allegations. We do not assert the allegations, and we do not dismiss them; we hold them at the uncorroborated-testimonial tier and note that their persistence is explained by the documented secrecy structure without requiring them to be true.
The analytic value of the machinery section is precisely that it lets this be handled honestly. One does not have to believe the allegations to see why they are difficult to refute, and one does not have to disbelieve them to hold them below the line pending corroboration. The secrecy structure is the reason both the allegation and its denial are hard to verify from outside, and that unverifiability is the environment in which a named prime operates.
The exposure for named primes
The exposure a prime should price is a corroboration event, not the current allegations. If any claim of contractor possession were corroborated to a standard that cleared the testimonial tier, or if a records-disclosure regime reached contractors holding relevant material, a named prime would face several exposures at once. There is contracting-integrity exposure, if a program's structure were found to have concealed activity from its lawful overseers. There is disclosure exposure, because a program or a records demand that became material would raise securities-disclosure obligations of the kind analyzed in the compliance literature, with the added difficulty that the classification prevents ordinary disclosure. There is litigation exposure, both securities and derivative, on the event-driven model in which a corrective disclosure triggers a stock drop and a claim. And there is headline and equity exposure, which, as the market analysis shows, would be genuinely two-sided: compression on the contracting-integrity and litigation reading, and a speculative premium on the reading that the named firm holds the most valuable technology on Earth.
The structural cruelty of the position is that the same opacity that would shield a real program prevents the firm from cleanly rebutting an allegation about one. A prime cannot fully disclose the contents of a waived program to disprove a claim, and its denial is discounted precisely because everyone knows the structure permits concealment. This is the reputational trap, and it is not a function of any wrongdoing. It is a function of operating inside a secrecy structure that the public and the market know can hide exactly what the allegation describes. A prime's risk posture has to account for the fact that it may at some point need to defend against a claim it is not permitted to fully answer.
Recommendations
For prime executives (immediate). Treat the concealment-allegation environment as a standing reputational and disclosure exposure, and prepare the governance and communications posture for a corroboration event or a records-disclosure mandate before either occurs. Ensure that whatever can be said within the classification is ready to be said, and that the board and general counsel have mapped the disclosure and litigation exposures that a material revelation or records demand would trigger.
For defense investors (immediate). Price the exposure as a two-sided catalyst rather than as a settled fact. The allegations are uncorroborated and AARO found no evidence, so the base case is no repricing; the tail is a corroboration event whose direction is genuinely uncertain. Do not overweight the allegation, and do not assume the catalyst, if it comes, resolves in a single direction.
For oversight committees (immediate). The lever is access, and 10 U.S.C. § 119a is the statutory basis for it. Enforced, expanded committee access to waived programs is the mechanism that would surface a concealed program or dispel an allegation, and it is the single action most likely to convert an unverifiable environment into a resolved one. Benchmark to reassess: a documented exercise of § 119a access, or a records-disclosure regime that reaches contractors, would materially change the exposure for named primes.
For all (monitoring triggers). Watch for corroboration that clears the testimonial tier, for a records-disclosure mandate reaching contractors, and for enforced committee access under § 119a. Any one of these moves the exposure from latent to active.
Caveats
Tiering. The 10 U.S.C. § 119 and § 119a statutory text, the SAP-tiering directives, the FOIA and appropriations features, the FY2024 NDAA records provisions, and AARO's Historical Record Report Volume I are DOCUMENTED with locators. The Grusch and "Immaculate Constellation" allegations are TESTIMONIAL and uncorroborated, and are held below the line. This piece asserts nothing about whether any contractor holds any such material.
The machinery is legitimate as well as opaque. The secrecy structure exists for valid national-security reasons. This analysis describes its capability to conceal and the exposure that capability creates, and makes no claim that its existence is improper.
The exposure is a corroboration event. The base case is that the allegations remain uncorroborated and no repricing occurs. The analysis prices what would activate if that changed.
Not investment or legal advice. Position, disclosure, and governance decisions are the reader's own, taken with their own counsel.
