Skip to content

SoK: Decentralized Agent Economic Infrastructure

Oct 2026 · 0 citations · 120 references
Computer Science

TL;DR

This study organizes security and economic requirements into 17 property families over six stages, with receipt soundness and completeness assessed separately, and introduces guarantee closure, a task-relative criterion for determining whether guarantees established at one stage remain available and constrain the later decisions that depend on them.

Abstract

Decentralized agent economies increasingly build a single task from protocols that were designed and secured separately. This creates a simple problem: a workflow can look correct at each step and still produce the wrong outcome. For example, a correct escrow may release payment on an authorized approval that provides little evidence that the delivered work actually satisfied the task. We systematize this problem across the full lifecycle of an agent task. Our study organizes security and economic requirements into 17 property families over six stages, with receipt soundness and completeness assessed separately. We examine 12 systems and standards, five reusable mechanism families, and four classical baselines. We introduce guarantee closure, a task-relative criterion for determining whether guarantees established at one stage remain available and constrain the later decisions that depend on them. We apply the criterion to controlled and native workflows, covering 840 matched executions and an exhaustive 11,648-case check over a finite objective-task domain. Our results expose recurring failures between verification and settlement, where conforming work can remain unaccepted or valid evidence can be ignored. Public records and model judgments further distinguish recorded approval from evidence of task conformance, while economic analysis identifies the report, penalty, and shared-error assumptions behind these guarantees. These findings show where end-to-end guarantees fail and what must be repaired to preserve them across the workflow.

View source

Similar papers

Open access Oct 2026

Agent Foundry: A Boundary-Preserving Architecture for Governed Agentic Platforms

Agent frameworks expose tools, delegation, memory and human approval, yet the controls attached to a request (identity, tenant, scopes, budgets, deadlines, rate limits, fail behavior) are routinely lost at execution boundaries: delegation, threads, streaming, resume, caching, retrieval and adapter exports. We present A...

Mukherjee Arghya · 0 citations
#artificial intelligence Review Sep 2026

Maat: Independent Deterministic Contract-Based Governance for Multi-Agent LLM Workflows

Maat is presented, a runtime governance layer that validates agent-to-agent handoffs against a versioned workflow contract, or anchor, with no language model in the validation or scoring path and the results support deterministic handoff validation for contract-expressible defects.

Uliana Elina · 0 citations
Preprint Nov 2026

Permitted but Unauthorized: Affordance-Induced Delegated-Scope Violations in Multi-Agent LLM Systems

Multi-agent LLM systems place several agents on shared infrastructure, where each agent holds permissions far broader than the task it is delegated -- so every agent is routinely permitted to act on a peer's resources it was never assigned. We ask: under competitive pressure, what determines whether an agent crosses fr...

Shravya Kanchi · 0 citations
#artificial intelligence Review Sep 2026

Relic: From Multi-Agent Collaboration to Persistent Organizational Capability

The introduction of Relic, which turns recurring collaboration failures into organization-owned, executable protocols, and how collaboration experience can become persistent organizational state that remains useful beyond the members who created it are shown.

Hong-Yi Du, Tian-Yi Zhang, Wei-Jia Zhang et al. · 0 citations
#machine learning Preprint Oct 2026

KedgeFlow: A Programmable Control Plane for Enterprise AI Agents

Enterprise AI agents can execute altered versions of approved actions, concurrently reuse the same permission, or retry operations whose responses were lost. These failures arise when approval and resource execution lack a shared contract. KedgeFlow specifies language-independent contracts for trusted controllers to au...

Jun-Fei He, De-Ying Yu · 0 citations

Related blog posts

We use cookies to run the site and, with your consent, for analytics and to show ads. See our Cookie Policy.