Exogram Action Admissibility Protocol (EAAP)
An open standard and architectural RFC designed to govern the tool execution boundaries of autonomous AI agents. EAAP defines a strict set of binary admissibility gates that filter and validate proposed agent actions against deterministic allowlists prior to execution. By decoupling the probabilistic reasoning of the LLM from the deterministic execution of the environment, EAAP ensures that agents cannot perform destructive, unauthorized, or financially ruinous actions, even if they hallucinate the intent to do so. This is the foundational protocol powering Exogram’s runtime governance.
“Govern the execution, not the imagination. Let the model dream, but strictly regulate what its hands can touch.”
As agents move into Zone 3 and Zone 4 of the AI Liability Gradient, relying on system prompts to enforce safety is structurally insufficient; LLMs can always be jailbroken or confused. EAAP provides a hard, cryptographic boundary at the execution layer. It guarantees that regardless of what the LLM decides to do, the system will only execute mathematically verified, pre-approved actions. This is the only way to safely deploy autonomous agents in high-stakes enterprise environments without exposing the company to infinite liability.
Richard Ewing’s Research Thesis
Enterprise agent deployment is negligent without a deterministic admissibility protocol intercepting all tool calls.
Why This Specification Exists
System prompts are continually bypassed, leading to dangerous autonomous agent behavior.
Telling the AI "do not do this" in the prompt.
No deterministic execution boundary between the LLM and the real-world environment.
A formal protocol (EAAP) that validates all agent actions against hard rules before execution.
What Changes If You Believe This?
Must build explicit deterministic boundaries around every tool exposed to an agent.
Lowers risk profile of enterprise AI deployments.
Must specify the exact tool parameters needed for a feature to function safely.
Security teams stop auditing prompts and start auditing execution allowlists.
Recommended Action by Role
Implement EAAP middleware before allowing any LLM to execute database mutations.
Latest Publications & Research Activity
Salesforce and SAP are putting AI agents inside your workflows. Who tells them no?
How to Prevent Memory Loss in AI Applications
Giving an AI a bigger memory window is like giving a confused worker a bigger inbox.
Frequently Asked Questions
Q:Why not just tell the agent not to do bad things?
LLMs are probabilistic. They do not understand hard boundaries. EAAP acts as a physical wall that the agent cannot pass, regardless of its instructions.
Q:Does EAAP limit agent capability?
It restricts freedom to ensure safety. The agent can only select tools that have been explicitly provisioned and cleared by the EAAP gateway.
Inspectable Evidence Ledger
Classified evidence items supporting, extending, or refining this canonical research specification.
Recommended Citation
Ewing, R. (2026). "Exogram Action Admissibility Protocol (EAAP)." Richard Ewing Research Canon. Available at: https://www.richardewing.io/concepts/eaap-protocol
@article{ewing_eaap_protocol,
author = {Ewing, Richard},
title = {Exogram Action Admissibility Protocol (EAAP)},
journal = {Richard Ewing Research Canon},
year = {2026},
url = {https://www.richardewing.io/concepts/eaap-protocol}
}