Sources & further reading
Primary documentation checked 6 October 2026. Diagrams are original conceptual illustrations. Historical analogies and adoption guidance are the speakers' interpretations.
Different decade, familiar integration problem
One model contract, several providers
Every new tool multiplies the wiring
MCP gives capabilities a common interface
Three primitives, three control patterns
A2A addresses an independent counterpart
A task can outlive a single response
Capability access + outcome delegation
Let the user follow and guide the work
A shared meaning can fit in a file
Follow one request across boundaries
Change the coding agent, keep the editor
The next boundary: money
Choose the interaction contract
A shared protocol still needs a trust model
Three UI contracts, different responsibilities
x402: authorization before settlement
Narrative and speaker notes: Markdown source