Agentomy Agent Governance Protocol
AGP defines what enterprise AI agent governance requires. Three tiers. Each tier maps directly to a specific EU AI Act article obligation. Any execution layer -- any AI agent framework, any on-device model, any cloud agent -- can implement this specification.
Three Tiers
The Operator Obligation
Enterprise AI vendors satisfy their own processor obligations through their product's governance features. The EU AI Act places separate obligations on the operator -- the organization deploying AI agents. AGP defines what the operator's governance infrastructure must include, independent of which vendor's AI agents are deployed.
Implementation
AGP is vendor-neutral. Any execution layer can implement the three tiers. The specification defines the minimum. What follows demonstrates what a complete implementation looks like.
For integration guidance, use the Request Access form.
Reference Implementation: Agentomy
AGP defines the minimum. Agentomy demonstrates what a complete implementation looks like. The three tiers remain the specification floor. Everything below exceeds it.
2. Trust -- validates trustworthiness across four modules (trust authority, chain validator, trust scorer, security policy).
3. Authorization -- tier-based permission check with inter-agent delegation support.
4. Behavioral Check -- baseline deviation detection and execution risk assessment.
5. Content Input Scan -- inbound payload threat scanning (injection, integrity, content filtering).
6. Action Execution -- controlled execution with evidence recording.
7. Output Scan -- IP leak scrubbing, compliance claim verification, content scanning.
8. Evidence Recording -- persistence to audit trail, trust ledger, and chain-of-custody ledger.
9. Drift Update -- behavioral baseline recalculation with threshold-based flagging.
10. Halt Evaluation -- final aggregation of all stage findings; triggers halt if any stage returned critical.
Each stage produces a SHA-256 hash-linked finding. The first stage hashes against 64 zeros. Each subsequent stage chains to the previous hash, forming a tamper-evident forensic evidence chain. The final evidence chain hash is returned in every authorization response and is independently verifiable.
Auditability -- every event recorded, hash-linked, exportable, tamper-evident.
Override Capability -- authorized operator halts all agents immediately; unauthorized halt blocked.
Behavioral Integrity -- anomalous behavior detected, flagged, and quarantined automatically.
OWASP Agentic Coverage -- adversarial threat detection across injection, supply chain, model integrity, and protocol-level attacks.
Agentomy result: 100/100. 224 scenarios across 5 dimensions. Zero failures. Any governance platform can run GovernanceBench against itself:
npx governancebench run --target http://your-platform:30005 RPA-specific -- tier escalation, external destination, config drift, lateral movement, unattended spawning.
5 algorithmic trading -- order velocity, position concentration, strategy drift, spoofing pattern, cross-venue exposure.
5 medical device -- dosage anomaly, calibration drift, protocol deviation, alert fatigue, device isolation breach.
5 AV fleet -- route deviation, sensor disagreement, communication dropout, geofence violation, fleet coordination failure.
5 industrial IoT -- setpoint drift, actuator conflict, network segmentation breach, safety interlock bypass, process variable excursion.
The 9 core methods operate standalone. The 25 vertical-specific methods require fleet infrastructure for cross-agent behavioral baselines. Auto-quarantine triggers on critical severity. Quarantined agents cannot execute further actions without explicit operator release.
Standalone deployments support halt for up to 10 locally governed agents. With fleet infrastructure: sub-50ms coordinated halt across 500+ concurrent agents. One operator decision stops every governed agent across every deployment surface. Post-halt agent registration is rejected -- no new agents can join while halt is active. Fleet-level coordination requires Agentomy fleet infrastructure.
Analyst -- standard task execution within defined scope. No irreversible actions without confirmation.
Builder -- elevated operations requiring explicit authorization before execution.
Operator -- administrative operations affecting system configuration. Requires senior approval.
Strategist -- system-level actions including kill switch execution and governance policy override. Cannot be delegated.
Every tier assignment is logged. Tier escalation via request body is structurally impossible -- enforced at the authorization stage of the 10-stage pipeline, not at the application layer.
Article 12 (Record-Keeping) -- Stage 8 (Evidence Recording): tamper-evident logging with hash-chain integrity, retained for operational lifetime plus applicable limitation period.
Article 14 (Human Oversight) -- Stage 10 (Halt Evaluation) + fleet halt: one authorized human halts all autonomous action immediately with signed proof record.
Article 15 (Accuracy and Robustness) -- Stages 5 (Content Input), 7 (Output Scan), 9 (Drift Update): continuous validation of input integrity, output correctness, and behavioral stability.
The three-tier AGP specification maps Articles 9, 12, and 14 as the minimum. The reference implementation additionally satisfies Article 15 obligations through input/output scanning and drift monitoring.
Agentomy is in active development. This specification reflects the current implementation, not an independently assessed standard.