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

1. Received

   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.

2. Assessed

   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 is not part of this verdict. Each security agent reaches a verdict based on your configuration.

3. Resolved

   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.

4. Final state

   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.

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.

---

Escalations

What happens when a high-criticality finding notifies your team.

Sessions

How traces are grouped into sessions.