{"version":"2.1.283","anchor":"new-guidance-when-publishing-over-a-workshop-page","canonical_anchor":"new-guidance-when-publishing-over-a-workshop-page","heading":"Claude is told what to do when publishing over a workshop page is refused","tier":"notice","area":"Artifacts","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/new-guidance-when-publishing-over-a-workshop-page","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Claude is told what to do when publishing over a workshop page is refused\n\nRefused publishes over a workshop page now tell Claude to read the page's live decisions instead, or to tell you the session can't build on it\n\n**Unclear.** Whether workshop pages are behind a remote switch in this release is not clear.\n\n**What**\n\nWhen Claude tries to publish over a workshop page and the publish is refused, Claude now gets instructions for two refusal reasons:\n\n- `workshop_schema`: instead of receiving the page's source, Claude is told to read the page's live decisions using `read_page_data` with the schema `workshop-decisions`\n\n- `workshop_ambiguous`: when the page's block of workshop decisions is ambiguous, Claude is told to tell you that this session cannot build on the page\n\nBefore, the `workshop_schema` reason existed but came with no explanation.\n\n**Why**\n\nThis stops Claude from resending outdated content over a workshop page and overwriting the decisions recorded on it.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}