The protocols in the Yandeh Holdings portfolio were not designed at a whiteboard. They were designed by someone who spent fifteen years inside the environments these protocols are meant to govern.
In fifteen years of working inside enterprise infrastructure and security environments — designing identity architectures, implementing secure communications systems, building out network and firewall governance, and responding to security incidents in high-stakes operational contexts — Papa Gora Samb kept encountering the same gap. Autonomous systems were making consequential decisions. Those decisions had no formal authority structure beneath them. There was no signed artifact encoding what the system was permitted to do. There was no state machine enforcing the lifecycle of that permission. There was no portable, independently verifiable record that the decision had been made under the conditions it claimed. The infrastructure layer that should have existed simply did not.
That observation is the origin of the Yandeh Holdings patent portfolio. AMIAP — the Autonomous Machine Identity and Authority Protocol — emerged directly from years of designing and operating identity and access management systems. Conventional IAM evaluates authorization at credential issuance time. By the time an autonomous machine acts on a credential, the conditions that justified the grant may have changed. AMIAP closes that window by requiring a signed authority artifact evaluated against the runtime context at the exact moment of execution. It is the protocol that should have been sitting beneath every machine-to-machine authorization system that Papa built or operated — and was not.
VEMP — the Verifiable Enterprise Messaging Protocol — came from years in secure email architecture and enterprise communications governance. The dominant secure messaging standards protect content in transit. None of them define a formal admission control evaluation between message delivery and content access. VEMP introduces that missing layer: a dual-plane architecture that evaluates a message authority artifact against the ciphertext before any decryption key is released, without exposing plaintext to the evaluation process.
AIRAP — the Autonomous Incident Response Authority Protocol — came from working in environments where automated incident response platforms executed remediation actions with no formal authority structure governing them. SOAR platforms execute playbooks. They do not define an incident-scoped authority artifact, a deterministic state machine with enforceable preconditions, or a cryptographically verifiable receipt chain that proves what actions were taken under what authority. AIRAP defines all three.
CVEAR — the Cryptographically Verifiable Execution Authorization Receipt Protocol — is the horizontal infrastructure beneath all of it. It defines what a receipt actually is: a structure that any authorized party can verify, in any domain, without asking the enforcement point anything. It is the evidence layer that makes every other protocol in the stack auditable, portable, and independently confirmable.
Papa holds an active TS/SCI security clearance — a reflection of a career grounded in operational trust, accountability, and environments where the absence of formal authority governance is not a theoretical concern. He is a CompTIA Secure Infrastructure Expert (CSIE), having earned Security+, CySA+, PenTest+, and SecurityX certifications — covering the full spectrum of defensive operations, offensive security, threat analysis, and security architecture. He studied Network Administration and Security at ASA College and Technology Leadership at Pace University.
The Yandeh Holdings portfolio was filed pro se at the USPTO — meaning Papa designed, drafted, and prosecuted each application himself, with Track One prioritized examination on all four parent applications. Each application was developed through full prosecution preparation: antecedent basis audit, §112 written description verification, prosecution history firewall, claim scope analysis, and continuation strategy. The decision to file pro se was intentional. It means the inventor controls the prosecution record, controls the claim scope, and carries full knowledge of every argument made before the USPTO — a position that simplifies licensing conversations and strengthens the portfolio's defensibility.