{"version":"2.1.187","anchor":"team-memory-partition-manifest-memory-sync-in-development","canonical_anchor":"team-memory-partition-manifest-memory-sync-in-development","heading":"Team memory partition manifest ( .memory-sync ) [In Development]","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.187\/e\/team-memory-partition-manifest-memory-sync-in-development","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.187","markdown":"### Team memory partition manifest (`.memory-sync`) [In Development]\n\n**What**\n\nTeam memory sync will gain a manifest file (`.memory-sync`) inside each mount directory to detect and handle cross-partition conflicts \u2014 preventing one team's memory store from silently being misused by another team that happens to share the same directory path.\n\n**Status**\n\nFeature-flagged (gated by `tengu_silk_almanac`)\n\n**Details**\n\n- Each team's memory is scoped to a unique `partitionId` (the backend's partition identifier, likely an org or team UUID)\n- Each mount directory gets a `.memory-sync` manifest (JSON: `{ v: 1, partitionId: \"...\" }`) written at sync time\n- On pull, the manifest's `partitionId` is compared against the expected backend partition; a mismatch invalidates the basis and forces a full re-sync\n- If a different partition's manifest is detected during a non-user-scoped mid-session sync, sync is suppressed entirely with a warning: \"mount dir holds a different partition's `.memory-sync` \u2014 suppressing sync (remove the dir to re-mount)\"\n- Without this flag enabled, two teams sharing the same directory path could silently read and overwrite each other's memory\n\n**Evidence**\n\nNew manifest functions (gated on `it(\"tengu_silk_almanac\", !1)`, search for `\".memory-sync\"` or `\"partition mismatch\"`)\n\n- Flag `tengu_silk_almanac`: Off in both readings (read for one account on one subscription tier against v2.1.187; this account: off, anonymous baseline: off, compiled default: off) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release."}