{"version":"2.1.269","anchor":"foreign-flag-added-to-synced-contentasset-schemas","canonical_anchor":"foreign-flag-added-to-synced-contentasset-schemas","heading":"'foreign' flag added to synced content\/asset schemas","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/foreign-flag-added-to-synced-contentasset-schemas","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### 'foreign' flag added to synced content\/asset schemas\n\nSynced content now carries a new 'foreign' flag alongside cowritten\/typeLocked metadata\n\n**Unclear.** What determines whether content is marked 'foreign', and what consuming that flag changes, is not stated.\n\n**What**\n\nContent schemas used for synced assets and comments, which already track fields like `cowritten`, `typeLocked`, and `writerClass`, gain a new optional boolean field called `foreign`. It's wired through the same serialization logic that handles those other fields.\n\n**Why**\n\nThe finding doesn't state what marks content as 'foreign' or how that distinction is used, only that the field now exists and is threaded through alongside the existing metadata.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}