{"version":"2.1.224","anchor":"memory-documents-carry-version-tokens-and-report-conflicts","canonical_anchor":"memory-documents-carry-version-tokens-and-report-conflicts","heading":"Memory documents carry version tokens and report conflicts","tier":"notice","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/memory-documents-carry-version-tokens-and-report-conflicts","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Memory documents carry version tokens and report conflicts\n\nOrg memory documents now show version tokens and report conflicts so concurrent edits get retried instead of clobbered.\n\n**What**\n\nReading an org memory document now shows a version token next to the updated date, writes report the version they produced, and a concurrent edit produces a distinct conflict result telling the model to re-read the document and retry with the fresh token. Requires org memory to be enabled for the session.\n\n**Details**\n\n- The conflict message is \"The memory store reported a concurrent change to this document.\"\n- The conflict result also carries the conflicting path taken from the server response.\n- The version token is appended to reads in the form `[version: ...]`.\n\n**Evidence**\n\n`The memory store reported a concurrent change to this document.`\n\n- Area: Memory\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 4\/5"}