Transcript - Special Access Required - the Secrecy of UFO Crash Retrieval Programs [VOL.2]

the cognizance of who was kind of leading the program changed over time epochs and the genesis was was in the Truman and Eisenhower National Security Council and and the CIA office of policy strategy but you know the atomic energy commission was involved department of defense at the time with how they hide this program based on time epochs and who they trust career civil servants career senior executives in industry they rotate it and it's there's no they randomize the schema too it's not like this one guy and this one DoD office always gets it. They spread it across and it's this like rule by committee flat hierarchy. What we've seen in previous administrations like Clint people the program thought Clinton was going to disclose in the '90s. Well, there was a burn bag and shred party um at a particular agency in the mid '90s I'm aware of. You have to remember so here's one of the loopholes they use, right? So there's there's white house special access programs. Uh there was something called covert action programs 50 US code 3093 those are the programs reported the gang of eight gang of four you know that's like assassination stuff etc you know other things the government doesn't acknowledge >> but there's a you know a a way to develop a white house sap that is non-covert action you know white house special access program if you look in the law there are no reporting carveouts uh that was one of the tricks of the trade burying it over in the department of energy but also keeping it in these non-covert action programs that like you know five people on the NYSE know about and the president at one time and then you know it has custodianship over across the battoic and MLAN. The singular purpose of my channel is to uncover the UFO legacy program architecture. special access, unagnowledged special access, controlled access, and non-covert action white house programs that are housed within elements of the United music States executive branch, armed forces, intelligence community, national laboratories, and defense industrial-based infrastructure that is tasked with the retrieval, collection, storage, music exploitation, and derivation of nonhuman technical vehicles and technologies of unknown origin. This once mighty and stalwarts national effort that I call the Manhattan Project 2.0 No. Spearheaded by the US's greatest music presidents, military leaders, senior statesmen and seasoned politicians under the opice of the National Security Council devolved and degraded during the cold war, breaking off pieces of itself and siloing itself music into cover offices and programs to morph and adapt to special access program oversight reforms and expansions during the 1970s and 1980s, ultimately relegating program control to a quasi government and industry control group of just over two dozen in 1994 in order to flee from the disclosure disposition of President Bill Clinton. Further disfiguring was done to this once mighty effort music when in the early days of the global war on terror 2005 to be specific. Certain defense contractors like Northrup Grumman harnessed company funded independent music research and development funds IRAD to ostensibly conduct their own breakaway UFO retrieval and exploitation activities. as well as 2009 when the last quote unquote mob boss who reigned control of the entire legacy program portfolio across the scattered silos and grains of rice in a rice bowl. Dick Cheney left office as VP. Indeed, the immense UFO crash retrieval and reverse engineering activities of Truman, Eisenhower, Nixon, Reagan, etc. are unrecognizable to the fractured ecosystem of today. a long past its prime portfolio of siloed program thiefs subject to severe redundancies and brain drain. Seriously at risk of losing a subrosa cold war with our peer adversaries to harness control over these quote unquote otherworldly technologies. to visualize such a tangled music and scattered web of programs that have seen nearly 80 years of morphing music and mangling. I visualize the modern-day UFO legacy program structure as a pyramid. Where further down the pyramid one travels sees far less access to program institutional knowledge and exponentially decreasing ability to peer across music program silos. To keep a hyper complex story short that I discuss in music the introduction of nearly every single one of my videos, this pyramid was once governed by a now amorphous centralized control group, Truman, Eisenhower, the National Security Council, and its 5412 committee special group music and that special group's MAG 12 or Majestic 12 ultimately degrading into the quasi industry and government control group of today that features a flat hierarchy where nobody after Dick Cheney operates full control and oversight of all siloed program directives. Below the control group sits program administration, best thought of by me as silo music containers housing specific programs and directives under specific elements of the armed music forces and intelligence community. Below the administrators sits music federally funded research and development centers, FFRDC's and GOK, government-owned contractor operated institutions. FFRDC's and GOKO structures allow the US government to attract the brightest of industry and subject matter experts music while still retaining strict control over programs, materials, breakthroughs, etc. music At the bottom layer of the pyramid sits the most security vulnerable aspect music of the legacy structure. Defense industrial-based prime contractors and their subcontractors. Only specific personnel within these companies are read into the legacy effort at a functional level including executive level positions, seuite executives or special program directors. The mortar that binds this structure together. Well, of course, this is the US defense industrial base whose authoritative channels are often music bypassed to allow UFO legacy programs to harness any US military and intelligence asset music that may be needed to accomplish these covert mission directives. But one aspect of this pyramid has not degraded and broken itself over time. Instead, this core element to the legacy pyramid has in a way increased music exponentially alongside the morphing of the legacy program structure. Indeed, I am speaking about the equivalent to the limestone casing that once encapsulated the great pyramids of Giza music to protect the structures from the elements. The UFO legacy program security apparatus. The security architecture of UFO crash retrieval and reverse engineering programs is so incredibly robust. Not only have I had to break this topic into music two separate parts to cover the changing security blanket obuscating UFO covert activities from 1947 to present. But I have also had to convey such a security apparatus analogous to an onion where akin to an onion center surrounded by many layers. The core secrets and extent presence of the UFO crash retrieval and exploitation portfolio is always hidden and obscured by another layer of protection and secrecy. So today I warmly welcome you to join me for part two of our investigation into UFO legacy program secrecy. After all, one of the most appropriate and poignant questions asked about the existence of UFO legacy programs is how can such technology, biologics, crash retrievalss, and programs be kept music secret and kept secret for 80 years at that. >> Here's the thing. >> Uh-huh. >> For those of you who still think that, you know, we've got little green men uh underground somewhere. >> Yeah. One of the things you learn as president, >> yes, >> is government is terrible at keeping secrets. This idea of conspiracy theories. If if there were aliens or alien spaceships or anything under the control of the United States government that we knew about, seen photographs, what have you. I promise you, some guy guarding the installation music would have taken a selfie with one of the aliens and sent it to his girlfriend to impress him. It it would leave. Today's project music seeks to pick up right where we left off, correcting the record on similar obscene comments like that from Obama. We will be leaving the epoch of 1947 to music 1994 where we explored the Manhattan Project 2.0's knows security apparatus music ripped straight from the Manhattan project investigated key individuals instrumental to establishing covert UFO recovery and study infrastructure distilled how statutory secrets derived from the 1954 Atomic Energy Act not only evade presidential declassification but also serve as the perfect vessels to hide UFO activities with an iron grip. identified the National Security Council as the top secret early legacy control group, narrowed in on the great schism that led to the Manhattan Project 2.0 taking drastic security measures during music the 1980s to maintain secrecy, leading directly to the fractured program ecosystem of today and so much more. As we depart the Manhattan Project 2.0 No. And quite frankly, it's music depressing devolution behind. We move on into the modern era to shift our lens on how UFO legacy activities today maintain secrecy. We will reorient our lens to study layers of the UFO legacy onion. Critical individual layers and concepts paramount to obiscating the core of the 21st century legacy apparatus. After all, here a cadre of covert, compartmented, and beyond top secret programs facilitating knowledge and need to know access to the greatest secret music in the history of mankind. The presence and procurement of non-human technology and their biological operators music existing as a hidden shadow symbiotically attached to the United States government armed forces intelligence community would require an ever evolving impenetrable and stalwart architecture to stay hidden from even presidents and other elected quote unquote temporary employees music would it not? So, let's peel back some layers of embedded secrecy where layers protect layers that obscure core secrets. From conceptualizing special access programs or SAPs to uncovering some of the loopholes for managed need to- know compartmented programs legacy operations have used with quote unquote non-covert white house programs to program protection agencies deputized to enforce insider music and outsider threat protection to maintain total program secrecy to the antibodies David Grush awoke when investigating the topic in a legal and empowered music manner to the disgraced Shan Kirkpatre and his ineffective all-domain anomaly resolution office arrow to the ATIP program protection management campaign and attempts music to talk about the subject outside of the proverbial onion to the myriad and I mean myriad criminal actions taken that aid the all-encompassing subject of quote unquote unrivaled secrecy. This project will not hold back and aims music to conduct a hyperspecific investigation into the modern-day legacy onion. So, as I said in part one, sit back, mark your notes, special access required, and let us deep dive into the secrecy and security mechanisms that embolden UFO legacy programs to operate in the shadows with unrivaled secrecy, power, and reach. Before jumping off into our investigation today, let us quickly define our onion analogy. recap part one of our investigation and lay out today's discussion points in an executive summary format. Part one focused predominantly on the rise of the Manhattan Project 2.0 security infrastructure and fall from grace during the Cold War into the fragmented and siloed program infrastructure of today. Within the Manhattan Project 2.0 no volume. We listened closely to the sage words of David Grush who directly stated the Manhattan Project secrecy apparatus was translated directly on to early UFO retrieval and exploitation efforts. >> First of it, obviously, it's understanding the situation, right? What do we have our hands on? And and like I've said in some other videos and stuff, you know, they took the Manhattan Project secrecy and overlaid it on this issue because that secrecy worked well for atomic bomb developments and whatnot. And and certainly this whole program in a nutshell, if I were to like summarize the 90 plus years of history, it is a reverse engineering program to garner some kind of insight. Indeed, we then explored five critical concepts of secrecy translated from the Manhattan Project directly onto the Manhattan Project 2.0. Compartmentalization, organizational architecture, physical security, classification, and information control, and finally, political shield/co. To summarize an hour plus section in just a few sentences, let's quickly recap and break down each of these points. Compartmenting or compartmentalizing programs or information operates as a defensive security mechanism, reducing attack vectors for espionage, leaks, and intrusions. The practice of compartmentalization sees program personnel granted access only to the specific information they need to perform their duties, even if they hold the necessary clearance level. The Manhattan music project served as a period of tremendous innovation of compartmented programs leading to the modern-day basis for special access programs. We also discussed organizational architecture being weaponized and leveraged for secrecy. The Manhattan Project was conducted out of the Manhattan Engineer District, MEED, which served as the legal and administrative entity through which the Manhattan Project operated. The MEED was chosen to be inconspicuous and essentially a container within the US music Army Corps of Engineers to house the top secret atomic project. We compared this secrecy practice with the early days of the quote unquote hidden wing, an Air Force series of UFO test and evaluation programs I've published extensively on that are housed as music a shadow hidden in plain sight within the Department of the Air Force. Moving on to physical security saw translation of the Manhattan project's most secret and heavily guarded sites. Los Alamos Oakidge and soon to be Los Alamos Z division at Sandia base aka Sandia National Lab onto the Manhattan Project 2.0. Indeed, within that section, we discussed alleged classified executive orders music signed by Truman in 1948, which relegated custody of recovered discs to Atomic Energy Commission National Laboratories music to be studied by the prestigious Dr. Vanavar Bush. And here we arrive to our final two Manhattan Project security blankets that are crucial to conceptualize as we move on to part two today. Classification and information control saw discussion of self-imposed and mandatory self-classification protocols for atomic scientists as well as a deep investigation into the 1946 and 1954 atomic energy acts. One of the most critical discussions of the entirety of part one was highlighting the introduction of two separate tracks of classification within the United States upon establishment of the Atomic Energy Commission. Track one of course being the standard executive order-based system. Think of the standard confidential, secret, and top secret levels of classification. Track two being the statutory atomic energy commission DOE and NNSA system whose authority is derived from the 1954 atomic energy agreements. The second track of US classification here sees equivalents to secret and top secret classifications with L and Q clearance respectively, but also restricted data, formally restricted data, special nuclear materials, all information quote unquote born classified. Such a second system is not subject to executive order and will likely prove to be a real can of worms for any president to music take full steps to disclose. Thanks to the Sage Council and discussion of Grush, we know both systems of classification are used by legacy programs to maintain secrecy. They're basically treating this as nuclear secrets because it gives off, you know, nuclear radiation. Because if you look at the ultra vague definition of special nuclear material, which is section 51 of the Atomic Energy Act of 1954, it says anything that gives off a sizable amount of atomic energy. Literally, that's what it says. Well, what's sizable? And what legal gymnastics are you saying this stuff which is obviously not a well who knows maybe it is a nuclear weapon and you're saying this is a US nuclear secret you're transclassifying it into a nuclear secret. Finally here we have the political shield/cover which existed as the quote unquote top policy group at the apex of the Manhattan project. The top policy group was the narrow and strict chain of command to which General Leslie Groves reported consisting of a handful of powerful figures like FDR/Trumman, Army Chief of Staff General George C. Marshall and Secretary of War Henry Stimson, and of course, don't forget head of the OSRD or Office of Scientific Research and Development music Vanavar Bush and his assistant. And the purpose of this group, well, this was to keep readin personnel and the existing control group small, minimize a paper trail, and maintain presidential control. Funny enough, here Truman wasn't briefed on the Manhattan Project as a senator or even vice president. Only when he was sworn in as president after FDR's death was he actually read in. Indeed, we discussed how Truman relegated control over the UFO portfolio to the National Security Council after the establishment of the 1947 National Security Act, but of significantly greater consequence. We discussed how in 1954 and 1955, President Eisenhower created the NSC 5412 committee special group and designated such a body focused on covert action as the Manhattan Project 2.0's knows control group. This is the Majestic 12, appropriately called at this time Match 12. Ultimately, within part one, we discussed the Cold War and the concept of changing tides, where the Wild Wild West days of the Legacy program ran from the 1950s up until the early 1980s. This epoch saw several executive orders expand and contract oversight over special access program precursors, aka black music projects. Indeed, Nixon's executive order 11652 saw tremendous concern over ad hoc security protocols, including top secret code word access. music We concluded the great schism that ended the Manhattan Project 2.0 know music was actually Ronald Reagan's 1982 executive order 12356 which ended the Wild Wild West days of legacy activities by effectively concluding top secret code word read on access and other ad hoc security protocols as well as the 1983 revelation of yellowfruit an army sod or special operations division unagnowledged special access program USAP this USAP a term we will use often today was discovered through a series of normal audits and revealed a shady world of data masking, cover offices, stage retirements, funding schemes, illegal covert activities, and so on. Yellow Fruit partially led to the uncovering of the Iran Contras and directly led to massive SAP reforms. Such reforms forced legacy activities to sever off their own limbs to hide and silo themselves within cover offices and programs. As a finishing bow on part one, we discussed how legacy operations, fearful of Clinton's disclosure appetite, permanently vested the UFO legacy program control group in 1994 into a quasi industry and government control group of just over two dozen. And again, it appears Dave Grush agrees with this statement. >> What we've seen in previous administrations, like Clint people, the program thought Clinton was going to disclose in the '90s. Well, there was a burn bag and shred party um at a particular agency in the mid '90s I'm aware of. >> The Manhattan Project formed our proverbial onion. However, unlike the great schism of the Manhattan Project 2.0, No. Which led to tremendous fracturing and weakening of the overall national effort to retrieve and exploit non-human technical vehicles. Every single special access reform period, whether it be expansion or retraction of oversight, every time legacy was forced to silo one of its limbs within a cover office like the music SAF AA, even when the legacy program vested control into a quasi government and industry control group. This all saw amplification, strengthening, and new layers added to the onion. The Manhattan Project secrecy apparatus itself can also be represented by a proverbial onion. Sure, if you were a low-level physicist, you were subject to Vanavar Bush's system music of self-censorship, Grove's compartmentalization, need to know access, the Manhattan Engineered District, music the top policy group, numerous layers that kept ordinary people on the project always a step away from the core of the atomic project. Now, recontextualized that atomic project onion model for the Manhattan Project 2.0 You know, in the ' 50s with the addition of restricted data in special nuclear materials under the 1954 Atomic Energy Act, custody of non-human materials being delegated via classified presidential executive order, a special group focused on covert activities being established within the National Security music Council, top secret code word program access similar to NRO by man, and a litany of security protocols, even more strict and expansive than the atomic project. overlaying this project portfolio. Now, imagine that same music security system in the 1980s, but with a fractured centralized leadership group to direct and establish security baselines for this once mighty national effort, where program elements were forced to burrow music even deeper into the shadows to hide from Pentagon audits. and throw in the Air Force and NRO program involvement being broken off and hidden within the Air Force SAF AA and understand music that naval involvement is hidden within programs, hidden within other programs themselves, hidden within even further programs like the Polaris program and Sand Dollar. Observe instances of projects within the armed forces and intelligence community being siloed into their own containers with a flat hierarchy. This leaves you with an onion model that quite literally doubles, triples, or even exponentially grows in size. Add to that concentrated efforts in the early 2010s music by specific FFRDC's and elements of the US government to quite literally restrict program history briefings on legacy incumbents to purposefully keep new program personnel ignorant to the scope and history of the legacy program portfolio and their specific siloed project. And no, I'm not joking there. Thus today we are left with an onion model of secrecy that is so vast, convoluted and severe. I am willing to wager any amount of money the following statement is true as I say this with the utmost confidence. Today only 40 to 50 people alive at any given time know the full breadth and history of the programs. Former chief scientist of the Navy Special Programs Office, Dr. John Pñena Craraven said it best when speaking about the sand dollar compartmented program. a program I highly wager was involved in undersea UFO recoveries with his quote unquote seventh fail analogy where even highly cleared individuals within top secret unagnowledged classified projects could never truly know if they'd reached the innermost layer of compartmentation or were in fact just working on a cover program in service of another cover program going on for an unknown length of time. So, as we investigate today, we cannot reconstruct the onion, but we can identify several of the layers that majorly factor into the modern-day security structure behind the mess music that is the UFO legacy program portfolio. These include possibly one of the most robust music and imperative outerish layers of the onion. The very vessels under which UFO legacy activities operate, receive funding and appropriations, maintain a baseline level of security, classification and need to know access and a vessel legacy activities often mold and stretch to suit the needs of these covert operations. I am talking of course of music special access programs SAPS out of the DoD and DOE and their intelligence community equivalents controlled access programs or CAPS as the very structure of SAPS which we will focus on significantly more than CAPS is so fundamental to understanding UFO legacy programs. We will spend an exorbitant music amount of time studying the ultra strict definitions, history, authority, limitations, etc. of SAPs and explain why exactly covert UFO activities have been for years hidden within special access programs and their precursor black programs under the authorities of Executive Order 10502, Executive Order 11652, and Executive Order 12356. music As we outlined in part one, most critical to understand about SAPS actually goes far beyond the standard definition and application of SAPs where SAPs are quotes established to control access, distribution, and provide protection for sensitive classified information beyond that normally required end quote. Indeed, for us, it is crucial to understand the three types of SAPs: acquisition, intelligence, and operations music and support programs. how such SAPs report to relevant OSD or office of the secretary of defense offices that are culpable in legacy operations including USD INS or intelligence and security, USD R&D music ANS or acquisition and sustainment. give examples of how each type of SAP can be implicated in UFO legacy activities as well as really digest the consequence behind the categories of SAPs acknowledged, unagnowledged, and waved. It is in fact the ability to wave unagnowledged SAPs with additional security protocols legacy programs have enjoyed to hide from traditional oversight channels. Of course, guys, it's me, so we will go much deeper here. We will not stop at a standard SAP analysis and thorough investigation of the skeleton of the gatekeeping and governance structure of SAPs, including the SAP and SAPCO. And if you don't know those definitions yet, don't worry cuz we will get to them. But also introduce the subject of quote unquote contentonly SAPs. Contentonly SAPs are quite the ingenious loophole legacy programs, specifically the White House and National Securityrun UFO crash retrieval activities have employed. As we will discuss, contentonly SAPs are not a type of SAP but a descriptive funding/administrative designation. Whereas a SAP holds or protects classified information aka content without dedicated music program specific funding lines, major resource allocation or separate budgetary authority. Such a system has been enjoyed to completely wave reporting requirements as indeed the SAP contains just music information. I strongly recommend if you take one thing away from this project, it is the topic of contentonly SAPs and what we summarize next. In addition to contentonly saps, we will distill what David Grush stated on his incredible judicial watch interview. The topic of covert action programs born out of 50 US code 3093. As David Grush stated, all lies on the White House here and specific importance on the National Security Council. And I love how when David Grush spoke on this topic, he mentioned alongside Eisenhower and Truman being the genesis for legacy activities, specifically five people in the National Security Council were involved at one time in the programs. Of course, part one focused heavily on Eisenhower's NSE 5412 committee special group, which was founded specifically to address covert actions. >> music >> Indeed, as I stated, Eisenhower relegated the NSE 5412 committee special group as the UFO Legacy Program administrator. And guess how many people were in the 5412 committee? That's right, five. So, music thanks again, David Grush. Uh, that was one of the tricks of the trade, burying it over in the Department of Energy, but also keeping it in these non-covert action programs that like, you know, five people in the NYSE know about and the president at one time. and then you know it has custodianship over across the battoomeic and MLAN. >> Anyways, as we will discuss the White House and NSC have taken covert action programs, designated them as non-COVIt action programs by utilizing contentonly SAPs and compartments, completely waving reporting requirements, and use such vessels for legacy activities. So again, I can't stress this enough. If you recall just two things from this video, non-covert action programs and contentonly SAPs are what I ask you to recall. Ingenious loopholes that have been historically utilized by the National Security Council's UFO Legacy Program portfolio. Let us also of course address some of the more nefarious and disturbing inner layers of the onion. Program protection offices. US agencies and services who see specific personnel and elements deputized to enforce UFO legacy activity security protocols. Akin to the antibodies David Grusher when he heroically pursued the UFO issue. These offices are inherently tasked with safeguarding some of the United States most intimate national security secrets, operate deep within unagnowledged SAP channels, and often feature career spooks with, let's just say, interesting careers in and out of government service, effectively making a perfect gatekeeping structure to mitigate program exposure and neutralize outsider and insider threats. One of the most prolific examples here, which we will actually not spend too much time on, as I covered this office and individual extensively in my Air Force project, is the AFOSIP PJ or Air Force Office of Special Investigations, Office of Special Projects. PJ is OSI's office tasked with safeguarding the Air Force's most sensitive music and national security imperative top secret research, development, and acquisition programs. And I am aware of specific instances in which former PJ executive director and former director of the entire Air Force SAP security enterprise and now vice president for security at Northrup Grumman, Terry Phillips and current PJ executive director and director of the entire Air Force SAP security enterprise, Mr. Lee M. Russ have acted as attack dogs music for the UFO legacy architecture. I would go so far as to say Terry and Lee are quite integral figures to legacy operations. Indeed, today we will mainly focus on three such program protection offices deputized to operate as legacy program Gestapo. The Defense Advanced Research Projects Agency's Security and Intelligence Directorate or DARPA SID, Air Force Life Cycle Management C Center's Information Protection Directorate or AFL CMC IP and the Department of Energy's Office of Intelligence and Counter Intelligence or OICI. On the subject of DARPA, I am going to introduce a legacy program senior who operates a very senior role within the program currently as principal deputy assistant secretary of defense for critical technologies out of the office of the under secretary of defense for research and engineering USD RNE, former director of research at the NGA, former director of IRPA or the intelligence advanced research projects agency and former deputy director and director of DARPA. Dr. Peter Heinum. People want names and here is a name of an individual at the highest echelons of UFO Legacy Program Science and Technology currently. We will investigate each of these offices missions, their cognizant authority, intriguing personnel, and outline my argument why these three offices in particular plus AFOSIPJ are some of the most critical legacy program protection features. I would also be remiss to not speak a bit on the surface of the onion. Disinformation and narrative control. The UFO topic is rife with disinformation, information control, narrative campaigns, etc., and has been for decades. So, I would like to quickly revisit the stigma that was carefully manufactured to make this topic obscure and appear nonsensical. I would also like to revisit the legacy apparatus's most recent narrative management tool, Arrow. and speak more on former disgraced arrow director Shan Kirkpatrick and his many halftruths and lies. Most consequently to the topic of narrative control and information ops will be to touch on the ATIP cover program, Luis Alzando to the stars academy and the coordinated attempt to prop up Hillary Clinton as the disclosure president. >> What else you want to know? In summary, the ATIP cover program for all intents and purposes operated as a cover for several national security council activities under DNI and former USD INS Lieutenant General James Clapper as a way to talk about the Onion outside of the Onion. The frontman for this operation was indeed Lou Alzando, who has far more of an intimate history with quote unquote national programs, USD INS, and the National Security Council than he has ever led on. We will extend coverage of this bizarre partial disclosure campaign and touch on the fallacies and partial truths outlined by Alzando and others within the Age of Disclosure documentary that attempted a revisionist structure of the legacy programs plural likely to delegate who gets to catch the live hand grenade when disclosure finally comes. And lastly, we will touch on the topic of unrivaled secrecy. numerous small or sub layers the legacy apparatus harnesses and have harnessed to maintain total secrecy. We will discuss cover offices and programs, gatekeeping structures, administrative terrorism, the subject of wet works and prospective whistleblowers possibly permanently being silenced. the practice of hiding in plain sight, frankly, ingenious misappropriation of funds and funding schemes, information siloing through GO and FFRDC's, program siloing leading to egregious redundancies, and so much more. So, let's waste no more time and dive right in. And when you say that they're above congressional oversight, what do you mean? Uh >> complicated question. Uh so there's, you know, some I would call it abuse here. So congressional oversight of conventional spe special access programs. So I'll use title 10. So DoD as an example, right? So 10 US code section 119 discusses congressional oversight of saps discusses the the depth sect defaf's ability to wave congressional reporting. However, the gang of eight is at least supposed to be notified if a you know a waved or wave bigoted unagnowledged sap is created and that's public law. >> The 2023 revelations of David Grush strongly cemented the reality of the UFO legacy program modus operandi. the retrieval, storage, exploitation, and possibly a host of weirder activities such as communication being housed within national programs, specifically special access programs, or SAPs, as I have called and will call them from here on out. Indeed, in every single project of mine, you will hear me speak at nauseium about elements of legacy activities being housed within SAPS. So I think it necessary and quite frankly mandatory we finally step back and get ultra specific on why such covert UFO activities have been hidden within SAPS for decades. Identify how the structure of music SAPS is perfect for this need to know ecosystem and get real specific on loopholes harnessed to keep such activities free from traditional oversight channels. Sure, this section may be a little academic at first, but I absolutely implore you to pay close attention and keep notes because special access programs plus additional access protocols as well as some creative loopholes are the vehicles music through which UFO legacy programs operate, get funded, and stay hidden from congressional oversight and music those they consider quote unquote temporary employees. And if you're like me and want some physical materials to follow along, two documents I would strongly recommend keeping handy are DoD instruction 5205.11, management, administration, and Oversight of DoD Special Access Programs, as well as DoD instruction 5205.07, Special Access Program Security Manual. The term special access program was first acknowledged in the 1980s. And prior to the 80s, precursors to SAPs did indeed exist, but as what one might call black programs. This era of black programs consisted of the early days of the NRO, stealth aircraft programs out of the Loheed skunk works, etc. As we've discussed so far in part one and here in part two at length, national programs critical to national security, US classification standards and oversight of compartmented need to know programs have fluctuated greatly from the 1947 National Security Act until present. Specifically in part one, we referenced Eisenhower's Executive Order 10501, which removed the restricted classification designation and introduced the era of ad hoc security protocols on sensitive programs such as top secret code word access, really introducing the concept of quote unquote special access. In part one, we also referenced Nixon's 1972 Executive Order 11652, which saw the formal framework for special access programs established, resulting in widespread concern of uncontrolled and rampant growth of unauthorized applications of special access labels across DoD compartments. with a House Committee on Government Operations report discussing quote widespread use of dozens of special access distribution or control labels, music stamps or markings on both classified and unclassified documents end quote. These access controls were harnessed by quote many executive agencies having classification authority and dozens of other agencies who do not possess such authority end quote. Finally, we discussed Reagan's 1982 Executive Order 12356, which expanded the categories of classifiable information music and lowered the threshold for classification, essentially tightening the grip of government secrecy from Carter's previous administration's attempts of government secrecy shifting towards declassification and transparency. However, as we discussed in part one, EO2356 essentially ended the wild wild west days of the golden age of legacy with the removal of top secret code word access. This plus the revelations of the yellow fruit USAP led to the great program schism we spoke on so much. But I digress here. Today, the framework of special access programs are primarily managed, authorized, and run out of the Department of Defense and governed by Executive Order 13526 titled quote classified national security information end quote. Because remember here the intelligence community has their own special programs caps controlled access programs and the atomic energy commission now the department of energy has their own special access programs governed by the 1954 atomic energy act but put a pin in that for later. Executive Order 13526 defines a SAP as a quote program established for a specific class of classified music information that imposes safeguarding and access requirements exceeding those normally required for information at the same classification level. End quote. SAPs are established when a program is required by statute. According to the Defense Counter Intelligence and Security Agency SAT training course, which we will be referencing quite often, quote, upon the finding of exceptional vulnerability of or threat to specific information, and if the normal criteria for determining access to information classified at the same levels are insufficient, end quote. The existence of special access programs are imperative to US national security for several reasons. Some SAPs protect technology breakthroughs and ensure the US maintains its leading technological edge. Some SAPs, according to the Defense Counter Intelligence and Security Agency, quote, ensure once we discover and exploit an adversar's vulnerabilities, the knowledge of the exploitation remains secure and the adversary does not develop a countermeasure. End quote. Some SAPs ensure sensitive operation plans are completed without disclosure and some SAPs protect sensitive intelligence information. I am willing to bet I do not need to explain why such a system is perfect for a portfolio of programs founded off exceptionally higher security than that of the atomic bomb project. tasked with top secret retrieval, exploitation, and storage of non-human technical vehicles mandated to be hidden from both US adversaries and any music USG element not deemed quote unquote need to know. And before we move any further, let's clear up just a few misconceptions about SAPS. SAPS are not a method to hide money spent on certain programs. SAPs are used to ensure the security and accountability music of a specific project is maintained to the highest level. Of course, as we have prior and will discuss further, legacy programs have used several loopholes to misappropriate illegal and inappropriate funding streams for their portfolio of UFO SAPs. Additionally, SAPs are not a classification designation like confidential, secret, and top secret. No, SAPs use the standard level of classification. So in simplest terms, a SAP is a classified and compartmented sensitive research, acquisition, intelligence, or operational activities program with enhanced safeguarding and access requirements. >> There's nothing that you're aware of that's music above special access program classification. It it's a misnomer that there's anything actually above top secret. Executive Order 13526 delineates the classification levels. If you are with me so far, just to contextualize here, some infamous examples of SAPs in the past include the F-17A Nighthawk, B21 Raider, RQ180, and Yellow Fruit we spoke on in part one. SAPs are inherently designed to compartment information and employ need to know access. Indeed, in part one, we discussed how the Manhattan Project inspired and influenced such controls. For one to access a music SAP, they must possess an appropriate need to know assessed and determined by a designated access approval authority. SAPs are so securely safeguarded that access to a SAP is limited to the minimum number of individuals essential for program success irrespective of rank, title or position. Shifting over for a moment to legacy activities here. I am aware of readins to a specific legacy activity SAP being kept so small and minimal. Program personnel were often given additional work tasks below their paygrade to avoid reading in additional personnel. An example there would include a senior scientist also performing account management or an industrial security professional also performing janitorial work. And just so we can be clear here, we discussed this at length in part one, but real fast, what exactly is and determines need to know? To quote again the DCSA SAP training course, need to know is defined as a quote fundamental principle in the protection of classified information and the protection of SAPs. It is not enough just to have the appropriate clearance and formal approval to access music a SAP. In addition, a person must have a need to know that pertains to these specific information. End quote. A SAP operates with an intriguing hierarchy, a system of further compartmentalization within the program to further isolate programs. Thus, SAPs are structured into hierarchical tiers called quote unquote umbrellas. Beneath a SAP umbrella sits several SAP compartments, and below music these compartments sit several SAP subcompartments. housing several operational projects. This framework is organized to group similar capabilities or information into a single subcompartment or compartment. Similar critical program information CPI here is grouped into a single SAP. We covered several such examples in part one, such as the Polaris submarine special program housing numerous hidden programs which in turn held the sand dollar covert program that I am highly confident was involved in undersea UFO retrieval operations. We additionally discussed the Army Special Operations Division's SAD's Yellowfruit USA which contained several classified operations as well as the Army CIA support for Latin American operations. This umbrella structure makes it shockingly easy to take an already classified program and further compartment and hide both projects and information within. Even the naming of special access programs are meant to compartment and hide information. SAPs commonly use an unclassified nickname comprised of two unrelated words that represent what's known as a program identifier or PID. Think here of yellowfruit or the 2010 Department of Homeland Security prospective special access program Kona blue which was meant to serve as a vehicle for Loheed Martin to pass UFO materials to the offset program as examples here. In addition to the two-word unclassified nickname representing the program identifier P, sometimes the special access program central office SAPCO might add an additional singular classified code word onto a program for enhanced compartmentation. So here's an example for a naming convention for a SAP. TS SAR hanger bully waved where TS means top secret classification. SAR means special access required. Hangar bully is the unclassified nickname representing the program identifier and waved is an additional control marking/ secondary layer of security we will expand on momentarily. Another example is the Kona blue marking on screen now with the additional control marker of no foreign short for not releasable to foreign nationals. Indeed, I am aware of specific UFO related SAPs in the early 2000s that extensively featured waved and no foreign controls. To make this even more complicated here, I'm aware of testimony from whistleblowers who have sworn statements before Congress that SAP's housing UFO legacy activities routinely rotate names, possibly even as frequently as monthly, for the purpose of more easily identifying security leaks. But before we get too ahead of our skis here, let's rewind and start to music break down the tangible functions and delineations of SAPS. SAPS are divided into three principal categories. Acquisition programs, intelligence programs, and operational programs involving active missions or activities. These three principal categories are further distinguished by three classification categories or protection levels. music Acknowledged, unagnowledged, and waved. Acquisition SAPs comprise the vast majority of Department of Defense special programs, constituting 75 to 80% of all SAPs. Acquisition programs focus on protecting sensitive RDT&E or research development test and evaluation, modification, and procurement efforts that if compromised would reveal critical asymmetric technological capabilities or vulnerabilities. Oversight for acquisition SAPs fall under the under secretary of defense for acquisition and sustainment, USDAs. USD ANS manages the SAP corporate portfolio to integrate music corporate work on carveout contracts within broader defense acquisition strategies. If you have watched a single one of my projects, you will immediately recall the consequences music of the USD ANS whose office has been previously known as the music oustat or USDA ATNL. The Wilson Davis notes. I said this in part one and I mean it again. I talk about these allegedly leaked notes so often I will not give a summary past one to two sentences. As always, I do question the credibility of the man who generated this document, Dr. Eric Davis. But I do believe the fundamental facts music of this document to be indeed true that in the late 1990s as deputy director of the DIA Defense Intelligence music Agency, Vice Admiral Thomas Wilson attempted to brute force a readen into the legacy program portfolio, but was ultimately stonewalled even with appropriate access credentials. Indeed, I additionally believe Wilson shared his misadventures with Davis. Within these notes, Admiral Wilson allegedly stated that in 1994, under sweeping SAP changes under then Deputy Secretary of Defense Bill Perry, the UFO Legacy Program portfolio was reorganized into a separate special records group, quote, a special subset of the unagnowledged carveouts waved programs not belonging to usual SAP divisions. End quote. The document then states the SAP or special access program oversight committee's newly established in 1994 music senior review group SRG served as a stalwart gatekeeping structure for legacy activities from even appropriately cleared agency directors. In short, the document is stating Bill Perry's 1994 actions to significantly strengthen and enhance DoD SAP management and control structures saw introduction of a Goliath gatekeeping structure within DoD's internal SAP channels specifically within SAPCO and SAPok SRG. And don't worry, we will spend time distilling these terms. And to my understanding, this is music absolutely true. I understand that in 1994 to hide from Clinton's disclosure appetite, legacy programs under Bill Perry's SAP management and control structure expansion saw both gatekeeping duties largely tasked to the Sappok SRG, but infinitely more important here. This also saw the legacy structure permanently vest top-down program control out of exclusively the USG shifting the control structure to a quasi government and industry music control group of a handful over two dozen individuals. We will of course talk about this much more, but let's rein it in here and get back to acquisition SAPS whose oversight authoritative body is the USDANS again the under secretary of defense for acquisition and sustainment. And for more context, I do highly recommend viewing my NRO project which talks much more about this music 1994 reorganization and Bill Perry. Well, within the Wilson Davis notes, the USDANS's former title, the oustat orat, under secretary of defense for acquisition and technology, is cited as one of the critical offices housing UFO legacy activity information post 1994 Bill music Perry SAP reorganization. Indeed, allegedly, it was Air Force General H. Marshall Ward, who served as former director of SAPCO or the special access program central office in the DoD, former executive secretary of the special access program oversight committee or SAP and former director of special programs within the modern-day term USDAs that outright told Admiral Wilson this special subset of the unagnowledged carveouts waved programs containing information on the legacy programs was housed within then aat music now USD. ANS. The important thing here is Wilson allegedly found this unusual records group within the UST, music now USD ANS, and read the index abstracts. The program record music contained zero budget info. Such information was kept in separate records for music audit purposes. And please, please remember this, the fact there was no budget info here is probably the most critical piece of the entire Wilson Davis notes and one of the most consequential pieces to this document that gives the document music authenticity to me. Please remember that in 1997, Wilson found the UFO legacy program portfolio record had zero budget info. The Ostat at the time of Wilson's conquest was one Mr. Paul Kaminsky, a man whom I have direct knowledge was indeed a very senior individual within the UFO legacy program portfolio. Kaminsky additionally served as a senior member of the SAP and more present day on the board of MITER. Indeed, I wager the modern-day USD ANS, who maintains oversight of music acquisition SAPs and according to Wilson's alleged disclosures, has in the past music housed records for the UFO legacy program portfolio is absolutely critical to covert UFO operations alongside the USD R& Secretary of Defense for Research and Engineering, which is the evolution of Vanavar Bush's Research and Development Board, RDB, as well as USD ins Under Secretary of Defense for Intelligence and Security, Lieutenant General James Clapper's previous role. Highlevel acquisition directors, offices, and functions have been highlighted again and again in my work as being imperative to the UFO Legacy Program structure. Indeed, I spent hours discussing SAF AQ or Air Force acquisition managed by the assistant secretary of the air force for acquisition technology and logistics and three components music within SAF AQ. SAF AQR science technology and engineering, SAF AQX acquisition integration, music and SAF AQL special programs as being a critical element to the Air Force's hidden wing program. The hidden wing centers on TN or test and evaluation of alien reproduction vehicles, derivative airframes, and the occasional music NHI craft. I've additionally spoken on the importance of NRO acquisitions in the context of covert UFO activities. NRO acquisitions are joint run by the DDNIATNF or deputy director of national intelligence for acquisition technology and facilities. And you guessed it, the USD ANS. music We've already talked plenty about USD ANS. But I am shocked at just how many agency spook music legacy gatekeepers have also served within the DDNI ATNF. These include Doug Wolf and Don Byer, both of whom also served as deputy director for the CIA's Directorate of music Science and Technology. Doug Wolf is a very bad man. Okay, let's finally music loop back to the three types of SAPs. Acquisition, intelligence, and operations and support SAPs. music Intelligence SAPs safeguard the execution and planning of sensitive intelligence and counter intelligence operations. Intelligence SAPs, as you can probably guess, are overseen by the USD INS, Intelligence music and Security. Again, former USD INS Lieutenant General James Clapper served as the closest thing to a Dick Cheney level UFO legacy program mob boss whilst he was DNI from 2010 to 2017 music where he previously served as USD INS from 2007 to 2010. I am going to say something rather controversial here which we will expand on later but with extreme confidence I will go out on a limb here and state that the ATIP the advanced aerospace threat Identification program a cover project for several national security council activities operated as a clapper given cover when he was USD INS onto DNI as a system to quote unquote talk about the onion outside of the onion The motives for Clapper pushing for partial transparency on UFOs are unknown, but I highly wager the fake at program was partially a cover for National Security Council intelligence SAPS. And who better to spearhead this job than Luis Alzando, who from 2013 to 2017 served as director for the national programs special management staff or NPMS. The USD INS NPMS or again National Program Special Management Staff Director runs coordination between National Security Council SAPS and the US Department of Defense/Intelligence community. The director of NPMS is one of the most critical jobs in the entirety of the United States that most people have never even heard of. The director of NPMS is usually the most cleared person in the entire DoD besides the secretary of defense themselves. Indeed, more cleared than the DoD special access program central office director. So when I say Lou tangoed music with the legacy architecture far more than he has ever led on, understand the extreme consequences and music importance of his former position as director of the national program's special management music staff. Now throughout this project, we've been talking a lot about elements and offices music within the Secretary of Defense. Just recall here that all three elements of the office of the secretary of defense I frequently accuse of being imperative to the UFO legacy program effort are also paramount to SAP structure. USD ANS which spearheads oversight for DoD acquisition SAPs. USD INS which spearheads oversight of intelligence saps and USD RNE the evolution of Vanavar Bush's research and development board RDB which according to DODDI5205.11 quotes music identifies and cultivates cuttingedge technology development technology transition developmental prototyping experimentation and developmental testing activities and programs requiring SAP protection to ensure continued US war fighter advantage. End quotes. I highlight this here to once again say the US government really isn't that smart. The infrastructure that has the cognizant authority, operational capacity, expressed mission, etc. to operate within UFO RDTini programs are more often than not the exact offices you'd expect, albeit in a shadow dual-headed capacity. Lastly here, operations and support SAPs or OSAPS quote protect the planning, execution, and logistical support of sensitive military operations, often involving tactical or strategic activities where operational details must remain obscured to preserve surprise or deny adversaries insight into US force capabilities." End quote. So, let's give an example on how all three SAP types would fit into a UFO legacy program activity. Let's say we are out on the Western Ranges, Edward's 412th test wing, specifically within the Air Force Test Center, AFTC, to operate on the hidden wing program. We have a triangular airframe whose electrogravidic propulsion system and cloaking capabilities were derived from a nonhuman technical vehicle that was recovered in the American Southwest. The development of such a craft likely down at Goko Air Force Plant 42 would be protected under an acquisition SAP. Once this triangle is operational and fielded for covert ISR missions, protection of these missions would be protected by an operations and support SAP. The sources and methods that justified the craft in the first place, recover non-human technology that was deemed to be exploitable would be protected by an intelligence sap. For our hidden wing electrovidic triangle, intelligence saps protect how the craft is built. OS apps protect how and where it's used and intelligence apps protect how we know what we know. Okay, now is where we must get ultra specific to speak on the protection levels of SAPs, acknowledged, unacknowledged, and waved. You will hear me often speak on wooaps or waved unacknowledged special access programs as the container for UFO legacy activities as these are the apex of secrecy for SAPs. Although all SAPs are closely guarded national programs, there are SAPs whose very existence is a core secret and thus more closely guarded with enhanced protection levels. An acknowledged SAP's existence can be openly recognized, although details of the program such as materials and techniques remain classified. The funding for such acknowledged SAPs is often unclassified. Acknowledged SAPs undergo full reporting to congressional defense and intelligence committees, essentially broad SAP music oversight while still retaining need to- know access for cleared program personnel. On the other hand, unacknowledged SAPs or USAPs are even more closely guarded secrets with the mere existence and purpose of the USAP being protected. Indeed, USP program funding is often classified, unacknowledged, hidden within the federal budget are not directly linked to the program. USPS are built to conceal program existence from all unauthorized individuals, including most US government officials and congressional committees. For USAPS, need to know access music far transcends traditional SAPs with cleared personnel often requiring additional indoctrination beyond topsecret clearance with sensitive compartmented information or TSSEI. Yellow Fruit, as we discussed in part one of this project, was indeed a USAP with a possible waved status. Recall how Army Chief of Staff John Wickham at the time claimed he was never briefed about the black operations run by the Army Special Operations Division SAD. According to the Joint Security Commission's 1994 report titled Redefining Security, unacknowledged SAPs run roughly 3 to 10 times the security costs of acknowledged SAPs. Indeed, the report states that estimated security costs for use music can be as high as 40% of total operational costs for unacknowledged programs. music This may initially seem at odds with what's presented in the Wilson Davis notes music where Wilson states that General Mike Costnik stated the security budget for music the legacy activities hidden within a special subset of unagnowledged carveout waved national programs was two to three times the actual program music budget. but in the past reached as high as six to seven times the program budget. But coming up soon, I'm music actually going to make a counterargument that we will expand on and state that this comment allegedly by costleneik makes perfect sense. Recall how the legacy program records within the oustat music now USDs, contained zero budget info. There is a very specific loophole that National Security Council spearheaded programs have enjoyed to wave budgetary and further reporting requirements in conjunction with myriad funding schemes including misappropriation music of funds, haircuts across multiple programs and self-fund. Put a pin in this budget topic once more. We will music return to this most crucial topic soon. A secrecy layer even deeper is the final protection level of SAPS waved. Waved unacknowledged programs are created under extremely limited circumstances. Waved programs have significantly more restrictive reporting requirements and access music controls. Literally waving or getting rid of SAP reporting requirements detailed in section 119 title 10 US code. WooPPS, as we call them, have far more strict carveout and reporting requirements than even USAPS. According to the war zone and DODI5205.05, the access approval authority for WOAPs consists solely of the deputy secretary of defense, special under secretaries of defense, or an amorphous component head with quote unquote cognizant authority. Waved programs here are still supposed to be reported to the Congressional Gang of Eight, which includes the majority and minority leaders of the House and Senate music and chairs and ranking members of the intelligence committees. But alas, we will discuss loopholes that waves even this reporting requirement as the gang of eight have clearly not been briefed on the legacy portfolio. And I met with Senator Harry Reid about nine months before he died. And of course, he's a private citizen now. And I wanted to brief him on the topic and I wanted to get his kind of thought leadership on it because, you know, he was a gang of eight member, right? You know, which is the top most cleared senators and congressmen. He was the majority leader for God's sakes of the Senate. And I knew, you know, he helped sponsor the OSAP program that I mentioned and where they looked at Skinwalker Ranch and some other things. And I wanted to understand like what does Harry Reid actually know? like why did he, you know, give $21 million to DIA and Bigalow Aerospace for this? So, I'm sitting there in Harry Reid's living room, you know, right next to him with some other witnesses that were there with me, and he straight up says, he's like, "Yeah, I knew we had UFO material. I was denied access for decades." And just like the no foreign are not releasable to foreign national control marker, a waved unagnowledged sap can also feature the informal control marker of bigoted. And I cannot think of anyone to explain this better than David Grush. So let's expand on what he said in the intro. One of the most serious saps you can ask for, what they call a bigoted, waved special access program. So waved means it's limited congressional reporting. Um that is a class of special access programs and bigoted means it's like by name. >> You have to remember so here's one of the loopholes they use, right? So there's there's white house special access programs. >> Uh there was something called covert access programs 50 US code 3093. Those are the programs reported the gang of eight, gang of four, you know, that's like assassination stuff, etc. You know, other things the government doesn't acknowledge. But there's a, you know, a a way to develop a White House SAP that is non-covert action, you know, White House special access program. If you look in the law, there are no reporting carveouts or requirements to tell like the speaker or the majority leader or anything like that. >> Okay, we have really started to dive into oversight and authority of SAPS. And like David Grush has stated, UFO Legacy Activity National Programs are structured in such a way to even avoid waved bigoted reporting. So before we discuss those loopholes I mentioned earlier, let's first briefly discuss the SAP oversight and governance structure in more detail. Because indeed, if elements of covert UFO programs operate within SAPS, which I will put any amount of money on that they do, surely special access programs must have an internal system of governance and gatekeeping to maintain total secrecy and make unauthorized access to the program portfolio impossible. Title 10 US Code 119 outlines reporting requirements for SAPS. And funny enough, such strict oversight actually arose from the yellow fruit fiasco in 1983, as we discussed in part one. But such discussion is trivial at best. Because, as we know, UFO legacy programs are not reported to congressional elements, bar a few Congress people here and there on the payroll of legacy programs. Mike Turner is likely one of these thug enforcers. Internal SAP governance is broken up into several clearly defined roles and layers to ensure the SAP enterprise runs smoothly, maintains appropriate access and enforces security protocols. The SAP governance structure is top down comprised of the SAP, SRG, and SAP co. And the SAP governance process relies upon personnel making the determination that the need for a SAP exists. The lowest rung of the totem pole here is component level special access program central offices or SAP music codes. Each branch of the armed forces, the joint chiefs of staff, DARPA and the missile defense agency possess a component level SAP code which is responsible for all SAPs under their purview. This here is a bit of a quandry. I am aware of individuals within component level SAP codes like William E. Mccclure of the Air Force's SAF AAZ or the director of security, special programs oversight and information protection who they and their offices operate key positions in legacy activity architecture. But I am also aware of instances in which component level SAP codes are bypassed by the legacy programs like when Edward C. Aldrich stuffed likely joint air force and NRO activities called quote unquote outside activities under SAF AA bypassing the AAZ I just mentioned. I believe the determination on if a component level SAP code is read into legacy activities depends completely on the director and their history in the programs. Above component level SAP codes sit OSD or office of the secretary of defense level SAP codes. We discussed this in relation to USD INS, USD ANS and USD R& earlier. Above OSD SAPCO sits DODD SAPCO whose director has often historically been the USD ANS. Former directors of DoD SAPCO that have almost certainly been legacy program personnel include General Dawn Dunlop and General H. Marshall Ward. DoD SAPCO serves as the primary staff support to something called the SAPPO. The SAP central office also serves as the primary point of contact with Congress, the National Security Council, and other government agencies/services. So yeah, I bet I know what you're thinking here. The SAPCO and SAP above it, which we will speak on momentarily here, are two of the critical gatekeeping fixtures within the SAP enterprise that get to decide who and what services access the legacy program portfolio. The DoD SAP code is supposed to complete PAR or program access requests and facilitate general access for Congress requiring access to a SAP. However, just as we discussed the amorphous access approval authority behind waved SAPs, the DoD SAP code makes a staunch exemption to this congressional music access for waved SAPs and waved subcomponents. But moving up the totem pole, let's now focus on the real meat and potatoes. The established in 1994 special access program oversight committee or SAPO chaired by the deputy secretary of defense like John M. Deutsch and Bill Perry. SAPOK has access to all DoD SAPS to provide DoDwide Departmental oversight and management and was built to quote ensure compliance with law, regulations, policies, and procedures and ensure required information is provided to the Congress end quote. SAPOK has oversight over all waved DoD SAPS to determine if there is a continued need for waved status. Sappok is supported by the SRG or senior review group which is really the apex of our totem pole here. To learn more about many individuals within Sappok and SRG like Mikelnik, Lynn Wells, Paul Kaminsky, etc. I do highly recommend referencing my NRO project. But I want to focus more on music the structure here. SRG again senior review group is comprised of a cadre of senior executive service level individuals to operate as the principal support to the SAP and ensure SAPs aren't duplicated across various SAP categories. H senior executive officials I wonder what kind of people Dave Grushed serve as gatekeepers for the legacy apparatus. >> So who gets to decide this in your opinion in the past? Uh it's a group of career uh senior executive officials. >> Okay. Are they government officials? >> Both in and out. >> Do what? >> Both in and out of government. And that's about as far as there. >> All right. Well, that's that leads to my next question. >> Within the Wilson Davis notes, the senior review group is labeled as the gatekeeping structure for the UFO portfolio with SRG members blocking Wilson from accessing the programs. quote, "I was to immediately drop the matter and let it go. Forget about it as I do not have purview over their project. It didn't fall within my oversight, etc." End quote. I vehemently agree with these statements allegedly made by Vice Admiral Thomas Wilson. Indeed, I am aware the Sappok SRG established in 1994 by then Deputy Secretary of Defense Bill Perry was tasked alongside its many oversight duties to gatekeep authoritative access to the legacy program portfolio. Short and narrow chains of command, as I always say. You see, as I understand, after the entire Manhattan Project 2.0 no schism that occurred in the 1980s with NSD-159, EO12356, and Yellow Fruit. As we spoke on in part one, the disclosure appetite of Clinton was the final straw for the ever crumbling legacy structure to permanently vest itself outside of fully contained executive branch oversight. So again, as I've stated so many times throughout this project because this is so critical to remember, as I understand, in 1994, legacy programs permanently transformed full oversight of the many legacy program silos to a quasi industry and government body of slightly over two dozen people. in the Sappok SRG was deputized music as the access approval authority to gatekeep even directors of intelligence agencies and general and flack officers who did not possess relevant need to know from accessing the programs. So just to be clear here SAP and its SRG are the skeleton gatekeeping structure and access approval authority for USG access into the legacy programs. Sappok SRG is not the boogeyman remnants of the match 12 or Majestic 12 entity that existed in Eisenhower's 5412 committee special group or Nixon's 303 committee. Nor is it the stalwart titan that protects inside access to an insidious and amorphous control group that exists as a pitiful shell of a once mighty music efforts. I additionally understand whilst SRG is tasked to ensure there is no duplication of SAPs across the entire DoD, these actions are not taken with legacy operations, the UFO portfolio is so fractured and siloed there is no way SRG can enforce program redundancies across the wider USG like similar exploitation efforts across the Army music and Navy. For example, the loopholes of saps enjoy to further obuscate legacy activities. This is both my favorite part of the entire video and in my opinion the most important. David Grush's recent Judicial Watch interview was absolutely brilliant. Like any Grush interview, if you really listen closely and is still what Grush is saying, there are veins of gold to mine. Let's listen in on Grush speaking about some of the tricks of the trade, so to speak. >> You have to remember, so here's one of the loopholes they use, right? So there's there's White House special access programs. Uh there was something called covert access programs, 50 US code 3093. Those are the programs reported, the gang of eight, gang of four, you know, that's like assassination stuff, etc., you know, other things the government doesn't acknowledge. But there's a, you know, a a way to develop a White House SAP that is non-covert action, music you know, White House special access program. If you look in the law, there are no reporting carveouts or requirements to tell like the speaker or the majority leader or anything like that. And so, uh, that was one of the tricks of the trade, burying it over in the Department of Energy, but also keeping it in these non-covert action programs that like, you know, five people in the NYSE know about. the president at one time and then music you know it has custodianship over across the battoic and MLAN. >> Wow guys, this is incredibly valuable. Basically what David Gush is saying here is that historically a loophole White House so National Security Council derived legacy operations have utilized was creating a White House controlled special access program specifically a non-covert action music program which completely removes any reporting and carveout requirements. Let's really break this down music and see how this can be done. As Grush stated, covert action programs music are defined by 50 US code 3093 and detailed programs or activities of the US government pertaining to assassination, clandestine operations, and covert activities of which the US government does not want to acknowledge their involvement. Covert action programs feature several similarities and differences to SAPs. Both systems harness compartmentalization and security controls beyond top secret. Both systems are music supposed to have congressional briefing channels and both operate with third-party and cover mechanisms. However, covert action programs and SAPS differ greatly on purpose and authority. Of course, covert action programs operate under 50 US code 3093 and SAPs operate under Executive Order 13526 music and 10 US code 119. As we stated, SAPs operate under three categories: music acquisition, intelligence, and operations and support. While covert action programs are almost always a specific category of activity authorized under title 50, although a covert action program will almost always be protected as a SAP or under SAP-like components. Perhaps it should really come as no shock, but I argued incessantly music in part one that Eisenhower relegated the UFO control group, literally once called the match 12 within the 5412 committee special group, music which operated from 1954 to 1964. This control group then translated onto Nixon's 303 committee from 1964 to 1970, then 1970 onward, a bit of an unknown until about 1994. But yes, I am literally stating the match 12 existed within the National Security Council's 5412 committee special group. So perhaps it should come as no surprise covert action approval was housed within the National Security Council subcommittee on covert action. the 5412 special group 303 committee and further iterations because at this time up until the mid1 1970s covert action approval was an entirely executive branch process governed by NSC activities. So, covert action programs are still supposed to be reported to Congress, at least the gang of eight or gang of four. But David Grush states these programs can be made non-covert, essentially becoming a White House controlled special music access program with no reporting requirements. And before we unpack this, I get it. Why so much discussion of the White House, National Security Council, etc. Aren't programs held from presidents and administrations? Yes, they are music indeed. But the framework and very skeleton for the legacy architecture, as we music discussed in part one, was formed by Truman and more consequentially Eisenhower. Indeed, through a series of classified presidential executive orders, Truman and Eisenhower vested legacy program management within the National Security Council with support from major elements of the US intelligence community and music armed forces, premier scientific institutions like Vanavar Bush's research and development board RDB and Atomic Energy Commission National Laboratories. over the epochs climaxing and ending in 1994 music when the programs completely wrestled the control group out of the US government into a quasi government and industry control group. The legacy program portfolio was primarily always a white house specifically national security council run activity. So power for the legacy programs has almost always been vested in the White House and at one time under presidential control and that is one of the most major concerns with the legacy programs. Sure, these activities conduct white and blue collar crimes extensively. music But perhaps the very existence of these programs are not illegal but protected by ironclad statutes. Anyways, rant here. Over. How are covert action programs transformed into White House controlled SAP non-covert action programs? White House SAPs are not unheard of. A well-known example here is Yankee White. A single scope background investigation required for direct music support for the White House, but Yankee White was indeed properly reported to Congress. So, let's say you have a White House SAP, similar to Yankee White, but is handled by the National Security Council and deals with what 50 US Code 3093 might consider quote unquote covert action. If the SAP is given the non-covert action designation as defined by 50 US code 3093, this completely removes music any presidential findings/reporting requirements to Congress and intelligence committees. The activity is then music treated as a sensitive but non- covert acquisition, intelligence, research or operation activity. Because the activity is not generated as a DoD SAP, it falls outside of 10 US code 119 and thus is not subject to title 10 requirements. The White House SAP then music exists in a crate area between 50 US code 3093 and 10 US code 119 with and write this down because this is critical no statutory reporting obligations yet still answers music directly to the National Security Council or Cognizant executive authority. One of the concerns music of how this has been historically accomplished is the wielding of unitary executive theory by presidents Eisenhower and Truman. Essentially leveraging and exploiting the executive body's inherent authority over classification and national security operations. But for a more tangible and concrete method here, this is really the most important part of the video. The loophole here is to harness contentonly special access programs. A contentonly special access program is defined as a highly restricted security protocol used within the US government to protect extremely sensitive information or intelligence rather than an entire project or acquisition. Thus, content only. Unlike acknowledged, unacknowledged, and waved, content only is not a protection level. Here's the kicker. It is a budgetary/structural tier and an administrative designation. Contentonly SAPs hold protected information, but they are technically unfunded. The SAP either has no funding at all or funding is rolled into normal executive, armed forces or intelligence budgets. Because content only is unfunded, these SAPs carry zero reporting requirements. Doesn't matter if it's title 10, title 50, none. Content only is an extremely niche designation spoken about extremely infrequently. Indeed, two of the only major discussions you will find on contentonly SAPs exist within AFI 116-701, which describes the designation music as quote a descriptive term used to describe a SAP or any sub element that contains information only and either has no funding associated with it or its funding is managed as part of the Air Force corporate budget process. End quote. as well as DODI5205.11 which describes content music SAPs as quote a SAP that protects discrete CPI end quotes. CPI of course is critical program information. So let's think this through here. Early UFO legacy program activities are conducted out of the 5412 committee special group. Thus retrieval, exploitation, and storage of nonhuman technical vehicles are inherently covert action. Bonus points because POTUS at the time, Eisenhower, most certainly did not want national acknowledgement of the UFO issue. Various classified presidential executive orders cemented program coordination within NSC's 5412 committee and successor groups. music And up until the Reagan administration, legacy programs did whatever they wanted, the Wild Wild West days. Major SAP crackdowns forced the legacy structure to start leveraging cover offices and programs to stay hidden, effectively siloing the programs. 1994 saw the programs vest management outside of the US government into a quasi government and industry control group that still features statutory controls and involvement by the National Security Council. Clapper, I'm looking at you. The introduction of 50 US Code 3093 in the early 1990s and 10 US Code 119 in the late 1980s forced Legacy to get creative again. Historically covert UFO activities have been run out of the White House and National Security Council. But with all of these US governmentwide oversight mechanisms, how does one make covert action programs and special access programs that wave Title 10 and Title 50 reporting requirements? You do this by making the covert action white house sap non-covert. So the solution here is to make covert UFO saps content only and thus all carveout and reporting requirements are hidden and waved. The actual SAP program record contains critical program information CPI only and actual craft retrieval, storage music and exploitation is not inherently conducted under the SAP. Akin to standard SAP umbrellas, the program structure can harness dual hated roles, something I talk about often, like the night shift guy at NASA, a parallel tier 1 element for retrievalss, or a hidden wing under the Edwards 412th test wing to harness elements of the defense industrial base for these covert mission directives whilst maintaining a short yet narrow chain of command. Of course, the program structure can use the subject matter experts and R&D aces, FFRDC's, which exist as Goko, government-owned, contractor operated to keep program materials, activities, deliverables, reports, etc. in a quasi government and industry state. Wink wink, MITER. And most importantly here, this SAP activity carries zero budget. The budget is rolled into standard USG budgets. music Think to when I talked about witness Ed, a lieutenant colonel within the hidden wing and a senior figure within SAF AQ or Air Force Acquisition. Ed stated money music was just pulled off the books of the Air Force budget into black holes before any sort of review by SAF FM or Financial Management with no dedicated budget carries little to no monetary footprint. Now, think back to the Wilson Davis notes. Remember what Wilson stated that the legacy program record within the oustat contained zero budget? That budget was kept in separate records for quote unquote audit purposes. This is one of the premier loopholes legacy uses alongside Wooaps to completely hide and obuscate UFO legacy programs. contentonly SAPs. Now, of course, similar systems exist within intelligence community controlled access programs, CAPS, and DOE SAPs. But I really wanted to take an extended top- down overview of how sensitive national programs and how the executive branch specifically has manipulated SAP structure to hide the legacy programs. And you have to remember the president has original classification authority over what they call uh classified national security information under executive order 13526. The issue is some of this is under the Atomic Energy Act in 1954 and the president does not have unilateral declassification authority. Of course, I must mention and we must spend some time discussing a nearly uncrackable system similar to White House non-COVIt action SAPs. These are department of energy saps. DOE saps get very spooky very fast. DOE SAP authority is given from both executive order 13526, same as DoD SAPs, but also the Atomic Energy Act of 1954. We discussed at length in part one the statutory authority born from the 1954 Atomic Energy Agreement. In short, the classification system for the Department of Energy and its precursor Atomic Energy Commission system is very different to the standard executive order-based classification system. Concepts like restricted data, formerly restricted data, and broad interpretations of special nuclear materials, as we know from David Grush, are inappropriately draped over the UFO topic to maintain airtight secrecy. Such systems born from the 1954 Atomic Energy Act are covered by statute and thus not responsive to magic executive orders and the standard DoD classification and declassification processes. They're basically treating this as nuclear secrets because it gives off, you know, nuclear radiation because if you look at the ultra vague definition of special nuclear material, which is section 51 of the Atomic Energy Act 1954, it says anything that gives off a sizable amount of atomic energy. Literally, that's what it says. Well, what's sizable? And what legal gymnastics are you saying this stuff which is obviously not a well who knows maybe it is laughter a nuclear weapon and you're saying this is a US nuclear secret you're transclassifying it into a nuclear secret which I understand maybe at first why they did that. So DOE SAPs can operate under DoD SAP guidelines or the DOE's own classification standard whose authority is the 1954 Atomic Energy Act. This second option here allows legacy elements within the Department of Energy and its semi-autonomous subordinate agency, the NNSA, National Nuclear Security Administration, to really deepix and hide their SAPs under the guise and liberal interpretations of quote unquote nuclear secrets. This is why I have stated on several occasions, the Department of Energy is figuratively baked into every single layer of the UFO legacy program pyramid, relegating program materials, reports, deliverables, etc. under DOE controls are incredibly airtight. An example here is actually the hidden wing. Again, witness Ed stated, "From day-to-day operations with the AFTC or Air Force test center on the Edwards 412 test wing all the way up to Air Force acquisition, the Department of Energy was intimately involved with every layer of the program." So, no, Lou Alzando, your false legacy program outline is inaccurate. The Department of Energy is not an equal player with the Air Force and Defense Industrial Base Prime contractors. Of course, in the future, I will do a full DOE investigation. Lastly, on our SAP section here, we have taken a top-down overview of SAPS, USAPS, WOAPS, covert and non-covert action programs, CAPS, DOE, SAPS, and national special access programs or NSAPS. But how can we translate these security protocols onto day-to-day operations of UFO legacy programs at defense industrial-based locations? From Dougway proving ground music to the Naval Surface Warfare Center Crane, I have not held back on locations that I am supremely confident engage with covert UFO retrieval and RDT&E. Indeed, I often state MRTFBS or major range and test facility bases are the paramount critical physical cores to such operations. Places like Dougway, the Nevada Test and Training Range, Utah Test and Training Range, China Lake, Edwards 412 Test Wing, Atlantic Undersea Test and Evaluation Center, etc. But to get real specific here in reference to SAPs, day-to-day handling of SAP material and physical access to SAP information must be confined to skiffs or secure compartmented information facilities or accredited special access program facilities, SAP FS, which are permanent locations alongside permanent accredited SAP FS. SAP activities involving the processing, music handling, and or storage of classified information can occur within several other facilities. These include temporary SAPFS or TAPFS which are limited to 12 months of operations, SAP compartmented areas, SAPKAS, SAP working areas for processing and discussion without storage of CPI SAP was and SAP temporary security working areas limited to 40 hours per month also called SAP TISWAS. SAP FS can be placed anywhere that meets or exceeds skiff standards prominently placed on contractor facilities within defense industrialbased infrastructure and employ extensive physical electronic visual etc safeguards to ensure the sanctity of SAP materials. Day-to-day operations of SAPS rely on both government and contractor personnel. Such a roster here includes a government program manager or GPM who is a senior government program official responsible for all aspects of the SAP, a contractor program manager or CPM who is the industry equivalent to the GPM and is responsible for the program's overall management within the contractor facility and is responsible for executing all contractual obligations. a program security officer or PSO who is responsible for full spectrum program security. Government SAP security officers or GSSOs under the PSO and a contractor program security officer or CPSO. This here is a perfect bridge into our next section. Program protection agencies who often live within the program security channels deputized by elements of the legacy programs to neutralize program exposure and insider and outsider threats. Uh but I I do have knowledge of um active planned uh reprisal activity against myself and other colleagues and it's music very very upsetting to me. >> Coming from where? >> Uh certain senior leadership at previous agencies I was associated with and that's all I'll say publicly but I can provide more details in a closed environment. Yeah, there were certain colleagues of mine that were brutally administratively attacked and it, you know, actually makes me very upset to as a leader to see that happen to other co-workers and actually superiors of mine over the last three years. >> How do you account for that response? That, that seems like a bizarre response. >> Uh, I call it administrative terrorism. That's their their quiver, their tool in the toolbox uh to silence people especially, you know, the uh career government service cares about their career, cares about their clearance, uh their reputation to climb the ladder. And when you threaten that, uh flow career path, u uh a lot of people back off. Um but I'm here to represent those people. Let us now move down the onion and identify program exposure management and protection agencies. Elements of specific US agencies/services music that are deputized to enforce insider and outsider threat protection all to enforce total security surrounding UFO legacy programs. If we have the core of our onion protected by layers of exploited special access program protocols which are in turn protected by the SAP SRG, think of program protection agencies as the antibodies that swarm to neutralize threats to the core of legacy. Of course, program protection and program exposure management are inherent to the SAP structure and we discussed as such in our SAP section with defining component USD and DoD level SAP codes, SAP and the SRG. There is nothing nefarious about program protection. Indeed, the concept is critical to maintaining a healthy SAP enterprise. I am stating that under or better phrase here within the SAP ecosystem exists several agencies, offices or services that are deputized to protect and neutralize threats towards high-risk waved national special access programs regarding covert UFO action. Unlike other program protection elements that music exist outside the SAPCO, SAPO and SRG DoD pyramid like the ISO music or the information security and oversight office and DCSA, Defense Counter Intelligence and Security Agency, the select agencies we will speak on exist within the very same agencies and music departments within the armed forces intelligence community and DoD that operate on UFO legacy activities. And I have spoken about one such agency extensively in my video on the Air Force Hidden Wing Program. This being the Air Force Office of Special Investigations, Office of Special Projects, or AFOSIPJ. Indeed, this office PJ is tasked with safeguarding the US Air Force's most sensitive and secretive special access programs. I really don't want to spend too much time on PJ, but once again, I will bring up two names attached to PJ that I am aware are paramount gatekeepers to the UFO topic. And these include former AFOSIPJ executive director and departmentwide Air Force SAP security director, now vice president of security at North of Grumman, former senior executive service, Mr. Terry Phillips. I am aware that before his retirement from federal service in 2021, Philillips operated as an enforcer for the UFO activity music administrative structure, leveraging administrative terrorism and much worse against prospective whistleblowers. Indeed, I understand Philillips continues similar work within North of Grumman to this day. Philip's successor in AFOSIPJ and the Air Force SAP security music enterprise is a man named Mr. Lee M. Russ, similar to Phillips, I understand Mr. Russ picked up right where Phillips left off within federal service. Let's just say I would not be surprised if documents are ever released that directly state Russ has been involved in UFO narrative shaping. Phillips and Russ are critical names, but alas, I have covered these two in great detail before. So, let's move on to new things here. I would like to now move on to the Defense Advanced Research Projects Agency, DARPA's Security and Intelligence Directorate, SID. Coming to DARPA is like grabbing the nose cone of a rocket and holding on for dear life. >> DARPA is a place where if you don't invent the internet, you only get a B. >> A DARPA program manager quite literally invents tomorrow. >> We are thinking about innovation unconstrained. Where can we go predict what is emerging as threats? >> We're looking for the applications that seem impossible. That passion will be saving lives 5, music 10, 15 years from now. >> Coming to work every day and being humbled by that. >> Real fast. What exactly is DARPA? DARPA is the DoD R&D, research and development agency reporting to the under secretary of defense for research and engineering that is tasked with development of emerging and advanced technologies for military use. As the agency that quote unquote shaped the modern world, DARPA is the tip of the spear for advanced asymmetrical advantages in national security related technology. DARPA is well worth an enormous exploration into possible involvement with recovered non-human materials, craft, and bodies, music as DARPA is strangely and largely missing from most UFO legacy program conversations. And do not fret, one day I will undertake this effort. The DARPA SID or again security and intelligence directorate is a critical support component within DARPA. SID works to ensure protection of DARPA's high-risk R&D programs that involve highly sensitive technologies critical to US national security. SID safeguards against insider threats, foreign influence, espionage, and a wide swath of protection protocols to ensure US technological dominance. DARPA SID is the premier program protection element for DARPA agencywide and inter agency SAP activity. quote planning, executing, and directing the information, personnel, industrial, information assurance, and physical security programs at DARPA and at specific contractor sites end quote. Indeed, Sid's expressed mission is to quote develop, manage, and implement programs that facilitate the secure and successful accomplishments of DARPA's mission while protecting DARPA technical and administrative personnel, information, property, and ensuring business continuity. End quote. In an almost comical statement, DARPAD's PSRs or program security representatives analyze and create protection strategies music and tactics. frequently for technologies that exist nowhere else. End quote. DARPADID is incredibly unique as an office because its security representatives are not stovepiped into specific types of program security support. music Example being just collateral, just SAP or SEI or just CUI. Instead, SID's PSRs are quotes responsible for providing expert security support to a program portfolio that may include fundamental research, controlled unclassified collateral SAP, SEI, and other compartmented information activities. End quote. And another music quote, quote, they are the tip of the spear for execution of SID's primary function, enabling the secure development of DARPA technologies. End quote. Now, apply this hands-on SID approach to some of the day-to-day music SAP operations we just spoke of. As best as I can tell, the SID was founded by at least 2003 when the first mention of SID I can find is a routing line for a DARPA information processing techniques office document. I wonder what office would ostensibly function as quote unquote antibodies if someone posed a security risk to the most covert deepixed inter agencywaved USAP portfolio in existence. I will go so far as to say I'm aware of former directors within DARPADID that have engaged in music serious crimes to silence whistleblowers and prevent program exposure. These include, but are not limited to, wet works operations. I would encourage Congress music to immediately construct interrogatories leveraged at DARPA SID and its SSO support services office. I would leverage questions towards former SID directors under penalty of prosecution if questions are not answered truthfully. I genuinely hope this does happen. Now, believe it or not, I do have some music sense of self-preservation, so I will not be naming this individual, but it would not be a Gerb video without names. DARPA reports through the office of the under secretary of defense for research and engineering directly to the USDRE. Recall from earlier, USDRE is the evolution of Vanavar Bush's research and development board, RDB. And according music to DODI5205.11, USD R&E quote identifies and cultivates cuttingedge technology developments, technology transition, developmental prototyping, experimentation, and developmental testing activities and programs requiring SAP protection to ensure continued US war fighting advantage. End quote. Since Sid is a support directorate directly under the DARPA director, Sid's direct administrative line of accountability traces directly to the under secretary of defense for research and engineering. So let's name a man within this chain of music command that I know to be legacy program. Dr. Peter Hinam. >> So DARPA works at the intersection music of national security and science and technology. Our job is to avoid and to impose technological surprise and we focus on the hardest problems. >> Dr. Heinam currently serves as the principal deputy assistant secretary of defense for critical technologies within the USD R&E. And by the way, critical technologies in highle DoD positions is often an indicator of legacy exposure. Prior to work within the OSD, Hinam operated as a DARPA program manager focused on electronic warfare and airborne communications. Served as director of ODNI's Intelligence Advanced Research Projects Agency, IRPA, director of research at the National Geospatial Intelligence Agency, NGA, then from 2018 to 2022 music served as deputy director and acting director of DARPA. If there is indeed an individual who has been integral music to coordinating legacy efforts between DARPA and USD R&E and then don't forget DARPA SID for program protection within the last 8 plus years as I am directly alleging it has been and music continues to be Dr. Peter Heinum. Since 2012 Sid has maintained an music intimate partnership with a company called System High. Indeed, since 2012, the two's music partnership has quote produced several novel advancements in security policies, enhanced methodologies, and tools music end quote. Indeed, in 20122, SID awarded a 5-year contract to System High to quote, provide multicurity services to our nation's premier innovation engine, responsible for developing and delivering breakthrough technologies critical to assuring US technical dominance and music overmatch. end quote. This 2022 contract was the third consecutive awarded to System High by SID. Founded in 2005, important year to contractor breakaway legacy programs. System High quote delivers the most advanced protection and security solutions to secure music and strengthen critical missions, programs, operations, and intelligence activities. End quotes. music The mission of System High is to be the only choice when the mission must be protected. To set the bar high and exceed it by working together to continuously improve and strengthen the protection landscape and deliver for our customers at a level no one else is capable of. Outside of DARPA SID here, System High currently has numerous contract vehicles, including Idiq, indefinite delivery, indefinite music quantity contracts with the Navy, Missile Defense Agency, MDA, and other agencies/services. System High has some rather intriguing individuals on its board, including former Seuite executive and president during our epoch of interest from 2019 to music 2025, Rob How, who prior to System High was a manager for quote unquote special activities at Northrup Grumman, a PSO or program security officer for SAFQ, again Air Force Acquisition, music and of course served in the Air Force at the AFTC. all major elements within UFO legacy programs. DARPADID is a very little known element that safeguards the US most innovative and secretive science and technology programs and an office that engages in UFO legacy program exposure management and protection. To the uniformed and civilian airmen of the Air Force Life Cycle music Management Center, our contractors, and the Defense Industrial Base, thank you for being music here, and thank you for all that you do to support our great nation during this time of consequence. Now, on to a mouthful here, AFL CMCIP or the Air Force Life Cycle Management C Center's Information Protection Directorate. AFL CMC is currently directed by Lieutenant General Donna D. Shipton, a senior individual within Air Force UFO Legacy Activities that also formerly served a senior position within SAFQ, music where Shipton was quote responsible for research and development, test, production, product support, and modernization of Air Force programs worth more than $60 billion annually. End quotes. AFL CMC is one of six major operational centers music under Air Force Major Command, Air Force Material Command, AFMC, alongside AFTC we spoke about earlier, as well as AFRL, Air Force Research Lab. My hidden wing project painstakingly details the history and evolution of AFMC and why this major command is one of the most critical to all of Air Force UFO activities. So, I do strongly recommend viewing that if you haven't already for some background. Centered out of Wright Patterson Air Force Base, the AFL CMC mission is to deliver affordable and sustainable warwinning capabilities to US and international partners on time, on cost, anywhere, anytime, from cradle to grave. AFL CMC is the single center responsible for total life cycle management of all aircraft, engines, music munitions, and electronic systems. AFL CMC's portfolio includes information technology systems and networks, music command, control, communications, intelligence, surveillance and reconnaissance systems, C4 ISR, armaments, strategic systems, aerial platforms, plus installation and infrastructure management, advanced training capabilities, as well as combat readiness programs that focus on equipping the war fighter with the tools needed for protection in all environments. AFL CMC IP or again information protection directorate is the premier program protection element for air force acquisition and sustainment. Again recall my hidden wing project where Saf under the assistant secretary of the air force for acquisition technology and logistics is a major administrative element within the air force's work on UFO RDT&E. The AFL CMC IP quote enhances the ability to acquire and support war-winning capabilities by providing a professional security workforce and riskbased processes music to protect technology and information from unauthorized disclosure or compromise throughout a program's life cycle. End quote. This protection of information and technology extends across the entire Air Force acquisition umbrella involving work within AFMC's other major operating areas including AFTC and AFRL Air Force Test and Evaluation or AFTTE specifically AFTTE special programs division and across all Air Force major range and test facility bases MRTFB. AFL CMCIP also interfaces with the Air Force component level SAPco SAF AAZ. We know from part one SAF AAZ has been bypassed for activities that I am highly confident are legacy operations quote unquote outside activities under Edward C. Aldrich but specific SAF AAZ heads music have been senior legacy officials before including William E. Mccclure. From studying the CV of the current director of IP, Mr. Terrence L. Reynolds, we can learn a little more about how extensive IP's program protection strategies reach across the entire Department of the Air Force. Mr. Reynolds guides the IP on quote information security, personnel security, industrial security, acquisition security, international program security, operation security, scientific and technical information program, and program protection planning. End quote. I don't want to spend too much time on IP here, but I did find such a directorate critical to mention as an addendum to my Air Force hidden wing project where AFL CMCIP is critical to information program protection with administrative levels of the Air Force, specifically Air Force acquisition. Last program protection office to cover here. Just as we shifted our sights ever so briefly to the Department of Energy towards the end of our special access program section and commented on how the DOE beholden to its own statutory authority separate from standard executive order-based classification systems gets real spooky real fast and operates as a perfect ecosystem for Wooaps with even tighter security protocols governed by the 1954 Atomic Energy Act. The Department of Energy actually has its own SAP. Its SAPS are that sensitive. Not a component level SAPCO, but its very own SAP. Similar to how AFL CMCIP, AFOSIPJ, and DARPAD are specialized units that aid in the safeguarding of SAP ecosystems, the DOE has their own very broad version of this as well. The DOE, OICI, or Office of Intelligence and Counter Intelligence. And that's right, the DOE has its own intelligence agency. DOE OICI, sometimes referred to as DOE in, according to its mission statement, quote, informs national security decision makers and mitigates threats to the DOE enterprise music and the nation's energy security by providing unique scientific and technical intelligence and expertise. End quotes. though quite small in size and maintaining a classified budget out of fiscal year 2026's $81.9 billion national intelligence program's budget. To say OICI is instrumental in DOE compartmented projects would be an egregious understatement. Not only is OICI the DOE's primary interface with ODNI and other intelligence agencies, OICI specializes on insights into foreign nuclear capabilities and activities. counter intelligence, including espionage and insider threats, nuclear material security, protects critical infrastructure and support music interactions with DOE's national laboratories, and much, much more. After all, ODNI states OICI's mission is to quote protect, enable, and represent the vast scientific brain trust resident in DOE's laboratories and plants end quotes. Perhaps it should be no surprise, but OICI's roots can be traced back to the Manhattan project's ALSOS music missions, which we discussed in great detail in part one. Basically, the blueprint music for a parallel intelligence apparatus for legacy activities completely removed from standard chains of command. I am particularly interested in OICI's nuclear materials information program, NMIP, established by NPD-48/HSPD-17. music As we know from part one in my other previous works as well as David Grush, language from the 1954 atomic energy agreement has been liberally distorted to treat UFO activities music as nuclear secrets. Controls like special nuclear materials, transclassified foreign nuclear information, TFNI, non-contract foreign intelligence information are some of the tools of the trade here. I wager beyond a shadow of a doubt some of OICI's nuclear programs also see engagement with the UFO portfolio. And of course, we will discuss this in much greater detail in my inevitable DOE project. But here I am also particularly interested in OICI's security offices and intelligence music operations center. These systems work closely with the larger IC and White House whilst conducting counter intelligence and insider threat support to DOE SAPS and skiff accreditation. Indeed, OICI maintains 14 field intelligence elements FIE at DOE labs facilities and sites and 15 counter intelligence field offices at DOE facilities worldwide. Some of these FIE sites exist at Los Alamos National Lab, Sandia National Lab, Lawrence Liverour, and Oak Ridge. As we discussed in part one, specifically surrounding physical security translated from the Manhattan Project onto the Manhattan Project 2.0, No, we discussed a series of alleged classified presidential executive orders in 1948 under Truman that vested custody of recovered music NHI vehicles within AEC national laboratories like those listed above. OICI really is still an emergent piece of the puzzle to me. One that like DOE is interwoven into the very fabric of UFO legacy activities, but also an element exceedingly difficult to crack. Please expect much more on OICI in a future Department of Energy project. >> You can say categorically you've seen no convincing confirmable evidence intact music spacecraft kept by the US government. >> No, I have seen nothing that leads me to that conclusion. >> Is it possible there is some secret program that you're just not aware of? I don't think so. I have access to anything and everything I need. >> The main players in the legacy program have long been the Central Intelligence Agency, the United States Air Force, the Department of Energy, and major defense contractors. The subject of UFO has been rife with lies, disinformation, narrative control, and bizarre limited hangouts since 1947. And I do not think that is a stretch or controversial statement to say. When one says UFO disinformation, you may immediately think of Rick Dodie and Paul Benowitz, Project Blue Book, Arrow in the disgraced Dr. Shan Kirkpatre, E4s telling Matt Gates they think there is a hybrid NHI breeding program or a litany of other intriguing and disturbing examples. But disinformation and narrative control is a paramount outer layer of the onion that has been harnessed for decades by elements of the legacy infrastructure. All to introduce stigma around the topic, warp narratives to expose the public to a narrow field of information and keep the US populace and lawmakers in a constant music state of disbelief and confusion within the topic. Like I said, this concept extends back decades. Knowledge is power and that couldn't be more true in the 21st century where multiple campaigns have been wagered from within the onion to shape and limit global perception on UFOs and these include but are not limited to Arrow and ATIP. What else you want to know? >> The Air Force was tasked in 1948 by the US government to conduct the first ever investigation into UFOs. An effort called Project S. sign quickly evolved into Project Grudge in 1949, which ran until 1951, where the infamous Project Blue Book took over and ran from 1952 to 1969. A massive schism occurred in these quote unquote official investigations into UFOs in 1953. The Robertson panel. Prior to 1953, there did seem to be some sort of transparency on this topic, and this can be perfectly observed within the words of Air Force Captain Edward J. Rupelt, who served as the director of Project Grudge and Blue Book. Rupelt would state in his 1956 book, The Report on Unidentified Flying Objects, that he observed a memo generated in 1948 from Project S. This memo stated UFOs were of quote unquote interplanetary origin. This memo, according to Rupel, was ordered for destruction by General Hoy Vandenberg, one of the original accused members of Match 12. Rupelt is music especially poignant now that Representative Berles has called out by name and file designation AF-ATIC-film music 0352 a briefing on film by rupelt titled Flying Saucer Talk. This 1952 film is held at MIT music Lincoln Labs of all places, an FFRDC that is the successor to Vanavar Bush's MIT Radiation Lab. Why would MIT Lincoln Labs that was established to spearhead one of the US's first national air defense systems be holding such a film? And why was this film never volunteered for mandatory NAR collection? probably because this film and others at Lincoln Lab depict sensitive and classified briefings and materials regarding non-human technical vehicles. Alas, 1953 observed the Robertson panel again, a CIA review of the Air Force's investigations into UFOs, at that time Blue Book. Obviously, as I have covered previously, Robertson panel was given prior mandates that the conclusions of the panel at the CIA's behest were to reduce public concern on the topic and state that UFOs could be explained as prosaic aerial phenomena. This same playbook was harnessed with Edward Condan's 1969 Condan Committee, which marked the end of Project Blue Book. J. Alan Heinik himself directly stated the Condan Committee outright ignored key evidence. This playbook was again harnessed in 2022 with the establishment of the all domain anomaly resolution office or Arrow. What was once supposed to be a joint UFO study effort called the UAP JPO or joint program office was distorted and twisted likely by the USD INS at the time, Ronald Moltry into the mangled arrow of today. Indeed, it was none other than Mr. for Ronald Moltry, former USD INS and Shawn Kirkpatre's good buddy that played a major role in establishing Arrow and provided oversight and direction to Arrow, including surveillance collection and reporting, system capabilities and design, intelligence, operations and analysis, mitigation and defeat, governance, and finally science and technology. Moltry is a seasoned deep state lifer and legacy senior. I must once again ask this man why his position on the MITER Corporation was removed from his public CV and bio. To this day, Arrow has operated as an extension of the Onion to exponentially increase the stigma around UFOs by constant dismissal of the topic. Language crafting from Susan Goff about the non-existence presence music of extraterrestrials on this planet and most importantly operating as a honeypot for whistleblowers. >> I've tried to help. I certainly uh met with Arrow twice as a staff member about a year ago. I actually offered to depose hostile witnesses in front of Arrow leadership. Uh they have yet to take me up on that. >> When the CIA squirmed out of answering lawful interrogatives, they directed Rep. Berles and Grush to Arrow. >> But I did offer my services. I gave them leads etc. And uh actually Congress has been sending inter interrogatives uh to cabinet agencies. something I touched on on Megan Kelly back in uh January, we actually got um we sent interrogatives to the CIA and the response uh Comr's committee gots was uh from the CIA was like, "We are not answering any of these questions. We'll refer you to Arrow." And I find that very curious. I don't know if John Ratcliffe and Michael Ellis knew that that's what CIA general counsel said back. Uh but CIA is unwilling to answer detailed questions that were obviously informed by my experience. >> Indeed, Arrow has outright lied through its teeth on numerous occasions. Several examples can be seen in Aeros historical report volume 1 where thanks to obtaining Michael Herrera's official Arrow memorandum for record, we can observe Arrow blatantly lied about Herrera's testimony, falsely stating Herrera discussed an extraterrestrial spacecraft and US special forces. Disgraced former deputy director of Arrow Tim Phillips and disgraced coward former director of Arrow Dr. Sean Kirkpatre have for years engaged in wildly inappropriate behavior, often resorting to emotional outbursts on LinkedIn for Phillips or sending unprofessional statements to Steven Greenreet from Kirkpatre. Both men have leveraged ad homonym attacks and false attacks to try and discredit David Grush. Kirkpatre even establishing a pitiful story to paint Grush as a villain by stating he ghosted Arrow for meetings. Gosh, I wonder why. And this goes without even mentioning the egregious falsities outlined in the Pentagon disinformation that fueled America's UFO mythology article by the Wall Street Journal, in which Kirkpatrick outright lied that the whole impetus for claims around UFO legacy programs was an illegal Air Force hazing program called Yankee Blue. Hey, Kirkpatrick, you told podcasters off air each branch of the armed forces had their own Yankee Blue equivalent. Why did you say this? And why was it never mentioned in the article or publicly? And somehow Steven Greenstreet got a copy of the Yankee Blue document, probably from Kirkpatrick, which features inaccurate security controls. So if this program was an illegal hazing ritual that tricked tens of thousands of Air Force officers for decades, there should be no problems in releasing the Yankee Blue document, right? If this is ever released, come back to this video and see whose signature is at the bottom of this report. On his Judicial Watch episode, David Grush perfectly laid it out regarding Yankee Blue. >> Well, yeah. And I certainly was worried about rumor in innuendo, you know, uh, hazing programs that tricked people. There's a, you know, a narrative being spun in the media, Wall Street Journal, etc. about that kind of thing. I was well aware of hazing activities. I was guilty of said hazing activities earlier in my career when I was a lieutenant and thought it was funny to make kidno laughter briefs the freak about the the two star general and certainly I was already aware of that and I was calibrated to you know lore in the community room as we say in the intel community and you know hazing activities so the the evidentiary threshold was high and the people I brought to ICIG you know were hands-on they touched it they were in the facilities >> music >> um and they you know they were well cleared people and they weren't misconstring a recovered adversarial aircraft for something else and some of that gaslighting that's been going on which I find honestly amusing to see uh certain you know former career bureaucrats you know use the narrative that it was some Yankee blue uh hazing uh program and those were certainly not the code words I you know I provided to the ICG and the intelligence communities. We know the right code words and we know uh which reported special access programs and controlled access programs were essentially covering it up in uh uh performing financial fraud um to hide the some of the paper trail, misappropriating funds and then taking haircuts across music other black programs to funnel the money um uh to to to those kind of activities to keep it off books. It is the expressed purpose of myself that deputy director of Arrow following Kirkpatrick, Tim Phillips, was a quote unquote useful idiot in that during his tenure at Arrow, Shan Kirkpatre was partially briefed into the legacy portfolio to limit program exposure and defame David Grush. Hey Shawn, are your hands still tied? Perhaps Shawn was rewarded for these unamerican and illegal actions with his senior position at Oak Ridge as chief technology officer for defense and intelligence programs after he fled Arrow that was mysteriously deleted from the internet. Perhaps he has continued to be rewarded now that his company Nonlinear Solutions LLC is subcontracting under MITER for US Spacecom. And Shawn can't seem to help himself but to stay engaged to this day. emotionally lashing out using Green Street as a vessel whenever he gets his feelings hurt. We talk often about Moltry and disgraced Kirkpatrick. But there is another culpable name here, the man who actually got Kirkpatrick employed at Arrow, Mr. David M. Taylor. Taylor currently serves as the Deputy Under Secretary of Defense for Intelligence and Security, USD INS, of course, and has been in similar positions of government service for 44 years. Of all the people to choose for Arrow that was supposed to be the UAP JPO and Taylor chose Kirk Patrick. I wonder if there are any legacy ties here. >> My name is Lou Alzando. In 2009, my life changed forever. That's when I was recruited into a highly sensitive government program that investigated unidentified aerial phenomenon, UAP, also commonly known as UFOs. Now, I must be music extremely careful with the following section here. One, because this is an extremely nuanced topic, and two, because critics of Alzando are often painted by the UFO community as music enemies. Let me get something clear here. My mission to reveal and uncover UFO legacy programs which have since music 1947 operated in a coordinated capacity to retrieve, store, and exploit non-human technical vehicles is stalwarts. I stand with the whistleblower. I stand with Dylan Borland. I stand with Matthew Brown. And I stand with witnesses I speak who will never go public. I stand with Ed. I stand with several figures that have appeared on my channel over the years. And most importantly of all, I stand with David Grush. My entire philosophy, methodology, and approach to this topic is modeled after the bravery, courage, and leadership David Grush has displayed since going public. But, and I need to be frank here, I do not stand with Alzando, nor do I trust Alzando. I believe Lu Alzando has been a central figure for a legacy activity to speak about the Onion outside of The Onion, aka a narrative control campaign. And let me just say this, I am speculating here and theorizing for entertainment purposes. I don't care to get sued, although counter questioning would be rather intriguing. >> The Advanced Aerospace Threat Identification Program ATIT. The funding for this effort was sponsored by then Senate Majority Leader Senator Harry Reid and together myself, Jay Stratton, and our team for nearly a decade investigated UAP incidents around the world. >> In 2025's Age of Disclosure, film protagonist Alzando lies incessantly about the structure of OAP, the Advanced Aerospace Weapons Systems Application Program and AIP. OAP out of the Defense Intelligence Agency, DIA, ran from 2008 to 2012 and did indeed have a budget of $22 million. And as David Grush stated on Rogan, one of the expressed missions of this program was to operate as the recipient of the Kona Blue DHS PAP transfer prospective special access program of UFO materials from Loheed Martin. ATIP is not OAP. ATIP was nothing more than an informal working group that was unfunded. This is common knowledge of course, but I will go a step further. ATIP was an informal working group that was a literal cover for several national security council activities that wished to speak about the Onion outside of the Onion. And who gave this top cover, James Clapper and Matt Ford actually asked this to Lou on Matt's show. Watch now how Lou dodges this music question. And I do recommend watching this full interview by Matt. It's really good. >> So, so my understanding of it was that it was in ATIP in in certain aspects of it were to essentially you had factions within the legacy program, factions that felt, you know, we need to let some of this out. And part of one of the elements of ATIP was to sort of peel away some of the the the layers of the onion. But this was done in coordination with the Obama administration. This was part of part of uh a something that came out of out of the National Security Council uh and in particular James uh James Clapper. Uh so can you speak to that? And again, were you ever or are you part of the legacy program? >> Well, I I worked with Jim Clapper. Actually, I worked for Jim Clapper, as a lot of people know, uh when he was under secretary of defense for intelligence after he was the director there at DIA, but before he was the director of national intelligence. Um, and I can't speak for for for Jim. Um, he would have to answer that to you. But what I'll tell you, at least when he was uh when I spoke to him, he was very happy um and that we had a a UAP program um in in the department. music Um now that doesn't mean anything. You ask him now, he may be think otherwise. Uh but that's certainly up to director, former director Clapper to to to opine music about. Um, as far as where this comes from from Obama, um, I never sat with Obama specifically about this topic, uh, or or this any other topic. I my my my my entree point was through the National Security Council for the programs that I was running um, in the special access world. Um, unfortunately, I probably wouldn't be able to elaborate too much on how that relationship works. um there is an established channel of communication that was between my office and and music that office uh but much beyond that I wouldn't be able to really provide any any fidelity to um you know we especially not just with classified information but special access programs there's a huge sensitivity there and especially when you're talking about SAPs in some cases and by the way I'm not saying this is one of them um if they're unagnowledged right that's that's music even that's even more sensitive so Um, boy, I don't know how to answer that question. It's a good question. Um, >> so in Age of Disclosure, when you listen music to Stratton and Alzando speak on ATIP as if it were a real working program with appropriations and see individuals like Put Off and Davis labeled as ATIP scientists, this is brazen nonsense. The primary operational years for ATIP were around 2009 to 2017, primarily when James Clapper was director of national intelligence and Mr. Alzando operated as the director of the national program special management staff NPMS. NPMS director operates under the USD INS of course also Clapper's former position from 2007 music to 2010. I'm sure there's no crossover here. An NPMS director runs coordination between National Security Council SAPS and the DoD/IC. As I stated earlier, the director of NPMS is usually the most cleared person in the entire DoD besides the secretary of defense, even more cleared than the director of DoD SAPCO. With this comes the baggage that even outside the ATIP NSE cover activity, Lou either prior to NPMS position or during NPMS position operated directly under or within the legacy programs. I once again echo this sentiment from Corbel. Yeah. So David Gres talked again and I was really glad he decided to cuz he's not all over the media. I I I do think that he has a difference of opinion and that's for him to talk about um when it comes to this stuff. You know, he really thinks everybody should just open up and say what they know. For example, he thinks that if Lu Alzando was part of the legacy UFO program that he should just say it, go out on the limb and just say it. music But ATIP, although Clapper or his superiors true motives for such an activity are unknown. Well, ATIP sought to conduct a partial disclosure campaign and establish Hillary Clinton as the disclosure president. These disclosures would have seen a huge emphasis on UFOs existing as a national security threat. Revelations of an amorphous non-human presence on this planet and the general discussion that we are not alone on this planet. These disclosures, however, would not have featured crash retrieval, reverse engineering, exploitation, NHI taxonomy, and of course, the revelations of the legacy programs. Indeed, prior to David Grush coming forward, Alzando would essentially only discuss crash retrievalss in reference to Roswell, which of course at this point is a cultural zeitgeist event and a well-known coverup. No harm, I guess, in discussing one singular crash retrieval event 70 years ago at the time, especially if you never mention the custodianship of the wreckage. Indeed, after Dave Grush went public in full kimono, Lou's crew was forced to reposture and discuss crash retrieval events and the legacy programs. This is extremely evident in the 2024 UAP hearings where Alzando seems rather caught off guard and nervous music compared to his usual interviews in which he can talk circles around really answering questions. >> Okay. Mr. Al Alzando, you state in your testimony that quote, "Advanced technologies not by our government or any other government are monitoring sensitive military installations around the globe." music End quote. If these technologies are not made by any government, who's making them? Private companies or are you implying they are crafted by a non-human intelligence? >> Well, ma'am, that's precisely why we're here. U the problem is that temporally speaking over decades, not just the last 10 years. Before to put this in perspective, when >> are these private companies you're implying or is this uh non-human intelligence? >> It may be both. Uh when it comes to Blue Force technologies, I would not be able to discuss them. >> Okay. Are you read into secret UAP crash retrieval programs? Um, we would have to have a conversation in a close session. Ma'am, I signed documentation three years ago that restricts my ability to discuss specifically crash retrievals. >> But let's quickly back up here as Alzando Melon, General Neil McCassland, John music Podesta, who was Hillary Clinton's campaign manager, and others used one specific vessel through which Lou executed ATIP's mission, and this was through Tom Dong and to the stars academy. I recognized that there were people in government that wanted to engage the public on topics that unfortunately had a stigma even though they were based in scientific fact. At the time, there was no mechanism for them to do this. Through a series of meetings, I was soon connected to a large group of US government officials from the CIA, the Department of Defense, and Loheed Martin Skunk Works. These guys were the ones involved in the secret of US government programs that dealt with these subjects. And they have all taken tremendous risks to themselves and their reputations to do something that can benefit the world. music They wanted to be a part of something special to be a part of a company that could not only change the way we see ourselves music but also change the path humanity is on. I have spoken at length about the quandry that is to the stars academy in which Dong, Alisando, Melon, Podesta, Halputoff, Major General Neil McCasteland, Major General Michael Kerry, Loheed Skunkworks Executive Vice President Rob Weiss all banded together for a slow disclosure campaign. I have also discussed several times how Alzando's ATIP's direction of such an idea was likely an evolution of project forum as outlined in the Bass 10-month report which was described as disclosure efforts through popular zeitgeist figures. And guys, this is not a knock at Tom. I personally love Tom. I believe Alzando and others parasitically attached themselves to his curiosity on the topic. Indeed, in my NRO project, I theorized Alzando even disclosed elements of the immaculate constellation music USAP to Dong, specifically surrounding episodic visits and foreign knowledge of UFO events as outlined in the IMCON music report. You know, you have people at the National Reconnaissance Office that have a perspective based on the satellite feeds they're getting and these things are coming in and out of the atmosphere. Then you also have people from the agency that are worried about and collecting information of what's going on with people in different countries and here uh but then you also have you know engineers that uh have a perspective on how the technology is made and what that might mean because there's a lot of consciousness stuff that that falls into this cate. So there's satellites that track them coming in and out of the atmosphere. >> Absolutely. Yeah. Absolutely. >> What kind of satellites are these? Uh, how I don't know. Usually forward-looking infrared, but I don't know what spectrum of the infrared they're looking at. >> So, there's some sort of a camera or some sort of a detection device that they have in the atmosphere just to check for UFOs. >> I don't know if it's just for UFOs. They can pick up very very specific heat signatures and they have algorithms because what you have is a di a satellite is a device that can pick up what you what you program it to pick up. Now you know you put a sensor on there but you got to tell the sensor what to do. >> So if the sensor says look something traveling at this speed with this kind of heat you know you got to record that you got to focus on it and that that's what we call an ICBM. But if something comes in and zigzags, stops and turns left and it's traveling 10 times faster than that, we need you to record that and focus in on that as well. But if something just is moving low and it's only going 300 miles an hour and it has these big wings and a low whatever, there that's just a plane, you know. So the what it captures is based on, you know, music how it's programmed in the first place. But >> so it can differentiate between meteorites and >> absolutely. So >> So how often are these things coming into our atmosphere? >> Oh, I don't know. But I I've had quite a few discussions. Um one of the people I I've music been I've been in contact uh one one of my adviserss was from the National Reconnaissance Office high up high up and um they call it episodic visits. That's all I know. episodic meaning like they have time periods where they like >> there was I saw a paper uh where they semesters I figured out um the department of defense figured out uh a physicist there an algorithm of how to compute when the things fly in and collect smaller ships like mother ships small ships what what at what longitude and latitude and uh and what essentially what orbit it would land at music when it would collect these other machines. And um so they tested that and in all I know is it was successful. >> Ultimately Hillary Clinton wasn't elected. TTSA failed. McCasslin got a slap on the wrist and Lou was forced to reposture. You would think after the failures of TTSA in the early 2020s before which Lou actually quote unquote left his position as director of NPMS to shortly join TTSA in 2017. That this limited disclosure effort would be disbanded. But seemingly it is alive and thriving but evolved music and morphed. Enter age of disclosure. >> And it was later in my career that I actually began running special access programs for the US government and in some cases reported directly to the White House and the National Security Council. The nerve to include Clapper and Age of Disclosure is one thing, but the documentary serving basically as an amnesty plea and misdirect on the legacy program structure is downright insulting to me. And this isn't a dig at Dan Farah, the film's director, or the quality of the documentary, but a staunch criticism towards Alzando and Stratton, who are bizarrely still protecting Clapper, the National Security Council, and pushing for limited disclosures. >> It is true. It does get a little lonely and and this subject brings out a lot of charlatans, a lot of people who want attention, a lot of people who want to generate certain narratives. I'm just here to do a job and to get this information out to the American public. And I would love to go back to my normal life. I live in in Colorado and I rather just ATV and hike with my dogs and not have to deal with this, you know, on the public stage. I never wanted to be a public personality. I have no book deal like other people in this space. And I I'll write a book. I promise I'll write a book after this is all over. It'll be my leadership meditations. My greatest critique of the film, as I have been oh so outspoken of, is the structure of the legacy program Alzando and others portray. The film states, "The legacy program, Singular, is spearheaded by the CIA DS&T or Directorate of Science and Technology. Within which the DS&T deputy director is the big bad mob boss of the program. Below DS&T on equal playing fields sits the DOE, Air Force, and contractors. music This is demonstrably false on so many levels, and you don't have to get into the details as I do on here, but I will not for one second believe this outline was crafted to translate the legacy programs to a general audience. No, I do believe such an organizational chart was generated to both protect Lou and Stratton's legacy friends and dictate who gets to catch the live hand grenade when and if disclosure comes. I won't go into too much detail, but as we know here, the DOE is baked into every single layer of the legacy structure, not beholden to the agency. We know that defense-industrial-based prime contractors, music besides the ones that broke free to use IRA to start their own programs in 2005, are the lowest level of the totem pole. Where is the Army? Where's the Navy? Where is the Office of Naval Intelligence, J Stratton? Where are five of the other big six intelligence agencies? Where's the DIA? Where are the FFRDC's, National music Labs, and UARKs? As it goes without saying, agency is not the UFO portfolio lead. Though of course, it has played a major major role throughout history. Indeed, the program activity lead, as David Grush recently stated, has often rotated for program purposes where administrative components to legacy operations often exist music in a flat hierarchy with a very fractured and loose top dog control group. >> That's a part of their program protection strategy where they do they do rotate things and that's the same thing with how they hide this program based on time epochs and who they trust, career civil servants, career senior executives in industry. They rotate it and it's there's no they randomize the schema too. It's not like this one guy and this one DoD office always gets it. They spread it across and it's this like rule by committee flat hierarchy and that's how they bounce. And I've seen that in conventional programs that that weren't reported to Congress as well. It has nothing to do with the subject. The way they just will hide things and and make a program that's not technically a compartment all that stuff. Why in this organizational chart is the National Security Council missing above the DS&T? Because this portfolio out of the US government is indeed run by the NSC. Oh, that's right. Probably to protect Clapper and Lou's old ATIP interests. Many, many questions still remain about Lou. What was his and Clapper's motive for the music ATIP cover program that served a partial disclosure campaign initiative? What is Lou's true background within the legacy programs? Why is Lou still protecting individuals and misleading in the age music of disclosure? Though it may not seem like it, both Arrow and Alzando through ATIP are two elements of the legacy program Onion systems to offer disinformation and egregious narrative control. And guys, although this section may have been harsh, I do need to state I am beholden to my mission of uncovering and exploring the legacy programs. Again, I stand with the whistleblower, but I do not trust Mr. Alzando nor the ATIP initiative. As we begin to finally wrap up our investigation into the secrecy apparatus behind UFO legacy programs, we will end our discussion with the concept of unrivaled secrecy. music various methods, operations, activities, and systems that legacy programs utilize to stay hidden that we could quantify as discrete or minor layers within our legacy onion. Critical secrecy mechanisms to discuss that won't feature their own section, but tie in intimately to major discussion points within our two-part investigation. Obviously, as we discussed today, legacy programs utilize contentonly SAPs to wave any and all carveout reporting requirements. These SAPs contain CPI only and feature no budget. Indeed, budget for such SAPs can be rolled into generic DoD, armed forces, etc. budgets. And we discussed as such with Air Force acquisition SAF AQ. we know the right code words and we know uh which reported special access programs and controlled access programs were essentially covering it up in uh music uh performing financial fraud um to hide the some of the paper trail, misappropriating funds and then taking haircuts across other black programs to funnel the money um uh to to to those kind of activities to keep it off books. Thanks to the sage council of David Grush, alongside the practice of making a White House special access program non-covert to wave reporting requirements with contentonly SAP application, we know that legacy programs have harnessed several methods of misappropriation of funds to keep legacy program records off books. My guesses, educated guesses might I add here for programs that get such haircuts that funnel into legacy would include USFS or US Forestry Service, BLM, Bureau of Land Management, and other obscure offices one would not immediately expect. A specific example here would be forest management money passing through USFS, but is ultimately diverted towards the crash retrieval portfolio. Alongside program haircuts, we also know that IRAD or independent research and development has been a method for legacy funding. >> Well, so that how does I mean I don't want to cut you off, but how does a program like that get funded? >> I will give you generalities. I can get very specific in a close session. Uh but a mis misappropriation of funds and uh >> does that mean does that mean that there is money in the budget that is said to go to a program but it doesn't and it goes to something else? >> Yes, I have specific knowledge of that. Yep. Do you think US corporations are over overcharging music for certain tech they're selling to the US government and that additional money is going to programs? >> Correct. Through something called IRA. >> Of course, one of the major investigations in my Northrup 2 project was exploring how Northrep and other contractors essentially began their own breakaway UFO retrieval and exploitation activities in music 2005 that featured little to no reporting to their original government handler. Further covert funding mechanisms for legacy programs likely include self-fund cutout activities. And we've actually seen this in part one with the Yellow Fruit USA in which Lieutenant Colonel Duncan staged his retirement from the US Army to operate Yellow Fruit activities through a quote unquote private consulting cutout called BSI. Additionally, I have talked in that sense at length about LTV Aerospace and their involvement in legacy architecture. LTV would evolve into e systems, a CIA cutout. I'm sure there are several other covert funding schemes to hide legacy financial books such as private capital and drug trafficking, but alas, the above mechanisms I do have specific knowledge on. Bob, I want to ask you about recent allegations you've made accusing intel agencies of hiding billions of dollars in secret government spending music from Congress. I mean, I we know about uh Air America. You know, CIA has done stuff like that. Even Iran Contra. So, we've seen this happen before. It's not, you know, it's not aliens, it's music what our government does. But tell us what you know about that. >> Yeah, certainly. Earlier in my career, I was a counter threat finance analyst. I actually worked in a special cell looking at arms trafficking and terrorist funding. So, I have that background in in counter finance. And what I found was there were haircuts taken to classified black programs music uh to fund this. There was also self-funding uh cutout companies if you're familiar and you mentioned Iran Contra and they had cutout companies um self-funding some of the arms purchases uh for the Contras. Uh but also uh criminal enterprises unfortunately is kind of the third way I saw laundering money. And I actually bumped into a very serious criminal enterprise and and all that information was actually reported to a Department of Justice and it led to um some federal investigations music and things I can't mention now, but uh uh the DOJ is actually handling that now cuz I bumped into a uh government-run music uh criminal enterprise that was siphoning money uh for this topic as well to pay for kind of the the crash retrieval operations off books. And make no mistake, the secrecy behind funding legacy programs is not discreet or minor within our onion analogy. I am only briefly touching on this now because of course in the future I would like to make a full project. Who knows, maybe a two-parter on the funding schemes and methods behind the legacy apparatus. We talked so much about program protection and program exposure mitigation within the legacy programs, but let's continue with a few specific examples. As we talked about with DARPA SID, there is of course the topic of wet works. I can think of no better possible alleged example than the hero who is the late Matthew Sullivan. As we know from Representative Berles, music Matthew Sullivan was set to deliver protected disclosures on the topic of UFO Legacy programs, whereas he mysteriously passed away from a quote unquote accidental overdose just 2 weeks prior. Sullivan was a decorated Air Force veteran who earned a bronze star for Valor in Operation Enduring Freedom. served within Air Force Intelligence, the National Security Agency, as well as the National Air and Space Intelligence Center, NASC. Many have wondered if indeed Sullivan was part of the legacy program and like swirling rumors suggested, had firstirhand experience with recovered UFO craft. To answer that question, who do you think David Grush is speaking about in this clip? we should be leveraging um you know national overhead enterprise and and other parts of our national intelligence enterprise on this topic but we use it you know in secret on the down low the night job of a certain analyst at NASC who also works for the the legacy program that's also analyzing this stuff without telling his boss that's essentially um how the program has um you know dealt with this over the time and I just think that that's a real travesty >> and Again, let's listen into what Dave Grush said recently on Fox News. >> And certainly recently, uh, my good air force friend Matthew calls sign Quake Sullivan music um, did uh, pass away mysteriously before he was willing, uh, to come to the Hill to testify about his knowledge of these activities and and music uh, Quake was a Bronstar recipient and an Air Force officer, intel officer friend of mine that I served with. And, you know, he was one of my, you know, sources in my investigation. and you know he you know he passed away mysteriously and that is an ongoing FBI matter so I won't characterize it and I'm open to you know different conclusions of what happened uh but just you know to your point there's been a lot of anomalous things that have happened to people >> as we know from Grush Borland Brown and others administrative terrorism is another vehicle harnessed by program protection elements to make a whistleblower or prospective whistleblower's life unbearable Since we just referenced Sid and I speak often on Northrup, perhaps this Matt Brown quote is quite poignant here. Key players in the legacy security architecture uh lately or currently at North Brahman. Uh and his name is >> name redacted. >> Show us a photo of that. >> I have it right here. I know you do. Before we look at this photo, not only that, you could prove it beyond a shadow of a doubt in the court of law. And if anything were to happen to you or anybody, then it'll all be put out anyway. >> Yes. And it's not just me. >> Yes. >> You know, in my last interview, I said that it's been a long hard road to find allies. Have them now. And I do >> and we are done taking punches and not punching back. >> Name redacted >> is responsible. >> Okay. So has been responsible for a lot of what you're talking about current snorts day. Current day as it relates to the UAP problem. He is a nexus point for legacy security. He is part of the dirty tricks department. People bring names that need to be handled to this individual. This person looks at those names, matches it to the capabilities to go achieve XYZ objectives and then the result is an ecosystem flooded with disinformation and psychological operations and targeted attacks against whistleblowers and their allies. >> How do you know it? >> So I cannot reveal everything about this because I am communicating it for others. >> And where um what is his current role in government if any? no role in government but in the military industrial complex. He is most recently at Northrup Grumman. And the little title he has here that people might find interesting is uh deputy uh SAPCO for DARPA. Within the David Grush Judicial Watch interview that we might have quoted a dozen times now and that keeps on giving, Grush spoke on some administrative terrorism that was leveraged against him to music destroy his career before, during, and after his public exposure. >> And there was all these manufactured allegations against me, whether from a security perspective, which is kind of funny because of what I did for a living, uh, from personal conduct, all that was unfounded and I maintained my, you know, TSSCI clearance. Uh but they, you know, went after several people I know administratively. Um even uh right after I left NGA, they went after my chief of staff, tried to revoke his clearance. They revoked my boss's clearance at the NRO and they just like they started like, well, who was Dave's enabler and who, you know, who might have told Dave something? And so they started potshotting people. And that's the insidious thing on the security mafia will do. It's, you know, your clearance is your livelihood and and your reputation from a conduct perspective. And I just know so many people in my orbit um that they went after either, you know, legally, administratively, ruin people's lives. I have friends of mine that have been out of work for three and a half years now. A very senior person in the in the SAP community uh was taken out and is still going through years of legal appeals. And even for my reprisal matter, music you know, trying to prove my case on that, I've been seeking documents since 2022 on that matter. I've been denied B7A, FOYA exemption, law enforcement records. Well, what's going on? What what investigations going on that affords that exemption? And I'm likely going to have to sue those law law enforcement agencies like I'm doing EDVA uh with with the Air Force complaint against myself because that's the only way I'm going to I'm going to get production in a timely fashion. And the process I feel is the punishment for a lot of whistleblowers. So there's this uh sophomoric analysis going around in the disclosure community. Oh well, they've never came after whistleblowers making classified disclosures to Congress. Well, that may be true literally on the books as a matter of legal record, but there's all these admin terrorism techniques they can do to you, your family. >> Unrivaled secrecy. We have spent at this point nearly 7 hours exhaustively discussing systems, methods, and loopholes legacy programs have taken for decades to carry out the retrieval, exploitation, and derivation of nonhuman technical vehicles with total impenetrable security. And the thing is, we are just scratching the surface here. Such systems we have talked about include translating the secrecy apparatus of the Manhattan Project onto what I dubbed the Manhattan Project 2.0, establishing the National Security Council's covert action 5412 committee special group as the early overall program coordinator, taking custody of recovered vehicles to atomic energy commission laboratories that would blossom to the current FFRDC go infrastructure within Legacy today. The 1954 Atomic Energy Act introducing a litany of further classification and security protocols protected by extreme statutory authority, breaking the programs into siloed containers hidden within cover offices and programs to hide from then black budget oversight reforms during the Cold War and permanently severing off the legacy program control group into a quasi government and music industry group of just over two dozen. In 1994, we discussed legacy activities exploiting special access, controlled access, and non-overt action programs. Specifically, the White House creating non-covert, contentonly, covert action special access programs to completely wave any reporting requirements and budgetary information. We analyze the SAP world to identify where gatekeeping structures are set up at the highest echelons of the SAP enterprise to restrict even credentialed individuals from accessing the programs if they do not possess a relevant need to know. We studied types and classifications of SAPs and ultimately discussed examples of such legacy SAPs crossing over with three relevant OSD departments that are critical to legacy operations. music USDI ins and USDs. Indeed, we also discussed DOE SAPS and their multiaceted authority from both EOE13526 and the 1954 Atomic Energy Act. We even analyzed misappropriation of funds used to funnel money to these programs, including haircuts across programs, IRAD, hidden budgets, self-fund, and possible illegal activity. We identified several program protection agencies deputized to enforce insider and outsider threat protection for the legacy infrastructure. These include a DARPA SID, AFOSIPJ, AFL CMCIP and DOE OICI. We even reviewed possible actions taken by these services such as wet works and administrative terrorism. Lastly, we have discussed disinformation and narrative management, highlighting a coordinated disinformation effort that has been in play since roughly 1953 with three major milestones. The Robertson music panel, Condan Committee, and Arrow. We studied a parallel effort to Arrow that while also operating as a narrative management campaign, originated from within a music different section of The Onion, Lou Alzando and the ATIP cover program. I'm sure I'll get flack for such discussion of Lou, but it is critical to discuss this topic and the nuances behind why there has always been so much controversy behind Alzando. Alzando is not the champion of disclosure we humans deserve. Once again, if Lu Alzando operated at the behest of legacy programs before, during, or after the music fake ATIP program, he should just come out and say it. He still does have time to do the right thing. And believe it or not, guys, there is still so much I haven't gotten to that I feel like I'm missing out by not including in our investigation. But this is already such a robust and long project. Two specific examples parallel to the SAP Enterprise come to music mind. Manage need to know MNTK codewords and constructs and alternative compensatory control measures, ACCMS. And yeah, music we'll probably get to these in the future. So, as we've seen here, the outermost protective layer of my legacy program pyramid, security, secrecy, and program protection, is no small fish to tackle. I sincerely hope over the course of this monolithic investigation, you have learned a thing or two as to how the legacy programs have maintained their covert, impenetrable nature. These programs are so secretive and siloed. We as Americans are facing a severe national issue where such legacy music programs are a pitiful shell of themselves rife with adversarial thiefts subject to insane brain music drain and a system of enormous waste. What's going on guys? It's Gerb. And I say this at the end of every single video, but I mean it especially now. If you're still here with me, thank you from the bottom of my heart. It means the most that you would watch this uh two-part at this point about 7-hour investigation with me. Uh learn with me, uh research with me, discover with me. So, thank you so much. I appreciate it more than you can ever possibly understand. Uh this two-part investigation has without a doubt been my favorite work to date. Uh, not only because this two-part has taken up so much of my life over the past couple of months. Uh, and that's not even considering the editing on the videos. That has taken forever. But, uh, the writing of the script, um, the researching, getting my thoughts together, collecting the statements, uh, into a digestible format that I've collected over the years. I really loved this project. And when I started off when I started off with this project, I thought it was going to be relatively simple, like I do with every single video. Uh but as you could see, I could make a part two. Uh this is a part two, I'm sorry, part three, possibly even a part four. You know, even in the SAP discussions, I didn't even get to manage need to know constructs and uh code words as well as ACCMS uh accredited compensatory control measures. And uh there's a lot more I would have loved to have talked about more program protection strategies, more of the history that we talked about so much in part one, but you know, if you're new to my channel, well, if you haven't watched part one, go watch it now because I'm about to say the same thing I said at the end of that. This is about the time, if you're new, where I do my post video rant. Uh, for me it's kind of a celebratory way to get on camera and just talk uh without a script, without worrying about how I'm going to construct the next statement, construct the next argument or lead into the next section. Uh, so it really is nice for me just to hop on here and talk with you guys and kind of share my thoughts at the end of the project without having to uh, you know, go ahead and edit the footage, uh, etc. So, uh, let's try and focus as much as we can here on part two today because I've already done a part one debrief and so on. Uh, part two, as I stated so often, the most important part of this project, and I'm going to stress it again, and maybe we'll spend a good amount of time talking about it here, is the specifics that the legacy programs has used uh to kind of manipulate and massage special access, controlled access, and covert action programs. Uh as I stated throughout this project, uh much of the argument about UFO legacy programs is presidents, temporary employees, the vast majority of the Congress and uh other uh appointed folks within the US government more often than not are not read into these programs. And I maintain that is true. As I've argued uh throughout my previous videos, throughout the two-part investigation today, is that the very legal and statutory basis for the legacy programs was born out of the executive branch, specifically the White House, specifically the National Security Council, uh specifically some stuff set up by Truman, and then more concretely the 5412 committee special group set up by Eisenhower. So uh since the 1950s that would be 1954 1955 for the NYSE 5412 uh the legacy program effort was concentrated out of the National Security Council up until about 1994. You know there was frag fragmentation of the programs uh throughout the Reagan administration, the ending of top secret code word access through executive order 12356, national security decision memorandum 159 and so forth. Uh but the controlling entity of the programs for the overwhelming majority of the program's lifespan has been the National Security Council. Now, as we talked about so much in 1994, there was a quasi industry and government control group of just over two dozen. I think if you watch back the video, you can find the exact number as I uh state it visually several times. Uh control was vested out of the National Security Council. Uh the primary reason here was uh fear over Clinton's disclosures and uh John M. Deutsch and and William Perry William Perry specifically his SAP reforms uh kind of it attempted to then serve as the primary gatekeeping structure. So before we talk about these specifics with contentonly and non-covert action programs, uh let's talk about the hierarchy of SAPs again because I do think this is very important. And of course we'll talk about the types of SAPs, uh the protection levels and just kind of rego over what we spent so much time talking about here. Uh the hierarchy and governance of special access programs. You have your component level SAP codes uh SAP central offices. Each element of the armed forces, so six total, has their own component level SAP co. Um, and the so does DARPA, so does the missile defense agency, and so do the joint chiefs of staff. And these component level SAP codes have kind of purview of all SAPs under their relevant departments. And then you have USD, now US W, I'm never going to call it the Department of War. It will always be the DoD for me. Uh, they have their own SAP code. And then you have the DoD level SAP code, the Department of Defense wide level SAP code. The DoD SAP code is kind of the interface and access approval authority basically for members of Congress. Uh the DoD SAP code also kind of governs SAP policy for all DoDwide uh SAPS. Above that you kind of have the senior review group which belongs to the SAPO, the oversight committee of SAPS. Uh the senior review group is a group of uh senior executive level officials, senior executive service individuals. Um I think that when Dave Gush in 2023 said uh senior executive officials instead of senior executive service uh this is because SCES members it's it's kind of more of a broad paintbrush. You know we talk about SCES individuals like William E Mccclure Randall G. Walden Terry Phillips Liam Russ etc. But there's also DIS defense intelligence senior executive service. This would be somebody like Jay Stratton while he was on O andi. So senior executive officials just kind of a broad term for that both in and out of government. Uh the senior review group is supposed to prevent kind of duplication of SAPS across the DoD and we know with legacy programs this hasn't been done. I do not mean it hyperbole when I talk about the army and another branch of the armed forces uh kind of having duplicated special access programs on the exotic front kind of crossing over doing the same thing I mean to say with no crossover of personnel program security officers SAP security officers uh contractors security officers etc completely siloed projects and then you have the SAPO and kind of the SAPO is where a lot of decisionm is made of special access programs. Uh we also had the it was the senior SAP working group we didn't really talk about but the the SAP is kind of the upper echelon here and from what I understand from the Wilson Davis notes that this is indeed true is in 1994 the SAP and the SAPOX SRG kind of got put in place as a gatekeeping structure uh for access into the legacy programs. This isn't to be confused with something like the Majestic 12. uh the Majestic 12 or modernday it's not the MJ27 but a group of uh quasi industry and government control group these are not the gatekeeping structure for the programs although they do involve for example if you have somebody like a DARPADID individual who's in this new group of over two dozen who needs somebody gone um that would be something that would be made at that sort of executive level position and then your program protection agencies would deal with that person But the the SAPO and their SRG are just more of of gatekeepers. Okay. They they keep the gates for specifically cleared personnel and uh to access the programs and manage need to know. Uh we know with Admiral Thomas Wilson that even though he was deputy director of the DIA at the time he was denied access. I'm aware of another four-star general who had no idea the programs existed and was somehow able to use his credentials and he had really good credentials after a period of time to uh brute force his way into the programs. But you know if you want to talk about your senior review group and within the Wilson Davis notes the watch committee uh the watch committee there would be directly connected possibly even carryover members uh to that uh quasi government and industry control group of of just over two dozen. So uh you know that's without even talking about the SAP security officers, PSOS, uh even further access approval authorities, but but that's sort of the hierarchy and governance of SAPs and at the SAP co but more importantly SAP and SRG level that's where a lot of the gatekeeping into the programs are. Uh we talked about the types of SAPS types of SAPS being acquisition which comprise about 75 to 80% of all SAPs, intelligence and operations and support. And I gave what I thought was a pretty a pretty good example of if you have a triangular airframe that incorporates several elements of of nonhuman technology. An acquisition sap uh you know you remember we have sap umbrellas but an acquisition sap on this project would be how this airframe is built. If this airframe in the example I used used a um reverse engineered propulsion system and electrooptic cloaking. Gosh I talk about electrooptic cloaking stripped from craft quite a lot don't I? I hope some people have picked up on that. Uh the intelligence sap would protect how we know what we know. Um kind of the intelligence behind that craft recovery and how those materials or those systems were deemed to be exploitable and the operations and support SAP would support how and where this craft or vehicle is used. Um maybe another example we could kind of chew through live would be the Immaculate Constellation activity. Uh recently Dave Grush has talked about which I I'm so happy he has because now I can kind of state this fact because I was also aware of this uh that the Immaculate Constellation activity was run out of the National Security Council uh established in about 2017. I reckon this was likely an intelligence sap uh just as I reckon that the ATIP was kind of even though an informal working group kind of disguised as an intelligence app. I'll I'll kind of say why there. Uh, recently at his uh I think it was California show where Jeremy Corbell was on, Lou Alzando was asked several questions about James Clapper and OAP ATIP. I apologize. My mind's running right now, guys. I have a million thoughts going through my head. So, if I'm tripping up, I'm so sorry. Uh Lou I I I reckon he kind of dug himself into more hot waters by saying that ATIP was a subsap to OAP. Now remember from the SAP umbrella, you have SAPS, you have the SAP umbrella, you have the sub compartments and you have even further compartmentation down to where similar CPI is grouped and so forth. Uh this isn't true. ATIP was an informal working group. So, uh, in my opinion, and I don't think it's my opinion, but, um, I don't think that's true that ATIP was a subsap to the OSAP. Um, ATIP directly operated out of the National Security Council, uh, and was a cover for several National Security Council activities. And as Lou continues to dodge the questions around Clapper, I wonder who gave uh, cover for these activities that ATIP was kind of acting through um, as a cover. So, there's a lot of pieces to pick up there. And then the uh the immaculate constellation activity I also believe was an intelligent SAP. Uh but let's talk about the protection levels of SAPs because my brain wants to go right now into content only and non-covert action programs, but I'm just trying to progress logically as we get there. We know that SAP's protection levels come unacnowledged which generally has an unclassified budget and a lot of congressional members can get a readin onto that. Unagnowledged which carry multitudes higher security budget than standard acknowledged SAPs. Often time the budgets for unacknowledged SAPs are kind of rolled into generic budgets or they are completely classified and then waved which are the most serious SAPs possible where the SAP which kind of reviews the the need and continued need for wave statuses because the SAP and its permanent members and its SRG are read into all waved use apps throughout the entire US government at least within the DoD. uh waved use apps are extremely serious and a lot of the times only the gang of eight or gang of four are supposed to be read into these projects but as we know with the legacy programs oftent times this is avoided and uh there's key congress people put here and there who are read into such activities um I would look at some senators or congressmen who were family or related to former presidents to kind of find out some some people who might fit that bill and then we know there's there's further uh uh kind of security not classifications but uh security protections that can be put on. We know bigoted as Dave Grush talked about which is by name. Uh we also of course know the more much more standard no foreign not releasable to foreign nationals. And I mentioned no foreign because I'm specifically aware of programs that utilize the no foreign carveout. Um back in their heyday those programs have ended. I imagine their records and materials have been either destroyed or buried. Um, but I am confident that that selection of of specific programs not only existed but uh dealt with some pretty pretty wide wide topics from reverse engineering to crash retrievalss to the study of biologics. So, now let's get finally to the real meat and potatoes and most interesting and most important part of this video in my opinion, which is how can legacy programs use special access programs to completely wave any carveout or reporting requirements and maintain total secrecy? Because this, after all, if we're studying the legacy programs in the modern day, is the whole crux and most important piece of this video. Dave Gusher's Judi Judicial Watch interview is sublime. It's probably the best interview I've ever seen on the topic. It's fantastic. And Dave Gush gave so many nuggets not only to kind of shout out that the National Security Council's 5412 committee with five initial members was sort of the initial program coordinator for the legacy structure, but so much more. Uh Dave talked about some of the tricks of the trade that have been used by the programs and that's to take covert action programs which are outlined by 50 US code 3093. Uh the 3093 specifically was established in the late uh sorry early 1990s. Uh but covert action goes way deeper. Covert action was born kind of officially out of the 1947 National Security Act and and cemented in the 1954 uh uh policy on covert action by Eisenhower which established the 5412 committee and its special group. Uh the 5412 committee was established to have oversight and purview of covert actions. Uh so inherently as I stated that if you have UFO legacy programs operating out of the National Security Council's 5412 committee special group which is true these activities would inherently be classified as covert action. As the epochs evolved these activities would be applicable under covert action programs as 50 US code 3093. So, as Dave Grush said, these covert action programs were transitioned into non-covert action programs, White House SAPs, which effective effectively waved all reporting and carveout requirements. Uh the the most important part of this video is how do you take a White House SAP uh title 10 US code 119 a slash a covert action program 30 US code uh 50 US code 3093 and how do you get this program to operate in the gray area between title 10 and title 50 with no reporting and no carveout requirements. There's so many pieces that if you've watched any of my other videos, you can kind of pick up on this, but this is the application of contentonly SAPs. Contentonly SAPs are not a type of SAP nor a protection level, but a budgetary tier/administrative designation. contentonly SAPs contain CPI critical program information only and do not have a budget or do not have an applicable budget because it is rolled into generic DoD armed forces or other defense related budgets. This is critical. This is why one of the hu one of the biggest talking points is how are these programs funded? There's so much talk about misappropriation of funds. The legacy programs have had to get ultra creative with funding schemes because the budget is outside of the program. The budget is outside of the program. We know and and these contentonly SAPs can still operate within a SAP umbrella or towards the top of a SAP umbrella where other uh activities compartments etc are below the contentonly SAP. So the actual crash retrieval operations reverse engineering are not done within the contentonly SAP or content only SAP umbrella but are attributable to that SAP. So that's why we have haircuts across programs. Uh that's why we have self-fund from agency cutout activities formerly like e systems. Uh that's why we have haircuts across the US forestry service, bureau of land management etc. And that's why disturbingly we have uh uh criminal enterprises that Dave Grush spoke of on Fox News. I have had the displeasure of learning a little bit more about those. And uh uh I I I really hope there is a continued federal investigation into some of the u criminal enterprise activities around these projects. And then of course we know from witness ed there's large swaths of money that reach Air Force acquisition and before any sort of review from Air Force Financial Management SAF FM are thrown away into some black hole pot that Ed kind of figured was a joint air force and NRO project. So contentonly SAPs this is one of the biggest tools of the trade. And guys this speaks to something which is far more concerning. Uh some of my contemporaries, I know uh Steven Greer does this quite a bit, uh states the legacy program apparatus is a cabal of illegal activity and are inherently unconstitutional. So everybody who signed a non-disclosure agreement at the behest of these uh special access projects, he calls them. Uh they're not the the NDAs inherently aren't real and you can violate them and there's no legal ramifications. That is not true. The biggest concern here is that the regulatory and statutory authority behind the legacy programs are absolutely legal. They exist in a gray area. They exist because of massaging of the special access program enterprise and control and governance structure. And they exist because of classified presidential executive orders back in the 40s and 50s. But the very SAPs themselves are not illegal. They're not they are uncon unconstitutional but not illegal. Now, the activities that these uh programs and special access programs and activities do, those are highly illegal. The misappropriation of funds, uh the possible blue-on-blue action that has been suffered in the past, the myriad white and blue collar crimes, those are illegal. But the very existence of the programs themselves, those are not illegal because there has been purposefully sought after gray areas in which to hide these programs. I these programs have matured for 80 plus years at this point. You got to think there there have been really crafty ways to hide this pro these programs and and the statutory authority behind these programs between title 10 title 50 authorities so that even empowered investigators like Dave Grush when they find the programs and they take their information to the inspector general it's going to be really dang hard for individuals with appropriate access credentials to follow up on that information. Uh these programs have gotten great at secrecy and like I talked about even though over the time epochs the programs have broken themselves apart from a once centralized effort under NSE 5412 special group uh into a quasi industry government and control group. The one thing that has gotten better is the secrecy apparatus of the programs. We face brain drain today. There's no collaboration across compartments. North Grumman's doing their own thing. Uh I mean they're still active in some NSC legacy activities, but for all in in large they're doing their own thing. We're at risk of severe brain drain. Has progress stagnated? I'm not sure. Uh if progress has stagnated, it would be post 2009 um when Dick Cheney left office. But what needs to happen alongside disclosure is a complete reorganization of oversight in the legacy program hierarchy. Imagine the brain power behind this program set if it was completely constitutional, above board, sure, still protected by waved use, but still reported to appropriate gang of eight uh congressional intelligence committees, etc., and had presidential overview. This could be the dawn of a new age for US uh science, technology, space programs. But these programs need to be back under traditional oversight channels. And it's not impossible, but it's very challenging because ever since I mean the dominoes were kind of put in place when the program was relegated to NC 5412, but really since Reagan in the early 1980s once yellow fruit was uncovered, uh these programs have been scattering, folding in on themselves, um I like to kind of visualize this is uh there's some string physicists who were creating objects uh shapes to kind of represent the manifold of like 11thdimensional space. I'm not sure who the physicist was, and I'm not sure where to find these objects. But that's how I imagine the legacy structure. Something infinitely more complex than a a test or a Mobius cube consistently folding in on itself, expanding and contracting in various areas where you might be able to look at the surface area of one part of the program, but it's constantly evolving. And, you know, I've done my best to try and capture that evolution throughout this uh throughout this series, but there's still so much more to cover. I'm going along on my rant, guys. Uh, we haven't even gotten to program protection agencies, but I've talked about those so much, especially the SID or narrative/disinformation control. I'm sure I'll get some flack about Lu Alisando, but I stand for transparency. Uh, partial disclosure due to protection of equities or protection of uh of co-workers or bosses or individuals that have worked within the legacy architecture for years. That's not going to fly right now. Uh, that sort of push within the age of disclosure, it's not going to continue to work. Uh this is why we need individuals like David Grush who are completely missionoriented open kimono not holding back besides not saying stuff to where he's going to get prosecuted or go to jail because he's had to avoid that in the past and I don't blame the guy for not incriminating himself and subjecting himself to espionage or treason by stating this is exactly where the crafts and biologics that I am aware of are are buried. Uh so these partial disclosure campaigns that have been pushed since 2020 2017 really back since the ATIP uh cover program was initiated, these won't fly. And the again if Lou Alzando was part of the legacy programs, he should just come out and say it. There's still time to do the right thing. Uh but as he said on a recent show, history will remember him as a hero or one of the biggest villains. I speak directly to you now, Mr. Alzando. you have a chance to still be an American hero. Uh if there is information you are holding on to, individuals you are protecting, lies you are telling, you will go down as a villain. Uh and as an American, I I hope the right choices can be made. That's that's all I'll say because I don't have a I can't direct you on on how to act, but now is the time to to push forward for disclosure and and really open transparency, especially your knowledge and involvement within the uh program data set. So, that's all I'll say there. And again, I still think they're worthy questions to be asked, like did Mr. Alzando expose Tom Dong um to elements of the Immaculate Constellation Project back in 2017 when he left as director of NPMS and join TTSA where he was liaison to the NRO, NGA agency, and several other uh agencies and services. I say this all allegedly. Uh I'm a character. I'm playing a character and this is all for entertainment purposes. But guys, thank you so much for joining me. From the bottom of my heart, it means the most. I'm recording this on the 17th of June, 2026. The video is to be posted the 19th. I got some awesome stuff coming up at the end of the month. I can't wait for you guys to watch that already on my whiteboard over here. I have the next three projects lined out. The next one I'm super excited to get to. It's going to be a blast. Uh so, thank you all so much for joining me. Uh remember, I do have a Patreon. I don't gatekeep content there. Uh so only support what you think the channel's worth. Who knows, maybe in the future I can do like uh a live every other week for Patreon and YouTube members because I have YouTube membership as well. Uh but right now I I I'm just pushing so hard to make real change in this topic. Please uh forgive me if I can't uh provide additional content right now for that. But everybody who supports that, I thank you so much from the bottom of my heart. You allow me to do this. You allow me to buy that Panasonic Tough book over the over my shoulder over there. Uh but please also remember to like and subscribe. U follow the Dreamland Motel, Xander Jones. He makes amazing music for this. Uh follow Mr. Justin who is a member of the Night Shift podcast. Uh he is currently helping me make my website. He's a wonderful man. He made that flux liner over my left shoulder. Incredible guy. Follow him. Follow Xander Jones. Follow Rob Jones. Follow Kermit. Follow all my friends who are doing great stuff in this work. Uh support Dave Grush. Support Dylan Borland. Support Matt Brown. And guys, thank you so much from the this end of Rand. if you can see, inspired me more than any other I've done. So, thank you guys. And I will catch you all in the next project. And please look forward to that because I'm really darn excited for it.