{"version":"2.1.273","anchor":"artifact-foreign-document-detection-now-also-checks-for-an","canonical_anchor":"artifact-foreign-document-detection-now-also-checks-for-an","heading":"Artifact 'foreign document' detection now also checks for an outside writer","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/artifact-foreign-document-detection-now-also-checks-for-an","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Artifact 'foreign document' detection now also checks for an outside writer\n\nArtifact database reads now also flag documents as foreign when an outside writer has touched them\n\n**What**\n\nWhen Claude Code reads an artifact's shared database, it checks whether the artifact is a \"foreign\" document, meaning someone other than your account wrote it. That check now also treats a document as foreign if your account is the owner but a new signal shows an \"outside writer\" has been involved, alongside the existing checks for documents co-written by others.\n\n**Why**\n\nThis closes a gap where a document could look like it belongs entirely to you even though someone outside had written to it, so Claude Code can flag it appropriately.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}