{"id":"recovery-simultaneously-over-and-under-engineered","text":"Recovery is paradoxically both over-engineered and under-implemented: the WAL builds complete sequence number and checkpoint infrastructure that's never consulted during replay, while the actual recovery paths lack batch atomicity and metadata CRC protection — engineering effort was invested in infrastructure that goes unused while the active recovery path remains unsafe.","truth_value":"OUT","source":"","source_url":"","source_hash":"","justifications":[{"type":"SL","antecedents":["wal-recovery-infrastructure-is-vestigial","storage-crash-recovery-has-no-safe-path"],"outlist":[],"label":"Vestigial recovery infrastructure coexists with unsafe actual recovery paths"}],"dependents":["no-subsystem-has-viable-recovery-strategy"],"metadata":{"last_reviewed":"2026-05-30T09:01:17","review_result":"pass"},"created_at":"","updated_at":"","reviewed_at":"","verified_at":"","retracted_at":"","explanation":{"steps":[{"node":"recovery-simultaneously-over-and-under-engineered","truth_value":"OUT","reason":"SL justification invalid","failed_antecedents":["wal-recovery-infrastructure-is-vestigial","storage-crash-recovery-has-no-safe-path"],"label":"Vestigial recovery infrastructure coexists with unsafe actual recovery paths"}]}}