# CI gates for LLM quality

A suite that only runs in a notebook is not a production gate. CI (or a scheduled harness) should fail the build or release when task success, groundedness, refusal, or cost thresholds regress.

## What a minimal gate looks like

- Frozen eval set and thresholds in version control  
- Same model and retrieval config labels recorded per run  
- Fail on hard policy breaks even if the average score looks fine  
- Cost and latency budgets optional but visible  

Open tools (Promptfoo, DeepEval, Ragas, LangSmith) fit many stacks. The method is provider-agnostic.

## Where Arviser stops

We deliver a repeatable suite and CI harness notes inside the written Audit scope. We do not run your production CI forever unless you buy a follow-on engagement. LLM Quality Audit is billed on its own and is not credited toward later packages.

**Next:** [LLM Quality Audit](/llm-quality-audit) · [Shared metrics](/guides/shared-metrics) · [Production sampling](/guides/production-sampling) · [Request scope](/#scope)
