{"version":"2.1.224","anchor":"artifact-skill-text-no-longer-promises-a-per-viewer-consent-","canonical_anchor":"artifact-skill-text-no-longer-promises-a-per-viewer-consent-","heading":"Artifact skill text no longer promises a per-viewer consent prompt","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224\/e\/artifact-skill-text-no-longer-promises-a-per-viewer-consent-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.224","markdown":"### Artifact skill text no longer promises a per-viewer consent prompt\n\nArtifact docs no longer claim each viewer is asked for consent before a page updates itself.\n\n**What**\n\nWorkshop and whiteboard skill and template text used to say the browser asks each viewer for consent before a page may update itself. That sentence is gone; only the server-side writer gate is described now.\n\n**Details**\n\n- The whiteboard template sends a one-way analytics message when a board is sent to Claude, which the surrounding shell forwards only if the event name is on its allowlist.\n\n**Evidence**\n\n`the shell enforces the writer gate server-side`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}