LangGraph boundary

Place AIT where a graph node, tool adapter, or agent client emits A2A or MCP traffic. LangGraph state remains inside the process and is useful trace context, but it is not evidence that a remote hop occurred.

Disable LangSmith or other exporters unless the assessment explicitly permits them. A local interception experiment should not create an unreviewed external telemetry path.

ait connections add --protocol a2a_jsonrpc --upstream http://specialist.internal/
ait intercept start --connection CONNECTION_ID --direction request

The optional extra declares langgraph >=1.2,<2. That is an installation range, not a claim that every version has passed an external fixture. Record the exact installed version and the graph node that made the protocol call.

Importing langgraph, compiling a StateGraph, or observing a state key proves nothing about a remote agent boundary. The evidence is the emitted protocol message, the selected receiver's state, and the experiment's separate effect observation. See Framework-mediated boundaries.