A safety property guarantees that something bad never happens during system execution. It is also an invariant: a condition that must remain true no matter what. section 6.4
Safety becomes concrete when expressed as a forbidden failure:
- A mutex-based system avoids deadlock, preventing threads from waiting forever. section 6.4
- A distributed database prevents two nodes from mistakenly believing they are leader. section 6.4
- A consensus algorithm may halt during a network partition rather than make an unsafe decision. section 6.4
Safety differs from liveness, which guarantees that something good eventually happens. Systems may prioritize safety by slowing or stopping when they cannot guarantee correctness; both properties matter in distributed systems and consensus. section 6.4 section 6.15











