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

# Traces

> Traces are the individual interactions within a session that Velatir captures and reviews.

## What Is a Trace?

A trace is a single AI interaction captured within a [session](/traces/understanding-sessions). Every request sent to an AI service, every response received, and every related event creates a trace.

Traces are the raw material agents review. Each one records what happened, where it came from, and what the outcome was.

## Trace Directions

Every trace has a direction that describes the type of interaction.

| Direction    | Description                            | Example                                      |
| ------------ | -------------------------------------- | -------------------------------------------- |
| **Inlet**    | A request going to an AI service       | Someone submits a prompt to a chat assistant |
| **Response** | A reply coming back from an AI service | The assistant's answer                       |
| **Signal**   | A related event                        | A session starting, or a background event    |

## Viewing a Trace

Within a session, select any trace to see its full details.

* **Direction and source** show the type of interaction and which service was involved.
* **Assessments** show what each agent found and the verdict it reached.
* **Outcome** shows whether the trace was allowed, flagged, or blocked.
* **Escalations** show which channels were notified, when applicable.

## What Happens After Capture

<Steps>
  <Step title="Agents review it" icon="shield-check">
    Your active agents review the trace, each recording its own assessment.
  </Step>

  <Step title="The outcome is resolved" icon="scale">
    Based on the security agents' findings and their roles, the trace is allowed, flagged, or blocked. The most restrictive outcome wins. High-criticality findings also notify your channels.
  </Step>

  <Step title="It is logged" icon="check">
    The trace reaches its final state and is recorded. Escalations are sent to your connected channels.
  </Step>
</Steps>

For the full picture, see [Trace lifecycle](/traces/trace-lifecycle).

***

<CardGroup cols={2}>
  <Card title="Sessions" icon="layers" href="/traces/understanding-sessions">
    How traces are grouped into sessions.
  </Card>

  <Card title="Trace lifecycle" icon="refresh-cw" href="/traces/trace-lifecycle">
    Follow a trace from capture to final state.
  </Card>
</CardGroup>