{"version":"2.1.234","anchor":"a-recording-storage-namespace-with-no-writer-in-this-build","canonical_anchor":"a-recording-storage-namespace-with-no-writer-in-this-build","heading":"A recording storage namespace with no writer in this build","tier":"internal","area":"Storage Backend","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/a-recording-storage-namespace-with-no-writer-in-this-build","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### A `recording` storage namespace with no writer in this build\n\nInternal storage keys learned a \"recording\" kind, but nothing in the build creates one.\n\n**What**\n\nThe component that builds and checks internal storage keys gained a `recording` kind, addressed by project, session id and a timestamp. Nothing in the build produces recordings, so what would create one is not settled here.\n\n**Details**\n\n- The timestamp is validated like other key parts, and session id is checked on lookup.\n- Requests that ask for a group of stored values but actually name a single stream are now rejected, with per-kind explanations for transcripts, logs and session logs: `names one agent transcript, a stream key, not a scope: narrow a scope with agentRelPath`.\n\n**Evidence**\n\n`namespace: \"recording\"`, `names one agent transcript, a stream key, not a scope: narrow a scope with agentRelPath`\n\n- Area: Storage Backend\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}