Microsoft Agent Framework boundary¶
Place AIT at the protocol client invoked by a workflow, executor, tool, or adapter. Framework-internal routing metadata is trace context, not evidence of an A2A or MCP hop.
The optional extra declares agent-framework-core >=1,<2. It deliberately does
not imply compatibility with every provider-heavy aggregate, release, or
workflow shape. Record the exact core version, the extension point that emitted
the exchange, its binding, and the receiver observation.
An import-only probe cannot support a compatibility claim. See Framework-mediated boundaries.