TessIndex: Capability Verified Identity System for the Agent Economy
Read the original on arXiv AI →The Flow has not summarised this story yet — read it at arXiv AI.
The Flow has not summarised this story yet — read it at arXiv AI.
arXiv:2610.17126v1 Announce Type: cross Abstract: The rapid proliferation of autonomous AI agents in decentralized ecosystems challenges existing identity paradigms. While human identity is tradition...
arXiv:2607. 12619v1 Announce Type: new Abstract: The rapid emergence of LLM-powered autonomous and semi-autonomous agents is reshaping software systems from static, request-response components into goal-directed, adaptive, and tool-using computational actors.
arXiv:2606. 30970v1 Announce Type: new Abstract: Autonomous AI agents increasingly perform consequential actions on behalf of human principals, including financial transactions, external communications, and enterprise workflows.
arXiv:2606. 30970v2 Announce Type: replace Abstract: Autonomous AI agents increasingly perform consequential actions on behalf of human principals, including financial transactions, external communications, and enterprise workflows.
The paper proposes five runtime primitives—discovery, identity, governance, attestation, and supply chain—to manage autonomous AI agents in enterprise settings. It argues that traditional control models fail because agents are transient, model-driven, and self‑discoverable, making runtime governance essential. The authors detail an implementation that mediates agent actions against policy, authorizes them via a per‑tenant vocabulary, and records them in a verifiable ledger, noting the associated operational costs and partial deployment status.
The paper introduces Agentic Cloud Workflow Engineering, a framework that converts natural‑language agentic cloud‑engineering tasks into validated code repositories and verified cloud deployments. It separates graph engineering for long‑horizon workflow progression, loop engineering for bounded diagnosis and recovery, and agent harness engineering for zero‑trust execution. Experiments on Google Cloud show that executions either produce a verified deployment or an auditable terminal failure within bounded recovery limits.