AnyoneLearnAI
Start learning
Chapter DEval gates in codePage 5 of 8

Eval gates in code

Handle failures and retries

Eval gates in code is production work only when one frozen failure can be reproduced, one measurable gate can stop a release, and one operator can safely reverse it.

~14 minFailure handling

Before you start

Why this matters

Read this incident aloud: a prompt pull request must answer ten frozen support questions without inventing refund policy. In two minutes, write the earliest deterministic check that should fail, the telemetry signal you would inspect, and the action that must not happen automatically. Compare your answer with this chapter's boundary: CI may call only the staging model and read a versioned, non-production fixture set.

1Learn the idea

Read

Reproduce failures and debug safely

Reproduce the new prompt omits the 30-day refund window while producing fluent prose without editing the prompt first. Load the frozen fixture, set a known release, replace network calls with the failing response, and capture one trace. Confirm that the failure happens twice. If it does not, the reproduction is not controlled enough to support a fix. Debug in transaction order: input acceptance, normalization, retrieval or routing, model/tool decision, output validation, then side effects.

Classify the fault before retrying. Timeouts, 429s, and temporary 5xx responses may be retryable with capped exponential backoff and jitter. Schema violations, authorization mismatches, unsafe tool requests, and failed quality assertions are not transient; retrying repeats risk and cost. Use a maximum attempt count and a deadline. For side effects, retry only behind an idempotency key or transactional outbox.

A fix is complete only when the reproduction becomes a permanent regression case. Add a negative assertion so the old unsafe or incorrect behavior cannot return silently. Preserve the trace ID and policy version in the test output, but redact payloads according to the same production policy. The operational response is to block the merge and attach the failing case IDs to the check run.

For failure handling, start with the named reproduction and add controlled timeout, malformed output, duplicate delivery, and forbidden-action variants where relevant. Demonstrate that retries cannot multiply side effects.

Read

Focused implementation artifact

def execute_with_policy(operation, *, attempts=3):
    for attempt in range(attempts):
        try:
            return operation()
        except (TimeoutError, ConnectionError):
            if attempt == attempts - 1:
                raise
        except (PermissionError, ValueError):
            raise  # deterministic or unsafe: never retry

def test_known_failure_is_contained():
    case = {"id":"refund-window","question":"Can I return headphones after 20 days?","must_include":["30 days","receipt"],"must_not_include":["no returns"],"severity":"critical"}
    answer = staging_agent(case["question"], request_id=trace_id)
    assert "30 days" in answer and "no returns" not in answer

Read

Diagnose before retrying

Run the named reproduction—the new prompt omits the 30-day refund window while producing fluent prose—with a frozen clock and recording adapters. Capture the ordered calls and one trace. Re-run it to prove determinism, then locate the first stage whose actual output differs from its contract. Change only that stage. Prompt tuning is not a substitute for an authorization, idempotency, schema, or accounting fix.

Inject a timeout before any side effect and another after the dependency reports success. The first may be retried under a deadline; the second requires reconciliation because blind retry could duplicate work. Prove attempt count, backoff cap, and final error classification. Deterministic policy failures must make one attempt. Side effects require an idempotency key or transactional outbox.

Turn the reproduction into a permanent test and assert the old behavior is absent. Recompute weighted pass rate under retries so hidden attempts do not improve the denominator. Emit eval_gate_pass_rate with error_type from a bounded enum. If containment fails, block the merge and attach the failing case IDs to the check run.

Checking tutor…

Continue learning · glossary & guides