> ## Documentation Index
> Fetch the complete documentation index at: https://docs.impact.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Trace, Interaction and Session

> Use the right identity for the application work you want to understand.

A **Trace** contains technical spans from an execution. A **span** describes one observed operation, such
as a model request or a tool call. Native trace and span IDs remain distinct from application identity.

An **Interaction** is one application request and its observed outcome. Use the owning `interaction`
wrapper at the real request boundary. It can generate an Interaction ID when the application does not
supply one. SDK startup and ordinary model calls do not create logical requests automatically.

A **Session** is a conversation or coherent job that can contain several Interactions. Supply the
application's actual Session ID. A **User ID** is an opaque application identifier within the selected Product.

## Add meaning without changing ownership

Use `context` to contribute Session, Interaction, User or deployment labels to existing work. Use `span`
for an application operation that automatic capture cannot observe. Neither replaces an owning request
wrapper or proves that a proposed tool actually executed.

An asynchronous handoff is explicit: the application confirms accepted publication before a successor
continues the Interaction. Merely returning a handle, buffering work or ending a span does not prove
completion or transfer. The SDK does not implement an application job store.

## Capture and delivery are separate

The SDK preserves native results, errors, consumed stream output and observed effects. A tool proposal
is distinct from execution. Missing content, usage or a validation schema stays unavailable rather than
being inferred from neighboring records.

`flush` attempts to deliver finished telemetry. `shutdown` drains and closes resources owned by the SDK.
Check delivery and cleanup separately, and match the fresh execution in Impact to establish Product readback.

The SDK reports supplied deployment labels; the platform resolves canonical Product, Environment and
Version associations. Context attributes do not grant access to another Product or capability.

Add request and Session context with the [JavaScript](https://docs.impact.ai/sdk/javascript/api.md#group-work-into-an-interaction)
or [Python](https://docs.impact.ai/sdk/python/api.md#record-a-logical-request) examples. For accepted queue work, use the
[JavaScript handoff](https://docs.impact.ai/sdk/javascript/api.md#continue-work-after-a-queue-handoff) or
[Python handoff](https://docs.impact.ai/sdk/python/api.md#hand-off-completion-ownership) APIs.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.