Gerb

YouTube - UAP Gerb

[Gerb @UAPGERB]

Decided to make a full, downloadable acronym list inspired by the work of @UFO_Technology last week!

I understand I use a tremendous amount of acronyms in my projects, sometimes bordering on absurdity. I also understand that often people voice they can have trouble keeping up with all the acronyms!

When discussing DOD/IC projects, programs, terminology, contracts, etc, it is far more efficient to utilize acronyms over full term definitions.

So bear with me and hope this list helps for quick referencing of various terms, organized as best as possible. Plan to periodically update the list, but attached are images and a PDF of my most commonly used acronyms.

#ufoX #ufo #Uap #uapX

[Gerb @UAPGERB]

@chriscampb87833 @The_Astral_ If I’m asked, I will serve. But no, not me

[Gerb @UAPGERB]

@dynomypiano I’m supremely confident in every single point, argument, statement, assertion, etc I made in the video. Especially surrounding SAP manipulation, VERY confident.

[Gerb @UAPGERB]

SPECIAL ACCESS REQUIRED - the Secrecy of UFO Crash Retrieval Programs

https://t.co/aVgmDYqq8A

Part 2 of 2 into investigating the security architecture behind UFO crash retrieval and reverse engineering programs. This massive exploration seeks to uncover the who, what, when, where, and why behind the covert nature of the UFO Legacy Program portfolio.

Watch Part 1 here: https://t.co/HfyPZ3xGA5

Best visualized as an onion, the UFO portfolio secrecy apparatus is seemingly structured as an infinite series of "layers", where the center of the onion is the core truths, materials, senior leadership, biologics, etc of the behind the UFO effort and seemingly infinite layers of protectoin exist to keep even presidential administrations and "temporary employees" one layer away from the beating heart of UFO Legacy Programs.

Today's project seeks to explore the current-day structure and layers of this onion, a fragmented and scattered "Manhattan Project 2.0." Indeed, today, the UFO Legacy Program portfolio seemingly operates in an extremely compartmentalized structure, featuring a fractured control group and select few personnel who can peer across the "silos" into other programs housed under a bizarre quasi-government and industry control group.... But this wasn't always the case....

This project picks up where Part 1 left off, where in 1994 the Special Access Program (SAP) enterprise was restructured to safely gatekeep USG access and vest permanent control of the UFO portfolio within the above-mentioned quasi-industry and government group.

Here I seek to perform an exhaustive dive into the structure of Special Access Programs (SAPs), Controlled Access Programs (CAPs), and Covert Action Programs (also CAPs), and explore how and why such compartmented national programs are the PERFECT ecosystem for hiding UFO crash retrieval and exploitation activities.

This investigation will explore the types of SAPs, protection levels of SAPs, governance structure of SAPs, and the who, what, when, where, and why of how SAPs operate.... Ultimately, giving examples for how each SAP type (Acquisition, Intelligence, and Operations and Support) with waived unacknowledged status can house UFO activities.

Indeed, the project will also explore SPECIFIC loopholes UFO Legacy Programs have exploited within White House SAPs and Covert Action Programs out of the National Security Council to operate "Non-Covert Action Programs" - programs with managed need-to-know (MNTK) access and mighty SAP security protocols with completely waived reporting and budgetary requirements! As this investigation will argue, this is done by taking White House SAP Non-Covert Action Programs and applying the "Content-Only SAP" designation to exist in a quasi Title 10 and Title 50 state!

Though the SAP ecosystem is absolutely the most critical piece of the investigation, this documentary also explores deputized agencies and services that mitigate program exposure and insider/outsider threat protection with DARPA SID, DOE OICI, AFOSI/PJ, and AFLCMC/IP, addresses onion-sponsored narrative control and disinformation campaigns including the Robertson Panel, Condon Committee, AARO, and AAWSAP, and evaluates much of the body of the modern-day onion through the concept of "unrivaled secrecy."

Short list of the MANY things we will explore today:

