The Pentagon’s Confidentiality Waiver: Permission to Talk, but Only to PURSUE
On September 14, 2026, the Department of War lifted the nondisclosure agreements of its personnel so they could talk about UAP. Only the civil and administrative clauses, and only to its own team. The 2022 law already gave more.
On September 14, 2026, the U.S. Department of War published a legal waiver allowing its current and former personnel to disclose UAP-related defense information to official representatives of the PURSUE team. The waiver reaches only the civil and administrative enforcement clauses of nondisclosure agreements and special access program indoctrination agreements, and only for those communications. Section 3373b of title 50, in force since December 2022, already offered broader protection, including criminal protection and the prohibition of reprisals, tied to the AARO channel.
Executive summary of the case file. Everything essential before you dig deeper.
Fact sheet
OSINT - Traceability
Five paragraphs. The note from the U.S. Department of War that has been going around the world for three weeks has five paragraphs, and the whole thing turns on two adjectives: civil and administrative. That is what was lifted on September 14, 2026: the civil and administrative consequences of the nondisclosure agreements its personnel signed, so that they can say what they know about unidentified anomalous phenomena. To one place. Their own.
I downloaded it the day it came out and reread it this week, when half the trade press was summing it up as “the Pentagon authorizes its people to reveal the UFO secrets.” It doesn’t say that. And the distance between what it says and what is being told is the difference between a permit and a funnel, far beyond a lawyer’s nuance. A permit lets you speak. A funnel lets you speak through the opening chosen by whoever gives it to you.
What makes this paper interesting is what it doesn’t contain, because it has been written down for four years somewhere else, with wider reach, passed by both chambers and signed as law. So belief does not enter into it: the job is to put a September 2026 press release next to an article from December 2022 and read both slowly. Paper against paper, which is the only thing I know how to do.
What can be verified, first
The document exists, it is dated and it can be read. It is titled “Department of War Issues Legal Waiver to Authorize Unidentified Anomalous Phenomena (UAP) Disclosures to PURSUE,” it is dated September 14, 2026 and it was published in the department’s press room. For a script it returns 403, which on .gov domains is usually a robot block and not a dead link, so I am working from the copy the Internet Archive captured on September 19. It is the same text, with the capture date on top.
The sentence that decides everything is the second one. It says the waiver supersedes civil and administrative enforcement provisions contained within Non-Disclosure Agreements (NDAs) and Special Access Program Indoctrination Agreements (SAPIAs) previously executed within the United States, strictly for communications directed to the PURSUE team. Put plainly: it voids the civil and administrative enforcement clauses of those agreements, and only for what is told to the PURSUE team.
Two things in one sentence, and both are cutbacks. The first is subject matter: civil and administrative. Not a word about criminal law. The second is the recipient: strictly, for communications directed to the PURSUE team. Not to a journalist, not to a congressional committee, not to a conference, not to a six-hour podcast. To them.
The subject, on the other hand, is wide. The note authorizes all current and former military personnel, civilian staff and contractors of the department who have or have had access to UAP-related defense information to disclose it directly to official representatives of PURSUE. And it explains why in a sentence worth its weight: historically, those with direct knowledge of these programs cited fear of legal liability, of losing their security clearance or of an administrative file.
The memorandum that arrived six weeks earlier
Six weeks earlier, the piece above it had arrived. On July 31, 2026, the Office of the Director of National Intelligence circulated an unclassified memorandum titled “Preliminary Guidance for Implementation of NDA Waivers,” reference ES 2026-00818, signed by principal deputy director Aaron Lukas. It gives intelligence community agencies thirty days to designate a liaison with PURSUE and covers disclosures made to designated representatives of AARO or of the PURSUE task force.
When someone lifts a prohibition for you and at the same time points to the door you have to go through, what they have given you is the door, not the key.
I have found no copy of that memorandum on any official portal. The one in circulation was published by space journalist Douglas Messier in his newsletter on August 2, and an international law firm’s analysis glosses it with the same reference and the same signatory. Two independent sources saying the same thing about the same paper. It is not a primary document in my hands, and I mark it as what it is.
And one detail that says a lot about the apparatus: the portal where the department publishes the batches of files, war.gov/UFO, does not mention the waiver. In the archived copy of October 4, the word waiver does not appear, nor NDA, nor any indication of how to locate a PURSUE representative. The only thing there for someone who wants to report something is a link that says “Visit AARO.mil.” Hold on to that link, because it comes back soon.
The law creates the channel and the shield
Section 1673 of the 2023 defense act orders a secure reporting mechanism to be set up and protects whoever uses it. Today it is 50 U.S.C. 3373b.
Source ↗AARO opens the window
The office announces the channel for current and former government personnel with direct knowledge of UAP programs since 1945.
Source ↗The presidential push
The department's portal dates here the message in which the president announces he will order UAP files to be identified and released.
Source ↗First PURSUE batch
File deliveries begin at war.gov/UFO, which the portal itself describes as unresolved cases.
Source ↗The ODNI memorandum
“Preliminary Guidance for Implementation of NDA Waivers,” ES 2026-00818: thirty days to designate a liaison with PURSUE.
Source ↗The Department of War waiver
Lifts the civil and administrative clauses of NDAs and SAPIAs, strictly for speaking to PURSUE.
Source ↗Sixth batch
Four days after the waiver, the sixth delivery of files arrives.
Source ↗Fiscal year 2026 closes
The law required reporting to Congress on the confidentiality agreements once per fiscal year until fiscal year 2026. That deadline has passed.
Source ↗No seventh batch
As of today the portal still lists the sixth as the last.
Source ↗What the law has already given since December 2022
This is where the note falls short. On December 23, 2022, the 2023 defense act was signed, and its section 1673 is today section 3373b of title 50 of the U.S. Code. That section orders the Secretary of Defense to set up a secure mechanism so that anyone can report two things: an anomalous phenomenon episode, and any government or contractor program or activity related to them, including material recovery, analysis and reverse engineering.
And then it does something a press release cannot do. In substance, it says that an authorized disclosure is not subject to any nondisclosure agreement signed by the person making it, is deemed to comply with any regulation or order issued under Executive Order 13526 or chapter 18 of the Atomic Energy Act of 1954, and does not constitute a violation of section 798 of title 18 or of any other provision of law concerning the disclosure of information.
Read that third leg again. Section 798 of title 18 is criminal law: disclosure of cryptographic and communications intelligence information. The Atomic Energy Act also has criminal teeth. The 2022 law covers that. The September 14, 2026 note doesn’t mention it even remotely: it stays, literally, with the civil and the administrative.
The law also carries a clause the note lacks. It prohibits reprisals: no one with authority to take or recommend a personnel action may use it against someone who makes an authorized disclosure, including revoking or suspending security clearances or firing. Exactly the two fears the department’s note acknowledges exist, and which it resolves by no longer naming them.
The law’s shield is tied to the AARO window
One detail ties it all together, and it is in the definitions. The section defines an authorized disclosure as a report made through the authorized reporting mechanism established under subsection (a)(1), and in compliance with it. And it defines the Office as AARO.
That is: the law’s shield does not hang on anyone’s goodwill. It hangs on having used the AARO channel, which has been open since October 31, 2023 and admits current and former government personnel with direct knowledge of UAP-related programs since 1945. That is the window with a law behind it.
It is worth saying what is fact and what is my reading. Fact: the two texts say what I have just cited, and anyone can check it at the link. My reading: a waiver that stays within the civil and administrative gives less coverage than a section of the Code that declares there is no criminal violation. It is a reading rather than a whimsical opinion, and I sign it as such.
There is one question the public material cannot answer, and it is precisely the one that matters to anyone with something to tell: whether a statement made to PURSUE counts as an authorized disclosure under the law. PURSUE does not appear in section 3373b, which dates from 2022 and names AARO.
The ODNI memorandum treats the two as equivalent routes. But a memorandum does not amend a law, and neither the department’s note nor the portal explains how the two doors fit together. Whoever tells me the answer is clear, let them show me the paragraph.
- No criminal law, not even section 798 of title 18.
- The Atomic Energy Act, which the 2022 law does cover.
- The 2022 law itself, neither its number nor AARO.
- Congress and its committees, the other classic legitimate recipient.
- The press, the route through which this has always become known.
- Reprisal, security clearance and dismissal as prohibited consequences.
- How to locate an official PURSUE representative.
- Who signs the waiver and under what document number.
What the note doesn’t say, checked line by line
I did not deduce that list: I counted it against the full text of the note, which is five paragraphs and fewer than three hundred words. I say so because here at Broken UFO a claim from absence has to be dated and checked, and it has gone wrong for us before. Here the absence is that of September 14, 2026, in the text as it was published and archived.
The biggest is the criminal one. Nobody who has signed an indoctrination agreement for a special access program fears a civil suit above all: they fear for their clearance and they fear the courtroom. The department has lifted the first and stayed silent on the second, and there is no promise in the note that prosecutors will not act. It may not need saying because the law already covers it. It may also need saying for exactly that reason.
The second is infrastructure. If tomorrow a former contractor decides he wants to tell what he saw, the path this paper offers him is to speak to an official PURSUE representative, and the program’s portal does not say who that is, or where, or with what form. It does say, on the other hand, “Visit AARO.mil,” which is the channel Congress built. The papers push toward the law’s window, and the headline pushes toward the new window.
The third is the phrase I have been staring at for three weeks without fully understanding it: the covered agreements are those “previously executed within the United States.” I don’t know what that leaves out. An agreement signed on a base abroad, for example, could end up on the other side of that comma. It may be pure department-lawyer formula. I am not going to pretend I know.
And the fourth is not from the note but from the law, and it seems to me the ugliest of all. Section 3373b requires the search for and delivery of the confidentiality agreements themselves signed on this subject, and reporting to Congress once per fiscal year through fiscal year 2026.
Fiscal year 2026 closed on September 30. Five days ago. If nobody extends it, the periodic obligation to tell Congress how many mouths were shut and with what paper has just lapsed, and it does so in the same month in which the department boasts of transparency. If any of those sessions took place, it is not public: they are reports to committees, so I cannot say whether all four were made.
What it could be, with no need for a stage-prop conspiracy
Before anyone builds a theory on this, the boring explanations, which are the ones that almost always win. I find the three compatible with each other, and none requires anyone hiding a saucer.
Belt and suspenders
The simplest hypothesis is that the department is repeating with its own signature what the law already said, giving nothing new, because a frightened official is reassured by a paper from his own house, not by a citation from the Code. In that case the waiver is redundant on purpose and its short reach means nothing, because the long shield is still in the law. It is a good explanation, and it has a hole: if it were that, mentioning the law would have cost one line.
PURSUE is not AARO, and it needed its own cover
The second is almost administrative. The 2022 shield is tied to the AARO channel by definition, and PURSUE is a later setup that lives elsewhere on the organization chart. If you want people to talk to the new team and not the old office, you have to manufacture a permit of its own for the new team, and the only thing a department can lift on its own is its own contracts: the civil and the administrative. This explanation fits the text word for word.
A gesture with a calendar
The third looks at the dates. The waiver arrives on Monday the 14th and the sixth batch of files on Friday the 18th, four days later. I don’t know whether one was prepared for the other and I am not going to say it was, but the effect is what it is: a week with two transparency headlines, and then a three-week silence in which the seventh batch has not arrived. As of October 5, the portal still lists the sixth as the last.
Why this matters more than a batch of files
Because the bottleneck in this affair is the living people who signed something, not the old documents. The files published at war.gov are, by the portal’s own definition, unresolved cases, material the government cannot explain. What could change the state of the question is someone with a name telling where it came from, under a protection that holds up in court, rather than one more 1998 infrared video.
And we have been circling that for a while. The 2023 law that was going to set up a full declassification system ended up toothless, and we told it in the UAP Disclosure Act case file. AARO’s annual report, the other leg of the apparatus, we read from top to bottom in this critical reading, and what shows most is what falls outside its definition of a case. It is a design problem rather than one of will.
The track record doesn’t help swallow the headlines whole either. The man who left the Pentagon saying there was a program and a prepublication review has his own case file in Luis Elizondo’s departure. The one who reached Congress in 2023 and has just returned to a podcast with thicker stories and the same gaps is in what’s new on Grusch and in his profile. Neither needed permission to talk: they needed a document, and we are still there.
If this seems exotic to you, look at what we did here. The Ejército del Aire (Spanish Air Force) declassified its files between 1992 and 1999, a general signed them with his full name and today they can be requested and read, with their crossings-out and their pencil sketches. We told it in the Spanish Air Force declassification and in the 1992 to 1999 process. It was neither perfect nor quick. But nobody had to set up a new acronym every two months.
What we would need to see for this to count
My bet, and it is a bet: this will be judged by one thing only, whether someone testifies by name to PURSUE, appears in the official bulletin of the matter and nothing happens to them, rather than by the number of files published. Until then, what we have is a five-paragraph note that lifts the cheapest part of a contract and leaves the expensive part where it was.
The black of the marker covers. This is something else: here nothing has been covered, a door has been put in and painted to look like glass. I want to know who is on the other side, and as of October 5, 2026 the portal doesn’t tell me.
OSINT – Source traceability
Quotations from the document are taken from the archived copy because war.gov returns 403 to an automated client, a robot block common on .gov sites. The claims from absence (criminal law, the press, Congress and reprisal are not mentioned) were checked against the full text of the note, not a summary. The comparative reading between the waiver and the law is marked in the body as the author's own interpretation. The ODNI memorandum is not cited as a primary document.