Trace a worked example

You operate an insurance claim assistant. A teammate proposes a change that sounds beneficial, but you require a trace connecting configuration to evidence. Here is the observed run:

A claimant says “rear-left door,” while photo OCR reads a workshop label and the vision model marks damage at coordinates (0.62, 0.48). A low-resolution run calls it the front door. Reprocessing the original image at higher resolution and checking vehicle orientation resolves the mismatch; the decision stores the crop and coordinate, not just prose.

First identify the input and scope. Which user, segment, document, image, query, hardware profile, or task was involved? Next record the exact configuration: model or checkpoint, prompt, index, context policy, sampler, thresholds, and tool versions that matter for multimodal AI. Then preserve the intermediate artifact that explains the result. Finally attach the user-visible output and measured consequence.

Write the trace as a sequence rather than a conclusion:

request + configuration
  -> intermediate evidence
  -> model or policy decision
  -> validation / fusion / routing
  -> user-visible action
  -> measured outcome

This format prevents hindsight from collapsing several stages into “AI error.” It also exposes where a deterministic check could have stopped propagation.

Use absolute counts alongside percentages. If success falls from 78 of 100 to 62 of 100, that is a 16 percentage-point decrease, not merely “16% worse.” If cost rises from $0.006 to $0.018 for one million requests, variable spend rises from $6,000 to $18,000. If a sample contains only ten cases from a critical language, one miss moves its rate by ten points; collect more evidence before claiming stability.

Score each modality and cross-modal reasoning separately: OCR word error, ASR word error, object or region grounding, temporal localization, task accuracy, calibration, latency, and performance by lighting, device, language, and accent. Require evidence coordinates or timestamps for consequential claims. Pick one primary metric and list gates separately. Do not average a privacy breach, severe unsafe action, or failed authorization with stylistic quality.

Generate at least three explanations: input mix changed; a component configuration changed; or measurement changed. Then propose a discriminating test for each. Replay the same cases on old and new configurations, compare intermediate artifacts, and rescore both with the same rubric. This controls more variables than debating outputs by eye.

Tiny text is unreadable, sampled video skips the decisive frame, ASR misses an accent, image metadata is treated as visual evidence, modalities contradict each other, and the model invents objects outside the crop. Prompt injection can appear inside an image or document. The likely failure should match the earliest divergent artifact. If it does not, revise the hypothesis.

Choose among keep, roll back, canary, route, or collect more data. State the owner and deadline. A rollback restores safety but does not explain root cause; preserve the failed configuration for offline reproduction. A successful fix adds the case to a regression set and updates the runbook.

The expert habit is modest: claim only what the trace supports. One run can demonstrate a mechanism, not a universal advantage. A coherent sequence with inspectable evidence teaches more than a polished before-and-after screenshot.