{"version":"2.1.236","anchor":"type-locked-artifacts-have-their-own-read-and-publish-rules-","canonical_anchor":"type-locked-artifacts-have-their-own-read-and-publish-rules-","heading":"Type-locked artifacts have their own read and publish rules, all inert in this build","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/type-locked-artifacts-have-their-own-read-and-publish-rules-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Type-locked artifacts have their own read and publish rules, all inert in this build\n\nArtifacts made from a template lock the template's files against edits, unreachable without two off switches.\n\n**What**\n\nAn artifact created from a type carries a lock recording which files belong to the type. Claude is told those files cannot be edited here, and publishing an `index.html` to such an artifact is refused because the page comes from the type. None of it is reachable without the two artifact-type flags, both of which default off.\n\n**Details**\n\n- The lock is carried through artifact read-back and share status, and the read path stops taking the plain-owner fast path for a locked artifact.\n- The tool description states verbatim that a type-owned file belongs to the artifact's type and can't be changed here.\n- Whether any of this is visible is frozen once per session at schema-build time.\n- Creating a new artifact from a type is additionally blocked inside remote sessions.\n- None of these symbols exist in v2.1.235.\n\n**Evidence**\n\n`this file belongs to the artifact's type and can't be changed here`\n\n- Area: Artifacts\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 4\/5\n- Present in the build but not switched on"}