Keep the lesson for the next incident
Document traversal semantics
Write page size, ordering fields, tie-breaker, cursor or offset meaning, boundary inclusivity, filters, source mutation behavior, and termination rule. Name any requirement for a stable snapshot. Keep examples of valid first, middle, and final page transitions beside the contract.
Keep coverage fixtures
Retain multi-page fixtures for exact boundaries, equal sort values, empty results, changed page sizes, and source mutation where relevant. Assert complete identifier sets and order after traversal. Include a negative case that would expose an inclusive or stale cursor.
Review recurrence
Assign an owner for the traversal contract and each critical consumer. Review page coverage, duplicate identifiers, and early termination across representative runs on a defined cadence. Reopen investigation for a new divergent boundary, changed ordering, or an unexplained difference in expected population.
What to carry forward
Close the learning record with traversal semantics, coverage fixtures, ownership, and a recurrence trigger for missing, repeated, or prematurely terminated records. Keep mutable-source limits explicit. The durable improvement is a visible completeness contract and faster diagnosis when a page boundary drifts.
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