{"version":"2.1.223","anchor":"memory-store-404s-distinguish-store-not-provisioned-from-a-m","canonical_anchor":"memory-store-404s-distinguish-store-not-provisioned-from-a-m","heading":"Memory-store 404s distinguish \"store not provisioned\" from a missing document","tier":"internal","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/memory-store-404s-distinguish-store-not-provisioned-from-a-m","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Memory-store 404s distinguish \"store not provisioned\" from a missing document\n\nMemory errors now tell you whether the whole store is missing or just a document.\n\n**What**\n\nA 404 from the memory backend now says whether the store itself does not exist or just the document.\n\n**Details**\n\n- The not-found error takes a kind, defaulting to \"document\"; memory-backend list and read paths construct it with \"store\".\n- Listing accepts `size_bytes` as a fallback when `content_size_bytes` is absent.\n- Listing now also records `updated_at`.\n\n**Evidence**\n\n`(store not provisioned)`\n\n- Area: Memory\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 0\/5"}