{"id":"sort-preprocessing-universally-correct","text":"Sort-then-scan preprocessing produces correct results across all solutions that use it, because sorting establishes exactly the adjacency and monotonicity invariants that the subsequent linear scan requires for correctness.","truth_value":"OUT","source":"","source_url":"","source_hash":"","justifications":[{"type":"SL","antecedents":["sort-preprocessing-enables-linear-scan","correctness-by-construction-not-validation"],"outlist":["sort-people-assumes-distinct-heights"],"label":"Sort preprocessing is correct by construction — UNLESS the sort comparison function cannot distinguish elements that must be ordered differently (as when duplicate heights cause tuple comparison to fall through to names)"}],"dependents":[],"metadata":{"source_type":"derived","_retracted":true},"created_at":"","updated_at":"2026-06-17T15:32:01+00:00","reviewed_at":"","verified_at":"","retracted_at":"2026-06-17T15:32:01+00:00","explanation":{"steps":[{"node":"sort-preprocessing-universally-correct","truth_value":"OUT","reason":"SL justification invalid","failed_antecedents":[],"label":"Sort preprocessing is correct by construction — UNLESS the sort comparison function cannot distinguish elements that must be ordered differently (as when duplicate heights cause tuple comparison to fall through to names)","violated_outlist":["sort-people-assumes-distinct-heights"]}]}}