Context Collision

The failure mode in which two agents operating on different context sets reach contradictory conclusions about the same operational state, producing divergent outputs that propagate through the workflow as if they were correct.

Context Collision is distinct from Handoff Friction and Context Leakage. Handoff Friction is a data format problem at system integration points — the receiving agent encounters an unexpected schema. Context Leakage is a within-run failure — the agent loses the intent of the original task as it progresses through a multi-step process. Context Collision is a knowledge continuity problem at agent boundaries: the receiving agent encounters unexpected reasoning, not unexpected data. It cannot validate what it has received because the upstream agent did not encode why it made the decisions it made — only what those decisions were.

The divergence propagates silently because both agents are operating correctly within their respective context sets. Neither has made an error by the rules of its own knowledge layer. The collision is visible only in the output — two branches of a multi-agent workflow producing contradictory results about the same operational state — and only if the system has audit infrastructure capable of tracing the divergence back to its origin. Without Proof of Action logs covering all agents in the chain, Context Collision manifests as an unexplained inconsistency whose source is structurally invisible.

First used: May 2026