Skip to main content

Rollout Guide

The path from install to production follows a deliberate sequence. Do not skip observe mode. Each stage validates the next.
1

Observe on real traffic

Goal: Baseline cost, latency, and model usage without affecting production.
What to look for:
  • Total cost per day/user/agent
  • Which models are called most
  • Average latency per step
  • Whether any calls would violate compliance rules
2

Validate policies in observe mode

Goal: Confirm that enforcement rules would behave correctly before enabling them.
If violations are unexpected, adjust budgets or policies before enforcing.
3

Enforce one constraint

Goal: Turn on enforcement for one dimension. Start generous.
Monitor for a few days. Look at stop rates, cost distributions, and agent completion rates.
4

Tighten and expand

Goal: Add more constraints once the first one is validated.
5

Per-agent policies

Goal: Different agents get different constraints based on their role.

Environment-Driven Mode

Use environment variables to control the mode per environment:

Validation Checklist

Before moving to the next stage, confirm:
  • Observe metrics match expectations (cost, latency, model usage)
  • No unexpected compliance violations in trace
  • Budget caps are set above the 95th percentile of observed runs
  • Agent completion rates remain acceptable under enforcement
  • Decision traces are reviewed for false positives
  • Monitoring and alerting are in place for stop actions

Next Step

Pick the right framework integration for your stack. Choose your integration →