{"id":"immutable-values-prevent-aliasing-bugs","text":"KV vector clocks return new instances on every operation and leaderboard updates by remove-then-reinsert rather than mutating in place; both approaches avoid aliasing bugs where shared mutable references could cause unintended state corruption.","truth_value":"IN","source":"","source_url":"","source_hash":"","justifications":[{"type":"SL","antecedents":["kv-vector-clock-immutable","leaderboard-update-by-remove-reinsert"],"outlist":[],"label":"Immutable-value semantics eliminate shared-reference aliasing at the cost of allocation overhead"}],"dependents":["structural-discipline-prevents-consistency-bugs"],"metadata":{"last_reviewed":"2026-06-05T18:21:49","review_result":"invalid"},"created_at":"","updated_at":"","reviewed_at":"","verified_at":"","retracted_at":"","explanation":{"steps":[{"node":"immutable-values-prevent-aliasing-bugs","truth_value":"IN","reason":"SL justification valid","antecedents":["kv-vector-clock-immutable","leaderboard-update-by-remove-reinsert"],"label":"Immutable-value semantics eliminate shared-reference aliasing at the cost of allocation overhead"},{"node":"kv-vector-clock-immutable","truth_value":"IN","reason":"premise"},{"node":"leaderboard-update-by-remove-reinsert","truth_value":"IN","reason":"premise"}]}}