{"id":"event-store-append-is-not-crash-consistent","text":"Event store appends update in-memory state before persisting to disk with no rollback on failure, batch appends can leave partial writes, and the per-call file open/close pattern adds overhead without providing atomicity guarantees.","truth_value":"IN","source":"","source_url":"","source_hash":"","justifications":[{"type":"SL","antecedents":["event-store-memory-ahead-of-disk","persist-after-memory","batch-append-not-crash-safe","persist-event-per-call-open"],"outlist":[],"label":"Memory-first writes with no rollback plus non-atomic batch persistence equals inconsistency after any crash"}],"dependents":["event-sourcing-lacks-any-durable-recovery-path"],"metadata":{"last_reviewed":"2026-05-30T09:01:17","review_result":"unnecessary"},"created_at":"","updated_at":"","reviewed_at":"","verified_at":"","retracted_at":"","explanation":{"steps":[{"node":"event-store-append-is-not-crash-consistent","truth_value":"IN","reason":"SL justification valid","antecedents":["event-store-memory-ahead-of-disk","persist-after-memory","batch-append-not-crash-safe","persist-event-per-call-open"],"label":"Memory-first writes with no rollback plus non-atomic batch persistence equals inconsistency after any crash"},{"node":"event-store-memory-ahead-of-disk","truth_value":"IN","reason":"premise"},{"node":"persist-after-memory","truth_value":"IN","reason":"premise"},{"node":"batch-append-not-crash-safe","truth_value":"IN","reason":"premise"},{"node":"persist-event-per-call-open","truth_value":"IN","reason":"premise"}]}}