{"version":"2.1.248","anchor":"storage-naming-rules-now-carry-per-field-error-guidance","canonical_anchor":"storage-naming-rules-now-carry-per-field-error-guidance","heading":"Storage naming rules now carry per-field error guidance","tier":"internal","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/storage-naming-rules-now-carry-per-field-error-guidance","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Storage naming rules now carry per-field error guidance\n\nStorage naming rules now give specific error messages and document the key layout.\n\n**What**\n\nThe storage layer gained explicit tables of which names are streams and which are scopes, with a specific message for each misuse, plus allow-lists of permitted directory names and files. They document the layout: task ids, mailbox teammates and cache ids are individual keys, not scopes you can narrow by.\n\n**Evidence**\n\n`names one task value, a key, not a scope: a list scope narrows with listId only`\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}