Source note2 min read
CAVA: Canonical Action Verification and Attestation for Runtime Governance of Agentic AI Systems
Source
arXiv
arxiv.org/abs/2607.13716v1
Source
- Source name: arXiv
- Source kind: paper
- Authors / organization: Zexun Wang
- Venue: arXiv: cs.AI
- Published: 2026-07-15
- Collected: 2026-07-16
- URL: http://arxiv.org/abs/2607.13716v1
- PDF: https://arxiv.org/pdf/2607.13716v1
- DOI: UNKNOWN
Plain-Language Brief
The paper presents Canonical Action Verification and Attestation (CAVA), a system that converts various runtime actions of agentic AI systems into standardized action objects, aiming to address the challenge of governing heterogeneous runtime activities. CAVA is designed to work below Proof-Carrying Agent Actions (PCAA). The paper discusses the formalization of canonical action identity, semantic pattern detection, approval binding, receipt integrity, runtime-portable projection, and optional attestation substrates.
What the Document Says
- The text presents a system called Canonical Action Verification and Attestation (CAVA).
- CAVA is designed for the governance of agentic AI systems with heterogeneous runtimes.
- Agentic AI actions, such as publishing code or moving money, may be represented by incompatible runtime records.
- CAVA aims to answer questions about approved actions and their execution.
- CAVA converts these heterogeneous actions into standardized action objects.
- Proof-Carrying Agent Actions (PCAA) defines a governance process, while CAVA focuses on the stable action object that process governs.
- The paper discusses formalization of canonical action identity, semantic pattern detection, approval binding, receipt integrity, runtime-portable projection, and optional attestation substrates.
Key Concepts Mentioned
- Agentic AI systems
- Heterogeneous runtimes
- Canonical Action Verification and Attestation (CAVA)
- Proof-Carrying Agent Actions (PCAA)
- Canonical action identity
- Semantic pattern detection
- Approval binding
- Receipt integrity
- Runtime-portable projection
- Attestation substrates
Claims Made by the Document
- CAVA converts heterogeneous agent activities into canonical runtime action objects.
- CAVA is positioned below PCAA.
Evidence Used
- The text states that CAVA aims to convert heterogeneous actions into standardized objects and is designed to work below PCAA.
Methods / Approach
UNKNOWN
Limitations Stated by the Authors
UNKNOWN
Limitations Noted by the Agent
Agent interpretation — not from the source.
UNKNOWN
Open Questions
UNKNOWN
Notes for Future Q&A
May include interpretation. Labeled where it does.
UNKNOWN
Raw Abstract / Excerpt
Agentic AI systems increasingly act through heterogeneous runtimes: local coding hooks, SDK tools, browser automation, managed-agent traces, API gateways, and workflow engines. A single operational act such as publishing code, changing identity state, moving money, or exporting data may therefore be represented by many incompatible runtime records. This makes a basic governance question difficult to answer: what action was actually approved, what evidence binds the approval to execution, and can an independent verifier reproduce the same action identity later? This paper presents Canonical Action Verification and Attestation (CAVA), a runtime-semantics layer for converting heterogeneous agent activity into canonical runtime action objects. CAVA is positioned below Proof-Carrying Agent Actions (PCAA): PCAA defines the deployer-owned route-review-prove governance process, while CAVA defines the stable action object that process governs. The paper formalizes canonical action identity, semantic pattern detection, approval binding, receipt integrity, runtime-portable projection, and optional attestation substrates. We study a reference implementation through a 96-seed, 384-variant benchmark covering semantic equivalence, semantic separation, wrapper bypass, false-positive control, approval binding, receipt reproducibility, attestation tamper detection, runtime portability, semantic pattern detection, policy degradation, and Azure deployment drills. The contribution is a systems formulation of action-level canonicalization and policy-addressable semantic patterns as a necessary substrate for deployer-side AI governance.
