Keep the lesson for the next incident
Identify the repeated gap
Compare prior diagnosis, fix, exposure, verification, and current failure. Name the condition that was never covered or the evidence that made two different symptoms look identical.
Preserve the comparison
Write the release, path, cohort, data, configuration, and delay context needed to reproduce the recurrence review. Keep the record concise enough to use during the next release.
Define a recurrence signal
Set a future review condition for the same behavior or the same uncovered boundary after release. Include the owner, comparison window, and evidence needed before calling the lesson durable.
What to carry forward
The lesson should change one verification boundary or release context record and define recurrence recognition. Treat prevention as unproven until a later release exercises the previously missed condition without the symptom returning. Capture the prior fix boundary, the new triggering condition, and one durable review check so future release reviews can detect recurrence without copying the old diagnosis.
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