Understanding Review Tasks

How agents escalate traces for human review and how decisions are made

What Are Review Tasks?

A review task is created when an agent determines that a trace requires human judgment. Only traces that an agent explicitly escalates result in a review task.

Review tasks are the primary mechanism for human oversight in Velatir. They ensure that high-risk AI interactions receive a human decision before proceeding.

When Review Tasks Are Created

Review tasks are created through the agent escalation process.

1. Trace Arrives

   An AI interaction is captured as a trace from one of your data sources.

2. Agents Evaluate

   All active agents assess the trace in parallel. Each agent specialises in a different compliance domain: data protection and access control.

3. Agent Escalates

   One or more agents determine the trace needs human review. The agent produces an Escalate intent, which triggers review task creation.

4. Review Task Created

   A review task is created and linked to the trace. Notifications are sent to connected channels so reviewers can act.

How Agents Evaluate Traces

All active agents evaluate every trace independently and in parallel.

Agent	What It Evaluates
Data Protection	Personally identifiable information, financial data, credentials, and health information
Gatekeeper	Access control violations and usage rule compliance

Each agent produces one of three intents for every trace.

Intent	Meaning
Allow	The trace is acceptable. No action needed from this agent.
Block	The trace should be rejected. The agent identified a clear violation.
Escalate	The trace needs human review. The agent identified a risk that requires judgment.

The agent’s role determines what it can actually do with its intent. An Observer can only report. An Enforcer can block or escalate to create review tasks.

Review Task States

State	Description
Pending	The review task is waiting for a human decision
Processing	A reviewer has started working on the task
Approved	The reviewer approved the trace to proceed
Rejected	The reviewer rejected the trace
Change Requested	The reviewer asked for modifications before the trace can proceed

Making Decisions

Reviewers see the original trace, the agent assessments that triggered the escalation, and any relevant session context. Three decision options are available.

Decision	What Happens
Approve	The trace is marked as Completed and allowed to proceed
Reject	The trace is marked as Rejected and blocked
Request Change	The trace is held while the requested modifications are made

Every decision is recorded with the reviewer’s identity, the channel used, an optional reason, and a timestamp. This creates a complete audit trail.

Where Decisions Happen

You can review and respond to tasks through any connected channel.

Channel	How It Works
Web Dashboard	Use the decision panel with full trace context and agent assessments
Slack	Receive a notification with action buttons to approve, reject, or request changes
Microsoft Teams	Receive an adaptive card with decision buttons
Email	Receive a summary and respond with your decision

All channels produce the same outcome. Choose whichever fits your team’s workflow.

Viewing Review Tasks

In the web dashboard, navigate to Review Tasks to see all tasks across your workspace. You can filter by state, agent, or date range.

Click any task to see the full details: the linked trace, session context, each agent’s assessment, and the decision history. For tasks that require multiple approvals, progress is shown in the task detail view.

---

Trace Lifecycle

Understand how traces flow through the platform.

Channels

Set up Slack, Teams, or Email for review notifications.

Core Concepts

See how all platform components fit together.