arXiv AI By Mehdi Shajari

Assurance-Conditioned Continuous Authorization for Autonomous AI Agents

Read the original on arXiv AI →

The paper introduces Assurance-Conditioned Continuous Authorization (ACCA), a framework that maintains operational authority for autonomous AI agents by separating evidence validity from contextual applicability. ACCA derives assurance claims from eligible evidence, resolves a multidimensional effective-authority envelope, and uses a typed dependency graph for selective re‑evaluation of authorization‑relevant changes. The authors demonstrate the approach with controlled scenario tests in a trading domain, showing implementation‑level evidence for the method’s effectiveness.

Machine-generated by The Flow from the publisher's headline and feed description — not written or checked by a human. The full article lives at arXiv AI.

arXiv AI
Jul 28

Intent-Governed Tool Authorization for AI Agents

arXiv:2606. 22916v2 Announce Type: replace Abstract: AI agents increasingly act through external tools: they read private data, construct structured payloads, submit write requests, export records, and coordinate workflows across application boundaries.

By Genliang Zhu, Chu Wang
Hugging Face Trending Papers
Jun 22

Intent-Governed Tool Authorization for AI Agents

AI agents increasingly act through external tools: they read private data, construct structured payloads, submit write requests, export records, and coordinate workflows across application boundaries. Existing authorization mechanisms usually ask whether an integration credential, app, or token can call a tool.

arXiv AI
Oct 21

Runtime Control for AI Agents: Closing the Evaluation--Execution Gap in Operational Workflows

The paper introduces a runtime assurance layer for language‑model agents operating in operational workflows, addressing the evaluation–execution gap where approvals may become invalid after changes in facts, evidence, policy, or authority. The proposed state‑bound configuration separates probabilistic measurement from deterministic adjudication, binds execution allowances to the basis of an approval, invalidates them upon logged changes, and rechecks admissibility at dispatch. In a scripted 42‑case replay, the approach identified 15 later‑invalidated approvals that a non‑re‑evaluating comparator missed, holding 14 affected actions before dispatch and compensating one landed effect.

By Jayesh Bhadane, Ramachandra Yerramsetti, Rajesh Gupta, Sumit Kumar