UAP Gerb — “The Manhattan Project 2.0: the Secrecy of UFO Crash Retrieval Programs” [VOL.1]
Source: UAP Gerb (YouTube channel @UAPGerb). Long-form documentary, Volume 1 of his crash-retrieval-secrecy series. URL: https://youtu.be/jR-h5p2bd-A Published: 2026-05-01. Duration: 3:31:13. Views at capture: ~193,600. Captured: 2026-06-19 via OpenAI Whisper (scripts/speech_to_text_remote.py, —timestamps; auto-chunked at 25MB, timestamps continuous across chunks). Single narrator (Gerb), with occasional embedded archival audio clips. Verbatim machine transcription — proper nouns, acronyms, and names may be mis-rendered; verify any specific citation against the video. What this is: Gerb’s core thesis statement — the “Manhattan Project 2.0” framing of an ~80-90-year UFO reverse-engineering program, established by at least 1947, that has degraded from a centralized effort into a fractured, siloed apparatus of special-access, unacknowledged-SAP, and controlled-access programs across the IC, armed forces, national labs, and defense-industrial base. Primary source for gerb-uap-open-source-researcher.
[0.0s → 14.0s] 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 We took the Manhattan Project secrecy and overlaid it on this issue because that secrecy worked well for atomic bomb [15.2s → 30.6s] developments and whatnots and and certainly this whole program in a nutshell for to like summarize the 90 plus years of history it is a reverse engineering program To garner some kind of insight [32.4s → 63.2s] And very few people kind of had that top-down could look across the silos and see what was going on It just became very dysfunctional and they were afraid of people being too cross-briefed into the different silos per counter espionage counter-intelligence that you know, they were gonna remember a bulk of this program is done during the Cold War and You know, we were afraid of Russian spies Soviet moles and so we made it ultra locked down but to the detriment of national security [65.7s → 85.8s] We have spent more than two billion dollars on the greatest scientific gamble in history and We have won But the greatest marvel is not the size of the enterprise its secrecy or its cost But the achievement of scientific brains in making it work [87.2s → 96.9s] There aren’t in fact very many secrets. There aren’t secrets about the world of nature There are secrets about the thoughts and intentions of men [98.7s → 140.5s] Sometimes they’re secret because a man doesn’t like to know what he’s up to if he can avoid it The Singular purpose of my channel is to uncover the UFO legacy program architecture a labyrinthine yet fractured ecosystem of special access unacknowledged special access and controlled access programs That are housed within elements of the United States government armed forces and intelligence community that are tasked with the retrieval collection storage Exploitation and derivation of non-human technical vehicles and technologies of unknown origin [142.3s → 161.0s] What was once a galvanized and unified effort of the United States most prestigious scientists general and flag officers seasoned politicians and senior statesmen established by at least 1947 under what we might call the quote-unquote Manhattan Project 2.0 [162.4s → 202.7s] clandestine and covert UFO programs now exist as scattered fiefdoms a siloed and viciously compartmentalized system in which several Administrative elements now own a piece of the former centralized effort Lacking a formal recognized oversight group presiding over all NHI recovery and exploitation activities Indeed after decades of quite observable cracks showing a loosening and weakening grip of a singular centralized program effort The Golden Age of the legacy apparatus appears to have conclusively ended in the early 2000s [203.4s → 235.1s] when according to David Grush certain contractors in my informed opinion Northrop Grumman Harnessed company-funded research and development aka IRAD to establish breakaway UFO retrieval and exploitation projects that became unaccountable to their original government handler and Finally complete oversight was lost by 2009 when Vice President Dick Cheney The last man to harness centralized leadership of these activities left office [235.9s → 275.2s] Whether it be lieutenant-general James Clapper the closest thing to a Cheney esque centralized oversight figure while serving as Director of National Intelligence Vannevar Bush who operated as a senior scientific figure during the 1940s and 1950s Manhattan Project 2.0 Mr. Terry Phillips who has allegedly engaged in reprisals against whistleblowers With an air force sat channels and Northrop Grumman or Edward C Aldrich who seemingly aided in the evolution of UFO programs Hiding within special access programs during the early 1980s [276.0s → 295.2s] My work aims to span decades to analyze not just the individuals But also places offices directorates laws Scandals, etc That have played an imperative role within the ever-changing and morphing legacy program structure over the decades [296.5s → 334.7s] Thus I’ve arrived at a functional ecosystem to represent the modern-day UFO legacy program structure that I call the legacy pyramid and Regular viewers bear with me guys, because I promise I will keep this very brief At the top of this pyramid sits the control group a now tenuous position once helmed by presidents career senior executive officials Dick Cheney Clapper in a knee-capped capacity that now sits empty with possibly a handful of individuals understanding the full scope of NHI retrieval and exploitation efforts [335.7s → 371.0s] Below the control group sits program administration best thought of by me as several silo containers housing specific programs and directives under specific elements of the armed forces and intelligence community an example here includes the National Security Council still maintaining a recovery effort of technical vehicles of exotic origin and Another specific example a selection of Air Force programs Involving numerous offices listed below for a short narrow and strict oversight chain [371.7s → 381.6s] That operates out in the Western Ranges that performs test and evaluation on airframes incorporating one or more elements of non-human technologies [383.0s → 408.1s] Below the administration level of my pyramid sits federally funded research and development centers or FFR DC’s and Gocos or government-owned contractor operated institutions These Gocos structures allow the US government to attract the brightest of industry and subject matter experts While still retaining strict control over programs materials breakthroughs, etc [409.3s → 445.9s] Such FFR DC Gocos efforts have been critical to the legacy program effort since the Truman administration all the way back to the late 1940s in which custody of recovered vehicles were given to now Department of Energy and former Atomic Energy Commission National Labs like Sandia, Los Alamos and Oak Ridge more specific examples of FFR DC’s and Gocos include the MITRE Corporation, RAND Corporation, Aerospace Corporation, CNA Corporation and Air Force Plant 42 within Palmdale, California [446.5s → 480.7s] At the bottom most layer of my pyramid sits the most security vulnerable aspect of the legacy structure defense industrial base 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 or special program directors while engineers Scientists and technicians who actually brush elbows with the programs through carve-out contracts are largely kept in the dark [482.7s → 521.9s] The mortar that binds this structure together, well, this is the US defense industrial base whose authoritative channels are often bypassed to allow UFO legacy programs to harness any US military and intelligence asset needed to accomplish these covert mission directives And finally, and our topic for this new two-part series, the limestone casing that once encapsulated the Great Pyramids of Giza to protect these structures from the elements Well, our equivalent today is the UFO legacy program security apparatus [523.7s → 533.9s] One of the most appropriate and poignant questions one could ask about the existence of UFO legacy programs is How could such technology, [534.6s → 541.1s] biologics, crash retrievals, and programs be kept secret and kept secret for nearly 90 years at that? [542.1s → 570.0s] After all, according to most conventional and wise thinking, the US government can’t keep a secret, right? I have spent so much time in my projects discussing the who, what, when, where, and why of UFO legacy programs that I think it is appropriate to finally step back and analyze the security apparatus behind these activities How program secrecy has evolved over time? [570.8s → 577.1s] What classification systems and directives provide foundational cover for covert UFO programs? [577.8s → 592.7s] What individuals and program protection offices have safeguarded these secrets for decades? How disinformation and narrative shaping is weaponized to reinforce a strong stigma around the UFO topic? [593.6s → 598.9s] And overall, how this seemingly infinitely layered secrecy apparatus is organized? [600.9s → 638.3s] Because at the end of the day here, covert and highly compartmented waived unacknowledged special access programs or WSAPs Facilitating and gatekeeping knowledge and need-to-know access to the greatest secret in the history of mankind Which is the presence and procurement of non-human technology and their occasional biological operators Existing as a hidden shadow Symbiotically attached to the United States government, armed forces, and intelligence community would require an ever-evolving impenetrable and stalwart [638.3s → 645.3s] Architecture to stay hidden from even presidents and other elected quote-unquote temporary employees [645.6s → 688.1s] Would it not? Thus for this massive pursuit, we will frame the legacy security architecture as an onion Layers upon layers of secrecy where the center of the onion, the core secrets and extant presence of the UFO crash Retrieval and exploitation portfolio is always hidden and obscured by another layer of protection and secrecy This onion analogy can be harnessed to understand so much of the program protection at play here and Not just in the modern day, but dating back decades as well as to the inception of this Manhattan Project 2.0 [689.1s → 723.8s] From stripping the Manhattan Project secrecy architecture to classified presidential executive orders under Truman and Eisenhower to the 1954 atomic energy agreements to Cold War special access program expansions and black project oversight reforms to close shave Pentagon audits to the ATIP program perception management campaign and Attempts to talk about the subject outside of this proverbial onion To the antibodies David Grush awoke when investigating the topic in a legal and empowered manner [724.3s → 761.3s] To the disgraced Sean Kirkpatrick in his ineffective all-domain anomaly resolution office Every one of these specific instances of program protection and secrecy as well as myriad others over the decades Can be seen in reference to layers of this outlined onion So indeed over the course of this pursuit We will attempt to peel back these layers of embedded secrecy where layers protect layers that obscure core secrets Analyze security structures behind the early legacy program effort again. Also known as the Manhattan Project 2.0 [762.0s → 800.6s] Observe changing laws and oversight regarding black projects and early special access programs during the height of the Cold War Unveil various program protection agencies and specific personnel that have been deputized and weaponized to enforce insider and outsider threat protection for the legacy efforts recognize the ever-present disinformation in narrative management that shapes the UFO topic and perform a critical analysis on the monumental apparatus that empowers UFO legacy programs with Unrivaled secrecy and [801.6s → 838.0s] In addition to everything I just said above I speak so often in my projects about UFO programs being hidden within SAPS or USAPS Aka special access and unacknowledged special access programs. I Think it’s finally about time. We take an opportunity to step back and discuss what exactly special access programs are How SAPS developed from post-world war 2 to today how additional security and reporting controls can be added to SAPS to restrict read-on-access and existence acknowledgement and [838.6s → 876.6s] ultimately study the crossover between the SAP and UFO legacy program ecosystem and Just so we’re clear guys this project aims to be Absolutely massive thus I am tackling this project in two separate parts So today we will devote hours Towards analyzing the blanketing of the Manhattan Project secrecy architecture on to early legacy efforts Which we will call the Manhattan Project 2.0 We will follow the Manhattan Project 2.0 throughout the decades during the Cold War and see how this once [877.1s → 909.9s] Centralized and stalwart effort began to splinter and scatter itself into the wind all to maintain total secrecy in an ever-changing US government structure So with all that out of the way sit back Mark your notes special access required and let us dive in to the secrecy and security mechanisms that embolden UFO legacy programs to operate within the shadows with unrivaled power Reach and secrecy You [932.1s → 959.7s] Yeah, I think there should be a public acknowledgement strategy Some of that needs to come from the White House in terms of how much that we acknowledge and reveal to the public But I would like to see greater integration with this problem set in our architectures a lot of it was We’ll call it in in an onion fashion in a lot of the space architectures a lot of the people in the audience are familiar with both classified and you know over white side of space world as [959.9s → 998.2s] I said throughout our introduction the greatest analogy in which we can effectively Conceptualize the UFO legacy program structure is with an onion where the core program elements senior leaders materials biologics recovered craft internal documents, etc Are protected and obfuscated by endless layers of protection We’re even seasoned flag officers and intelligence agency directors Like Admiral Thomas Wilson can only get so close and so many layers down towards UFO recovery and exploitation activities before program antibodies push back and [999.3s → 1037.0s] Thus this short section outline detailing the onion will serve as today’s executive summary Where we will further flesh out the onion analogy and discuss a handful of the layers We will dive into in great detail during our two-part investigation the onion UFO legacy program protection model is structured to be Impenetrable and impossible to navigate for non read-on or need-to-know individuals that exist outside of this security apparatus but is also structured to be impossible for actual legacy program personnel relegated to specific [1037.3s → 1075.4s] Compartmentalized activities within the legacy programs to peer across or further down the onion. I Think often to an individual who claimed to me that I believe by the way to have operated for years on legacy programs Security for the Navy and a specific FFRDC’s operations regarding a USO activity This individual was literally tasked with giving what he referred to as the quote-unquote Onion briefing to specific senior statesmen general and flag officers and other relevant special programs personnel hundreds of times I [1075.5s → 1085.0s] Will never forget when this person said to me quotes I was on the legacy program when I found out there were others end quote [1086.3s → 1104.5s] But I digress though intriguing and poignant this individual statements are not the focus of today’s investigation Nor are these several other claimed first handers I have spoken with who comment on the existence of the quote-unquote onion within and across their respective program silo [1105.8s → 1144.1s] Before launching full steam ahead into our two-part investigation Let’s outline our theoretical onion model and speak on several of the individual layers we are going to spend ample amounts of time investigating and Again, recall the core of this system holds the beating heart of UFO legacy activities the retrieval storage exploitation and derivation of non-human technical vehicles and their occasional biological occupants The original body of this onion was made flesh in 1947 under the presidential administration of Harry Truman [1144.7s → 1180.4s] Though elements of the United States leadership likely had awareness and familiarity of crashed non-human technical vehicles before and I am referencing the 1933 Magenta, Italy crash, of course for all intents and purposes immediately following 1947’s Roswell appears to be when organized and empowered efforts began to collect and exploit these rare and coveted quote-unquote exotic technologies as We will discuss ad nauseum today. The early UFO legacy program structure was [1181.0s → 1212.4s] Directly copied from the United States atomic weapons project the infamous Manhattan project from compartmentalization organizational architecture physical security classification and information control and political shielding slash cover this system of Compartmenting covert operations worked so well for the Manhattan project It seemingly was directly translated onto a national effort even more secret than the atomic project [1214.1s → 1249.8s] With a keen and trained eye here We can actually outline several figures who likely served paramount roles in draping the Manhattan project secrecy blanket over UFO crash retrieval and exploitation programs and These include dr. Vannevar Bush and George C. Marshall. I Even theorize we could observe a clear inspiration for the architecture of clandestine UFO crash retrieval teams from Bush’s and Marshall’s work on the Manhattan project during World War two the Alsos missions and T force an [1250.3s → 1284.2s] organized Manhattan project intelligence operation to physically secured Nazi scientists facilities Laboratories technology and materials on the war’s front lines to gauge progress in the Nazi atomic program that operated completely separate from traditional military intelligence channels Indeed as we will discuss throughout today, it appears the late 1940s and early 1950s Observed the Truman administration and Eisenhower administration employ several classified presidential executive orders [1284.9s → 1322.1s] Infamously sometimes referred to as Pete’s or presidential emergency action documents that equipped emboldened weaponized and galvanized early legacy efforts These include as we will touch on an alleged 1948 classified presidential executive order by Truman that gave custody of recovered UFOs to Atomic Energy Commission GoCo or government-owned contractor operated national laboratories that would evolve into modern-day federally funded research and development centers such as Sandia, Los Alamos, Lawrence Livermore and Oak Ridge as [1322.9s → 1358.6s] far as I understand it was president Dwight D Eisenhower who conducted the lion’s share of establishing the early framework for UFO legacy activities What we have called and will call throughout today as the Manhattan Project 2.0 Such as establishing a covert UFO control group hidden within the National Security Council’s 5412 committee The United States Atomic Energy Commission is responsible to the president and accounts to the Congress principally through the Joint Committee on Atomic Energy The [1359.3s → 1371.5s] Chairman and the commissioners of the AEC are like a chairman and a board of directors in industry The general manager and the division directors like the president and vice presidents of a private company [1374.0s → 1394.1s] To carry out the United States Atomic Energy policy AEC officials direct a vast nationwide industrial scientific and educational complex The cost More than two billion dollars a year about half for national security the rest for peaceful uses [1397.9s → 1427.6s] Much of the vast research and development work is done in national laboratories across the country Brookhaven in New York And Oak Ridge in Tennessee Argonne in Illinois Los Alamos in New Mexico and Lawrence Radiation Laboratory in California the secrecy surrounding the programs in the 1950s were exponentially amplified with the 1954 Atomic Energy Agreement [1427.6s → 1444.2s] Which expanded upon the concept of restricted data and a litany of creative classification standards including? Transclassified foreign nuclear information foreign intelligence information and special nuclear material we will speak on later They’re basically treating this as [1445.7s → 1485.8s] Nuclear secrets because it gives off a you know nuclear radiation because if you look at the ultra-vague definition of special nuclear material Which is section 51 the Atomic Energy Act in 1954 it says anything that gives off a sizable amount of atomic energy Literally, that’s what it says well, what sizable and What legal gymnastics are you saying this stuff which is obviously not a well who knows maybe it is Nuclear weapon and you’re saying this is a US nuclear secret. You’re trans classifying it into a nuclear secret Which I understand [1486.5s → 1527.1s] Maybe at first why they did that Though the early days of UFO legacy activities were deep-sixed and relegated to the highest levels of need-to-know Access within the United States government this Manhattan project 2.0 seems to be a stark Contrast to the legacy structure of today in which the legacy glory days once employed some of the United States most prolific scientists general officers senior statesmen, etc while today most Individuals involved in the programs are sheep-dipped Data-masked or the names the populace has never and will never hear of [1529.0s → 1549.1s] Lastly today, we will also study the 1970s 1980s and onward in which due to various special access program expansions Oversight reforms legal molding and the looming threat of Soviet spycraft. I Strongly hypothesize the Manhattan project 2.0 began to break itself into pieces [1550.3s → 1588.0s] Effectively scattering itself into the wind to morph and adapt hiding within cover programs leveraging creative funding mechanisms and Amplifying layers of secrecy and security effectively leading to the siloed program architecture of today and giving rise to the modern-day onion Later on down the line part two of our investigation will begin moving into the modern era of legacy activities and we will discuss the concept of Unrivaled secrecy and discuss numerous systems and onion layers the UFO legacy program portfolio is harnessed [1588.0s → 1624.3s] to maintain covert operations including a broad range of cover offices and programs specifically within the Air Force Navy and DARPA The concept of dual-hatted positions within the US Armed Forces and I see That actually functions similar to a CIA knock or non-official cover various funding schemes legacy programs harnessed to capture enormous funds while staying under the radar Integral elements within USG crucial to maintaining the onion structure and so much more [1625.3s → 1663.1s] Within part two, I will additionally seek to propose a rough outline structure of the onion as it exists today defining and exploring several layers within the legacy framework Remember almost everything we discuss in these two parts from cover offices and programs to trans classified foreign nuclear information and special nuclear material as detailed in the 1954 atomic energy agreement To shaving off small amounts of money from a wide swath of programs to fund program activities Well, these are all layers of the legacy structure onion though [1663.1s → 1696.1s] There are a handful of quote-unquote major layers I would like to define that I believe are imperative to understanding this security structure These will include the outermost layer or skin of the onion disinformation and narrative management This effort will see us discuss multiple initiatives from the 1950s onward to the modern-day all domain anomaly resolution office That have attempted to swell public perception of the UFO topic as well as perpetuate the decades-long stigma surrounding the topic [1697.1s → 1724.1s] Whilst on the subject we will also speak on narrative management Methods the legacy program structure have taken for partial Transparency or derived methods to talk about the topic outside of the onion these include the a tip cover program effort with to the Stars Academy or TTSA an Attempts to establish a democratic political candidate Hillary Clinton, of course as the disclosure president [1724.9s → 1738.6s] What is intriguing about this partial transparency effort is it seems to originate from within the onion itself? Specifically from the National Security Council and senior UFO control group individual lieutenant-general James Clapper [1739.8s → 1776.9s] Within part two as well as we spoke of in the intro We will discuss a full overview of the US classification system and special access programs or SAPS This section will explore how exactly legacy activities hide within SAPS The history of SAPS and how SAPS can become waived and unacknowledged To hide from even the US Congress and temporary employees like presidential administrations layers below the special access program model We will explore program protection agencies in which individuals [1777.3s → 1808.9s] Directorates or units within agencies that actually protect the most critical US SAPS imperative to national security Seem to have been deputized as assets enforcing the inner layers of the legacy onion in a sense these program protection agencies seem to act like antibodies that swarm to mitigate and Neutralize both insider and outsider threats that threaten the complete secrecy of the legacy structure For all intents and purposes [1808.9s → 1848.5s] This seems to be what David Grush encountered during his investigation into UFO crash retrieval and exploitation activities Some offices here that we will talk about include DOD and component level SAP codes or special access program central offices the AFOS IPJ or office of special investigations office of special projects DARPA CID or security and intelligence directorate Department of Energy OICI or office of intelligence and counterintelligence and AFL CMC or Air Force lifecycle management center information protection directorate and [1849.7s → 1870.7s] Finally, we will end our monolithic two-part investigation with the subject of quote-unquote unrivaled secrecy Numerous layers between the SAP layer and core legacy secrecy structure within the onion model That are imperative to the functioning of these covert activities, but may not exactly warrant their own section [1872.1s → 1912.0s] So no when individuals associated with the narrative management campaign of the UFO issue like Hal put off Claim the entire UFO legacy program portfolio is held within Contractors to avoid FOIA or Freedom of Information Act requests as We can see and as we will find out the legacy security apparatus is nowhere near that simple as we look at the actual structure of the interaction between the government and private industry in this UAP area over the years it is morphed Transitioned into it being largely in the ages of the contractors [1912.5s → 1945.0s] If you do something within the government eventually it can be accessed by Freedom of Information Act But if you do something through contractors, they’re not Available through Freedom of Information Act So now that we’ve described the onion and several critical topics paramount to our investigation over the course of this series Let’s rewind the clock and investigate the origin of the secrecy behind the Manhattan Project 2.0 You [1946.5s → 1960.4s] 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 we took the Manhattan Project secrecy and overlaid it on this issue because that secrecy worked well for atomic bomb [1961.7s → 1997.1s] developments and whatnots and and certainly This whole program in a nutshell for to like summarize the 90 plus years of history It is a reverse engineering program to garner some kind of insight and of course not a lot of the things that we’ve learned from it are like directly You know ripped off the technology we found but it has inspired Other innovations that made its way into other US classified programs over the year for national defense reasons, you know And it’s a myriad of different things [1998.1s → 2028.6s] With global war the government stepped into the picture General Groves head of the project teamed up with Vannevar Bush government director of science and research and with dr Richard Tolman technological expert according to David Grosh the inception of the original UFO legacy program portfolio saw an adapted and abridged security apparatus plucked from the Manhattan Project itself Effectively leading to what I like to call the Manhattan Project 2.0 a [2029.5s → 2066.5s] highly compartmentalized in top-secret national effort restricted to quote-unquote need-to-know personnel featuring extensive counterintelligence and security shields to retrieve store and exploit recovered UFOs of course with early crash retrieval cases such as 1933’s Magenta, Italy There is certainly a case to be made that certain USG officials were indeed aware of crash retrievals prior to the atomic bomb program However, the Manhattan Project 2.0 seemingly kicked into gear and galvanized a covert national effort [2066.9s → 2103.3s] immediately following the July 1947 Roswell, New Mexico crashes and several subsequent crashes in the American Southwest in the late 1940s and early 1950s And I have talked about several such cases that I believe were instrumental to early retrieval and exploitation efforts including 1948’s Aztec, New Mexico and 1953’s Kingman, Arizona indeed, I have also discussed Sandia National Laboratory in great detail a modern-day DOE NNSA National Lab FFRDC [2103.7s → 2136.8s] That was once established as Los Alamos National Labs Z Division during the midst of the Manhattan Project in 1945 Becoming the Sandia of today in 1949 Of course, I believe Sandia like other similar national labs have been and still are instrumental to the legacy efforts But let’s really slow down here and distill what Grush is saying Like I’ve said in some other videos and stuff You know that we took the Manhattan Project secrecy and overlaid it on this issue because that secrecy worked well for atomic bomb [2138.1s → 2167.6s] Developments and whatnots if on several occasions David Grush has directly stated the Manhattan Project secrecy apparatus was outright overlaid onto the UFO issue Because of the efficacy of the Manhattan Project secrecy architecture Perhaps then it would behoove us to really step back and see what sort of secrecy systems and program protection strategies from the Manhattan Project would translate on to early UFO legacy activity efforts and [2168.4s → 2204.9s] I say this because I personally believe we can observe the formation and maturing of the early UFO legacy program apparatus in a time epoch covering roughly seven years 1947 to 1954 that ultimately resulted in the Manhattan Project 2.0 that stood stalwart for several decades until the 1980s So let us review cornerstone concepts dates individuals ideas and more that helped solidify the total security and deep-sixed nature of the Manhattan Project 2.0 [2205.7s → 2240.5s] It goes without saying that the Manhattan Project, the R&D program to produce the world’s first atomic bombs operated with a legendary and then unprecedented security apparatus costing near 24 billion dollars in today’s currency and employed nearly 130,000 people The Manhattan Project operated as a deeply compartmentalized multi-layered project that made famous the term need-to-know Where Manhattan Project individuals bar a handful of scientists, program managers and program security personnel [2240.9s → 2269.5s] were read into only what was absolutely necessary to complete their specific task Well, that’s exactly how Manhattan was right people working on the fuses for the bomb Didn’t necessarily know it was going to a nuclear weapon And so and I’ve seen this kind of compartmentation is up to secrecy and other programs and it is debilitating for progress And honestly as a fiduciary of the taxpayer dollars. It’s not the best modus operandus to do it that way [2270.5s → 2303.5s] And very few people kind of had that top-down could look across the silos and see what was going on It just became very dysfunctional and they were afraid of people who were not To boil down a fascinating topic that would require hundreds of hours of study into very, very, very simple terms here The Manhattan Project security apparatus consisted of several foundational pieces that I would like to speak on today Compartmentalization, organizational architecture, flexibility, and security [2304.3s → 2314.3s] I would like to cover each of these foundational security pillars on the Manhattan Project and explain how I believe such practices were abridged into the Manhattan Project 2.0 [2316.3s → 2358.9s] To begin here, compartmentalization is the most important part of the Manhattan Project It is the most important part of the Manhattan Project To begin here, compartmentalization really goes without saying The practice of compartmentalization simply limits exposure Within a classified program, personnel are granted access only to the specific information they need to perform their duties Even if they hold the necessary clearance level Compartmentalization operates as a defensive security mechanism [2358.9s → 2394.7s] reducing attack vectors for espionage, leaks, and intrusions Compartmentalization is the basis for modern-day special access programs, as we will discuss later with a singular SAP umbrella containing numerous compartmented subcomponents Granting Oppenheimer’s request for a single isolated lab where the bomb could be designed and built General Groves appropriated the remote school and officially named Oppenheimer scientific director Oppenheimer’s first job was to convince scientists and their families to join him for the duration of the war [2394.7s → 2430.5s] in a place he was not allowed to identify to work on a project he was not always allowed to describe There aren’t, in fact, very many secrets There aren’t secrets about the world of nature There are secrets about the thoughts and intentions of men Sometimes they’re secrets because a man doesn’t like to know what he’s up to if he can avoid it Obviously, aspects of the Manhattan Project were compartmented to strengthen program security in the realm of the Manhattan Project 2.0, aka early UFO legacy programs [2431.5s → 2466.1s] Everyone from David Grush to more controversial figures like Bob Lazar have spoken on compartmentalization within UFO activities With Bob Lazar infamously discussing how teams studying the propulsion of recovered NHI craft were not able to interface with other scientific teams to share and collaborate on discoveries oftentimes only being able to share information with their immediate lab partner And to be clear, I have stated plenty of times that I am biased towards Lazar so I do not factor his testimony into my critical analyses [2467.1s → 2503.9s] This is just an interesting point by him that many others have spoken on as well That individual I spoke of in our Onion Outline who served on a naval and specific FFRDC legacy program security structure stated to me the various programs he oversaw were so siloed and compartmentalized Some personnel were given several roles within the programs to keep read-in personnel as sparse as possible This included scientists also doing accounting work to not read-in financial personnel or red-in industrial security personnel performing janitorial work [2504.9s → 2541.9s] to not expose a custodian to program SAPFs or SAP facilities I sincerely believe that compartmentalization is a pretty simple concept to grasp and we are going to cover it so much more in our second part to our investigation where we talk about special access programs So I wanted to keep exposure to that topic brief for now so let’s go ahead and move on We have spent more than $2 billion on the greatest science ever scientific gamble in history, and we have won. But the greatest marvel is not the size [2541.9s → 2549.3s] of the enterprise, its secrecy, or its cost, but the achievement of scientific brains in [2549.3s → 2583.1s] making it work. Organizational architecture being weaponized and leveraged for secrecy is a fascinating topic I am so keen to speak on. The Manhattan Project got its name from the Manhattan Engineer District, or MED. The Manhattan Engineer District was the U.S. Army Corps of Engineers organization that served as the administrative and organizational entity for the atomic program. During the onset of the Manhattan Project, the U.S. Army Corps of Engineers worked in geographic quote-unquote [2583.1s → 2596.5s] districts. The Omaha District, Pittsburgh District, etc. This district apparatus was used to create the Manhattan Engineer District, under which the Manhattan Project was conducted, [2596.5s → 2627.3s] a name that was deliberately mundane and completely separate from the topic of nuclear weapons. The MED served as the legal and administrative entity through which the Manhattan Project operated. The MED handled acquisitions, contracting, construction, personnel security, and the enormous infrastructure required to complete program objectives. Regardless of the program being sequestered to a simple Army Corps of Engineers cover district, Commander Leslie [2627.3s → 2665.1s] Groves enjoyed unobstructed autonomy to run the Manhattan Project, reporting to an extremely short chain of command, such as directly to the Secretary of War and Army Chief of Staff one General George Marshall. And remember him as he is critical to our entire discussion today. This short chain of command allowed Groves to aggressively skirt standard acquisition channels and bureaucratic red tape. I wonder if all of this is starting to sound familiar to anyone else. Two projects ago at this point, I published on the quote-unquote hidden wing, [2665.1s → 2696.3s] the Air Force’s UFO material exploitation program, whose administrative command seems to peak with elements of the National Security Council, and whose roots can be traced back to the early days of UFO legacy program operations, specifically to our time epoch of interest, the late 1940s, specifically starting with 47. I ask you to shift your lens ever so briefly to the modern day really fast. One of the expressed objectives of that project on the [2696.3s → 2728.6s] Air Force was to outline the complete organizational and operational structure for the hidden wing, a centralized effort to perform tests and evaluation on recovered UFOs, derivative airframes, and alien reproduction vehicles on the US Western Ranges. In short, and excuse the technical speak, I do recommend watching that project, as in my opinion, it is still my most important work to date. Day-to-day operations of the hidden wing are conducted on several Air Force [2728.6s → 2769.5s] Major Range and Test Facility bases, or MRTFBs, specifically the Edwards 412th Test Wing, Utah Test and Training Range, and Nevada Test and Training Range, and features support and material housing from nearby GOCO installations, such as Air Force Plant 42. Primary T&E or Test and Evaluation work is conducted on the 412th Test Wing out of Edwards Air Force Base, and is primarily run by Air Force Test and Evaluation, or AFTE, with day-to-day operations run by AFTC, or Air Force Test Center, featuring ACE pilots from AFTC’s TPS, or Test Pilot [2769.5s → 2805.4s] School. AFTC is an operational element of Air Force Major Commander MAJCOM, Air Force Material Command, AFMC. AFMC is the RDT&E, or Research, Development, Test, and Evaluation, brainpower of the entire US Air Force, and is headquartered out of where else but Wright-Patterson Air Force Base. Administration and acquisition of these programs are held within Air Force Acquisition, or SAF-AQ. Specifically, SAF-AQL Special Programs, AQX Acquisition Integration, [2805.4s → 2840.7s] and AQR Science, Technology, and Engineering. Within the same administrational capacity is the SAF-AA, or Administrative Assistant to the Secretary of the Air Force, which we will discuss later as imperative to legacy cover offices. Specifically under SAF-AAH, or Sensitive Activities, and AAZ, Security, Special Programs Oversight, Info Protection. A mouthful I know, but the key aspect to this entire structure is the DAF-RCO, or Air Force Rapid Capabilities Office. RCO is an [2840.7s → 2874.3s] office that operates with the ability to function within the gray area of standard acquisition without bureaucratic oversight or hurdles. With access to near limitless budgets, bypassing long chains of command and oversight. An office uniquely positioned to oversee administrative and acquisition functions of a covert, deeply compartmented UFO RDT&E program that likely also features retrieval and storage tendrils. Does this sound at all akin to Groves leveraging the [2874.3s → 2895.7s] Manhattan Engineered District to bypass narrow chains of command to aggressively pursue program objectives for the Manhattan Project? Indeed, I believe this is particularly poignant, as I believe from the onset of legacy activities, again 1947, the fledgling US Air Force was [2895.7s → 2910.9s] designated as the primary RDT&E element for analysis of recovered non-human vehicles. Just bear with me in the modern day for just another second. Again, I stated Air Force [2910.9s → 2947.4s] Materiel Command, AFMC, is the modern day major command behind the Hidden Wing effort. Within AFMC’s six major operational areas, I am aware of three of these being directly involved with the UFO efforts. AFTC, or again, the Air Force Test Center, AFLCMC, or the Air Force Life Cycle Management Center, and the AFRL, or Air Force Research Laboratory, which oddly enough, was General Neal McCaslin’s former command. AFMC rose in 1992 from the joining of former [2947.4s → 2967.3s] major commands AFLC, Air Force Logistics Command, and AFSC, Air Force Systems Command. And remember Air Force Systems Command here soon. AFLC and AFSC were 1961 evolutions of two former major commands that transitioned into these iterations, [2968.1s → 3004.1s] Air Materiel Command, AMC, and Air Research and Development Command, ARDC, respectively. Established originally in 1950, Air Research and Development Command overtook R&D functions from Air Materiel Command in around 1951. Indeed, this ARDC, or again, Air Research and Development Command, also contained another former major command, the AFSWC, or Air Force Special Weapons Center, whose Office of Primary Responsibility, or OPR, ultimately transferred to Air Force Research Lab in 1992. [3006.4s → 3018.6s] All of the elements I listed above have been historically implicated in legacy program efforts. Specifically here, in 1947, Air Materiel Command attempted to recruit [3018.6s → 3035.7s] Nazi engineers through Operation Paperclip for a quote-unquote underground plant program. Air Force Systems Command, the evolution of Air Research and Development Command, was labeled in the early 1990s by New Mexico State Representative J. Andrew Kistner, sort of [3035.7s → 3041.9s] a mini David Grush prototype, as imperative to the original legacy efforts and so much more. [3043.3s → 3066.5s] Specifically here, I think there is a strong likelihood that UFO crash retrieval activities were partially housed under the Air Research and Development Command all the way back in 1953, when the Kingman, Arizona UFO crash retrieval was conducted under the Operation Upshot Knothole nuclear tests. Indeed, one of the several critical personnel named by eyewitness [3066.5s → 3101.0s] Arthur Stansell Jr. as leading the UFO crash retrieval effort was one Dr. Eric Henry Wang. Wang served as Chief of the Special Studies Office out of the ARDC out of Wright-Patterson Air Force Base, and moved on as a critical engineer from the Research Directorate of the Air Force Special Weapons Center, again AFSWC, out of Kirtland Air Force Base, which of course co-inhabits land with Sandia National Labs, which will be critical to our investigation today. Indeed Wang, a figure [3101.0s → 3135.9s] literally named as leading the reverse engineering effort on Kingman, was also implicated in even earlier cases such as 1948’s Aztec New Mexico crash retrieval, a complex and convoluted case that I do believe is a real instance of a UFO crash retrieval. So you see, that entire fast forward to the modern day within the Air Force, and quick time summarizing an enormous part of my work within Air Force Major Commands in the 1940s, 1950s, and 1960s. And yeah, cut me some slack, [3135.9s → 3165.7s] I know that was a ton of acronyms. But I discussed that to illustrate how Leslie Grove’s work within the MED, or the Manhattan Engineer District within the Manhattan Project, can directly translate to both modern day Air Force legacy programs, and the Air Force’s involvement in the inception of legacy activities. I believe we can observe a very clear instance of the fledgling UFO legacy operations copying the Manhattan Project, all to hide program [3165.7s → 3186.0s] elements within Air Force Major Commands and Offices in the late 1940s and early 1950s. Specifically as I discussed again, Air Material Command AMC, Air Research and Development Command ARDC, and the Air Force Special Weapons Center AFSWC. And if none of this is making sense, [3186.0s → 3216.0s] I strongly recommend watching my Air Force project to learn significantly more there. Outside of the Air Force here, I am thinking specifically of one more former US agency that, in my opinion, operated dual-hatted roles between the Manhattan Project and its successor, the UFO Legacy Program Portfolio, weaponizing security architecture to hide UFO retrieval and exploitation activities. And of course, I am talking here of the Armed Forces Special Weapons [3216.5s → 3223.3s] Project, AFSWP, not to be confused with the Air Force Special Weapons Center, AFSWC. [3225.3s → 3234.2s] Back within January of 1947, 29 January 1947 to be exact, Secretary of War Robert P. Patterson [3234.2s → 3276.9s] and Secretary of the Navy, original accused MJ-12 member and likely murder victim, James V. Forrestal, established the Armed Forces Special Weapons Project, or AFSWP, a joint Army and Navy venture to manage nuclear weapons following the Atomic Energy Commission’s succession of the Manhattan Project. AFSWP and Los Alamos Sea Division established operations at Sandia Base, and I highly recommend watching my Sandia Project for a much more robust overview here, including how AFSWP’s modern iteration, DITRA, the Defense Threat Reduction Agency, [3277.7s → 3309.6s] may in fact be holding on to old Atomic Energy Commission files that conclude some UFOs are of extraterrestrial origin. The AFSWP has surfaced in quite a bit of my work, such as discussing the aforementioned Representative J. Andrew Kistner’s assertions that early UFO legacy programs featured military support from Air Materiel Command and the AFSWP on the then-legacy site Linchpin, Sandia Base, as well as being mentioned in the contentious [3309.6s → 3340.9s] Interplanetary Phenomenon Unit documents, which we will actually discuss again soon. Recently in my project on Northrop Grumman and TRW, I discussed Dr. Edward Bushnell Dahl, a Senior Executive Vice President of TRW Systems Group and veteran physicist on the Manhattan Project, specifically the Manhattan Project’s Project Alberta. In 1953, as Chairman of the Stanford Research Institute, or SRI International, Dahl was sent to operate on Operation Upshot [3341.4s → 3376.8s] Knothole’s nuclear tests under a joint DOD and Atomic Energy Commission task force overseen by the Armed Forces Special Weapons Project. It was here Dahl would be accused by Arthur Stansell, Jr. as coordinating personnel and logistics surrounding the Kingman, Arizona UFO crash retrieval case. Short mention here, but I wonder if AFSWP also featured compartmented aspects and personnel, like Dahl of course, on the crash retrieval issue? Okay, I could really talk about [3376.8s → 3389.3s] Dahl all day, but let’s go ahead and return to the various security foundations that were copied from the Manhattan Project onto the Manhattan Project 2.0. This organizational architecture [3389.3s → 3418.3s] is so crucial to touch on because I disagree from many talking heads in the UFO community. I do not believe UFO legacy programs are run with a complete lack of oversights, but instead, as I say oh so often, a short, stripped, yet extremely concise chain of command, with only need-to-know personnel and offices read in, an organizational structure borrowed from Leslie Groves and the Manhattan Project. [3418.9s → 3450.6s] 2 billion dollars went into research and plants, such as this one at Richland, Washington. One of the world’s most closely guarded secrets, the atomic bomb process was developed in widely separated areas. Even the thousands of men and women working on the project had no idea of the staggering energy they were to release. Physical security here should really come as a no-brainer. Whether it be retrieving and safeguarding recovered UFOs, or building and safeguarding nuclear weapons, comprehensive and [3450.6s → 3486.2s] strict physical security is an absolute necessity. During the Manhattan Project, physical security maintained a permanent presence at three, maybe four sites. Los Alamos in Albuquerque, New Mexico, Oak Ridge, and Hanford. As we know from my work, Sandia and Los Alamos, two DOE and NSA national laboratories, are imperative to the modern-day legacy program structure. I have also discussed firsthand testimony delivered to me about claims of underground covert activities, [3486.8s → 3525.8s] studying the skin of recovered UFOs beneath Oak Ridge, amongst the larger Y-12 complex. I have a three-hour project explaining why national labs, Sandia in specific, are critical to legacy efforts. But earlier I made mention of classified presidential executive orders under Truman and Eisenhower that gave the Manhattan Project 2.0 some teeth. Well, let’s return here to J. Andrew Kistner. In the early 1990s, New Mexico State Rep. Kistner embarked on a proto David Grush-esque journey, interviewing and interfacing with as many UFO legacy program [3525.8s → 3558.3s] first-handers as humanly possible. His findings ultimately led to other Congressman Stephen Schiff launching a General Accounting Office investigation into Roswell. Kistner’s disclosures are intriguing, most of which I am in firm agreement with, including the inclusion of Air Force Major Commands and the AFSWP within early legacy efforts, and the presence of high-powered triangulated radar arrays such as the Lash-Up Network possibly being incidentally responsible [3558.3s → 3580.4s] for early UFO crash retrievals such as 1948’s Aztec. Kistner stated he learned 1940s and 1950s efforts saw recovered UFOs processed and analyzed by teams under the illustrious Dr. Vannevar Bush, in cooperation with the Atomic Energy Commission’s Los Alamos Scientific Laboratory [3580.4s → 3612.1s] and its Z Division at Sandia Base, another point I am in firm solidarity with. Furthermore here, Kistner stated that in July of 1948, a classified Presidential Executive Order signed by Truman vested custody of recovered technical vehicles within the Atomic Energy Commission and its National Laboratories, of course featuring support from the Air Force Systems Command, Naval Research Lab, and more. This divesting of custody into GOCO or again Government [3612.1s → 3651.9s] Owned Contractor Operated Institutions is exactly what I speak about when referencing in my UFO Legacy Program Pyramid where FFRDCs and GOCO Institutions separate Program Administration and Defense Industrial Base Prime Contractors. The federally funded Research and Development Center slash Government Owned Contractor Operated Layer of my Pyramid is a massive Security Enforcement Layer where Government Program Administrator Sponsors slash Handlers can attract Subject Matter Experts, R&D Aces, and Industries Brightest, while still retaining [3651.9s → 3690.4s] strict handling of Program Materials, Data, Files, Scope, etc. And most importantly in my opinion, harness the FFRDC slash GOCO Layer to arbitrate knowledge and access to information to the lowest level of the Pyramid, DIB Prime Contractors and their Subcontractors. The FFRDC GOCO Layer to me is as important as Program Compartmentalization itself, where read-in Program Administrative Personnel can offload most importantly Recovered Vehicles and Biologics to FFRDC Handling to [3690.4s → 3711.1s] maintain plausible Program Deniability, but also maintain an iron grip over Program Materials and Deliverables. I simply cannot stress enough how incorrect it is when individuals knowingly falsely state Crash Retrieval Programs are relegated to Private Contractors. This system [3711.1s → 3717.8s] is unbelievably vulnerable to Security Leaks, Espionage, Unauthorized Access, etc. [3719.3s → 3731.3s] Thus why I believe with fervor that Legacy Programs like the Manhattan Project before them, entrusted some of the most secretive aspects of their respected Programs to what [3731.3s → 3768.5s] would become Atomic Energy Commission then DOE slash NNSA FFRDC GOCO National Laboratories. Now don’t even get me started on FFRDCs or their precursors in this time FCRCs, Federal Contract Research Corporations. As many here could probably guess, I could spend hours discussing how specific FFRDCs, whose roots can be traced back to the Manhattan Project, became imperative to the Manhattan Project 2.0, such as MIT Lincoln Laboratories as the re-establishment of Vannevar [3768.9s → 3807.7s] Bush’s MIT Radiation Lab, or Lawrence Livermore National Laboratory, a joint venture by Dr. Edward Teller and Dr. Ernest Lawrence in 1952, I speak of often in my work. Maybe look for that in our future, but this project is on the Manhattan Project 2.0’s secrecy apparatus, so I’m afraid we’ll have to move on here. As in the days of the Manhattan Project, modern-day DOE-NNSA National Labs, hiding UFO legacy activities within their bones features stringent security forces. I mean, just look on screen now at these Los Alamos [3807.7s → 3813.3s] Protective Forces from the 1980s. And of course, coming up shortly, we will speak on [3813.3s → 3843.9s] DOE-NNSA Special Response Teams, SRTs, entrusted with safeguarding U.S. nuclear secrets. I speak on personnel security relatively often, whether it be industrial security personnel guarding UFO legacy SAPFs, or Special Access Program Facilities, within defense industrial based sites like the West Desert Test Center out on Dugway Proving Ground. And I recommend re-listening to the case of MS out there, or guards on the Nevada Test Site in Area 51, [3843.9s → 3884.0s] Tonopah Test Range, etc., hailing from the enigmatic Wackenhut Services, Inc. But I theorize here that the Manhattan Project employed a shrewd technique regarding physical security, and the Manhattan Project 2.0 took this idea and really ran with it. And this is the lack of physical security and hiding within plain sight. I speak often on the UFO legacy program structure being hidden as a shadow underneath but alongside the U.S. government and defense industrial base, operating hidden within plain sight. Indeed, I am familiar with [3884.0s → 3921.1s] corporate parks out on the western seaboard of the U.S. that once allegedly held recovered non-human bodies, alongside the standard office work and pencil pushers. Scientific parks on the east coast of the continental United States, housing UFO material exploitation efforts alongside standard research. And covert SAPFs, literally built into everyday infrastructure we take for granted, like doors in a shopping mall that lead to an underground sprawling covert facility. And I mean that literally. I talked about several similar instances in my [3921.1s → 3954.5s] video on DUMs, Deep Underground Military Bases, where nondescript buildings or offices sometimes house entrances to clandestine UFO and non-UFO related covert facilities. And I talked about this more in my second Northrop project, where I believe the Tejon Raider cross-section facility is made to appear abandoned and derelict, while still housing active underground components focused on UFO recovery and RDT&E. These sites often feature zero overt security but extensive [3954.5s → 3987.7s] hidden security, all to stay hidden in plain sight. And this was of course a feature learned from the Manhattan Project. Sure, Los Alamos, Hanford, and Oak Ridge were heavily guarded, as are several UFO legacy activity sites. But the Manhattan Project also operated literally under our feet in some instances. Take Enrico Fermi and the Chicago Pile-1 for example, the world’s first artificial nuclear reactor built in 1942. This work by Fermi was imperative [3987.7s → 4002.0s] to the Manhattan Project, a secret experiment that produced the first self-sustaining chain reaction. Chicago Pile-1 was not out in the open like Los Alamos, Oak Ridge, or Hanford. Indeed, Pile-1 [4002.0s → 4008.0s] was hidden under a squash court, under the stands of Stagg Field at the University of Chicago. [4008.0s → 4026.0s] This project by Enrico Fermi was so secret, it was not relayed to the Chicago mayor at the time. Again, I recommend watching my dumb video to learn more, but one thing the Manhattan Project 2.0 took from the Manhattan Project was hiding within plain sight, restricting physical [4026.0s → 4058.0s] security to the background, to operate right in front of everyone’s eyes. Classification and Information Control. I wish to primarily speak on this subject in relation to the 1954 Atomic Energy Agreement. As in Part 2 of this project, we will dive in great detail into classification control and special access programs. However, there is still some poignant discussion to be had in relation to the Manhattan Project. Early nuclear secrets showed that [4058.9s → 4076.9s] Early nuclear secrets during the Manhattan Project were overseen by an internal system of self-censorship and publication control, with the Office of Scientific Research and Development spearheaded by the illustrious Vannevar Bush and later the Manhattan Engineering District, establishing [4076.9s → 4099.7s] voluntary, then mandatory censorship of nuclear physics discussions and publications. Indeed, it was none other than General Leslie Groves who additionally implemented early iterations of modern secure compartmented information and special access program compartmentalization within the Manhattan Project, implementing a tiered system where access to [4099.7s → 4105.4s] information and core program secrets were granted on a compartmented and need-to-know basis. [4107.1s → 4140.5s] During the course of the Manhattan Project, both the Manhattan Project and its immediate successor, the Atomic Energy Commission founded in 1946, developed their own personal security clearance systems separate from DoD and Executive Branch frameworks. These being Q-clearance, equivalent to top-secret restricted data, and L-clearance, equivalent to confidential restricted data. And this is where we must really dig in. The establishment of the Atomic Energy [4140.5s → 4147.7s] Commission in 1946, as the successor to the Manhattan Project, saw the advent of quote-unquote [4147.7s → 4187.9s] restricted data. If you are curious for more, I do suggest reading the Atomic Energy Act of 1946. An informal practice during the Manhattan Project under Groves was the idea of information quote-unquote born secret. If a scientist wrote down core fission nuclear secrets, that information was inherently classified by nature, not by a review and classification designation. Thus, this once-informal idea was made law in the 1946 Atomic Energy Agreement, which introduced restricted data. Today, restricted data is the only classification [4187.9s → 4228.7s] that applies automatically to information by subject matter, rather than by a formal classification decision. And thus, we arrive to one of the core concepts of the Manhattan Project 2.0, that I believe continues to this day. The existence of the Manhattan Project split U.S. classification into two parallel tracts. Tract 1 being the executive order-based system covering confidential, secret, and top-secret classification, as well as the SEI slash SAP compartment layers under Obama’s 2009 Executive Order 13526, which is an iteration [4228.7s → 4268.7s] of Reagan’s 1982 Executive Order 12356. In Tract 2, the statutory Atomic Energy Act system of restricted data, now overseen by the Department of Energy. These two systems have completely different legal bases, declassification procedures, and oversight mechanisms. So, no, an Executive Order by Trump to reveal the UFO files would not touch any DOE-restricted data covered by a statutory order. Perhaps this is why, according to my understanding, the DOE is quite literally [4268.7s → 4304.9s] baked into every single layer of the legacy program structure. For example, the Air Force program structure I just outlined. The DOE is involved in everything from day-to-day involvement performing T&E on derivative technologies on the Edwards 412 test wing, to working alongside the DAF RCO on legacy administrative properties. So, now let’s fast forward to the Atomic Energy Act of 1954, where I believe we can observe when the Manhattan Project 2.0’s classification teeth [4304.9s → 4340.5s] grew into fangs. And, you know, and you notice the Schumer Amendment, if anybody reads it, awkwardly calls out the Atomic Energy Act of 1954, right? And 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, [4340.5s → 4371.4s] 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 U.S. nuclear secret. You’re trans-classifying it into a nuclear secret, which I understand, maybe at first, why they did that. And I’m not admonishing the hard decisions that presidents and other folks did many years ago when this was more of an enigma, [4371.4s → 4381.7s] and we wanted to, like, lock it down, figure it out, and then see what we’re going to do. This is far from a novel discussion point on my channel, but I speak often of creative [4381.7s → 4388.2s] classification loopholes within the DOE that legacy programs enjoy to safeguard UFO activities. [4389.9s → 4429.6s] One such misclassification is the concept of special nuclear material, whose information is inherently covered by restricted data. And as David Gruss just stated, such a system can be abused to improperly classify UFO materials under extremely strict DOE classification controls, essentially safeguarding UFO materials and information with the same severity as nuclear secrets. Indeed, the 1954 Atomic Energy Agreement, Section 142 to be specific, also gave statutory authority for trans-classified [4429.6s → 4464.9s] foreign nuclear information, or TFNI, which was given the unique name of TFNI in 2010 under 32 CFR Part 2001. Trans-classified foreign nuclear information exists as a type of classified information, not inherently a classification level like restricted data and formerly restricted data within the DOE. For example here, restricted data may get trans-classified out of the restricted data section under Section 142 of the 1954 Atomic Energy Agreement, then handled like [4464.9s → 4500.7s] national security information, but still subject to atomic energy protections like exemption from declassification. Essentially, TFNI enjoys both the Atomic Energy Commission and Executive Order Classification Framework. TFNI is the language used specifically in the Schumer legislation, aka the UAPDA, where it is explicitly stated UFO legacy programs have misclassified UFO materials, data, files, programs, discoveries, etc. as trans-classified foreign nuclear information [4500.7s → 4508.7s] to utilize the most deep-sixed channels of US classification. This is where our section on [4508.7s → 4520.5s] classification and information control ties into our physical security section. I have spoken numerous times on how DOE classification controls are abused for legacy [4520.5s → 4528.4s] operations, and thus special teams operating under DOE controls are mobilized for legacy activities. [4529.9s → 4546.0s] These include DOE SRTs, or Special Response Teams, which are tasked with safeguarding premier DOE NNSA sites like Sandia, Oak Ridge, and Los Alamos. I have theorized that SRTs may [4546.0s → 4584.6s] be involved as ground element direct action forces within UFO crash retrieval teams. I have theorized with low confidence that SRTs were a ground element to securing the UFO crash retrieval that USMC Lance Corporal Jonathan Wegant observed in Peru during 1997’s Operation Laser Strike. I have theorized with medium to high confidence that SRTs operated as a ground element for test operations of an enormous derivative triangular airframe observed by USMC Sergeant Roderick Castle during 1997’s Hunter-Warrior Advanced Warfighting Experiment [4584.6s → 4622.4s] in Southern California. Outside of DOE SRTs, I have spoken frequently about DOE NNSA NEST, or the Nuclear Emergency Support Teams. NEST was created under Executive Order 12656 to operate under the primary authority of the 1954 Atomic Energy Act. NEST was founded as a DOE specialized nuclear emergency organization that assisted the FBI and numerous government agencies by quote, providing technical expertise and advice in response to a variety of potential [4622.4s → 4656.4s] incident threats involving nuclear materials, end quote. NEST operates as an umbrella organization to handle all nuclear and radiological emergencies for the DOE. NEST’s mission is to quote, be prepared to respond immediately to any type of radiological accident or incident anywhere in the world, end quote. While on the subject of NEST, I hypothesize with near total certainty that NEST was the ground element team dressed in MOP, or Mission-Oriented Protective [4656.4s → 4695.3s] Posture gear, that Lance Corporal Jonathan Wegant observed securing a UFO crash site. Just as I hypothesize with near total certainty one of NEST’s core element, the NF-MAP, or Nuclear Forensics Material Analysis Program, is a paramount component to crash retrieval programs, I highly suggest you commit to memory. Within NEST, NF-MAP is tasked to deliver quote, timely, specific, state-of-the-art forensic results for nuclear materials found outside regulatory control, whether intercepted, discovered, or taken from an undetonated [4695.3s → 4719.9s] nuclear device, end quote. Essentially, NF-MAP operates to answer this question. If nuclear material or a nuclear device were intercepted in the United States, where did it come from, and who was responsible? Perhaps then it should really be no surprise that non-regulatory, and remember that, non-regulatory nuclear materials that are [4719.9s → 4755.7s] collected by NEST and NF-MAP are then transported to locations I have accused on numerous occasions. As recently as the Sandia Project, as existing as core legacy program elements, including quote, key NNSA facilities, Los Alamos National Laboratory and Lawrence Livermore National Laboratory, other DOE NNSA facilities that participate in the National Nuclear Material Archive Program within NF-MAP, Oak Ridge National Laboratory, Pacific Northwest National Laboratory, and Y-12 National Security Complex, end quote. Does this seem familiar? [4757.1s → 4789.6s] Lastly, let’s briefly touch on the OST, or Office of Secure Transportation, I spoke of in my Sandia Project, which works closely alongside the DOE NNSA NEST. Since 1947, the U.S. Department of Energy, DOE, and its predecessor agencies have moved nuclear weapons and nuclear weapons components and special nuclear material by a variety of commercial and government transportation modes. In the late 1960s, the Albuquerque Operations Office was directed to expand its [4789.6s → 4820.3s] transportation system to provide protection to all shipments involving special nuclear material. An increase in political act of violence prompted a review of procedures for the safeguarding of the materials. In 1975, the Office of Secure Transportation was established, and responsibility for nuclear weapons transportation was transferred to the Albuquerque Operations Office of the Atomic Energy Commission, predecessor to the Department of Energy. In 2000, DOE created the National [4820.3s → 4826.1s] Nuclear Security Administration. This office administers the total United States nuclear [4826.1s → 4850.2s] weapons program, including the design, production, and delivery of nuclear weapons and components. Under DOE Order 153.1a, the Office of Secure Transportation may provide transportation for the NNEST nuclear weapons, nuclear weapon components, and special nuclear material within the continental United States. [4852.3s → 4873.2s] OST operates within Amarillo, Texas, Oak Ridge, Tennessee, and Albuquerque, New Mexico, home to three DOE FFRDCs. Indeed, Sandia themselves have supplied the OST with MGTs, or Mobile Guardian Transport Units, for transportation of, quote, [4873.2s → 4888.1s] nuclear materials, special components, and nuclear weapons across the country, end quote. I have theorized with extreme confidence the OST under the DOE and NNSA directly transports UFO [4888.1s → 4926.1s] materials and secrets across the CONUS, or continental United States. OST convoys are composed of unmarked escort and transport vehicles. The only easily recognized feature is the U.S. government license plate. Escort vehicles always accompany transport vehicles. Transports are conventional three-axle truck-tractors with two-axle semi-trailers, while the escort vehicles vary in design. The personnel who operate these vehicles are NNSA federal agents. They are highly trained, well-armed, and authorized to use deadly force [4926.1s → 4943.4s] to protect their cargo. Each federal agent completes more than 1,000 hours of agent-candidate training and receives continuous training throughout his or her career in the form of operational readiness training. They receive detailed instruction on the techniques of [4943.4s → 4948.4s] operating all necessary equipment, as well as conducting paramilitary operations. [4949.1s → 4988.9s] They also receive expert instruction in tactics, including the use of a variety of firearms. Instruction on the complex operating procedures and safe handling of the tractor-trailers are given enormous emphasis because the Office of Secure Transportation logs over 4.5 million miles each year. And now, a complete theory of mine. Under the DOE’s Semi-Autonomous Agency, the National Nuclear Security Administration, or NNSA, using FFRDCs such as Sandia, Los Alamos, Oak Ridge, and Lawrence Livermore, the NNSA leverages NEST, [4988.9s → 5004.1s] OST, and SRT for the on-site recovery, procurement, and transportation of recovered UFOs under the guise of the 1954 Atomic Energy Act. And shout out here to my one specific good [5004.1s → 5009.3s] friend that I am talking about OST again. I know you’re jumping for joy watching this. [5010.9s → 5050.8s] So you see, the concept of restricted data and creative classification systems arose from the Manhattan Project onto 1946’s Atomic Energy Commission. And we can find nearly identical practices taken with even greater security mechanisms and lockdown classifications by the Manhattan Project 2.0. We can also find modern-day DOE and NNSA special teams emboldened by the 1954 Atomic Energy Commission agreements. The linchpin for the Manhattan Project 2.0’s classification structure that, in my opinion, plays imperative roles in scientific analysis [5050.8s → 5063.4s] of UFO crash retrievals, transportation of recovered UFOs and their biological occupants, actually retrieving UFOs, and safeguarding UFO National Laboratory sites. [5066.6s → 5100.8s] Lastly here, we arrive to another security infrastructure concept copied from the Manhattan Project onto the Manhattan Project 2.0, the political shield slash cover. The Manhattan Project saw civilian and political oversight spearheaded by an incredibly small and tight-knit group called the Top Policy Group. The Top Policy Group served as the mechanism through which the president was able to retain control over the Manhattan Project while circumnavigating normal government channels to maintain the [5100.8s → 5138.2s] secrecy of the project. Sound familiar? Initial membership for this group consisted of President FDR, who would be replaced by President Truman, Vice President Henry Wallace, Secretary of War Henry Stimson, Army Chief of Staff George Marshall, and again remember that name, Vannevar Bush of the OSRD, Office of Scientific Research and Development, and James Conant, Bush’s deputy. Funny enough, when Truman became FDR’s Vice President for the 1944 election, he was not briefed into the Manhattan Project and only received a briefing from the [5138.2s → 5176.2s] Top Policy Group when he took office in 1945. Almost even more comically here, Truman did in fact brush elbows with the Manhattan Project during World War II in his prior capacity as a senator when Truman spearheaded the Truman Committee, a committee reviewing defense programs. Here, Truman witnessed the funneling of millions of dollars into a project labeled, quote, expediting production, end quote, that featured no further descriptions or explanations on that hastily labeled project. At this time, Truman even approached Stimson for [5176.2s → 5182.1s] answers, yet Stimson just told Truman, quote, that the information was classified [5182.1s → 5230.9s] in order to protect national security, end quote. You, Dwight D. Eisenhower, do solemnly swear, I, Dwight D. Eisenhower, do solemnly swear that you will faithfully execute the office of President of the United States, that I will faithfully execute the office of the President of the United States, and will to the best of your ability, and will to the best of my ability, preserve, protect, and defend the Constitution of the United States, preserve, protect, and defend the Constitution of the United States. So [5230.9s → 5271.2s] help you God. So help me God. As I stated, I believe Truman and Eisenhower laid the foundations for the Manhattan Project 2.0. I am again in full agreement here with former New Mexico State Representative J. Andrew Kistner that the program coordinator for the fledgling Manhattan Project 2.0 was relegated to the newly formed in August of 1947 National Security Council. The National Security Council, of course, is harnessed by the President of the United States for national security, military, and foreign policy matters. The NSC, as we [5271.2s → 5304.2s] will call it for short, originates from within the White House as part of the executive office and is composed of senior national security advisors and presidential cabinet officials. Of course, we cannot speak of 1947 UFO programs and Truman without mention of the enigmatic Majestic 12. I have a full video on the Majestic 12 with the world’s best Majestic 12 researcher, Ryan S. Wood, so I highly recommend checking that out. I of course believe that Truman establishing [5304.2s → 5341.3s] the National Security Council as the UFO legacy program coordinating body stands on its own, but let’s briefly discuss that MJ-12 connection here. I will not waste time explaining what the MJ-12 is or its history and evolution. What I can tell you is I believe with confidence that regardless of the documents, a group called Maj-12, and Maj-12 specifically, did indeed exist under at least Eisenhower, and we will address that shortly. The Eisenhower briefing document, stamped 18 [5341.3s → 5379.2s] November 1952, sought to allegedly brief presidential incumbent General Dwight D. Eisenhower on the Majestic 12 operations, as well as origins and modus operandi of this shadowy group. The EBD, as I will call it from here, is the first Majestic 12 document to quote-unquote leak, and is one I find somewhat convincing due to the authentication work done by the late legend Stanton Friedman. The EBD contains some rather interesting parallels to actually known events, such as the Eisenhower briefing document containing a memorandum for SecDef [5379.2s → 5418.2s] Secretary of Defense James Forrestal, from President Harry Truman himself, dated 24 September 1947, discussing the authorization for Forrestal and Bush to proceed with Operation Majestic 12. Of course, in real life, Truman, Forrestal, and Bush did in fact meet on 24 September 1947. And of course, James Forrestal was a key member of the National Security Council from its very inception until 1949, when he died. And Vannevar Bush was a key scientific consultant to the NSC, especially as chairman of the Research and Development [5418.2s → 5458.6s] Board, or RDB. We can find other interesting parallels around the real life death of Secretary Forrestal, who allegedly threw himself out of the window of Bethesda Naval Hospital on 22 May 1949. The EBD here discussed General Walter Bedell Smith being appointed as Forrestal’s replacement after his passing in the Majestic 12 on 1 August 1950. And of course, in Truman’s very real daily appointments on 1 August 1950, we can find an off-record meeting with General Walter Smith. The EBD details the entirety of the original Majestic 12 [5458.6s → 5470.3s] team, including Forrestal-Smith, Admiral Roscoe H. Hillencoder, the illustrious Dr. Vannevar Bush, General Nathan Twining, General Hoyt Vandenberg, [5470.3s → 5510.1s] Dr. Detlev Bronk, Dr. Jerome Hunsaker, Mr. Sidney Sowers, Mr. Gordon Gray, Dr. Donald Menzel, General Robert H. Montague, as well as Dr. Lloyd Berkner. Now, I do not know if Truman established the Maj 12, but again, I am quite confident the Maj 12 existed under the Eisenhower administration. Indeed, I understand through a series of classified presidential executive orders, or presidential emergency action documents, again the acronym PEEDS, like the top policy group under administrations before him, Eisenhower took a similar [5510.1s → 5549.4s] route and hid this UFO control group, the Maj 12, under the National Security Council’s 5412 committee. But threats, new in kind or degree, constantly arise. Of these I mention two only. A vital element in keeping the peace is our military establishment. Our arms must be mighty, ready for instant action, so that no potential aggressor may be tempted to risk his own destruction. Our military organization today bears little relation to that known of any of my predecessors [5549.4s → 5591.3s] in peacetime, or indeed by the fighting men of World War II or Korea. The 5412 committee took a similar model and outline to the Manhattan Project’s top policy group. Keep read-in personnel and control groups small, minimize a paper trail, and maintain presidential control through a trusted intermediary. Shortly after taking office, on 15 March 1954, Eisenhower established and approved the NSC 5412, establishing the 5412 committee for the purpose of serving as an interdepartmental US executive body to review and approve covert US operations, [5591.8s → 5614.4s] NSC 5412 formally defined covert operations for US policy purposes, as well as established CIA as the executor for covert operations. The 5412 committee originally consisted of the Deputy Undersecretary of State, Deputy Secretary of Defense, the President’s Special Assistant for National Security [5614.4s → 5655.2s] Affairs, and the Director of the CIA serving as the group’s action officer. Now, circle back to that Eisenhower briefing document to EBD, and see one accused original MJ-12 member being Mr. Gordon Gray, at that time President Truman’s Assistant Secretary of the Army. Well, from 1958 to 1961, Gray would also serve as Eisenhower’s National Security Advisor, aka a member of the 5412 committee. I firmly believe the match 12, or whatever naming convention it evolved into, continued covertly as the control group for the Manhattan Project [5655.2s → 5682.1s] 2.0, throughout iterations of the 5412 committee, such as Nixon’s 303 committee, before the group ultimately went into a black box, or broke apart into siloed containers during the 1980s. However, I do still firmly believe an element of the National Security Council retains oversight of one singular UFO crash retrieval portfolio to this day, involving the Department of Energy, Air [5682.1s → 5706.6s] Force, CIA’s Directorate of Science and Technology, and select primes and FFRDCs. This, of course, is the legacy program structure the Age of Disclosure was attempting to outline. However, this is not the singular legacy program portfolio, so no, there is no one monolithic program. In the Age of Disclosure conveniently left out the National Security Council as the program [5706.6s → 5733.1s] coordinator here. This, of course, was to protect Lieutenant General James Clapper. This is because, whilst Director of National Intelligence from 2010 to 2017 within the Obama administration, Clapper, alongside his principals and deputies, including Stephanie O’Sullivan and Michael Dempsey, spearheaded the NSC UFO crash retrieval portfolio. And don’t just take my word for it here. Listen to [5733.1s → 5768.8s] David Grush say the same. In fact, without being inappropriate, I will say that General Clapper was well aware of the crash retrieval issue, managed the crash retrieval issue, and when he was the DNI, USDI, and DIA director, he placed people in critical roles to manage this issue, both publicly and, I’ll just say, non-publicly as well. And I’ll allow the audience to distill what I’m saying at the risk of being inappropriate or going too far with my discussion. So General Clapper, Stephanie O’Sullivan, other folks [5768.8s → 5785.4s] in the IC that are well aware of this issue, that were in rooms discussing this issue, I ask you to be greater leaders on this. I should not be the only former military officer and intelligence official that is being completely candid [5785.6s → 5805.2s] with the information that they were exposed to. Indeed, this NSC program portfolio with Clapper gets rather nefarious, with Clapper likely blessing the director of the National Special Program Management Staff, or NPMS, Luis Elizondo with top cover for the ATIP program as a way to [5805.2s → 5845.2s] talk about the onion outside of the onion. So, you see, I say all of this because I theorize with near certainty that Truman carried on the legacy of the Manhattan Project’s top policy group on to the Manhattan Project 2.0, relegated in 1947 to the newly formed National Security Council. Eisenhower, shortly upon taking office, effectively, quote unquote, deep-sixed the UFO top policy group within the National Security Council by creating the 5412 Committee, aka the, quote unquote, Special Group. The 5412 Committee or Special Group allowed the [5845.2s → 5878.4s] president and read-in program individuals to hide the UFO control group even deeper than the former top policy group. As we will continue to discuss thoroughly, I believe the architecture of the 5412 Special Group, directly leading UFO programs in an operational capacity, evolved into a system free from traditional oversight of presidents and, quote unquote, temporary employees. You see, while official National Security Council meetings require full council presence, informal meetings with NSC members [5878.4s → 5912.9s] with relevant expertise are held off books and often go unrecorded. And thus, with the stroke of his pen, Eisenhower created the impenetrable UFO control group that would ultimately usurp our system of checks and balances. Though there have been several precedents read into the UFO legacy portfolio following Eisenhower, I believe the empowering of and deep-sixed nature of the 5412 Special Groups and its evolutions, such as the 303 Committee, began to show traditional presidential power and [5912.9s → 5929.2s] oversight over UFO crash retrieval and reverse engineering operations slip towards the tail end of the Eisenhower administration. Perhaps this is what Eisenhower was referring to in his infamous military-industrial complex speech when leaving office. [5930.5s → 5956.7s] In the councils of government, we must guard against the acquisition of unwarranted influence, whether sought or unsought, by the military-industrial complex. The potential for the disastrous rise of misplaced power exists and will persist. We must never let the weight of this combination endanger our liberties or democratic processes. We should take nothing for granted. [5958.0s → 5973.7s] Only an alert and knowledgeable citizenry can compel the proper meshing of the huge industrial and military machinery of defense with our peaceful methods and goals, so that security and liberty may prosper together. [5975.9s → 6016.0s] Akin to and largely responsible for the sweeping changes in our industrial military posture has been the technological revolution during recent decades. In this revolution, research has become central. It also becomes more formalized, complex, and costly. A steadily increasing share is conducted for, by, or at the direction of the federal government. Today, the solitary inventor, tinkering in his shop, has been overshadowed by task forces of scientists in laboratories and testing fields. In the [6016.0s → 6059.5s] same fashion, the free university, historically the fountainhead of free ideas and scientific discovery, has experienced a revolution in the conduct of research. Partly because of the huge costs involved, a government contract becomes virtually a substitute for intellectual curiosity. For every old blackboard, there are now hundreds of new electronic computers. The prospect of domination of the nation’s scholars by federal employment, project allocations, and the power of money is ever present and is gravely to be regarded. [6062.8s → 6096.7s] So to make a hyper long section short, we covered security mechanisms, the Manhattan Project 2.0 plucked from the Manhattan Project. And these include compartmentalization, organizational architecture, physical security, classification, and information control. And finally, political shield slash cover. To summarize this insanely long section, these include legacy operations, borrowing directly or conceptually from the Manhattan Project, to operate on a highly compartmentalized need to know basis, [6097.1s → 6133.9s] establishing unique chains of command hidden in plain sight, we can observe in the modern day Air Force legacy program structure. Physical security delegating custody of recovered NHI vehicles to modern day DOE and NSA national labs like Sandia, Los Alamos, and Oak Ridge. Classification and information control through broad interpretations of the 1946 and 1954 atomic energy acts, as well as the implementation of inherited self imposed classification practices from General Leslie Groves, while also using [6133.9s → 6180.5s] such classifications to empower DOE slash NNSA special teams, such as SRT, OST, and NEST to operate on the forefront of CONUS based UFO crash retrieval missions. And finally, the Manhattan Project 2.0, replicating the Manhattan Project control group, the top policy group, this time within the US National Security Council, specifically the 5412 committee, to conduct such covert UFO activities with an extremely small and tight knit control group. But after all that, let’s go ahead and move on. Because I now want to talk about some possible personnel who moved from the Manhattan Project security apparatus on to the Manhattan Project 2.0. [6188.2s → 6233.0s] If you got to ask one question to ask someone who is not alive anymore, that you feel could answer a lot for you, who would you pick? And what would the question be? I would probably ask Sarbacher, Oppenheimer, and be like, what was your thought process in the 40s and 50s? You know, scrolling this away, I mean, besides overlaying the Manhattan Project secrecy. Because Oppenheimer was the one who created the classification that included the UFO stuff? Oh, all those guys. The guys that were involved in Manhattan were overlaying the same ecosystem of secrecy in some of the same ways to protect stuff that they were [6233.0s → 6264.6s] protecting our nuclear secrets. I want to spend some time here strengthening my argument that the UFO legacy program security control structure, aka the Manhattan Project 2.0, was quite literally ripped from the Manhattan Project. And I want to do this by exploring personnel who likely served pivotal roles shaping covert policy within both of these programs. And I can really think of nowhere better to start than with one of the greatest scientific minds in American history. A [6264.6s → 6298.3s] man who pioneered the concept of FFRDCs and UARCs through revolutionizing the partnership between government funding and university research. A man who literally spearheaded the American scientific structure through World War Two, the Manhattan Project in the early days of the Cold War. And a man who was entrusted with the greatest scientific secrets of the 20th century. This is a man who if I could sit down and have dinner with anyone from history would be near the top of my list. I am talking about the illustrious Dr. Vannevar Bush. [6298.7s → 6330.8s] Hello, I’m John Fitch, MIT science reporter. We’re at the home of Dr. Vannevar Bush in Belmont, Massachusetts. During World War Two, Dr. Bush was the organizer, guiding spirit, and driving force of our nation’s scientific efforts in a global conflict. As director of the Office of Scientific Research and Development, he was responsible for mobilizing the forces which produced many of the technological advances that played an important part in the winning of the war. Dr. Bush worked closely with Presidents Roosevelt and Truman and in [6330.8s → 6341.4s] effect was the first of our scientific advisors. He shared the enormous responsibility for the development and use of our most fearsome weapon, the atomic bomb. Let’s meet Dr. Bush. [6345.7s → 6360.8s] John, good to have you here. Well, Dr. Bush, this is certainly a beautiful home that you have here. I think it’s a very nice one. We built it soon after the war, some eight years ago, some after, soon after I came up from Washington eight years ago. And it’s [6360.8s → 6393.8s] worked out very well. Vannevar Bush is one of the United States’ most celebrated men of science, an engineer, inventor, and scientist who helmed the U.S.’s scientific effort during World War Two and beyond. Indeed, during the Great War, Bush headed the OSRD, or Office of Scientific Research and Development, and following the war, helped establish the Research and Development Board, RDB, on which he would serve as chairman from 1947 to 1948. Of course, two years imperative to the Manhattan [6393.8s → 6428.9s] Project 2.0, which saw the creation of the 1947 National Security Act, establishing the National Security Council, Air Force, CIA, and other agencies, and alleged classified presidential executive orders in 1948, delegating custody of recovered disks to the Atomic Energy Commission’s National Labs. Because you see, while at heart Bush existed as an engineer and scientist who wished nothing more than to tinker and invent, through establishing the OSRD, JRDB, RDB, compartmentalization, and secrecy of the [6428.9s → 6464.0s] Manhattan Project, and conceptualizing the blueprints for modern day FFRD seasoned UARCs, Bush grew to know, quote, more about our defense and military administration than anyone else who can be named, end quote. Bush served the U.S. military establishment as a stalwart scientific leader and policymaker, more akin to a director of an agency, and quite literally established the modern day structure and relationship between scientists and engineers in the U.S. government. Today, compartmented military GOCO, [6464.0s → 6472.2s] government-owned contractor-operated contracts for science and technology and research, development, tests, and evaluation, exist because of the [6472.2s → 6485.0s] foundational work and ingenuity by Dr. Bush. Well, in this country, World War II was certainly an important turning point for science. What about in the role of the science advisor? How has that [6485.0s → 6526.3s] changed over the years since then? Well, you spoke of me as being the first presidential advisor. Actually, my post was somewhat different from that. I was advisor to the president, but my principal job was running a government agency as an executive. On the other hand, Dr. Killian and Wiesner, the ones that have fallen in since the war, have been our advisors. Now, in both cases, in their case and in mine, we’ve never taken this as a matter of giving personal advice. My job, their job, was to get to the president of the United States the best possible scientific [6526.3s → 6559.3s] advice available anywhere in the country. Indeed, I think it highly likely Bush’s National Military Establishment Research and Development Board, RDB, created under the 1947 National Security Act, which saw drastically broadened duties and responsibilities from the former 1946 to 1947 Joint Research and Development Board, held the top secret scientific apparatus behind UFO crash retrievals and reverse engineering helmed by Bush himself. I believe RDB was the tip of the spear [6559.3s → 6596.9s] for such scientific covert operations from specifically 1947 to 1953, when the RDB was transitioned into the newly created Assistant Secretary of Defense for Research and Development, where it now exists today as the Undersecretary of Defense for Research and Engineering, an OSD or Office of Secretary of Defense position, along with others, specifically the USD ANS, Acquisition and Sustainment, and USD INS, Intelligence and Security, that are very often associated with UFO legacy activities. The Research and Development [6596.9s → 6629.6s] Board under the 1947 National Security Act was directed to accomplish several specific tasks, including to prepare a complete and integrated program of research and development for military purposes, to advise with regards to trends in scientific research relating to national security and the measures necessary to assure continued and increasing progress, to recommend measures of coordination of research and development among the military departments and allocation among them of responsibilities for specific [6629.6s → 6665.0s] programs of joint interest, to formulate policy for the national military establishment in connection with research and development matters involving agencies outside the national military establishment, and finally, to perform such other duties as the Secretary of Defense may direct. Without Vannevar Bush, there would be no Atomic Energy Commission and likely no successful Manhattan Project or Manhattan Project 2.0. Bush was truly one of the greatest pioneers in establishing American scientific [6665.0s → 6698.2s] infrastructure. Though not running day-to-day operations on the Manhattan Project like Groves or Oppenheimer, Bush is one of the most pivotal figures who established the institutional architecture for the Manhattan Project, and most imperative to our discussion, the Manhattan Project’s secrecy apparatus. Recall that Bush was instrumental in the self-classification and self-censorship apparatus within the Manhattan Project, pioneering control of civilian research within the most highly classified channels of military R&D. Bush [6698.2s → 6729.9s] was one of the senior leaders who had to navigate need-to-know compartmentalization within the Manhattan Project, often handling Oppenheimer’s complaints that Groves’ need-to-know apparatus hindered overall scientific progress. Indeed, also recall Bush being a critical member of the top policy group, whereas Bush aided in gatekeeping who in the U.S. government learned about the Manhattan Project’s existence. Seen as Bush was one of the greatest pioneers in establishing modern U.S. military and scientific [6729.9s → 6760.0s] infrastructure, and one of the first men to navigate need-to-know and compartmented prototypes to waived, unacknowledged special access programs, Bush would be the perfect man to install to aid in the construction of the Manhattan Project 2.0, would he not? Especially if this project dealt with recovered non-human technical vehicles. Well, perhaps it should come as no surprise, but Bush is one of the most infamous men associated with 1940s and [6760.0s → 6767.5s] 1950s crash retrieval programs. I wonder if you’d care to comment on the increasing role and importance of that [6767.5s → 6799.2s] role of the scientist in our society and in government? Well, of course, we see it everywhere. Science has been remaking our lives in every way. It’s going to do so in the future, and it’s inevitable, therefore, that scientists and engineers have far more to do with government. Then, too, we have an enormous increase in the support by government of scientific work, which means that many scientists in this country are working indirectly for [6799.2s → 6822.3s] government. I understand it’s something like two out of three. Something of the sort. And that inevitably brings scientists in contact with government on all sorts of fronts. As appointed men, usually, in the administrative branch, the executive branch of government, scientists and engineers don’t run for Congress very much. [6822.3s → 6855.5s] I will keep things brief here, as I could spend an entire video on Bush. But from Rhett Kisner’s disclosures, to the disputed Majestic documents, to William Steinman’s fantastic investigations into the 1948 Aztec New Mexico crash retrieval, Vannevar Bush is almost ubiquitously labeled as THE first man to spearhead UFO crash retrieval and reverse engineering operations. With Mr. J. Andrew Kisner outright stating that collected non-human technical vehicles were processed and analyzed directly under [6855.5s → 6876.9s] Bush’s supervision. Indeed, in regards to Bush and early legacy program secrecy, I am most intrigued here by the statements of Einstein’s protege, Dr. Robert Sarbacher. I have spoken about Sarbacher ad nauseum in works prior. So to get a more well-rounded understanding of Sarbacher and Bush [6876.9s → 6911.6s] in regards to the Aztec case, go watch my Aztec investigation. In 1950, Canadian government senior radio engineer, Wilbur B. Smith, wrote to the Comptroller of Telecommunications within Canada’s Department of Transport, requesting for Canada to begin its first official investigation into UFOs. Specifically studying complex magnetism as a form of propulsion. This document was classified top secret within Canada’s classification structure until 15 September 1969. And fast forward to [6911.6s → 6922.4s] 1978, where UFO researchers Arthur Bray and Stanton Friedman obtained copies. In this letter, Smith made three astounding claims told to him [6922.4s → 6931.3s] by a source within Washington regarding UFOs. 1. The matter is the most highly classified subject in the United [6931.3s → 6942.7s] States government, rating even higher than the H-bomb. 2. Flying saucers exist. 3. Their modus operandi is unknown, but [6942.7s → 6956.2s] concentrated effort is being made by a small group headed by Dr. Vannevar Bush. And finally, 4. The entire matter is considered by the United States authorities to be of tremendous significance. [6957.9s → 6993.2s] This source of Wilbur Smith? Well, of course, Dr. Robert Sarbacher, a respected physicist and consultant to the DoD’s Research and Development Board in the 1950s under the Truman administration. Indeed, Sarbacher’s disclosures from subsequent 1980s interviews between William Steinman and Sarbacher are intriguing to say the least. These interviews invoked the name of a man who self-admitted to attending the 1965 Kecksburg, Pennsylvania UFO crash, Dr. Eric A. Walker. And again, go watch that Aztec project for a more comprehensive overview there. [6994.5s → 7027.6s] Conceptualizing the words of Sarbacher here, and as I state again, it should really be no surprise to recall that Dr. Vannevar Bush was accused of leading the scientific crash recovery team out of the 1948 Aztec, New Mexico UFO crash retrieval case. I really won’t spend much time here, but 1986’s excellent UFO crash at Aztec, a well-kept secret by William Steinman, proposed a lengthy argument regarding Bush spearheading this late 1940s crash that I consider to be very real. I think often on David [7027.6s → 7059.3s] Grush stating there is a sub-Rosa Cold War that has been waging for decades between the U.S. and our adversaries, intent on mastering recovered NHI technology. And according to Grush, this obscene security infrastructure was present even in the fledgling years of the Manhattan Project 2.0. You’ve got to remember a bulk of this program was done during the Cold War. And, you know, we were afraid of Russian spies, Soviet moles. And so we made it ultra locked down, but to the detriment [7059.3s → 7093.5s] of national security. And there’s more. Grush says the United States is not the only country that’s encountered NHI and their technology. He says our geopolitical rivals have their own crash retrieval programs, which they are also secretly exploiting for military purposes. We’re in a competition with their adversaries to understand this. And it’s a multi-decade Cold War that has been under our nose for so long. The Soviet Union, of course, penetrated the Manhattan Project through [7093.5s → 7126.8s] spycraft under Klaus Fuchs. Perhaps part of the reason the Manhattan Project 2.0 never saw any semblance of disclosure was Vannevar Bush’s fear and respect of the newfound Soviet scientific prowess. Well, again, nothing new in the way of weapons came out of Russia. They did enormous things in producing great masses of artillery and so forth, but no innovations that I know of that amounted to anything. That’s changed somewhat. Oh, yes. Changed very much. And I can tell you the [7126.8s → 7159.5s] reason that it’s changed. And it’s an interesting one. Right after the war, I said that I didn’t believe that Russia would produce much in the way of science or technology. And the reason was that their laboratories were all commissar ridden. They were politically controlled, and their programs were made up by communists who knew nothing about science. But they changed all of that a few years ago. They took their commissars out of the laboratory. They gave them their freedom. They gave them [7159.5s → 7168.4s] their entire opportunity to make their own programs. And the result was a great burst of scientific achievement and technological engineering [7168.4s → 7209.7s] achievement. It’s the exuberance of newfound freedom, perhaps. I could really talk about Bush all day and how his ingenuity led to the modern-day go-co, government-owned, contractor-operated structure, such as Bush establishing MIT Radiation Lab, which reopened as the modern-day FFRDC MIT Lincoln Labs, an institution I understand was a major player in the early legacy effort. But alas, perhaps one day we will engage in a full pursuit of understanding Vannevar Bush. Outside of Vannevar Bush, several integral figures to the Manhattan [7209.7s → 7225.7s] Project also feature claims and links to the Manhattan Project 2.0. And let’s continue with the obvious here. One of the most prolific men in American history, the father of the atomic bomb himself, Dr. J. Robert [7225.7s → 7242.9s] Oppenheimer. We had the pride of thinking we knew what was good for man. And I do think it has left a mark on many of those who were responsibly engaged. This is [7242.9s → 7266.7s] not the natural business of a scientist. I need to waste no time here introducing Oppenheimer, and I won’t, since our investigation is already so robust. And if you aren’t super familiar with Oppenheimer, I recommend pausing and going to watch the 2023 masterpiece that is Christopher Nolan’s Oppenheimer. And even if you have watched that movie, I recommend watching it again, with our [7266.7s → 7286.1s] project today in mind. It is an incredible watch, trust me. Following the atomic bomb project, Oppenheimer was mentioned frequently throughout the 1980s as a critical scientific member to 1940s and 1950s UFO crash retrieval operations. And it seems that David Grush himself [7286.1s → 7299.8s] shares this sentiment. I would probably ask Sarbacher, Oppenheimer, and be like, what was your thought process in the 40s and 50s, you know, scrolling this away? I mean, [7299.9s → 7326.5s] besides overlaying the Manhattan Project secrecy. Indeed, in communications with William Steinman in 1983, the man who we just discussed as categorically stating Vannevar Bush’s involvement in the Manhattan Project 2.0, Dr. Robert Sarbacher, would state he was aware Dr. John von Neumann was definitely involved in 1940s and 1950s crash retrieval programs, and that he strongly theorized Dr. Robert [7326.5s → 7343.8s] Oppenheimer was also. Just three years after Sarbacher’s comments, Steinman would publish his magnum opus, UFO Crash at Aztec, a well-kept secret. This coveted book is the definitive exploration into the 1948 Aztec case, alongside the [7343.8s → 7358.4s] work of Scott and Suzanne Ramsey. Steinman here did some truly incredible work, including chasing down the storied Mr. G’s, an amalgamation of scientists who disclosed knowledge of crash retrievals to key figures to the Aztec case, [7358.4s → 7373.7s] Mr. Silas Newton and Leo Jabaur. And that’s not even half of it. The Aztec case is so intriguing and convoluted, I do recommend going to watch that video now. Within the book, Steinman detailed the Aztec saucer recovery [7373.7s → 7394.3s] scientific team members. This team was of course helmed by Dr. Vannevar Bush, featured three original accused Majestic 12 members, including Dr. Detlev Wolf-Bronk, Dr. Lloyd Berkner, and Dr. Jerome Hunsaker. Also on the team was one Dr. Carl A. Hyland, in my opinion, [7394.3s → 7401.3s] a possible linchpin to this case, Dr. John von Neumann, and Dr. J. Robert Oppenheimer. [7403.0s → 7414.7s] But just hold on a second here. Before we can take this and run with it, I have openly stated my frustration, Steinman did not meticulously detail his work and sources, to reveal under what grounds he arrived [7414.7s → 7437.1s] at this scientific team roster. His most concrete name here is Dr. Carl Hyland, who did resurface with the Silas Newton and Leo Jabaur drama on the Aztec case. Specifically within Colorado court records, where Hyland appeared to be forced as a hostile witness to improperly label Jabaur and Newton as conmen. Indeed, perhaps Steinman reached [7437.1s → 7453.4s] this Oppenheimer conclusion from his communications with Sarbacher. Or perhaps, as one of the leading figures to reveal this office through FOIA, Steinman learned of Oppenheimer’s involvement from the quote-unquote leaked Interplanetary Phenomenon Unit reports. [7454.9s → 7463.3s] But before we move on to the IPU real fast, as we discussed earlier, Oppenheimer also voiced concerns regarding Groves Manhattan Project [7463.3s → 7500.0s] secrecy apparatus actually hindering overall scientific progress. One must wonder if Oppenheimer really did engage with the Manhattan Project 2.0 in the 40s and 50s. If he shared similar concerns, that the compartmentalization and secrecy surrounding the hiding of non-human intelligence hindered both scientific progress and rightful human understanding. This is total speculation here. I do not have any strong theory with supporting evidence. But remember back to the video’s introduction where Oppenheimer commented on secrets not existing in [7500.0s → 7538.7s] nature, but within the hearts of men. If Oppenheimer operated on the Manhattan Project 2.0, perhaps like the Atomic Project before, he became disenfranchised with the total secrecy, compartmentalization, and need to know access of the legacy programs. Maybe, just maybe, there are parallels here to the Atomic Energy Commission stripping Oppenheimer’s clearance in 1954 in a kangaroo court mastermind by Louis Strauss. Maybe, just maybe, there was a need to remove Oppenheimer from the UFO legacy program portfolio. [7542.5s → 7576.1s] But back to that interplanetary phenomenon unit I just mentioned. I’ve discussed this group several times before and covered in great detail the allegedly leaked reports from this group. The IPU was revealed through several FOIA pursuits by UFO researchers including Steinman. And though shadowed in secrecy, there are several facts we know for certain about the IPU. The Army confirmed with the Army Department of Counterintelligence there was, in fact, an Interplanetary Phenomenon Unit, or IPU. The IPU [7576.1s → 7601.9s] was disestablished in the late 1950s. The IPU records were surrendered to the Air Force, AFOSI, in conjunction with Project Blue Book, confirming that the IPU dealt with the UFO phenomenon. The unit was a quote-unquote in-house project as an interest item for an unnamed Assistant Chief of Staff for Intelligence. The unit lacked formal function, mission, or [7601.9s → 7610.0s] authority. is only through quote-unquote institutional memory that the army even knows of the ipu’s existence [7611.4s → 7643.3s] debates wager on to this day about the existence of the ipu with some individuals claiming this unit was simply the input processing unit of the army’s mail room while of course others claim there was a purposeful attempt to destroy records and hide the very real interplanetary phenomenon unit now according to foia the ipu was an in-house project for an unnamed army assistant chief of staff for intelligence aka a g2 however according to several researchers such as ryan and the late [7643.3s → 7681.1s] dr robert woods the g2 position in reference to the ipu was actually a compartmented office from which the ipu was conducted with real ipu leadership being general george c marshall chief of staff of the army from 1939 to 1945 secretary of state from 1947 to 1949 and secretary of defense from 1950 to 1951 and before we go any further just conceptually this makes sense think back to the top policy group if as we talk about george c marshall did indeed lead the ipu or a similar [7681.1s → 7714.7s] ufo crash retrieval group it would make sense to put compartmented leadership of the office within a subordinate office effectively removing himself from chain of command perhaps this should come as no surprise seeing as marshall is all over the alleged majestic 12 documents including a 5 march 1942 memo allegedly from marshall to franklin d roosevelt discussing the recovery of an unidentified airplane following the infamous 1942 battle of los angeles marshall says in this [7714.7s → 7754.2s] disputed document the craft was likely of quote-unquote interplanetary origin and suggested a special intelligence unit be created to further investigate the phenomenon marshall is also featured in the alleged ipu report leaked alongside some of the majestic documents take the ipu report dated 22 july 1947 for example this alleged ipu report states george c marshall then secretary of state was the only cabinet member to know of the crashed ufos but that sect def james forestall would be briefed on certain aspects of course an mj-12 lore like [7754.2s → 7790.3s] we talked about more appropriately match 12 lore truman and forestall engaged in september of 1947 meetings to establish the match 12. the ipu report also states select scientists from the atomic energy commission were amongst this ufo crash retrieval team including dr robert oppenheimer intriguing here to me is mention of one colonel housebrook of the armed forces special weapons project afswp who according to the report ordered a special radiobiological team accompanied by a sed [7790.3s → 7825.9s] sed and a security detail from sandia national labs to secure the immediate area surrounding the roswell crash site as it turns out colonel sherman v housebrook was indeed a very real army colonel who even served as a high-ranking member in post-world war ii nuclear programs and even worked closely with leslie groves again the u.s army corps of engineer officer who oversaw the construction of the pentagon and directed the manhattan project and colonel housebrook did indeed aid in fleshing out the afswp we talked about earlier in relation to [7825.9s → 7859.1s] the manhattan project 2.0 plucking administrative architecture from the manhattan project indeed in that same frame of reference the accused said under colonel housebrook for ufo retrievals well this is what’s known as a special engineer detachment a manhattan project artifact in 1943 the manhattan engineer district established seds an army unit designation for military personnel with scientific and technical backgrounds who were assigned to work on the manhattan project [7859.1s → 7891.4s] alongside civilian scientists seds worked at critical manhattan project sites including los alamos z division at sandia base oakridge etc following the manhattan project as it transitioned onto the atomic energy commission most said personnel served prominent careers in physics engineering and academia rather intriguing this ipu doc would discuss seds being an imperative on-site unit alongside scientific personnel at ufo crash sites what president truman presented [7891.4s → 7922.3s] marshall with the distinguished service medal in 1945 he said that although millions gave america extraordinary service marshall gave it victory but i digress here there is more to discuss regarding george c marshall george marshall served in the manhattan project’s top policy group alongside bush fdr truman stimson and others the extremely small and tight-knit project control group and as army chief of staff was the apex of the short and narrow chain of command through [7922.3s → 7954.7s] which leslie groves reported in essence here marshall was paramount to the manhattan project especially as a senior leader within covert unacknowledged control groups and i believe of course there is an argument to be made that marshall alongside vannevar bush established the early framework for covert ufo crash retrieval teams marshall received the oath of office as secretary of state from chief justice vinson early in 1947 the president enthusiastically endorsed [7954.7s → 7983.5s] the former chief of staff at a critical time in history it was fairly said that mr truman selected him not because of his experience but because he was marshall there’s nothing that i can say at this time regarding matters that pertain to my position in the state department but i assume the students were that great for the feeling of great responsibility and a very earnest desire to [7985.1s → 8021.6s] carry out the foreign policy of this government marshall is one of the most pivotal figures in the entirety of the second world war according to the marshall foundation quotes george c marshall’s contributions to our nation and the world cannot be overstated he was the organizer of victory and the architect of peace during and following world war ii he won the war and won the peace end quotes whether this was building the u.s army for world war ii spearheading senior leadership in the manhattan project or leading the wildly successful marshall [8021.6s → 8045.4s] plan to rebuild western europe with the modern day equivalent of 100 billion dollars following world war ii marshall’s legacy is undeniable and as we will talk about i additionally believe during the manhattan project 2.0 as secretary of state and secretary of defense marshall was instrumental in building the architecture of legacy programs [8048.1s → 8077.7s] the alsos mission was a little-known intelligence operation conducted in europe by the manhattan engineer district to learn firsthand how close germany was to developing its own atomic weapons to quote the atomic heritage foundation quotes under the command of general leslie groves these operations succeeded in capturing most of the key german scientists stores of uranium ore and other nuclear raw materials and thousands of research documents regarding the development of atomic [8077.7s → 8110.3s] energy end quotes the u.s considered it critical to gather intelligence on progress made if any within the germans atomic weapons program however a unique problem presented itself the secrecy surrounding the manhattan project was so robust military intelligence could not be briefed into anything regarding atomic energy thus military intelligence was fully unequipped to analyze german atomic progress general marshall of course found a solution in 1943 suggesting a separate [8110.3s → 8142.7s] intelligence operation under the umbrella of the manhattan engineer district to be established the alsos missions these missions were overseen by who else but general leslie groves general george marshall and his g2 at the time colonel boris pash and dr vannevar bush so as we go forward just remember at this time general marshall was fully prepared to utilize his g2 for covert and unacknowledged missions alsos was conducted in three phases with an original detachment [8142.7s → 8173.9s] consisting of 13 military personnel including interpreters and five scientists phase one of alsos saw operations in italy whose objective was to quote obtain advanced information regarding scientific development in enemy research and development and to secure all important persons laboratories and scientific information immediately upon their becoming available end quote phase two of alsos in france operated to quote begin the awesome task of searching for [8173.9s → 8205.1s] the german scientists capturing any nuclear related materials such as uranium and heavy water in locating and deciphering any related scientific documents end quotes finally phase three of alsos in germany was executed near the tail end of world war ii when it was widely known the nazis did not have a successful atomic program phase three continued to secure nazi personnel facilities research etc with the expressed mission to allow none of germany’s nuclear materials and [8205.1s → 8210.3s] absolutely none of the german scientists to be allowed to fall into soviet hands [8211.7s → 8251.5s] alsos manhattan’s intelligence operation to identify and secure facilities personnel research materials etc regarding the world’s then greatest secret was a resounding success this sounds an awful lot like the intelligence apparatus behind ufo crash retrieval teams does it not being able to secure ufos under total secrecy with zero interference from traditional military intelligence channels in competition with adversarial teams intriguing how marshall seemed to establish this quote-unquote rapid recovery apparatus what is even more intriguing [8251.5s → 8291.9s] here is this if alsos contains small teams mostly specializing in intelligence and science how did they forcefully secure atomic infrastructure well let’s go ahead and meet the t-force an operational arm of the world war ii supreme headquarters allied expeditionary force tasked with operating on the front lines securing german scientists scientific and industrial technology laboratories facilities etc before they could be destroyed in a scorched earth effort by retreating nazis or seized by soviets t-force was ordered to quote identify secure [8291.9s → 8325.5s] guard and exploit valuable and special information including documents equipment and persons of value to allied armies end quotes t-forces were lightly armed extremely mobile deployed rapidly and secured a site for special investigators to move in and exploit what had been captured of nazi infrastructure and these special teams that’s right of course the alsos missions teams for the alsos missions t-forces captured a sub-critical experimental nuclear reactor [8325.5s → 8357.7s] uranium ingots heavy water and several dozen atomic scientists and their staffs including the infamous werner heisenberg this seizing of scientists was often done in a heavy-handed method quotes their methods had echoes of the gestapo kidnapping at night by state officials who offered no evidence of identity end quotes indeed for the alsos missions t-forces even captured nazi atomic materials processing plants within soviet controlled territory [8359.0s → 8392.1s] so you see the manhattan project not only laid out the secrecy apparatus for the entire security and secrecy structure behind the manhattan project 2.0 which one could strongly argue was infinitely more secret than the atomic project but the manhattan project also saw the direct blueprints laid by general marshall for rapid reaction ufo recovery teams often compartmented or hid within offices like marshall’s g2 the alsos and t-force directly mirror the ufo recovery teams [8392.1s → 8433.9s] of today a highly mobile light direct action team oftentimes parallel tier one elements who can secure a ufo crash site until a highly specialized scientific team oftentimes doe and an s8 nest nuclear emergency support team can roll in to decide how to proceed with removal transport and exploitation of recovered materials all supported by an intelligence apparatus answering directly to legacy program elements completely removed from standard dod slash ic intelligence channels now moving on here we have translated the shifting of the manhattan [8433.9s → 8470.2s] project secrecy structure onto the manhattan project 2.0 and explored critical personnel and concepts paramount to copying the atomic project security blanket onto the early ufo legacy program efforts the two most critical figures to this discussion that i strongly believe constructed the very skeleton for the compartmented and need to know secrecy architecture behind ufo legacy programs are dr vannevar bush and general george c marshall and of course i must give a huge shout out to general leslie groves for outline the conceptual blueprint [8470.2s → 8503.1s] for this security architecture there are myriad more manhattan project scientists military officials and more that likely moved on to the manhattan project 2.0 from the atomic project but really fall outside of our scope of work today specifically analyzing the security architecture such as possibly dr edward teller father of the hydrogen bomb who allegedly got hired at s4 under eg and g perhaps we will revisit these names and numerous more in the future [8511.0s → 8549.5s] as i state oh so often the ufo legacy program structure of today and the onion of secrecy exists in a fragmented shell of itself far removed from the golden age we just spent two hours speaking about in my understanding in the modern day the head of the legacy pyramid which is the ufo control group has sat empty since the departure of vice president dick cheney in 2009 with the closest quote-unquote mob boss being dni james clapper from 2010 to 2017 although clapper served a role with remarkably less power than cheney we’re now today a group [8549.5s → 8586.1s] of slightly over two dozen alive at any given time have any idea of the total breadth of siloed ufo programs indeed in my legacy program structure the administrators often elements of dod and ic agencies operate legacy activities in siloed containers often with little to no cross collaboration across branches of the armed forces or intelligence agencies i have published extensively on how likely in the early 2000s 2005 and 2006 to be hyper specific select prime contractors like [8586.1s → 8617.2s] northrop grumman harnessed irad or independent research and development to seize an opportunity to fund and operate their own breakaway ufo retrieval and exploitation activities so in the modern day of 2026 we are left with a legacy program portfolio with no element of central leadership a system in which everyone owns a proverbial piece of the pie with no centralized effort objective or roadmap that operates under exponentially more heightened security and secrecy [8617.2s → 8646.9s] protocols than the manhattan project 2.0 that came before these grains of rice within a rice bowl are indeed a far cry to say the least from the manhattan project 2.0 we spent two plus hours breaking down which existed as a centralized effort with strong leadership by presidents cabinet level officials select statesmen and some of the most accomplished military and scientific minds the united states had to offer while the manhattan project 2.0 was also subject to [8646.9s → 8682.3s] compartmentation and restricted need to know access like its precursor the atomic project the manhattan project 2.0 seemingly operated with a very clear directive to retrieve and exploit crashed landed or downed non-human technical vehicles attempt to understand the modus operandi behind this non-human presence store and study the occasional craft occupant or pilot and employ extensive defensive countermeasures such as counterintelligence passage material disinformation campaigns and general spy craft [8682.3s → 8712.9s] to protect against both insider and outsider threats and of course the question must be asked why was such a secrecy blackout undertaken in the manhattan project 2.0 besides the obvious budding sub rosa cold war with our adversaries was soviet espionage and spy craft in particular where the need to hide asymmetric warfare capabilities and enforce feudalistic dominance was paramount well who knows this is certainly up to interpretation perhaps the presence of [8712.9s → 8743.1s] non-human bodies was deemed too psychologically damaging and existentially damaging immediately following world war ii one thing though is for certain here the application of the manhattan project security blanket onto the manhattan project 2.0 certainly introduced an immediate ultra-compartmented portfolio of programs that could be run alongside but undetected from the larger u.s government whose existence could not be revealed by the congress executive order or [8743.1s → 8777.7s] any one core program members deemed quote-unquote temporary employees like future democratic presidents so with the iron grip of the manhattan project 2.0 secrecy apparatus how do we today have an even more strict security apparatus that exists as a fragmented and scattered legacy program portfolio what exactly is the nexus or chain of dominoes that led to this incredible schism well i believe we can find answers in studying the creation expansion reforms [8777.7s → 8784.8s] and changing of special access programs during the height of the cold war specifically the 1980s [8791.9s → 8827.9s] i’ve always been into computers in this computer i’m working with now this computer is hot we’ve got some of the fastest computers in the world aim high air force now in part two of this project or perhaps right now you’re watching a supercut and this is all one ginormous project we are going to dive into the ultra strict definition of special access programs or saps their history and applications to investigate why and how ufo programs are protected by such systems beyond standard classification but here today we will [8827.9s → 8858.7s] do a little review of history recall that the manhattan project and thus the manhattan project 2.0 operated off of what would become the groundwork for special access programs a system of total secrecy and compartmentalization beyond standard classification levels to ensure total program secrecy need to know access in a single centralized control group with minimal chains of command the manhattan project 2.0 of course enjoyed expanded secrecy with the introduction [8858.7s → 8892.7s] of the 1954 atomic energy agreement as i discussed i believe truman and eisenhower largely laid the groundwork for ufo legacy program secrecy through legislation and classified presidential executive orders eisenhower in particular introduced the modern day u.s classification framework through the 1954 atomic energy agreement as well as executive order 10501 which got rid of restricted classification not to be confused with the does restricted data and introduced the modern [8892.7s → 8928.6s] day three levels of classification confidential secret and top secret this time epoch largely saw dod and ic agencies adapt ad hoc special access program protocols to layer on to top secret classification for unique threats and programs and these include top secret code word read on access which you can observe extensively in the early days of the nro thus here we see the rise in quote-unquote black programs such as 1958’s greenbrier congressional bunker and indeed of [8928.6s → 8964.7s] course i believe eisenhower himself implemented an ad hoc special access protocol system learned from the manhattan project to hide senior leadership of the manhattan project 2.0 within the national security council’s 5412 committee special group i firmly theorized the 1950s 1960s 1970s into the early 1980s observed the glory days of the manhattan project 2.0 successfully retrieving crashed ufos worldwide and performing exploitative rd tne practices at aec and doe [8964.7s → 9005.5s] national labs and defense industrial base military infrastructure indeed i believe this epoch saw the addition of numerous ffrdc’s and contractors to aid within the effort such as the mitre corporation aerospace corporation trw lockheed corporation sperry rand ltv and so on bear with me and fast forward just a little bit in this golden age where i imagine ufo legacy senior leadership then hidden within nixon’s 303 committee an evolution of the 5412 committee jumped with joy when in march 1972 nixon’s executive order 11652 took place which saw [9005.5s → 9041.4s] the formal framework for special access programs officially established this executive order legitimized enhanced access controls for programs involving severe national security concerns shifting from informal ad hoc practices seen in the eisenhower days to structured policy frameworks while maintaining strict bottlenecks on congressional and interagency awareness in short this nixon effort greatly authorized heightened security protocols for information and programs beyond top secret handling and let me be clear here because i say that [9041.4s → 9073.8s] there is a strong argument that nixon like select other presidents we will speak on was well versed and informed with ufo legacy activities i strongly theorized this aggressive expansion of implementation of deeply covert unacknowledged special access program precursors within the 1970s and 1980s leveraged to protect dod acquisition programs stealth aircraft and most importantly in my opinion ufo retrieval and exploitation programs directly led to the exposing [9073.8s → 9110.3s] of the program ecosystem to unwanted eyes the u.s congress after all a 1973 house committee on government operations report documented widespread and uncontrolled growth of unauthorized applications of special access labels across dod components this report directly addressed tremendous concerns from nixon’s executive order 11652 including quotes widespread use of dozens of special access distribution or control labels stamps or markings on both classified and unclassified documents [9110.3s → 9138.9s] end quotes these access controls were harnessed by quotes many executive agencies having classification authority and dozens of other agencies who do not possess such authority end quotes intriguing statements especially in reference to what i just spoke of that ad hoc security protocols specifically top secret code word access were rampant since the days of truman and eisenhower indeed with glimpses of the secrecy architecture beginning to show themselves in the [9138.9s → 9172.3s] 1970s we now arrive to the great schism which can be observed within the presidential administration of reagan who like truman eisenhower johnson and nixon before him was highly likely read into and served a senior leadership position for ufo legacy activities i call upon the scientific community in our country those who gave us nuclear weapons to turn their great talents now to the cause of mankind and world peace to give us the means of rendering these nuclear weapons [9172.8s → 9213.1s] impotent and obsolete the 1980s was a period of massive overhaul controversy and shifting tides regarding the structure secrecy and top cover of the u.s’s most top secret programs up until the 1980s clandestine unacknowledged programs established to protect dod acquisition programs and often used to hide sensitive operations existed as saps in all but named being referred to in the 1980s and decades prior as quote-unquote black programs such black programs included stealth aircraft development under the lockheed skunkworks and north of grumman [9213.1s → 9240.3s] including the f-117a nighthawk and b2 bomber respectively of course within the same subset of stealth aircraft black programs there is an extremely strong argument to be made that major undertakings were underway to adapt derivative technologies onto human-made airframes such as those enormous black triangles with three lights on each vertex and one light in the center that are observed oh so often [9242.5s → 9285.4s] black programs as the precursor to saps saw significant shifting in security structure similar in concept to nixon’s 1972 executive order 11652 with ronald reagan’s 1982 executive order one two three five six eo12356 titled national security information served as the latest iteration of special access program and black program frameworks following nixon’s executive order 11652 and eisenhower’s executive order 10501 this reagan executive order expanded the categories of classifiable information and lowered the threshold for classification [9285.4s → 9325.6s] essentially tightening the grip of government secrecy from carter’s previous administration’s attempts specifically in 1977 of government secrecy shifting towards declassification transparency and let me be clear here as we move on eo12356 did not trend towards government transparency no indeed this order greatly standardized and expanded the sap framework but crucially here saw expanded oversight and governance over covert programs which was a sharp course correct from the less consistent governance that existed since the manhattan project [9327.6s → 9362.7s] this point i am making here is very very very important i am even pausing to explicitly speak on this topic reagan’s executive order one two three five six effectively ended the days of the legacy program wild wild west where the program could do whatever in the world it wanted with top secret codeword access prior to this time epoch u.s black programs heavily featured top secret codeword read-on access for covert programs such as world war ii segant or signals intelligence [9362.7s → 9396.2s] compartments the manhattan project early nro programs black programs of the 1970s and so on reagan’s executive order largely formalized and tightened this compartmented security read-on structure so with the days of the wild wild west ending where legacy operations could no longer stuff programs wherever and however they wanted with complete and impenetrable security plus some massive sap exposure we will speak on momentarily legacy programs were forced to turn to alternative [9396.2s → 9427.2s] and new methods to stay secret we will of course speak on this more later and in part two indeed as we will discuss in part two our sap overview modern day dod and sometimes department of energy cite their establishing authority for saps as ronald reagan’s executive order one two three five six and further superseding orders like obama’s executive order one three five two six the defense counterintelligence and security agency’s special access program training course [9427.6s → 9467.6s] directly states saps were publicly acknowledged for the first time in the early 1980s why was this well enter yellow fruit in the iran contra a few months ago i told the american people i did not trade arms for hostages my heart and my best intentions still tell me that’s true but the facts and the evidence tell me it is not as the tower board reported what began as a strategic opening to iran deteriorated in its implementation into trading arms for hostages this runs counter to my own beliefs to administration policy and to the original [9467.6s → 9500.3s] strategy we had in mind the iran contra scandal is one of the united states largest political scandals in history from 1981 to 1986 elements of the reagan administration specifically individuals within the national security council trafficked arms to iran then under an arms embargo and used the proceeds from the sales to fund the contras a nicaraguan military rebel group the iran contras triggered congressional hearings an independent council investigation and brought [9500.3s → 9533.3s] forth a serious constitutional crisis over executive power covert action and the ability for elements of the executive branch to circumnavigate the congress sound familiar preceding the breaking of the iran contra in 1986 was another massive scandal focused on the prior decades expansion of covert operations that helped expose some of the broader connective tissue to the iran contra enterprise in 1983 an unremarkable dod internal audit turned up a covert unacknowledged [9533.3s → 9568.3s] special access program by the name yellow fruit out of the army’s special operations division sod the purpose of yellow fruit to provide additional operational security and counterintelligence for the central american contra mission as well as other classified operations now quickly take a step back yellow fruit why this name no not to reference a banana in south america sap naming convention is actually quite interesting and we will cover this more in part two saps are often [9568.3s → 9598.9s] given an operational unclassified nickname consisting of two unrelated words plus possible sapco additional classified code words okay but what is interesting about the conceptual basis for yellow fruit here was the program being run out of sod or the army special operations division according to the u.s army war college several indications state that covert military intelligence organizations had been quote utilized to circumnavigate congressional restrictions and [9598.9s → 9636.8s] reporting requirements levied onto the cia and quote an example here of course is the army sod who quote provided the cia with various types of covert military support in latin america that the agency itself was restricted from doing by congressional mandate end quotes an intelligence apparatus working within covert special access programs that circumnavigates standard chains of command and traditional reporting hmm does this ring a bell to anyone whether the also’s missions or the common legacy framework i think so anyways yellow fruits cover [9636.9s → 9654.2s] was blown due to significant cost discrepancies being discovered through internal audits under lieutenant colonel james e duncan who was tasked with providing top cover and support for yellow fruit from his staff position within the assistant chief of staff for intelligence of course the g2 [9655.9s → 9687.0s] to not blow his cover during yellow fruit and be connected back to the pentagon lieutenant colonel duncan would retire from the army and set up his own private consulting firm bsi this is quite literally data masking a staged retirement to continue covert operations within the same capacity i have actually seen this exact sort of behavior before with major generals within the air force hidden wing program circa the late 2000s and cut out companies for covert operations [9687.0s → 9721.8s] should not come as a shock here in fact the cia has done this plenty of times for both clandestine activities and in my opinion self-fund for ufo legacy programs one tangible example here is e-systems a cia shell company that was once ltv a defense contractor that i am quite confident worked within the manhattan project 2.0 in the 60s and 70s shockingly top army leadership were never briefed about yellow fruit operating as a commercial cutout outside the pentagon [9722.6s → 9761.4s] indeed army chief of staff john wickman stated they had never been fully briefed at all about the quote-unquote black programs run by the special operations division sod essentially army brass had zero clue what was going on in their own army the revelation of yellow fruit led to not only court marshals in prison time but also to significantly increased oversight for special access programs fast forward here to the wilson davis notes of the early 2000s i will not waste more than a minute recounting these notes i speak on terribly often which [9761.4s → 9796.0s] recount a meeting with senior ic official and rear admiral thomas wilson and dr eric davis in the parking lot of egng in 2002 these alleged notes recall wilson attempting and being stonewalled in accessing the ufo legacy program portfolio partially hidden within the usd ans or undersecretary of defense for acquisition and sustainment then known as the oustat gatekept by the special access program oversight committee senior review group srg as always i do have my [9796.0s → 9827.7s] issues with eric davis and do question his trustworthiness specifically regarding derivative technologies most of his secondhand information on legacy seems to come from a retired four-star general officer who brute-forced his way into touching a recovered craft and a senior trw vice president who engaged with retrieval operations for decades both of whom i strongly believe are credible and legitimate sources i do not know why the wilson davis notes leaked in fact eric davis [9827.7s → 9858.6s] on american alchemy recently obtusely confirmed the validity of these notes and remarked how the notes were supposed to be for internal use how did admiral thomas wilson react uh when you when you met him in 1997 and why i guess why did people direct him to you and then uh what transpired in the in the meeting get into that okay i can’t confirm or deny that we met for the security reasons okay there are legal issues still involved that are active so um uh because i can’t reveal [9858.6s → 9891.0s] that in public that wasn’t meant for public uh consumption and that was released from mitchell’s estate and that was supposed to be destroyed one year after mitchell got a copy of it as a courtesy from from who generated it regardless of the credibility questions surrounding davis i believe the fundamental facts of these notes are indeed true that wilson attempted to use his need to know authority as deputy dia director to access the legacy portfolio and was denied within the [9891.0s → 9927.1s] notes wilson allegedly states the gatekeeping structure for ufo programs was a necessary redundancy quote they said they were formed out of necessity to protect themselves after a near disaster in the past almost blew their cover something to do with an agreement that was reached with a couple of pentagon ses’s senior executive service overseeing saps in those days were vague about what that was end quote furthermore to nail in on specifics here wilson allegedly stated quotes they said years ago in past an audit investigation led to them [9927.1s → 9960.3s] and it wasn’t supposed to nearly outed end quote i have theorized on myriad occasions the origin of this audit investigation indeed i’ve investigated nro carryover and forward funding scandals when the nro was declassified in the early 1990s mid-1980s instances of the u.s air force and navy not following special access program protocols and mid-1980s instances in which the lockheed corporation mishandled classified documents for carveout contracts [9961.6s → 9995.2s] all of these likely have seen gao or pentagon investigators brush elbows with the legacy portfolio and here today in 2026 i am quite confident the audit surrounding yellow fruit and internal dod audits in the mid-1980s leading to major sap oversight changes in conjunction with ronald reagan’s 1982 executive order 1-2-3-5-6 which effectively ended the wild wild west days of top secret code word legacy activities was a major piece in the impetus for legacy programs [9995.2s → 10025.5s] taking drastic and severe measures to burrow even deeper into secrecy channels to hide themselves from u.s government and temporary employees these snowballing protective countermeasures eventually culminated in 1994 under the clinton administration where legacy took even further precautions to hide from unauthorized u.s government access breaking itself apart and scattering itself into the wind even further when william perry as deputy secretary of defense [10025.5s → 10057.8s] reorganized sap structure greatly expanding the sapco special access program central office and sapok special access program oversight committee and established the srg senior review group this effectively transitioned legacy-led activity oversight into a quasi-government and industry control panel of just over two dozen individuals i highly recommend listening back to that last sentence but with yellow fruit in the early 1980s justice wilson’s watch committee stated [10057.8s → 10092.6s] this audit led to immediate measures to protect the portfolio with enhanced secrecy and gatekeeping structures i theorize with the utmost confidence this series of events plus reagan ending the legacy days of wild wild west top secret codeword access directly led to the fracturing of the centralized manhattan project 2.0 and led to the scattering and siloed nature of the programs that culminated in 1994 as i just spoke of to today and let me explain here with some very specific examples [10092.9s → 10127.6s] okay hold your horses before we do that let me briefly explain why i believe this yellow fruit and wider dod sap protocol series of audits and investigations actually almost revealed the ufo legacy program portfolio remember yellow fruit as a usap served to conduct operations around the latin american contras and quote other army classified operations the way saps against special access programs operate as we will discuss at great length in part two is you have a wide [10127.6s → 10144.9s] arcing singular tier one sap umbrella underneath the umbrella sits several tier two sap compartments beneath the compartments sit even farther Tier 3 SAP sub-compartments with several operational projects. This framework is organized [10144.9s → 10150.3s] to group similar capabilities or information into a single compartment or sub-compartment. [10150.9s → 10156.4s] Similar Critical Program Information, CPI, will be grouped together into a singular SAP. [10157.6s → 10163.6s] Yellow Fruit handled a multi-faceted mission, including the CONTRAS and other covert activities. [10164.1s → 10176.4s] Thus, Yellow Fruit was a USAP umbrella, or Unacknowledged Special Access Program. Indeed, I think it highly probable within the Yellow Fruit umbrellas sat individual SAPs [10176.4s → 10188.9s] dealing with the SODS, Special Operations Division, involvement in UFO activities. Thus here, the audit into Yellow Fruit nearly exposed whatever this covert involvement was, [10188.9s → 10227.2s] be it counterintelligence for programs, retrieval operations in Latin American countries, etc. And this really isn’t a shock here. We have a similar example I have covered within the Navy several times. Recall back to my Naval Legacy Programs project, one of my favorite pieces I have ever done that likely warrants a second part in the future. Within the investigation, I spent quite a bit of time discussing maritime UFO and USO retrieval operations, including a fascinating 1991 story off the coast of Aberdeen, Scotland, in which a crewman of a [10227.2s → 10262.4s] DSRV, Deep Submergence Rescue Vehicle, or possibly a DSSV, Deep Submergence Search Vehicle, claimed to have retrieved an exotic triangular craft with glyphic writing from the seafloor. After observing this craft wedged into the ocean floor and sat about a naval vessel after recovery, it was the expressed opinion of this diver, Mark, the vehicle was not of human origin. One of the major objectives of this project was exploring 1964’s DSSP, or the Deep Submergence Systems Project. The DSSP, [10262.4s → 10273.9s] helmed by Chief Scientist of the Navy Special Projects Office, Dr. John Pania Craven, sought to develop technologies to drastically increase the depths with which the Navy could perform [10273.9s → 10314.8s] deep ocean engineering, specifically for search, rescue, salvage, and recovery operations. Products of the DSSP include the aforementioned DSRVs, and two of such vessels were built, the Lockheed Martin Mystic and Avalon, meant to rescue stranded submarines, as well as the never-built, on an acknowledged basis, DSSV, which enjoyed drastically deeper operational depths and salvage-slash-recovery capabilities over its sister DSRV. Regardless, Pania and others stated these vessels were sent on numerous clandestine missions. In his fantastic book, [10314.8s → 10345.1s] The Silent War, The Cold War Beneath the Sea, Craven wrote that the DSSP was established to satisfy the whims of one Project Sand Dollar, an extremely compartmented and top-secret program meant to identify and retrieve items of national security interest on the seafloor. In Craven’s own words, quote, I was shown an inventory itemizing the items known to be on the seabed, and a map of their distribution throughout the world. Could I organize and manage a program to [10345.1s → 10369.1s] carry out this mission using the assets of the DSSP? Furthermore, could I carry it out in such a manner that my family and friends and closest professional colleagues would have no idea that I was involved in such a project? End quote. Craven was briefed into Sand Dollar in 1965, after establishing the DSSP from a naval intelligence officer. The briefing was kept [10369.1s → 10393.0s] so secretive, not even Craven’s staff was to know where he was going, and with whom he was meeting. Craven was taken into a skiff by a well-known submarine officer from the Polaris submarine launched ballistic missile program. When briefed into Sand Dollar, Craven learned this well-known officer’s involvement with Polaris was indeed a cover for Sand Dollar. In fact, Craven would learn [10393.0s → 10398.8s] Sand Dollar was nestled within a complex web of programs, itself hidden under the Polaris program. [10399.7s → 10405.3s] Essentially, Polaris led to several layers of cover programs which led to Sand Dollar. [10406.5s → 10445.9s] This is the exact same matrix with SAP umbrellas, compartments, and sub-compartments as outlined in DoD Directive 5205.07. The same architecture Yellowfruit enjoyed where Polaris is the SAP Umbrella, and nestled within that compartmented architecture sat Sand Dollar, a program deeply embedded in the SAP Umbrella, I highly wager was imperative to maritime UFO crash retrieval operations. I wager that similar to Sand Dollar within Polaris, similar UFO activities existed under the Yellowfruit SAP Umbrella that were almost [10445.9s → 10474.8s] exposed in the 1983 audit that we talked about. Oh, what I wouldn’t have given to have met Craven. Chapter 10 of his book titled, Spooked, details Craven learning of Sand Dollar. It is a truly poignant section to our investigation today. This section details Craven discussing all special intelligence projects out of the Navy requiring a real cover project to operate, where most people working on the cover project did not know it was a cover, [10475.5s → 10493.2s] where one or more individuals cleared for both levels served as the link between the projects. Craven even demonstrated an early outline of the Onion with his quote, seventh veil, end quote, an apparatus of secrecy surrounding top-secret unacknowledged programs, [10493.2s → 10498.4s] in which one could never truly be sure they’d reached the innermost layer of compartmentation. [10501.4s → 10517.8s] Okay, but now let’s circle back because we can finally cover a hyper-specific example, where I theorize we can observe UFO legacy programs burrowing deeper into the Onion or Seventh Veil to disguise themselves following Reagan’s executive orders and the mid-1980s [10517.8s → 10523.4s] audits that led to enormous SAP reforms and expanded oversight over covert projects. [10524.8s → 10557.5s] So, let’s return to a concept I introduced in my recent Northrop Grumman project and visit with the U.S. Air Force. Within the Department of the Air Force, the DAF, the overarching structure of the Air Force, sits the Headquarters of the Air Force, or HAF. The HAF consists of the Air Staff, the top military leadership supporting the Secretary of the Air Force. There are numerous compartments within the HAF that I’ve accused of operating within Air Force legacy activities and the Hidden Wing Program, but let’s focus in on the SAFAA, [10557.5s → 10571.4s] or the Administrative Assistant to the Secretary of the Air Force. SAFAA is a senior executive official-run organization within the Department of the Air Force, responsible for providing administration, management, and support [10571.4s → 10596.9s] services to the Secretariat, SAFOS, and Headquarters of the Air Force, HAF. And I would like to visit a document titled, quote, A History of the Office of the Administrative Assistant to the Secretary of the Air Force, end quote. Out of the Air Force History and Museums Project, where I am shocked, we can find a specific discussion in an unclassified setting. Within the document, [10596.9s → 10615.2s] we can find a section titled, quote, SAFAA and Outside Activities, end quote. This section referenced a 2018 interview with retired Administrative Assistant, aka SAFAA, William A. Davidson. In this interview, Davidson discussed several, quote, [10615.2s → 10628.2s] outside activities, end quote, in which the SAFAA had been and continue to be involved. Davidson stated there were, quote, several activities that were in other agencies, [10628.2s → 10648.6s] over which the Air Force had administrative control, end quote. And let me just say that again, plainly, several activities that existed outside of the Air Force that SAFAA specifically wielded administrative and operational control. In any definition, this is what’s known as a cover program. [10649.4s → 10687.7s] Davidson stated two such programs were started, quote, in Pete Aldridge’s day, end quote. The quote-unquote outside activities did not show up in mission directives modern day, and operated exclusively under the SAFAA. For inarguable proof, these outside activities were stashed under SAFAA as a cover program. Please note, these outside activities did not fall under the oversight of SAFAA-Z, the Directorate of Security, Special Program Oversight, and Information Protection within the SAFAA. SAFAA-Z is the Air Force Component [10687.7s → 10714.4s] Level SAPCO, or Special Access Program Central Office. So, these outside activities established under Edward C. Aldridge were covert enough to be hidden away from the standard Air Force Special Access Program Oversight channels, and even the Air Force’s own SAPCO, let alone the Air Force at large, and were stuffed exclusively under the management and operational control of the Administrative Assistant to the Secretary of the Air Force. [10715.7s → 10736.8s] And let me be plain here, I do not think these activities were started under Aldridge’s day. Moreover, these activities outside the Air Force were re-rolled and hidden within SAFAA to operate as a cover office after a series of audits and SAP reforms, led to overall SAP reform in the mid-1980s. [10738.6s → 10769.4s] Edward C. Aldridge has one of the most impressive CVs I have ever discovered. Aldridge served as CEO of the Aerospace Corporation, President of McDonnell Douglas, Senior Manager within LTV Aerospace, Undersecretary of Defense for Acquisition, Technology, and Logistics from 2001 to 2003, of course a position I believe is paramount to gatekeeping UFO programs, Director of the NRO from 1981 to 1988, and Secretary of the Air Force [10769.4s → 10810.8s] from 1986 to 1988, as well as Undersecretary of the Air Force from 1981 to 1986. Since Air Force activities were spun up in Pete Aldridge’s day, this is when Aldridge was Undersecretary of the Air Force from 1981 to 1986. Funny enough, this is exactly the same period Aldridge also served a dual role as Director of the NRO. Indeed, whilst serving these dual Air Force and NRO roles, Aldridge had additional responsibilities for providing overall direction, guidance, and supervision for Air Force space programs, including launch and on-orbit [10810.8s → 10833.1s] operations and planning for future space capabilities. So, I wager with the utmost confidence these roles were dual-hatted, with Aldridge also serving a Senior Executive Official role within UFO legacy programs, specifically within Joint NRO and Air Force program, [10833.2s → 10859.3s] which believe it or not, have been quite common throughout the decades. Indeed, I am familiar that as of 2017, specific funds have been misappropriated and earmarked for Joint NRO and Air Force UFO legacy activity efforts, so the idea of Joint NRO Air Force operations is not indeed a stretch. After all, the NRO was established to coordinate [10859.3s → 10882.8s] intelligence activities between the Air Force and CIA in the early 1960s. I wonder if the NRO and Air Force have worked together specifically not just on ISR, Intelligence, Surveillance, and Reconnaissance for UFO crash retrieval operations, but also Joint RDT&E, Research, Development, Test, and Evaluation, on derivative technologies [10882.8s → 10888.0s] or alien reproduction vehicles that can operate in both atmosphere and microgravity. [10889.6s → 10920.2s] So, if my thesis here is correct, these outside activities were originally stashed and operated out of the NRO, with the Air Force maintaining administrative and operational control, and due to audits nearly ousting elements of the legacy architecture. In the mid-1980s, while Director of the NRO and Undersecretary of the Air Force, Edward C. Aldridge, stuffed these activities under the SAPAA to operate as a cover office to completely bypass the standard Air Force [10920.2s → 10952.7s] SAP oversight channels. I believe such operations were largely ubiquitous across the U.S. Armed Forces and intelligence agencies involved in the UFO legacy program efforts. Shifting SAP controls and the death of the Wild Wild West days of the legacy effort, as well as the 1980s nearly exposing the program to Congress and non-REDN personnel, saw the once-unified legacy structure that in the 40s through the early 80s housed a tiny oversight body, had already stretched itself thin over the [10952.7s → 10972.4s] decades in the Wild Wild West by hiding within SAP umbrellas, introducing ad-hoc security access protocols and wildly loose top-secret codeword read-on access, and included several contractors and FFRDCs which resulted in numerous a la carte security and read-on protocols, finally started [10972.4s → 10978.7s] to show its cracks, and thus the Manhattan Project 2.0 was forced to dismember itself. [10979.9s → 11010.0s] This is my entire thesis for the schism from the Manhattan Project 2.0 to the shattered and scattered siloed programs of today, existing as grains of rice in a rice bowl. Reagan ending top-secret codeword Wild Wild West legacy activities, in addition to close-shape audits and various risks of spotlight, forced the legacy architecture to sever off many of its limbs to hide under different rocks to ensure the program infrastructure was as compartmented, deep-sixed, [11010.0s → 11021.6s] and hidden as theoretically possible. Thus the process began of legacy programs folding like origami and scattering itself beneath too many layers of cover offices and programs, [11022.2s → 11046.9s] and over time central leadership lost its grasp over these now siloed activities. This shattering and siloing of the programs was cemented in 1994, when oversight of the legacy structure was permanently transitioned into a quasi-government and industry group of slightly over two dozen individuals. And the last man who possessed the tradecraft and Machiavellian [11046.9s → 11052.0s] politics to hold together this fractured shell was Darth Vader himself, Dick Cheney. [11054.0s → 11060.7s] Perhaps, as an example here, once upon a time, scientists from the Navy Special Program and Air [11060.7s → 11089.0s] Force Test and Evaluation operated together on recovered vehicles of unknown origin. But after this schism, this collaboration was siloed apart. Thus the Air Force and Navy continued on with these programs separately without any sort of collaboration or communication across compartments. And after decades of scientists, security managers, and senior executive officials come and go, the program greybeards aren’t even aware of a similar redundant program [11089.0s → 11103.6s] across the armed forces. This is why I speak of the golden era of legacy being long gone. Where significant brain drain, redundancy, and lack of centralized leadership is dooming this once great effort. [11126.3s → 11145.2s] Into part one of two of analyzing the overall UFO legacy program, security architecture, onion, however you want to call it. Now, in the making of this project, I’m sure as you can guess, I was thrilled to hear Dave Grush speak at that space symposium and actually talk about the onion and sort of the rice bowl infrastructure of the programs when [11145.2s → 11149.8s] he was speaking to Jeremy Corbell and Mike Gold. So, of course, that made a fantastic clip. [11151.2s → 11176.3s] If you’re new to the channel, thank you so much for joining me this whole adventure. I think this was about three hours, five minutes, seven minutes. So, from the bottom of my heart, thank you. And if you’re new, this is about the time where I launch into my post video rant, kind of recapping everything we talked about. So, what seems to be the case with every single project I do these days, I set out to make a project. I think to myself, this is going to be great. This [11176.3s → 11202.5s] is going to be an hour and a half. This is going to be two hours, two and a half hours tops after my end of video rant. And quickly, before I know it, things start spiraling into three-hour videos, four-hour videos where I have to cut a lot out. So, because I wanted to talk so much about the UFO Legacy Program security apparatus, that’s not a hour and a half, two-hour, three-hour video to make. And I learned that very quickly. So, again, this is a part one of two. Part one today focused [11202.5s → 11235.2s] on the inception of the UFO Legacy Program security apparatus. Mainly, this be the Manhattan Project 2.0. Key individuals with the Manhattan Project 2.0, specifically George C. Marshall, as well as Dr. Vannevar Bush, and how these gentlemen probably configured the architecture and the framework for the secrecy apparatus. And I do want to dive in and talk about that a bit more. We also, of course, talked today about changing tides in the Cold War. I cannot wait to expand on that more, specifically [11235.2s → 11264.5s] with something I think I said twice throughout the video, which is, even though the great schism of the Manhattan Project 2.0, this largely centralized effort that was spearheaded by presidents, by key national security officials, by the National Security Council, specifically its 5412 Committee Special Group, and the 303 Committee under Nixon. This great schism occurred due to special access program reform. And again, let’s talk about through that, which kind of climaxed in [11264.5s → 11292.8s] 1983 to 1985. And then specifically what I want to speak about again is 1994, under the Clinton administration, when William J. Perry reorganized the Special Access Program Oversight Committee to include the SAPCO, the Special Access Program Central Office, and the SRG. You know, I talk about this a lot in reference to the Wilson Davis notes. I do now possess knowledge that this was a real instance of sequestering and hiding away the legacy program portfolio, [11292.8s → 11324.3s] completely removed from Eric Davis and the Wilson Davis notes. So with supremely high confidence, again, with extremely high confidence, outside of Eric Davis, outside of the whole circular reporting crew, I am quite confident that in 1994, this was the last year that legacy programs had any semblance of centralized leadership. After 94, with William J. Perry’s actions, the UFO legacy program portfolio was fully scattered into the wind, into a quasi-government [11324.3s → 11335.2s] and industry group of just over two dozen people. And if you hear me say just over two dozen people, I’m sure you can infer the exact number. So let’s start back today. [11337.2s → 11356.2s] What was really great about this program, I mean, this was a very difficult project to make just because I cover so many decades. I mean, realistically, we covered 1943 about up to 1994, so quite a bit to cover. But what was fantastic about this video, which I loved so much, [11357.5s → 11363.0s] is I got to watch Christopher Nolan’s Oppenheimer several times just to kind of get inspired, [11363.0s → 11389.2s] understand the individuals in the film that I was going to speak about and so forth. I wish I could have included more footage from Oppenheimer, but of course, I don’t want to get copyright striked. I really wanted to show figures that I was talking about and their character in Oppenheimer. For example, Gordon Gray on Dwight D. Eisenhower’s National Security Council as his key national security advisor. If you remember the trial of Oppenheimer, the gentleman and the prosecutor who were asking him questions, I can’t remember the [11389.2s → 11401.6s] actor’s name, but the man at the head of the table directly across from Oppenheimer, that was Gordon Gray. You can see Stimson in the meeting where Oppenheimer is speaking with other individuals like George C. Marshall, of course, sitting in the corner [11401.6s → 11431.2s] talking about where to drop the first atomic bombs. Of course, there’s Leslie Groves. There’s Klaus Fuchs. There’s Dr. Lawrence. There’s so many individuals. And of course, there is Vannevar Bush, famously played by the actor who also plays, I think, Papa in Stranger Things. So that’s quite refreshing to see. Of course, Oppenheimer is about Oppenheimer, so Vannevar Bush plays a pretty minor role. He’s only in a couple scenes, including the Trinity test, including being at Princeton, or was it Berkeley, where he’s speaking to Dr. Lawrence [11431.2s → 11453.5s] about the atomic project. And I think he is also at an AEC meeting with Louis Strauss. So that was just so great. If you didn’t watch Oppenheimer before this project, I highly recommend watching it now and try to view it in a different lens. It’s very hauntingly beautiful. Now, of course, I wanted to include music from Oppenheimer, mainly the primary song, [11453.8s → 11466.7s] you could call it Can You Hear the Music? But you can’t do that with music laws on YouTube. That would have been excellent. So we talked about several concepts stripped from the Manhattan Project onto the Manhattan Project 2.0. These include [11467.3s → 11495.2s] political shield slash cover, physical security, compartmentalization, and so on. I think the most obvious sort of transition from Manhattan to Manhattan 2.0 is, of course, compartmentalization. As we discussed today, Leslie Groves subjected the Manhattan Project to extreme compartmentalization. If you watch Oppenheimer, you’ll see that as well, where various departments weren’t able to speak to each other. As Leslie Groves famously said, [11495.2s → 11519.1s] scientists, engineers, technicians knew just what they needed to do to accomplish their mission. Of course, this led to rising tensions between Oppenheimer and Leslie Groves. But of course, we also had Vannevar Bush, who I believe is one of the most central figures in the entire United States to establish not only the legacy program security structure, [11519.1s → 11535.9s] but also legacy programs outright. Let me explain that a little bit. For the compartmentalization and secrecy apparatus, Vannevar Bush was famous for the initial systems of self-censorship, kind of the precursor to restricted data, where a scientist or a technician [11535.9s → 11568.2s] would write down data or ideas about atomic energy, and that would be inherently classified. And at first, there was a system of self-censorship, where the scientist, the technician, the physicist was expected not to talk about that breakthrough, that understanding, that document. And of course, that was written into law and even slapped with restricted data, where something is born classified. So Vannevar Bush is not only one of the most important scientific figures in all of United States history, but he is also the foundational [11568.2s → 11594.8s] individual behind our scientific and government partnership of industry. And let me explain that. If you watched my Aztec video, you will know conceptually a little bit of what I’m talking about. But in 1942, I believe it was, when Vannevar Bush was with the OSRD, the Office of Scientific Research and Development. This, of course, was a precursor to the JRDB, Joint Research and Development Board, and Research and Development Board, which arose out of the 1947 [11595.3s → 11635.8s] National Security Act. Vannevar Bush kind of spearheaded scientific progress and weapons progress and the scientific and military relationship during World War II. Famously, Bush set up the MIT Radiation Lab, which was a precursor FFRDC. Shortly after the war, MIT Rad Lab closed and reopened as MIT Lincoln Laboratory. In some of the Bush clips we talked about, Bush was famous for establishing the relationship with the scientist and the government. So Vannevar Bush, he was huge into university-sponsored research. I mean, [11635.8s → 11674.1s] his right-hand man, who was also on the top policy group within the Manhattan Project, was, I believe, Harvard’s either dean or dean of the sciences, what have you. But Vannevar Bush really set the precursor for both FFRDCs, federally funded research and development centers, their precursors, FCRCs, federal contract research centers, and UARCs, university-affiliated research centers. I don’t talk about UARCs as much lately than I used to, mainly because FFRDCs are a little bit more prominent in actually controlling and PMing, program managing, [11674.1s → 11691.4s] various aspects of legacy programs. UARCs are more of a specialized think tank to also conduct tasks or ideas or scientific pursuits that their government customer couldn’t otherwise accomplish in-house. So I talk about UARCs quite a bit. I’d return to some of my discussion about [11691.4s → 11720.2s] them, but Vannevar Bush established so much of our current military and scientific infrastructure. And of course, that’s not even to mention the various crash-retrieval cases he’s been connected to, most famously Aztec by William Steinman. I expressed my frustration then, and I’ll express my frustration again, that William Steinman, although his work is legendary and excellent, was not more fastidious about documenting his sources. I can’t fully rule out that Steinman [11720.2s → 11738.3s] was able to pluck ideas of Vannevar Bush and his inclusion from maybe IPU documents that circulated before they leaked in the early 90s. I can’t rule that out. However, I still maintain I do believe Vannevar Bush was a key member of the Manhattan Project 2.0. Leslie Groves, I don’t [11738.3s → 11748.4s] believe so. I think he was forced to retire shortly after the Manhattan Project. George C. Marshall, of course, integrals of the Manhattan Project 2.0 and founding the skeleton of the [11748.4s → 11780.0s] security structure, he left pretty early. He never served on Eisenhower’s administration. I believe he left in 50 or 51 after his stint as Secretary of State. But as we can see, which actually parallels really interesting to the IPU documents, is George Marshall was the brain behind the Alsos missions. And George C. Marshall tasked his G-2 to perform covert intelligence missions for the Manhattan Project under the auspice of the Alsos missions, which Alsos means groves in [11780.0s → 11808.4s] Greek. When I was reading from the Nuclear History Museum on Alsos, Leslie Groves was not pleased about the Alsos missions being called such. So a stripped intelligence center and a line of intelligence or intelligence operation that operates alongside but outside traditional military intelligence channels, where have we seen that before? As well as the T-Force, which is almost equatable to modern day UFO rapid reaction teams. T-Forces were lightly armored [11808.4s → 11831.6s] ordered to secure sites for the Alsos personnel to kind of come in and exploit or to take whatever they needed about the Germans’ atomic progress and so on. I was fascinated that the T-Force was able to secure German atomic infrastructure in Soviet-controlled territory. So if that doesn’t say how specialized and well-trained these units were, I don’t know what will. [11833.3s → 11863.5s] The G-2 as well, even outside the IPU, as we saw with Yellow Fruit, with the Army Special Operations Division, SAWD, a couple decades later, there were personnel plucked from the Assistant Chief of Staff for Intelligence who did cover work for Yellow Fruit and Lieutenant Colonel Duncan, of course, working under the G-2. So I do find it fascinating that even outside of the subject of UFOs, we can see how the U.S. Army and key individuals within the Army used the G-2 for some [11863.5s → 11900.2s] extremely covert operations. Extremely covert. Again, even outside of the testimony of Representative J. Andrew Kistner, who again, I have spoken to, I do firmly believe that 1947, the National Security Act saw the foundational pieces laid out for the legacy program infrastructure, whether that be the Air Force, the National Security Council, or the Research and Development Board, which is now, of course, the Undersecretary of Defense for Research and Engineering, who alongside the USDI and USDANS, I believe are integral to the [11900.2s → 11927.1s] legacy program effort. USDANS, I don’t even need to say any more. Just go watch anything I’ve ever talked on the Wilson Davis Notes in the former name of the USDANS, Undersecretary of Defense for Acquisition and Sustainment, which was the Undersecretary of Defense for Acquisition and Technology, AUSTAT, or Undersecretary for Defense for Acquisition Technology and Logistics, ATL at the end. Just kind of go read about that. But of course, the Undersecretary of Defense for [11927.1s → 11942.8s] Research and Engineering was a direct lineage from Vannevar Bush’s RDB, especially the chairman position. And USDI, of course, that’s our old friend, Ronald Moultrie, who helped set up ARO, and of course, James Clapper, who may or may not have provided some cover for the ATIP programs [11942.8s → 11976.0s] and Luis Elizondo in his tenure from 2010 to 2017 as USDI. Anyways, I was talking about Truman. 1947 saw the 1947 National Security Act, but I do believe 1948 in particular is when several classified presidential executive orders, infamously referred to by Eric Davis as PEDS, Presidential Emergency Action Documents, established the National Security Council as the program manager or oversight body of the centralized Manhattan Project 2.0. And most, [11976.0s → 12008.1s] if not more importantly, I’m going to say, is that custody of recovered disks were to be analyzed by Vannevar Bush, and custody was to be given to Atomic Energy Commission National Laboratories, places at this time like Sandia. Well, Sandia would come next year in 1949 when Truman asked AT&T and Western Electric to take over Sandia base, Los Alamos, Oak Ridge, and yeah, does that ring a bell? I firmly believe that is the case. And of course, that corresponds so well with my [12008.1s → 12037.9s] UFO legacy program outline where FFRDCs and GOCO institutions, most prominently DOE and NNSA National Labs, hold much of the material and gatekeep knowledge to the lowest rung of the latter, which is defense industrial base prime contractors and their subcontractors. And that seemed to be the case until Northrop Grumman, Lockheed Martin, and a couple others. In 2005 and 2006, the early days of the war on terror decided to do their own thing with their own [12037.9s → 12069.6s] self-fund through misappropriation of IRAD funds. Anyways, that kind of reviews the political shield cover as well with the top policy group. And we talked about Truman setting up the National Security Council as the UFO crash retrieval and legacy program centralized body. And of course, Eisenhower continued that trend with the National Security Council 5412 Committee signed in 1954 and 1955. Literally under the 5412 Committee was the quote unquote special group. And following on to [12069.6s → 12081.2s] that was, of course, Nixon’s 303 Committee. So let’s start to talk about these Cold War transitions because that’s what I find so interesting. Of course, Eisenhower was so [12081.2s → 12113.1s] imperative not only to UFO legacy programs, but also the modern day classification system. With his Executive Order 10501, Eisenhower got rid of the restricted classification, not to be confused with restricted data in the DOE. Restricted was a fourth classification level outside of confidential, secret and top secret. And during this time epoch, program leaders were quite peeved about this removal of the restricted classification. So they started introducing [12113.1s → 12142.2s] ad hoc security protocols, specifically top secret code word rate on access. And that sort of thing continued for decades on. And that’s the wild, wild west days of the programs where the programs could exploit top secret code word rate on access controls like the NRO used with like the Byman classification system, for example. And so this was standard practice as well as U.S. classification and the legacy program infrastructure got an enormous bolster with the 1954 Atomic Energy [12142.2s → 12175.7s] Agreement. As we talked about in 1954 Atomic Energy Agreement, special nuclear materials, restricted data, formally restricted data is subject to statutory authority. So DOE classification essentially branched off from standard U.S. and executive order based classification, which isn’t subject to secret, top secret. I’m sorry, confidential, secret and top secret clearance. You have L and Q clearance in the DOE, which is equivalent to secret and top secret, respectively. But then you can also have Q clearance in the DOE with kind of more added [12175.7s → 12205.8s] on like restricted data, Q plus restricted data. And so that sort of classification system is statutory. It is empowered by the 1954 Atomic Energy Agreement and classified material born classified and not subject to automatic declassification review. It is extremely different from the executive order based classification system and is not subject to a simple presidential executive order. I’ve talked to many people about this and many people who are in positions of consequence are well aware of this. But an executive order by Trump to release [12205.8s → 12232.0s] the UFO files will not touch things covered by statutory authority. I’ve talked about this several times by now, but I think back to Dylan Borland saying whilst working at DITRA, nearby there were old Atomic Energy Commission files that concluded that some UFOs were of extraterrestrial origin. Files like this are what I’m talking about. I personally don’t know how to pry those loose so easily, but I’m sure that the executive branch, I’m sure Rubio, since he knows [12232.0s → 12255.3s] this, since Dave Grush handed everything off to Rubio, but Rubio was pretty shrewd. He was able to kind of use separation of individuals to gather information for plausible deniability or just to keep himself at arm’s length. Rubio will know about this stuff, so hopefully he can use that to his advantage if he’s trying to keep the cards close to his chest or he wants to be the one to spearhead a disclosure movement so he can run for office in the future term. Probably politicking [12255.3s → 12285.0s] with this disclosure movement currently, it’s annoying, but it is what it is and we just kind of have to suffer it. So Executive Order 10501, Nixon’s 1972 Executive Order 11652, which was subject to criticism shortly after that. We talked about that Congressional Research Service report that talked about people essentially being incredibly peeved and concerned that so many authorities really not connected with U.S. classification were able to slap on their [12285.0s → 12314.9s] own classification controls. Now we start to see the decline of the legacy program security structure with Jimmy Carter in 1977, who of course moved the U.S. classification towards more government transparency. This is probably why the legacy programs haven’t trusted as many Democratic politicians with UFO legacy program read-ons or partial read-ons. I firmly believe this because we could see that Clinton, Obama, and so forth, Biden, after the fact, were not [12314.9s → 12328.0s] read into the program. They were just temporary employees and so forth. So 1982, Reagan kind of, he strips away the ability to use these ad hoc security protocols as well as National Security [12328.0s → 12344.1s] Decision Memorandum 519, I believe it was, which came in 1985 shortly after Yellow Fruit. So 1982, Executive Order 12356 and NSDD 519 were sort of what really tightened the grasp [12344.1s → 12376.1s] on special access programs. More oversight, not government transparency, but more oversight. And of course, Yellow Fruit was a disaster. Yellow Fruit was part of the impetus for the Iran-Contra findings, and Yellow Fruit was out of the U.S. Army Special Operations Division in 1981. I firmly believe the investigations and audits into Lieutenant Colonel Duncan not only found other covert activities in Yellow Fruit, but also the Army sawed. And I think this was a major domino [12376.1s → 12380.5s] in the Wilson Davis Notes, the senior review group saying, hey, years ago our program was [12380.5s → 12385.6s] almost infiltrated in a series of audits, so we had to get cozy and hide ourselves. [12385.6s → 12392.8s] I do believe that sort of massive SAP scandal really, really, really nearly exposed the programs. [12393.3s → 12402.3s] Of course, I believe the senior review group also talked about one of the issues being money. Of course, in the Lieutenant Colonel Duncan audits that revealed Yellow Fruit, [12402.3s → 12428.0s] a lot of those were initially financial audits, so there’s some pieces to put together there. And of course, at that time, as we see with Edward C. Aldrich, legacy programs were forced to start using cover offices within the United States government with Edward Aldrich and the Air Force outside activities. Previously, programs have been hiding in SAP umbrellas, precursor to SAPs at this point, like Polaris and SandDollar. But literally, we see programs that [12428.0s → 12440.5s] were once funded from probably the U.S. Treasury and had an actual presidentially mandated funding mechanism start to hide and cover programs because there’s no Wild Wild West. These programs, [12440.5s → 12459.4s] these joint Air Force and NRO activities aren’t able to use their top secret code word. So these activities outside the Air Force that the Air Force has administrative and operational control over, we hide those in the Air Force under the SAP AA and bypass the AAZ, which is the component level SAP code for the Air Force. That in itself is just to cover office. It’s [12460.8s → 12471.3s] really intriguing. And then, of course, in 1994, again, we see the programs fully separate. It took a man with a Machiavellian political [12473.2s → 12502.0s] malleability and maneuvering like Dick Cheney to hold the programs together until he left office in 2009. And then the closest individual to be a mob boss, if you will, was Lieutenant General James Clapper. Who even holds the crumbs of what Clapper once held? I don’t know. But I would imagine it’s a small group. But yes, we talked about The Onion. We will talk so much more about The Onion in part two. We are going to talk about specifically what special access programs are, [12502.0s → 12531.7s] how they become unacknowledged and waived, what a bigot list is, more on SAP history, how you access SAPs, different SAP security checkpoints and so on. We’re going to talk about the concept of unrivaled secrecy, funding mechanisms, insider and outsider threat protection mechanisms and so forth, the legacy programs used today. And we’re going to talk about several modern-day program protection agencies. These are going to include the DARPA SID, Security and Intelligence Directorate, DOE-OACI, Office of Intelligence and Counterintelligence, [12532.4s → 12553.3s] AFL-CMC-IPD, the Air Force Lifecycle Management Center, Information Protection Directorate. I’m sorry. And then maybe we’ll talk a little bit more about AFOS-IPJ, but I’ve already talked about that plenty. Never forget the name Terry Phillips. Never forget his successor, Lee M. Russ. So with [12553.3s → 12581.2s] that out of the way, guys, I’ll start to wrap it up today. I want to thank everybody for being here. Please remember to like and subscribe. The channel’s almost to 120,000 subscribers. Never in my wildest dreams did I ever think that was possible. So from the bottom of my heart for everybody, thank you. I do have a Patreon and I do have YouTube memberships. I don’t gatekeep content. So only support what you think the channel is worth. Maybe sometime in the future, [12581.2s → 12615.1s] we can do just Q&A lives for the patrons and members. But as far as my overall content, I don’t gatekeep content. So just support what you think the channel is worth. On YouTube, if you become a member, you do get some emblems by your name. I can’t remember what I have, but I think I have the OSI PJ special agent emblem. So that’s pretty cool. Outside of that, yep, just support the channel by that. Liking and subscribing, watching the videos, or joining Patreon or YouTube members. It’s not mandatory, but it’s greatly encouraged, [12615.1s → 12645.3s] and I should say greatly appreciated. Outside of that, you guys know directly what I have coming next. So everybody will know what part two is. After that, I got a video in mind that it might be a fireside conversation type thing with myself and another individual that I’m trying to put together that I’m super excited for. I may do a couple lives with my good buddies, Rob Jones and Kermit. I do plan on seeing them next week. I’m actually going to be in D.C. and see both of those [12645.3s → 12665.2s] lads. So if that’s the case, we’ll try and do a live in person. Always love hanging out with those guys. They always got something crazy going on. And of course, Rob Jones is networking for News Nation. So that’s great. I hope we can talk to him and hear a little bit more about that. But like and subscribe. I can’t wait to see you guys on the next time. And let me know what you think [12665.2s → 12672.6s] down in the comments. I don’t even know what to say. We’re about three and a half hours in now. There’s so much we covered. So thank you all so much for being here. Bye.