Check whether the outcome improved
Assert comparison cases
Run fixtures for ascending and descending values, null placement, case or locale variants, numeric-looking text, and equal primary keys. Assert exact identifier sequence and the documented secondary key. Include malformed values so the fallback or review outcome is observable.
Check consumer consistency
Compare the same bounded records in list, paginated, report, and export contexts that claim the ordering. Verify filters and page boundaries do not change the rule. Inspect the first inversion and tied group directly rather than relying on a matching first or last record.
Exercise stability limits
Repeat an equal-key sequence and run it across relevant page sizes or source snapshots. Confirm the tie-breaker produces a deterministic order, or document the explicit instability contract. Retain input values, expected sequence, request parameters, and revision for later verification.
What to carry forward
Accept ordering when every covered consumer follows the documented fields, direction, null policy, type comparison, and deterministic tie rule. Keep the gate open for an undefined locale or mutable source. Report exact fixtures, pages, consumers, and known limitations with the evidence.
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