Status: IN
Event sourcing is fundamentally unreliable at two independent levels: it has no durable recovery mechanism (in-memory state updated before disk, no crash-consistent append, ephemeral snapshots), and its core addressing abstraction conflates stream-scoped and global ID spaces across read paths, meaning even successfully persisted events may be incorrectly reconstructed.
Non-durable persistence combined with inconsistent event addressing undermines both storage and retrieval
Depends on (SL): event-sourcing-lacks-any-durable-recovery-path, event-sourcing-conflates-two-id-spaces