Keep the lesson for the next incident
Compare boundary patterns
Group prior cases by input boundary, state history, role, environment, and consequence. Separate recurring structural gaps from unrelated rare conditions that only look similar.
Preserve the expected result
Write the intended outcome and the neighboring cases that define it. Keep sensitive values out while retaining a fixture shape and sequence that future reviewers can safely reuse.
Define a recurrence signal
Set a review trigger for a new valid boundary with the same state transition or consequence. Name the owner and the evidence needed to decide whether the pattern is a defect or a product choice.
What to carry forward
The lesson should add one boundary example or expectation record and a recurrence rule. Treat coverage as provisional until later changes exercise the same class of valid inputs without reopening the gap. Preserve a boundary matrix with expected outcomes and representative fixtures, and review it when validation, parsing, formatting, or domain rules change.
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