{"version":"2.1.227","anchor":"newer-storage-layer-reaches-org-memory-plugin-caches-and-plu","canonical_anchor":"newer-storage-layer-reaches-org-memory-plugin-caches-and-plu","heading":"Newer storage layer reaches org memory, plugin caches and plugin skills","tier":"internal","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/newer-storage-layer-reaches-org-memory-plugin-caches-and-plu","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Newer storage layer reaches org memory, plugin caches and plugin skills\n\nOrg memory cache, plugin orphan markers and plugin skills can route through the storage layer.\n\n**What**\n\nThe organisation memory discovery cache, plugin version orphan markers and plugin skill loading now accept an optional storage handle and route reads and writes through it, each falling back to the previous direct filesystem path when no handle is passed.\n\n**Details**\n\n- Orphan marker write, delete and stat go through a plugin cache key when the path maps to a marketplace, plugin and version; plugin skills memoise in a separate cache slot when a handle is present.\n- References to this storage handle rise from a few dozen in the previous build to several hundred, so this release is mostly migration groundwork.\n- Which of the two paths a given user gets is decided by the callers and is not fixed in the source.\n\n**Evidence**\n\n`skillsV5`\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}