- Continued investigation into UFO Legacy Programs being housed (partially modern day) within the National Security Council's subgroup on covert action (5412 Special Group, 303 Committee, etc)
- Define DoD Special Access Programs (SAPs), Intelligence Community Controlled Access Programs (CAPs), and National Security Council Covert Action Programs (Also CAPs)
- Explore how the National Security Council (NSC) has utilized White House SAPs with the "Content-Only" budgetary tier/administrative designation to create "Non-Covert Action Programs effectively" that waive ALL budgetary and reporting requirements
- Define the Content-Only SAP designation and describe how making a SAP contain CPI (Critical Program Information) is imperative to Legacy Program Secrecy
- Explain 10 USC § 119 and 50 USC § 3093 and argue why these UFO White House SAP Non-Covert Action Programs exist in a grey area between Title 10 and Title 50, not adherent to either's reporting structure
- Define and give examples for the three types and three protection levels of SAPs - Acquisition, Intelligence, Operations, and Support, and Acknowledged, Unacknowledged, and Waived, respectively
- Construct an illustrative example of how each type of SAP would be used on the Hidden Wing UFO exploitation program out of Air Force Acquisition
- Identify how all points above are massaged to completely waive congressional briefings and traditional oversight reporting for UFO-related SAPs
- Study SAP naming conventions and additional security controls such as NOFORN (Not Releasable to Foreign National)
- Identify how @ENERGY SAPs answer to their own statutory authority and get real spooky, real fast!
- Explore the SAP governance hierarchy, including: Component SAPCO (SAP Special Office), USD SAPCO, DoD SAPCO, SAPOC (SAP Central Office), and SRG (Senior Review Group)
- Argue why DoD SAPCO, SAPOC, and SRG are premier gatekeeping institutions for USG access into the programs
- Identify relevant USD (Undersecretary of Defense) departments connected to specific SAP types and capable of UFO activities (USD(I&S), USD(A&S), USD(R&E))
- Discuss several funding schemes the Legay structure harnesses for program funding: haircuts across black projects and unexpected offices/services, self-fund through cutout activities, hiding budget in generic DoD budgets with Content-Only SAPs, criminal enterprises, IR&D, etc
- Name several agencies/services within USG SAP architecture that serve as program protection and exposure mitigation for the Legacy apparatus, including: AFOSI/PJ (Office of Special Projects), DOE OICI (Office of Intelligence and Counterintelligence), AFLCMC/IP (Air Force Life Cycle Management Center Information Protection Directorate), and DARPA SID (Security & Intelligence Directorate)
- While on the subject of DARPA, identify Dr. Peter Highman (Principal Deputy Assistant Secretary of War for Critical Technologies, Office of the Under Secretary of Defense for Research and Engineering) as a senior Legacy Program scientist at the upper echelons of the SAP ecosystem
- Discuss narrative campaigns/disinformation operations from the Legacy onion, including 1953 Robertson Panel, 1969 Condon Committee, and 2022 AARO
- Explore NSC, James Clapper-sponsored partial transparency campaigns through the AATIP (allegedly)
- Identify the frontman for these operations, Lue Elizondo (allegedly)
- Inquire into how the Clapper/Elizondo partial transparency campaign evolved through AATIP, TTSA, the 2017 NYT article, the 2024 hearings, and Age of Disclosure (allegedly)
- Isolate on Lue Elziondo's former position as Director, National Programs Special Management Staff (NPMS) under USD(I&S), and once again ask if Elizondo has prior experience WITHIN the Legacy Programs and possibly exposed Tom Delonge to elements of the NSC Immaculate Constellation Activity (allegedly)
- Criticize the evolved narrative-campaign, amnesty please, and incomplete legacy outline presented in the Age of Disclosure Documentary, and ask why the National Security Council is missing from the Legacy Program silo falsely presented as the monolithic Legacy Program
- So much more, I am just scratching the surface!!

Thank you @imxanderjones for the great music and thank you @UAPNinja for making me a 3D printed Flux Liner!

[Gerb @UAPGERB]

Thank you for your response! I am encouraged and believe this sort of thoughtful answer is excellent for discourse on the topic.

I do have a response to you crafted, though I would like to ask you to discuss your point of view and politely debate this topic in a video-recorded, in-person format on my platform.

I host few interviews; however, it appears we will both be in the Capital at the end of the month, and I think the public would have a voracious appetite to see an accomplished USG official like yourself and me respectfully debate these points and explore the Legacy Program vs. sensor data discussion topic!

