{"version":"2.1.232","anchor":"team-memory-skills-can-be-read-through-the-memory-backend-in","canonical_anchor":"team-memory-skills-can-be-read-through-the-memory-backend-in","heading":"Team-memory skills can be read through the memory backend instead of disk","tier":"internal","area":"Team Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/team-memory-skills-can-be-read-through-the-memory-backend-in","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Team-memory skills can be read through the memory backend instead of disk\n\nSkills in team memory can be read through the memory backend instead of the filesystem.\n\n**What**\n\nSkills stored under a team-memory mount can now be listed and read through the memory backend's own hardened text reader rather than reading files from disk. The disk path is kept for mounts that have no backend handle.\n\n**Details**\n\n- Taken only when both a backend handle and a project key are supplied; nothing in the code read shows what turns that backend on.\n- New diagnostics distinguish a skill not at its expected location, one that moved, one carrying other names, and one that is not a plain small file.\n- One message covers \"a second name on the file, or the backend's own publish in flight\".\n\n**Evidence**\n\n`a second name on the file, or the backend's own publish in flight`\n\n- Area: Team Memory\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5"}