{"version":"2.1.269","anchor":"system-instruction-for-publishing-finished-work-replaced-ent","canonical_anchor":"system-instruction-for-publishing-finished-work-replaced-ent","heading":"System instruction for publishing finished work replaced entirely \u2014 now covers Artifacts and document connectors","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/system-instruction-for-publishing-finished-work-replaced-ent","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### System instruction for publishing finished work replaced entirely \u2014 now covers Artifacts and document connectors\n\nGuidance on publishing finished work rewritten to cover Artifacts and document connectors, not just HTML page titles\n\n**What**\n\nAn internal instruction that guides Claude's behavior was completely rewritten. It used to be narrow advice about setting an HTML `<title>` tag. It now gives much broader guidance on when Claude should publish a finished piece of work as an Artifact (a standalone piece of content like a document or app shown alongside the chat) or through a first-party document connector (an integration the host explicitly designates as such) \u2014 including giving the person a link to it, offering rather than immediately publishing a page when it's unclear whether that's wanted, and never treating a connector as first-party unless the host has said so.\n\n**Why**\n\nThis changes how Claude decides whether to hand you a finished artifact directly, publish it to a connected document service, or just offer it, so results should better match what you actually intended to do with the output.\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 2\/5"}