If you are open to this, please connect with me here on Twitter DMs where we can exchange emails/Signal contact. I would be happy to set up a time, date, and location.

[Christopher K. Mellon @ChrisKMellon]

Congress has repeatedly asked about crash debris etc. and the answer is always the same, “We don’t know what you are talking about.” Repeatedly asking the same question and getting the same answer is not helpful. We need a strategy to build a wider, broader base of support to press further and eventually get to the bottom of this. My premise is that to get to the holy grail of recovered ET materials, if indeed we have any, first requires a greater public consensus and demand for the truth and support from key committees. One of the best ways to get there is to show UAP entering and leaving the atmosphere; or exceeding all known science and aeronautic
principles regarding acceleration etc. We’ve established there are strange and mysterious objects out there but we are a long way from demonstrating to the satisfaction of most people that UAP are so advanced they are definitely of non-human origin. If we can get this other data out, our prospects for successfully obtaining the release of recovered materials will be far, far greater and the public will be better prepared to accept this. This is a step by step process unless Congress is able to leapfrog to the alleged recovered materials which isn’t looking likely at the moment. So if we can get there directly that would be great, but we still have a lot of convincing to do and the data I propose seeking offers a logical and reliable step towards the common objective of getting to the truth with genuine highly compelling data that exists but has not yet been released. Meanwhile we continue to look for and support whistleblowers.

[Gerb @UAPGERB]

@DanielOsma95053 Lickin his chops

[Gerb @UAPGERB]

https://t.co/NtJCKiWxfK

[Gerb @UAPGERB]

@DanielOsma95053 I need this framed

[Gerb @UAPGERB]

@DanielOsma95053 @robjonesreports Please never terminate your account I love you

[Gerb @UAPGERB]

Excellent! This is a very important piece of the puzzle that was curiously quickly dropped. I covered this pretty extensively in my USAF video and theorized why I'm almost certain the SES-2 gatekeeper is either SAF/AAH now SAF/OC Russell E. Wyler (thanks for the amazing hypothesis by @OntologyShock ) or SAF/AAZ William E. Maclure

[Gerb @UAPGERB]

Mr. Mellon,

While many, including myself, appreciate your tenacity here, this is a perplexing tweet...

You are calling for the release of UAP space data, satellite data, and detection from the Ballistic Missile Early Warning System; however, you yourself have commented on several occasions on the existence of both the legacy programs and recovered materials/biological samples.

The number one example that comes to mind is this redacted Signal messaging screenshot you released in 2024 in response to Sean Kirkpatrick voluntarily offering Signal exchanges between you and him for a FOIA release.

This redacted exchange with an unknown individual not only confirms you know the management structure, security control systems, and ownership of the crash retrieval portfolio, but that you are also aware of a highly classified memo by SecAF in the 1950s that is still in effect to maintain cover for the legacy programs.

Indeed, you also in this exchange confirm you are aware of the Air Force legacy SES-2 gatekeeper (likely Russel E. Wyler) and state the 1953 Kingman, Arizona UFO crash was indeed real and recovered.

So why exactly is this memo by a former SecAF or the release of the Kingman wreckage and biologics not a priority for you? These have lower precedence than your listed IMINT/SIGINT data?....

You have said similar things on several occasions regarding UFO retrieval and exploitation, including a 2023 NewsNation appearance with Chris Cuomo where you stated: "I’ve been told that we have recovered technology that did not originate on this Earth, by officials in the Department of Defense and by former intelligence officials."

https://t.co/Bnin6fajhK

This feels like a bizarre pivot back to your and Mr. Elizondo's ~ 2017-2023 narrative of discussing an amorphous non-human presence on this planet without breaking into the fine details of recovered technical vehicles or biologics.

At the same time, I find it bizarre that your list is excluding maritime UFO sensor data encounters. We know, all the way back to the days of Project Blue Book, USO/maritime UFO encounters are often strikingly anomalous and occur almost more frequently than any space-based UFO monitoring and tracking.

