{"version":"2.1.232","anchor":"team-memory-sync-can-route-through-a-new-storage-backend","canonical_anchor":"team-memory-sync-can-route-through-a-new-storage-backend","heading":"Team memory sync can route through a new storage backend","tier":"soon","area":"Team Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/team-memory-sync-can-route-through-a-new-storage-backend","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Team memory sync can route through a new storage backend\n\nTeam memory sync can use a storage backend instead of plain files, but nothing turns it on.\n\n**What**\n\nManifest, read, write, stat and delete steps in team memory sync now go through a storage backend when one is present, falling back to plain filesystem calls when it is not. Nothing in this build turns that backend on.\n\n**Details**\n\n- Listing and reading of memory entries gained storage-backed paths too.\n- Each operation has its own failure message, so a backend fault names the step that failed.\n\n**Evidence**\n\n`multi-store-sync: local entry not writable via storage`\n\n- Area: Team Memory\n- Tier: Nothing to try yet\n- Useful: 1\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}