SYNTHESIS NOTE
Topics›Agents Multi Architecture›this note

How do failures cross boundaries between multiple agents?

Explores four distinct mechanisms—messages, shared state, aggregation, and delegation—that allow a failure or attack originating in one principal to propagate through multi-agent systems. Understanding these pathways is essential for designing agent interactions that contain rather than amplify risk.

Synthesis note · 2026-09-23 · sourced from Agents Multi Architecture

The introduction packs the mechanism into one sentence: "Messages propagate influence between principals, a shared state preserves propagated influence, aggregation combines local outputs from different principals, and delegation transfers authority across boundaries." Each verb is a different thing an interaction can do to a failure. A message moves influence from one principal to another. Shared state lets the influence outlast the exchange, so a later principal inherits what an earlier one absorbed. Aggregation merges local outputs, so a wrong or manipulated contribution can carry into a group result. Delegation moves authority rather than information, which is what lets attacker content reach a privileged tool.

This differs from the inventory in Do internal agent hops in pipelines need security monitoring?. That note counts five arrows in one pipeline shape, so it is a list by position. The four verbs are a list by mechanism and do not depend on the topology. Two of them are not hops at all: aggregation is a combination step and shared state is a place, and the vault note on that inventory observes it has no peer-to-peer hop, which is the "messages" case in Can one compromised agent corrupt an entire multi-agent network?.

The vault already holds an instance of most verbs. Shared state: Can ordinary infrastructure become unplanned agent memory? and Can shared agent memory systems reliably delete information?. Aggregation: Can a quorum of honest validators certify an invalid transition? and Does confidence drive influence in multi-agent deliberation systems?. Delegation: the path a taint travels in Can semantic labels on requests prevent malicious propagation through agent networks?. Those mappings are my reading, not the paper's.

A caution on scope. The abstract separately counts "six interaction interfaces", and the excerpt does not say how the four verbs relate to them: a subset, a coarser cut, or an independent one. Treat the verbs as the introduction's own summary of mechanism, not as the interface taxonomy (see Can adversary position unify fragmented multi-agent attack models?).

What the excerpt does not give. No examples per verb, no ranking of which mechanism dominates, and no mapping to the six interfaces.

Inquiring lines that read this note 55

This note is a source for these research framings, grouped by the broader line of inquiry each explores. Scan the bold lines of inquiry; follow any specific question forward.

Should multi-agent systems use structured protocols or natural language communication? Does multi-agent architecture create security vulnerabilities single-agent defenses can't address? How should persistent agent-authored code be governed and shared? How do agents coordinate to violate constraints despite individual-level safeguards? Why do autonomous agents report success despite actually failing? How does workflow position amplify security failures in multi-agent systems? How do multi-agent systems balance consensus-building with error detection in collaborative reasoning? How should agent identity and authorization work across organizational boundaries? How do social dynamics and peer behavior influence agent decision-making and cooperation? What determines effective LLM routing across cost, quality, and governance? What evidence best independently verifies agent behavior for safety? How do multi-agent LLM systems fail at genuine coordination and deliberation? How should control and autonomy be allocated in human-AI workplace collaboration? When do multi-agent systems outperform single-agent approaches for complex task execution? Can sequences of locally safe agent actions violate system-level constraints? Does extending agent autonomy erode human capacity for meaningful oversight? How can we ensure AI systems reliably follow constraints rather than circumvent them? Do safety evaluations reliably measure real deployed AI safety risks?

Related concepts in this collection 4

This note in its neighbourhood — explore the map, then jump to a related concept in the list below.

Concept map
14 direct connections · 109 in 2-hop network ·medium cluster Open in graph ↗

Click a node to walk · click center to open · click Open in graph to see this note in the full knowledge graph

your link semantically near linked from elsewhere

Related papers in this collection 8

Papers most semantically related to this note, ranked by cosine similarity in the embedding space.

Original note title

messages propagate influence, shared state preserves it, aggregation combines local outputs and delegation transfers authority — four ways interaction carries a failure across principal boundaries