Environments
Environments help you ship changes safely. The same workflow behaves differently depending on prompt versions, retrieval configs, and model parameters—so you want clear boundaries and promotion flows.
Typical environments
| Environment | Purpose | What changes here |
|---|---|---|
| Development | fast iteration | drafts, experiments, noisy telemetry |
| Staging | pre-production validation | full eval suites, release candidates |
| Production | user traffic | only promoted and reviewed versions |
What should be environment-scoped
- active prompt versions
- model/provider defaults
- tool allowlists and rate limits
- retention and sampling policies (often stricter in prod)
Promotion workflow (recommended)
- Draft in dev → run targeted evals
- Promote to staging → run full suites + check latency/cost
- Promote to prod → monitor traces, errors, and budgets
- Roll back immediately if critical metrics regress
Next steps
- Read Evaluations for staging/prod gates.