{"id":"sstable-write-path-has-dual-fragility","text":"The SSTable write path has two independent fragility points: sorted key order is the caller's responsibility with no enforcement (violation silently corrupts binary search), and the file header is written as a placeholder then patched via seek-back after all entries are written (a crash between data write and header patch leaves a structurally invalid file).","truth_value":"OUT","source":"","source_url":"","source_hash":"","justifications":[{"type":"SL","antecedents":["sstable-sorted-order-caller-responsibility","sstable-writer-append-then-patch"],"outlist":[],"label":"Both the invariant contract and the write protocol have independent unguarded failure modes"}],"dependents":[],"metadata":{"last_reviewed":"2026-05-30T09:01:17","review_result":"pass"},"created_at":"","updated_at":"","reviewed_at":"","verified_at":"","retracted_at":"","explanation":{"steps":[{"node":"sstable-write-path-has-dual-fragility","truth_value":"OUT","reason":"SL justification invalid","failed_antecedents":["sstable-sorted-order-caller-responsibility"],"label":"Both the invariant contract and the write protocol have independent unguarded failure modes"}]}}