{
  "status": "unknown",
  "advantages": [],
  "limitations": [],
  "supersedes": [],
  "supersededBy": [],
  "firstSeen": null,
  "lastSeen": null,
  "updated": "2026-10-19",
  "slug": "read-atomic-isolation",
  "term": "Read-atomic isolation",
  "aliases": [
    "RA isolation",
    "Read Atomic isolation"
  ],
  "definition": "Read-atomic isolation excludes fractured reads and reads of uncommitted, aborted or intermediate transaction versions.",
  "note": "It constrains visibility, not serial execution or concurrent update conflicts. A later version may replace a companion write. [ramp]",
  "related": [
    "fractured-read",
    "monotonic-atomic-view",
    "snapshot-isolation",
    "linearizability"
  ],
  "citations": [
    {
      "id": "ramp",
      "title": "Bailis et al. Scalable Atomic Visibility with RAMP Transactions. SIGMOD 2014, sections 3-4. DOI: 10.1145/2588555.2588562.",
      "url": "https://www.bailis.org/papers/ramp-sigmod2014.pdf",
      "accessed": "2026-10-19"
    },
    {
      "id": "hesela-consistency",
      "title": "Hesela: storage consistency and read-set visibility examples.",
      "url": "https://hesela.com/analyses/storage-consistency-ordering/#read-atomic",
      "accessed": "2026-10-19"
    }
  ],
  "provenance": [
    "The cited 2014 paper defines this model; firstSeen is unset rather than asserting historical priority. Lifecycle status is unknown because this is a semantic guarantee, not a hardware product. [ramp]"
  ]
}