Conversations

A conversation is the durable runtime record for an interaction with an agent. It contains transcript, context, active capability state, structured cards, artifacts, delivery events, and human participation.

Runtime lifecycle

1. Open a new conversation or resume an existing one.
2. Send a message or structured card interaction.
3. Receive an inline response or stream delivery events.
4. Reconcile history after reconnecting.
5. Continue until completion, escalation, handoff, or abandonment.

Human takeover does not create a separate conversation. Ownership and execution state change while the same transcript and audit history continue.

Applications should use the runtime SDK unless they need to implement the lower-level runtime contract.