> ## 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.

# Trace Lifecycle

> How a trace flows through Velatir from capture to final state.

## Overview

Every AI interaction captured by Velatir follows the same path. Understanding it helps you read trace outcomes and configure your agents well.

## The Stages

<Steps>
  <Step title="Received" icon="inbox">
    The browser extension or desktop app sends an interaction to Velatir. The trace is stored and grouped into a session with any related traces. Review begins straight away.
  </Step>

  <Step title="Assessed" icon="shield-check">
    Gatekeeper and Data Protector review the trace at the same time, each recording an assessment.

    | Agent              | Looks at                                                                 |
    | ------------------ | ------------------------------------------------------------------------ |
    | **Gatekeeper**     | Which service is being used                                              |
    | **Data Protector** | Sensitive content such as credentials, personal data, and financial data |

    [Coach](/agents/coach) is not part of this verdict. Each security agent reaches a verdict based on your configuration.
  </Step>

  <Step title="Resolved" icon="scale">
    The outcome depends on each agent's role.

    | Role         | What it can do                                                         |
    | ------------ | ---------------------------------------------------------------------- |
    | **Observer** | Flags its finding for review. Does not block or notify.                |
    | **Enforcer** | Blocks the trace. High-criticality findings also notify your channels. |

    The most restrictive outcome wins. If either agent blocks, the trace is blocked.
  </Step>

  <Step title="Final state" icon="check">
    The trace settles as **Allowed**, **Flagged**, or **Blocked**. Channel notifications do not change that outcome, and they do not hold the prompt for a dashboard decision.
  </Step>
</Steps>

## Sessions Give Context

Related traces are grouped into a session that represents a complete conversation or workflow. When a reviewer looks at a blocked or notified trace, they see the whole session around it rather than a single interaction on its own.

## Monitoring

* **Sessions** shows activity grouped into complete interactions.
* **Assessments** shows every security-agent verdict, with reasoning and any applied instruction.
* Open any trace to see each agent's assessment, how the outcome was resolved, and any channel notification.

***

<CardGroup cols={2}>
  <Card title="Escalations" icon="bell" href="/traces/escalations">
    What happens when a high-criticality finding notifies your team.
  </Card>

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