{
  "status": "unknown",
  "advantages": [],
  "limitations": [],
  "supersedes": [],
  "supersededBy": [],
  "firstSeen": null,
  "lastSeen": null,
  "updated": "2026-11-20",
  "slug": "safety-property",
  "term": "Safety property",
  "aliases": [
    "safety (distributed systems)"
  ],
  "definition": "A safety property is an execution requirement whose every violation has a finite prefix that no continuation can make compliant.",
  "note": "In one consensus instance, choosing two different values violates agreement; later agreement cannot erase those conflicting decisions. Safety does not require a decision to occur. Protocol guarantees still depend on the specified fault model and retained state. [paxos-simple]\n\nA finite run without a violation does not prove safety for every allowed execution. The definition classifies a property, not the completeness of a test suite. [defining-liveness]\n\nA specified completion deadline is also a safety requirement in a timed model: later completion cannot undo a missed deadline. This is different from unbounded eventual completion. [fairness-position]",
  "related": [
    "liveness-property",
    "consensus",
    "linearizability"
  ],
  "citations": [
    {
      "id": "defining-liveness",
      "title": "Alpern and Schneider. Defining Liveness. Information Processing Letters 21(4), 181-185 (1985), sections 1-3.",
      "url": "https://www.cs.cornell.edu/fbs/publications/DefLiveness.pdf",
      "accessed": "2026-11-20"
    },
    {
      "id": "paxos-simple",
      "title": "Lamport. Paxos Made Simple (2001), sections 2.1, 2.4 and 2.5.",
      "url": "https://lamport.azurewebsites.net/pubs/paxos-simple.pdf",
      "accessed": "2026-11-20"
    },
    {
      "id": "fairness-position",
      "title": "Schneider and Lamport. Another Position Paper on Fairness. Software Engineering Notes 13(3), 1988, pp. 1-2.",
      "url": "https://www.cs.cornell.edu/fbs/publications/fairnessPos.pdf",
      "accessed": "2026-11-20"
    }
  ],
  "provenance": [
    "Primary-source synthesis with constructed reasoning examples, not a protocol execution, implementation certification or new proof."
  ]
}