Others and I share the concern that within the Age of Disclosure documentary, Jay Stratton, who retired as a Defense Intelligence Senior Executive (DISES) from the Office of Naval Intelligence (ONI), purposefully excluded Navy elements from the film's "Legacy Program" outline to protect his Naval interest or prior exposure to Naval Legacy Elements. Mr. Mellon, are you doing the same? Admiral Gallaudet has advocated for the study of UFO/USO in maritime environments tirelessly. Why do you not also advocate for release of such data?

An additional worthy pursuit, as I have publicly requested, is for you to comment on your former SSCI coworker, Mary K. Sturtevant. As I have stated, I am aware that whilst Sturtevant was Lockheed Martin VP of Government Affairs and VP for Intelligence, Joint and Science & Technology Progams, she aided in the blocking of the Kona Blue PSAP UFO materials transfer between Lockheed Martin and the AAWSAP. My public request to you can be found here:

https://t.co/gAD3Lv6R6V

Why is UFO retrieval, exploitation, and reverse engineering, for which you have advocated transparency in the past, taking a backseat to a handful of specific sensor data?

[Christopher K. Mellon @ChrisKMellon]

The other day I was asked by an Administration official what my priorities would be for release of UAP information. I replied as follows:

1) UAP Space Data

UAP detected in space, either in orbit or entering and departing the Earth’s atmosphere. I believe we have such data yet nothing of this kind has been released. We have numerous systems performing space surveillance, including the world’s most powerful radars. The power, sophistication and range of those systems leads me to believe they must inevitably collect and track UAP.

2) Satellite Data

This is another category of UAP data that has not been released to date. I’ve seen some of this imagery and what I’ve seen was impressive. Although typically highly classified, under present circumstances, with pressure from the White House, it may well be possible to release some or all of this overhead UAP data.

3) UAP Data from the Ballistic Missile Early Warning System

The old Ballistic Missile Early Warning System has been continuously updated since the end of the Cold War to its current condition. These are believed to be the most powerful emitters on the planet. Further, numerous UAP encounters have clearly occurred within their areas of coverage. For example, during the Nimitz incident numerous UAP were descending from roughly 80,000 ft to 20,000 feet, in mere seconds, for several days, directly in front of the powerful strategic radar at Beale Air Force Base. Yet, none of this data has been released. Data from each of these systems could appreciably add to our knowledge of the UAP phenomenon.

I’m hoping they have the latitude and determination needed to come clean with this information.

[Gerb @UAPGERB]

@ebravo_x I believe several factions have attempted since the early to mid-2010s to pursue their own disclosure narratives.

[Gerb @UAPGERB]

@wlcm2intimes A witch hunt would imply unfair criticism with baseless evidence. I strongly believe a SecAF memo protecting the crash retrieval portfolio and evidence/chain of custody of the Kingman retrieval is significantly more consequential than the outlined sensor data.

[Gerb @UAPGERB]

@tricky_2001 Lol without spoiling yes! Almost positive the “civilian” reference in that specific scene was Walker

[Gerb @UAPGERB]

@pavelibarrameda Between this, Disclosure Day, Obsession, and Backrooms we have been spoiled for choice in the theater! I’ll probably see this on the weekend, huge fan of modern action martial arts films. If you haven’t seen the Raid Redemption and the Raid 2 I recommend watching those asap

[Gerb @UAPGERB]

True American leadership

[Gerb @UAPGERB]

@robjonesreports Lookin sharp

[Gerb @UAPGERB]

@ManzoBanana @calin2k 6ft so not too tall but I weigh in at 210-215lb with a pretty big frame

[Gerb @UAPGERB]

Great perspective Ross and I would love to weigh in here as well. Although I see no connections to the topic of UFO Legacy Programs in this case, I think this article by WaPo is an INVALUABLE example of how DoD/IC elements can use Special Access Programs (SAPs) or Controlled Access Programs (CAPs) to hide from oversight.

The article states that Agency Officer Rush essentially built out his own Continuity of Government (COG) SAP to steal $40m in gold bars, $2m in cash, and dozens of luxury watches. This endeavour involved Rush swindling a defense contractor through a fraudulent government contract.

According to the article, Rush fabricated much of his past prior to CIA, including Navy service and college degrees, and somehow fooled CIA security to get hired... miraculously not getting flagged in a series of lengthy and rigorous background checks, blood tests, psychological evaluations, polygraphs, military records search, etc.

