liveBook · Manning

Artifact

As explained in Context Engineering

An A2A artifact is a concrete output produced by a server agent, such as a report, diagram, data table, or code file.

An A2A artifact is a concrete output produced by a server agent, such as a report, diagram, data table, or code file. Artifact exchange lets a server share results with the client agent that delegated the work. section 7.8.1

Delegated travel planning

A travel-planning agent can delegate work to specialist agents, sharing relevant dates, location constraints, or budget preferences. A server agent processes its request in an isolated context and returns results to the client; concrete outputs are artifacts. section 7.8.1

A2A is an evolving interoperability standard. Check the current specification before deploying artifact exchange in production. section 7.8.1

How Context Engineering covers it

How deep it goes
Defines concrete outputs and situates their exchange within A2A, without detailing artifact structure.
Examples
Names reports, diagrams, data tables, and code files as possible artifacts.
What you can do after
Evaluate and understand how server-agent outputs fit into delegated A2A interactions.
How it connects
Connects artifacts to agent-to-agent protocol, task lifecycle management, and context exchange.

Also explained in

Compare how 2 books explain artifact →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Context Engineering. The section links point to the parts of the book it draws on.