Keep the lesson for the next incident
Record the boundary
Write down the source shape, processing stage, affected cohorts, and final resolution with links to reviewed fixtures or queries. Note which observations were unavailable. This preserves a reusable trail for the next field omission and keeps hypotheses separate from confirmed behavior.
Strengthen examples
Add representative complete, permitted-empty, null, and malformed cases to the existing contract or transformation test set. Include the source variation that mattered, such as an older payload or alternate record state. Keep examples small enough that a maintainer can understand the expected output.
Set recurrence review
Choose a field-level signal, owner, review interval, and threshold that prompt another bounded investigation. Review both new omissions and unexpected reductions in record volume. Retire the follow-up only after several relevant batches meet the documented contract and the evidence is retained.
What to carry forward
Close the learning loop with a concise record of what changed in the contract, fixtures, ownership, and recurrence review. Keep unresolved source behavior visible as a follow-up. The durable outcome is a faster, repeatable detection path, not a claim that similar omissions are impossible.
Keep the decision with the work.
Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.
Create an account See the product workflow