SovAIHub
ModulesSAI-250
SAI-250 table of contents
Concept2 min readPrototype

Evaluation and release gates

Turn acceptance criteria into repeatable promotion decisions with recorded evidence and rollback conditions.

Last content review 2026-08-03Included in SAI-210, SAI-220, SAI-230, SAI-240, SAI-250, SAI-260, SAI-280

A release gate is a decision system

An AI release gate turns requirements into a repeatable allow, reject, hold, or exception decision. It applies to models, prompts, retrieval pipelines, policies, runtimes, tools, infrastructure, and complete workload releases.

A gate is more than a test suite. It defines the candidate, acceptance criteria, evidence, decision authority, exception route, promotion destination, and rollback conditions.

Build the gate contract

For each gate, specify:

  1. Candidate identity: the immutable versions and configuration being evaluated.
  2. Approved purpose: workload, users, data classes, deployment boundary, and prohibited uses.
  3. Evaluation set: representative, boundary, adversarial, permission, failure, and regression cases.
  4. Measures: quality, safety, security, latency, capacity, reliability, cost, and policy outcomes that matter.
  5. Thresholds: pass, fail, warning, and manual-review criteria with justified tolerances.
  6. Decision authority: who can approve, reject, or accept an exception.
  7. Evidence: inputs, environment, results, logs, reviewer notes, decision, and integrity information.
  8. Aftercare: monitoring signals, rollback trigger, expiry, and required reassessment events.

Avoid metric theatre

A high aggregate score can hide an unacceptable failure for a specific user group, permission case, language, content type, or high-impact task. Keep disaggregated results and inspect failure severity as well as frequency.

Do not reuse a pass outside its evaluated context. A new prompt, knowledge corpus, quantization, runtime, policy, tool, hardware profile, or deployment boundary can change behavior and may require partial or complete reassessment.

Exceptions

An exception should identify the failed criterion, rationale, compensating controls, owner, affected scope, expiry date, monitoring, and closure evidence. Exceptions must not silently redefine the acceptance threshold.

Release evidence

The final record should allow an independent reviewer to reproduce the decision logic: what was tested, under which conditions, what failed, who decided, what was promoted, and how it can be rolled back.