{"version":"2.1.274","anchor":"new-artifact-provisioned-schema-for-storage-backing","canonical_anchor":"new-artifact-provisioned-schema-for-storage-backing","heading":"Artifact creation now reports where it's stored","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/new-artifact-provisioned-schema-for-storage-backing","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Artifact creation now reports where it's stored\n\nArtifact create results now include a 'provisioned' field describing the storage backend (store, project_id, file_id, node_id)\n\n**What**\n\n- Artifact publish\/session objects, and the result of a successful artifact-create call, now carry an optional `provisioned` field.\n\n- This field describes where and how the artifact is backed in storage: a `store` reference, `project_id`, and optional `file_id`\/`node_id`, parsed from the server's response via a new schema\/validator.\n\n- Whether an artifact was provisioned (`provisioned: true`\/`false`) is also recorded in telemetry.\n\n**Why**\n\nThis lets Claude Code (and its telemetry) know exactly which storage backend and location an artifact ended up in, which is useful for debugging and for features that need to reference the artifact's underlying storage location later.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}