The Adapter Passed Every Test and Still Failed in Production

A fictionalised but technically plausible postmortem about evaluation-set mismatch. The useful result is a method that preserves evidence, exposes constraints, and makes the next decision reviewable. This note describes an engineering workflow rather than a claim about a particular organization or production event.

Establish the boundary

Label the scenario as a reconstructed engineering example. Keep the source version, configuration, and stable identifier together while this work is performed. That gives a reviewer a direct path from an observed outcome to the input and rule that produced it. Treat automatic checks and human judgment as separate controls, then record both in the incident note.

Use a fixed holdout or review sample for this step. Include normal records, rare boundary cases, and at least one input designed to fail safely. A useful change improves the intended condition without removing evidence about a known limitation.

The release gate and why it appeared sufficient

Describe the release gate and why it appeared sufficient. Keep the source version, configuration, and stable identifier together while this work is performed. That gives a reviewer a direct path from an observed outcome to the input and rule that produced it. Treat automatic checks and human judgment as separate controls, then record both in the incident note.

A production input slice absent from evaluation

Identify a production input slice absent from evaluation. Keep the source version, configuration, and stable identifier together while this work is performed. That gives a reviewer a direct path from an observed outcome to the input and rule that produced it. Treat automatic checks and human judgment as separate controls, then record both in the incident note.

Detection, rollback, and containment

Explain detection, rollback, and containment. Keep the source version, configuration, and stable identifier together while this work is performed. That gives a reviewer a direct path from an observed outcome to the input and rule that produced it. Treat automatic checks and human judgment as separate controls, then record both in the incident note.

Add the missing slice without overfitting to one incident

Add the missing slice without overfitting to one incident. Keep the source version, configuration, and stable identifier together while this work is performed. That gives a reviewer a direct path from an observed outcome to the input and rule that produced it. Treat automatic checks and human judgment as separate controls, then record both in the incident note.

Corrective actions with owners and verification criteria

Record corrective actions with owners and verification criteria. Keep the source version, configuration, and stable identifier together while this work is performed. That gives a reviewer a direct path from an observed outcome to the input and rule that produced it. Treat automatic checks and human judgment as separate controls, then record both in the incident note.

Practical check

Postmortem timeline and revised release checklist. The example below is intentionally small enough to run before a larger recovery or release workflow.

from pathlib import Path

for path in Path("runs").glob("*.json"):
    if path.stat().st_size == 0:
        print(f"empty run record: {path}")

Evidence for the next decision

Keep the input digest, outcome, and reviewer note with the resulting artifact or postmortem. Inventing a real customer incident or company. When evidence is incomplete, preserve the failing example, define the missing validation, and defer promotion until results can be compared fairly.

Make the process idempotent. Repeating the same step on unchanged input should not append metadata, discard extra detail, or silently change ownership. Idempotence makes retries safe and exposes hidden state when outputs differ.

Review results by failure category rather than a single blended number. A small number of high-risk failures can outweigh an improvement on common cases, particularly when output feeds a release workflow.

Keep accepted and rejected examples together. A concise rejected sample with its expected outcome is a durable regression test and prevents the same edge condition from returning as an unexplained surprise.

Use a separate holdout set for release decisions. Training records can guide implementation, but they cannot demonstrate correct behaviour on new wording, new sources, or changed input order.