I see several issues here and think it far more likely this COG SAP was a coordinated CIA DS&T and Directorate of Operations (DO) activity built to hide from oversight, and Officer Rush is the scapegoat here.

First off, although there is a non-zero possibility, there is nearly a zero percent chance that Rush was able to hoodwink CIA security and "slip through the cracks". What is more likely here, in my opinion, Rush's CV is data masked to match his living alias, aka he had a much longer history with the Agency and operated with standard CIA practice of Non-Official Cover or a NOC.

Second, I find it extremely unbelievable that an officer was able to carve out his own basically waived COG (Continuity of Government) SAPs. Establishment, governance, and the lifecycle of a SAP generally involve numerous oversight mechanisms to ensure the need for a SAP, confirm that there is no SAP duplication across departments/services, etc.

COG SAPs, on the other hand, have a very similar structure to UFO Legacy Program SAPs due to a few massaging techniques that waive all congressional and budgetary reporting requirements. These are NOT easy to make and basically have to be spun up at a white house/NSC level due to some interesting molding of Title 10 and Title 50 to get the SAP to exist in a grey area.

So again, I contest that this activity was likely a CIA DS&T/DO COG SAP built for covert operations outside of traditional oversight.... Perhaps in this case, due to the presence of gold bars, overseas trafficking or influence operations.

Indeed, this situation parallels the revelations of 1983's Yellow Fruit USAP (Unacknowledged Special Access Program) out of the Army's Special Operations Division or SOD which directly led to numerous government oversight reforms on National Programs.

Yellow Fruit operated to provide operational security and counterintelligence for CIA Central American missions (Nicaraguan Contras) and "other Army Classified Operations".

When Yellow Fruit was revealed through a series of normal audits, Lt. Col. Duncan was the fall guy. Army Chiefs of Staff were apparently never read into this activity and were shocked they had no idea what was going on in their own Army!

Col. Duncan served on the staff for the Army Chief of Staff for Intelligence (ASCI). For the security of Yellow Fruit, Duncan performed a staged retirement so the activity could operate outside the Pentagon and within a "black" commercial cover company. In this instance, Duncan would serve the Army SOD's Yellow Fruit USAP through his corporate cover cut-out company, "Business Security International" aka BSI.

Both Army SOD and Yellow Fruit were disbanded with the revelations of Yellow Fruit, and Col. Duncan was one of the few men punished, receiving a full court-martial and a 10-year sentence at Leavenworth!

To state again, I do not think this Agency scandal detailed in WaPo has anything to do with UFO programs; however, I do think it is an incredibly valuable case study.

The events outlined in this article and the Yellow Fruit saga closely parallel and give a firm conceptual understanding of what I speak on oh so often - UFO Legacy Program Secrecy with COG SAP constructs (coming soon), avoidance of traditional oversight channels, NOCs and Datamasked program members, corporate cut-outs, misappropriation and illegal handling of funds, and so much more!

This article is fantastic and I highly recommend giving it a read.

[Ross Coulthart @rosscoulthart]

Ironic to read the @washingtonpost today reporting that charged @CIA officer David Rush Rush allegedly misused a SAP - Special Access Program - to defraud US taxpayers, hiding the millions of dollars he allegedly stole behind a fraudulent Government contract. This is exactly what David Grusch alleges has been happening with legacy UAP programs concealed from Congress.

Rush is said to have “read in,” or initiated, two colleagues into the highly secretive sham program, effectively cultivating them as perhaps unwitting accomplices and preventing them from talking to others about it. He persuaded one of them to transfer millions of dollars to the program via a government contract that was also fraudulent.

It's the perfect scam because even intelligence personnel with the highest security clearance cannot access an individual SAP without specific authorization.

Rush worked in the CIA's Directorate of Science & Technology, the same office where the Office of Global Access (OGA) has allegedly been playing a key role in the retrieval of NHI tech. His alleged fraud shows just how OGA may well have diverted public funds illegally from other contracts to fund covert operations without public accountability to Congress.

https://t.co/CuWLjIkmXY

[Gerb @UAPGERB]

@calin2k 0