Skip to content
XEVRION
Get started
Menu
ProductOverviewReviewProveControlObserveImproveHow it works
TeamsEngineeringSecurityComplianceOperations
CompanyAboutContactChangelogSecurity
ResourcesDocsGlossaryFAQPricingPrivacy

Review

Your rules decide who looks at what

Each action your agent proposes is sorted by your policy: go ahead alone, ask one person, or ask two.

Get startedSee pricing →
app.xevrion.co.uk / policies / refundsExample data

Rules, top to bottom

First match wins
  • Risk is criticalNever auto-approved2 reviewers
  • Refund over £500refund.issue2 reviewers
  • Refund up to £50, confidence 0.9+refund.issue · low riskAuto-approve
  • Everything elseDefault1 reviewer

Try an action

Before it goes live
Action
refund.issue
Amount
£540
Confidence
0.82
Matched
Rule 2
Outcome
Two reviewers

The same rule as code

// policies/refunds.yamlwhen: refund.issue  amount: > 500then: require 2 reviewerswhy: Over the £500 limit

Why it matters

What policy routing changes

  • Safe actions go straight through. Risky ones reach a person.
  • Your policy picks one person, two people, or a refusal.
  • Every route stores the rule that sent it.
  • Every action pings someone, or none do.
  • Who looks at what is settled in chat.
  • Nothing records why a request went where it did.

The resultPeople only see what needs them.

What you get

Policy routing, in practice

  • Four routes

    Auto-approve, one reviewer, four-eyes approval, or reject outright. You choose per action and per risk.

  • Rules as code

    Keep policies in your own repo. A new policy is replayed on past requests before it can go live.

  • Plain reasons

    Every route records why it was picked, so a reviewer sees the rule that sent the request to them.

How it works

Step by step

  1. 1

    Agent proposes

    It sends the action, the data and a confidence score.

  2. 2

    Policy reads it

    Action type, risk and amount are checked against your rules.

  3. 3

    Route chosen

    Alone, one person, two people, or declined.

  4. 4

    Reason saved

    The rule that fired goes in the record.

Questions

About policy routing

Can I test a rule before it goes live?

Yes. A new policy is replayed on your own past requests first, and activation can be blocked until that passes.

What if no rule matches?

Policies end with a default route, so every request still gets an answer.

Next

Works well with

Know what your agents did.

Start free. Guard your first agent in a few minutes, and keep a record anyone can check.

Get started freeSee pricing →
  • Free plan, no card
  • Signed, chained decisions
  • Checked offline, without us