Pharns Genece — Builder of the AI Governance Standard¶

The Builder¶

I'm building the measurement standard for governed autonomous action — for AI agents and physical autonomous systems, under one filed architecture.

Not dashboards. Not generic compliance decks. The architecture itself: a governance layer that classifies risk at dispatch, bounds authority before execution, and produces audit evidence outside the autonomous system. Filed at the USPTO. Listed in the NIST OLIR catalog. Running today, governing my own multi-agent system.

The architecture comes first. Advisory engagements implement the standard for organizations who choose to adopt it. The work is the standard. The consulting is how it lands.

The doctrine is published in the permanent scholarly record: deposited, timestamped, and citable by anyone, with no ability for me to quietly revise it after the fact. ORCID 0009-0009-0791-4124; the deposits and their DOIs are listed on the evidence page.

Why AAM Cyber¶

AAM Cyber is named for Advanced Air Mobility.

I built my first drone as a hobbyist, before DJI existed, and ended up on large-format automated commercial drones with custom and specialized cargo systems. I founded Unmanned Systems Operations Group (USOG, Inc.) while the industry was still arguing about what a drone was allowed to do. Where it was heading was already visible: the aircraft would keep getting larger, and eventually the category would carry people. The FAA would come to call that Advanced Air Mobility.

Governance stopped being abstract at that point. A drone that fails is an expense. An aircraft carrying passengers that fails is something else, and the question becomes who authorized it to act and what bounded it before it did. First the concern was RF: someone taking control of an aircraft they didn't own. Then the harder one: an autonomous system deciding something nobody approved, with people onboard.

That is what the company was named for, and still hopes to solve. The AI agents came later; the control problem didn't change. The answer turned out to be larger than aviation. Governing a machine that can cause great harm is the same problem whether it flies, senses, or reasons.

Why I Built This Work¶

My perspective comes from working across the autonomy continuum: automation → autonomy → AI. It started with a drone I built myself, as a hobbyist, and the FAA Part 107 certificate that followed. Then the initial cohort of MiraCosta College's ROV/Drone Operator Technician Program: remotely operated underwater vehicles and unmanned aircraft, machine design and FAA regulation. I returned to teach in that program in 2019. From there: physical autonomous systems, RF and spectrum sensing, then cybersecurity and digital AI agents. I governed machines that could cause great harm before I governed software, and the control problem turned out to be the same one.

I arrived at autonomous-systems governance from the operating side of complex systems, not from commentary.

Across my career, the pattern has been consistent: systems fail when authority is unclear, escalation is weak, and evidence does not survive contact with reality. Autonomous systems — AI agents and physical autonomous systems alike — create the same problem at a new scale and across a new domain.

The trade press covers AI agent incidents in one column, drone near-misses in another, critical infrastructure vulnerabilities in a third. Nobody is writing about the connecting thread.

The connecting thread is this: an autonomous system acts without a human at the controls in that moment. The system that should have governed the action either does not exist or does not bind. That is the gap. That is what runtime governance is for.

So I built it. Both substrates. One standard. The receipts are in the filings.

Background¶

• Career Air Force veteran
• Former CEO of a drone logistics company
• Walt Disney Company Audio Engineer — technical precision at world-class standards
• FAA Part 107 licensed drone pilot
• First-generation Haitian-American
• Active professional certifications across security, networking, and operations — independently verifiable on Credly
• WGU B.S. Cybersecurity and Information Assurance
• M.S. Cybersecurity and Information Assurance — begins November 2026

Why Buyers Engage Me¶

I coined the term I believe the field will eventually use for this work: governed autonomous execution.

I did not stop at naming it. I built the architecture, backed it with patents, submitted it to NIST through the OLIR program, ran it continuously on my own multi-agent system, and measured outcomes that matter to both security leadership and the business.

That combination is the reason buyers engage me:

• I built the standard, not just commentary about it
• The architecture is filed, federally referenced, and operational
• Dual-domain coverage — digital agents and physical autonomous systems under one filed architecture
• NIST OLIR Trifecta — three Concept Crosswalks cataloged: AI RMF 1.0 (Ref ID 220), CSF 2.0 (Ref ID 215), SP 800-53 Rev 5.2.0 (Ref ID 217) — all Final Informative References
• NIST OLIR, Five Laws of AI Governance: three crosswalks (AI RMF 1.0, CSF 2.0, SP 800-53 Rev 5.2.0) catalogued as Draft Informative References on 2026-10-06, in 30-day public review
• Five U.S. provisional patents, 45 families, 334 total claims
• Measurable proof instead of vague assurance

Advisory engagements implement the standard. They are downstream of the work, not the primary offer.

Expertise¶

Pharns Genece is the inventor of a patent-filed governance architecture for autonomous systems — covering both digital agents and physical autonomous systems under one filed measurement standard. He built the architecture across five U.S. provisional patent applications covering 45 patent families and 334 total claims. Three NIST OLIR Concept Crosswalks are cataloged — AI RMF 1.0 (Ref ID 220), CSF 2.0 (Ref ID 215), and SP 800-53 Rev 5.2.0 (Ref ID 217), all Final Informative References. He coined the category term governed autonomous execution. He advises enterprise CISOs, Chief AI Governance Officers (CAIGOs), federal program managers, Critical Infrastructure Directors, and prime contractors implementing the AQ Score™ governance architecture across both software agents and physical autonomous systems including drones, RF, and critical infrastructure. Full patent record and public disclosure: aamcyber.com/inventor/.

At A Glance¶

Fit¶

If you need a large implementation team, I am not that.

If you need the architect of the standard itself — to define the governance architecture for your autonomous systems, identify the real control gaps, and help your organization move from autonomous-systems experimentation to governed operations — that is where I fit. The architecture is filed and operational. The advisory work installs it.

See The Receipts Read the Architecture