AI, RAG & ML · Audit

AI Evaluation Audit

Audit an AI evaluation system as a release gate across task definition, datasets, scorers/judges, uncertainty, slices, regressions, and online correlation.

MCP library 1.6.1 · Instruction library 1.6.1 · English technical instructions

← Back to search

Use this workflow

Connect Vibe Coding Library to a coding agent that supports MCP over Streamable HTTP. Choose Other / MCP agent for a neutral prompt, or a ready-made Codex or Claude Code invocation. Add your task details below.

Operation

Inspect the selected behavior and report evidence-backed defects; do not change product code.

Goal and scope

Audit an AI evaluation system as a release gate across task definition, datasets, scorers/judges, uncertainty, slices, regressions, and online correlation.

Domain invariants

  • The evaluated task, unit, input context, reference/acceptable outcomes, failure taxonomy, and decision threshold match the shipped product behavior.
  • Evaluation data has provenance, consent/retention, deduplication, contamination/leakage controls, versioning, and representative risk slices.
  • Deterministic scorers, human rubrics, and model judges expose validity limits; judge prompts/models/settings are versioned and calibrated against human labels.
  • Comparisons use paired examples where possible, report uncertainty and practical effect, and do not tune repeatedly against a held-out release set.
  • Safety, latency, cost, tool/grounding, abstention, and product outcome metrics are separated instead of collapsed into one opaque score.
  • Regression gates define allowed variance, flaky/nondeterministic handling, ownership, artifact lineage, and what blocks release.

Audit method

  1. Map the production decision path to evaluation cases, scorers, rubrics, datasets, model/config identity, reports, and release gates.
  2. Inspect sampling, duplicates, contamination, slice coverage, reference quality, annotator/judge disagreement, and missing/error handling.
  3. Re-run a representative subset to measure scorer determinism and compare judge/human labels by failure class.
  4. Check statistical unit, paired comparison, confidence/uncertainty, multiple variants, threshold selection, and test-set reuse.
  5. Compare offline failures with available online incidents/feedback without claiming causal equivalence.

Handoff

Return the mismeasured product decision, affected dataset/slice, scorer or judge owner, and a labelled example that exposes the problem. Identify whether the correction belongs to data validity, scoring, uncertainty or the release decision. Feed that evidence into Improve AI Evaluation; a higher aggregate score is not a correction when the scorer still rewards the wrong outcome.

Workflow ID: ai-evaluation-audit · View the versioned source · Shared workflow and authority rules