{"version":"2.1.315","anchor":"claude-docs-artifacts-armed-for-durable-subscribe","canonical_anchor":"claude-docs-artifacts-armed-for-durable-subscribe","heading":"A new claudeDoc flag for artifacts and their durable subscriptions","tier":"notice","area":"Artifacts","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/claude-docs-artifacts-armed-for-durable-subscribe","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### A new claudeDoc flag for artifacts and their durable subscriptions\n\nArtifact publishing gains a claudeDoc flag that can set up a durable subscription, with a new claude_doc_not_admitted failure reason\n\n**Unclear.** It is not clear what triggers Claude doc publishing or whether users can reach it in this release.\n\n**What**\n\nArtifacts are documents Claude Code can publish. Pieces of a new Claude docs kind of artifact have appeared:\n\n- The publish step takes a new `claudeDoc` setting, and the tracking of finished publishes checks `claudeDocSlugs`.\n\n- A new function publishes with `claudeDoc` turned on. It reports whether a durable subscribe was armed, meaning an ongoing watch on the document was set up.\n\n- A data format now accepts an optional `claude_doc` true-or-false value, which is ignored if it is malformed. It maps to `claudeDoc` being on.\n\n- A failed subscription can now be reported with the reason `claude_doc_not_admitted`.\n\nWhat produces or uses `claude_doc` was not traced, and no feature flag was found controlling it.\n\n**Why**\n\nThis looks like groundwork for a kind of document that Claude Code can keep watching, where the watch can be refused. Since what produces or uses it was not traced, there may be nothing visible yet.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 5\/5\n- Scope: individual\n- Heads-up: no"}