arXiv (All)
open access
Attesting Outputs and Delegation Ancestry in Multi-Agent AI Systems
Multi-agent applications delegate work across independently operated deployers. After an incident, a verifier must answer two questions: which deployer released the reported bytes, and whether each cross-deployer edge was authorized. Credentials establish who may act, but need not bind them to later
Conceptio Open Archive
Analyze & explore related research in Conceptio
Connect this record directly into your research workflow or AI agent. Explore citations across open repositories, query full text, and export structured proof bundles.
This document is indexed with metadata only: full text is not available in the archive for this record. Open the official source ↗
Related documents
- LLM-as-Code Agentic Programming for Agent Harness#282880
- Bot or Not? Detecting AI-Driven Web Traffic Using Network Metadata AnalysisWhitepaperCyber Defense, Artificial Intelligence22 Sep 2026William Hatfield#1055178
- From Agent Traces to Trust: Evidence Tracing and Execution Provenance in LLM Agents#259384
- Behavioral Integrity Verification for AI Agent Skills#178803
- Hard Stop: Kernel-Level Preemption and Containment for Rogue Agentic Execution#1108865
Record · ID 799591
Retrieved via Conceptio: every document is proof-bundled with source, license, and retrieval metadata.
Retrieved via Conceptio: every document is proof-bundled with source, license, and retrieval metadata.
Bring this data into your agent: Connect via MCP or API · 20 free credits to start · no card required
Read the Docs → · View CLI source on GitHub · Conceptio Open Knowledge Archive
Read the Docs → · View CLI source on GitHub · Conceptio Open Knowledge Archive