MCP Result Manipulation to A2A Effect

Methodology, not an executable workflow. This page defines a trust boundary, close control, and evidence requirement. The operator must implement it against a specific authorized target; no command here claims to execute the full chain.

Initialize MCP only after graph-wide preflight. Mutate a tool result, bind the decoded result into an A2A message/send, follow the task and artifact identifiers, and finish at a controlled external oracle. Preserve JSON-RPC request ID, MCP session ID, A2A context/task/artifact IDs, and delegated-hop links.

The close control changes only the result mutation. Use transcript 2.1 rule evaluation to prove a true miss separately from delivery failure. Ablate the A2A delegation or task-artifact stage. A target-accepted task does not prove impact; open the terminal callback, file, data-store change, or tool event.