arXivDaily arXiv每日学术速递 周一至周五更新
arXiv周末暂无论文更新,休息一下吧,周末愉快~~
arXiv 2607.05397cs.CRcs.AI
收藏

执行证明:受治理人工智能代理行动的运行时验证

Proof of Execution: Runtime Verification for Governed AI Agent Actions

AlphaBitCore, Inc.(AlphaBitCore公司)

James Rhodes, George Kang

AI总结:

研究人工智能代理行动正确性验证问题,提出运行时证明(PoE)方法构建执行三元组及相关谓词和保证,证明其合理性,通过原型测试验证效果,能将多方面绑定到可检查对象,使受治理执行可证。

摘要:

代理系统越来越多地执行而非提供建议。当人工智能代理查询受监管数据、调用有效工具并改变持久状态时,仅终端输出看似合理并不能保证正确性。关键问题包括每一步是否在合同下被授权、记录的历史是否可防篡改以及轨迹能否被确定性重建。我们将此形式化为执行的运行时证明。执行是三元组\(x = (C, T, R)\),包括合同\(C\)、执行因果事件流\(T\)和重放上下文\(R\)。一个良构谓词和五个验证器可检查的不变量构成了PoE有效性谓词。五个语义保证描述了授权、路径合规、拒绝时无影响、历史完整性和可重放性。我们在明确的加密和部署假设下证明了其合理性:任何产生违反语义保证的PoE有效执行的PPT对手都会导致签名伪造、哈希冲突或量化的部署失败事件。主执行模型将规划、执行、效果和记录保存分离到不同的权限平面;一个引理将跟踪完整性简化为仅效应器的凭证。仅当PoE = 1时才颁发执行证明证书。在单节点TypeScript原型中,PoE在最小流上增加约2.7毫秒,在并发批处理工作负载上增加4.4%的开销;一个标准的八事件跟踪压缩到约1.1 KB;注入的网关绕过和跟踪变异攻击被拒绝。PoE不取代共识、可信执行环境或零知识虚拟机;它将授权、效果、历史和重放绑定到一个单一的运行时可检查对象中,以便受治理的执行在合同下可证明。

英文摘要:

Agent systems increasingly execute rather than advise. When an AI agent queries regulated data, invokes effectful tools, and mutates persistent state, correctness is not captured by whether a terminal output looks plausible. The operative questions are whether each step was authorized under a contract, whether the recorded history is tamper-evident, and whether the trajectory can be reconstructed deterministically. We formalize this as runtime proof of execution. An execution is a triple $x = (C, T, R)$: a contract $C$, an Execution Causal Event Stream (ECES) $T$, and a replay context $R$. A well-formedness predicate and five validator-checkable invariants form the PoE validity predicate. Five semantic guarantees describe authorization, path compliance, null effect on deny, history integrity, and replayability. We prove soundness under explicit cryptographic and deployment assumptions: any PPT adversary that produces a PoE-valid execution violating a semantic guarantee yields a signature forgery, a hash collision, or a quantified deployment-failure event. The Prime Execution Model (PEM) separates planning, enforcement, effect, and recordkeeping into distinct authority planes; a lemma reduces trace completeness to Effector-exclusive credentialing. An Execution Attestation Certificate is issued only when PoE = 1. In a single-node TypeScript prototype, PoE adds approximately 2.7 ms on a minimal flow and 4.4% overhead on concurrent batch workloads; a standard eight-event trace compresses to approximately 1.1 KB; injected Gateway-bypass and trace-mutation attacks are rejected. PoE does not replace consensus, TEEs, or zkVMs; it binds authorization, effect, history, and replay into a single runtime-checkable object so that governed execution becomes attestable under contract.

机构、总结、中文摘要均由AI分析而来,可能存在错误,请以论文正文为准。

↑