{"version":"2.1.281","anchor":"share-metadata-gains-type-first-party-and-caps-read-not-foun","canonical_anchor":"share-metadata-gains-type-first-party-and-caps-read-not-foun","heading":"Shared artifacts get a first-party type check and a new type-declaration mark","tier":"internal","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/share-metadata-gains-type-first-party-and-caps-read-not-foun","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Shared artifacts get a first-party type check and a new type-declaration mark\n\nArtifact shares now record type_first_party and caps_read_not_found and are flagged when a first-party type claim cannot be confirmed\n\n**Unclear.** The finding does not say how the handling of a share differs when these fields are set.\n\n**What**\n\nArtifacts are items that can be shared with you. Claude Code attaches risk marks to an artifact share, which are warnings about what it could not verify. It now checks more carefully whether a shared artifact really comes from a first-party type.\n\n- The share details gain two optional yes\/no fields. `type_first_party` is set when the type is \"first_party_type\". `caps_read_not_found` is set when the capabilities lookup came back not found. Both are read when deciding how to treat a share.\n\n- The `attested` mark is now also added when a share claims `type_first_party` but the local record does not show a `first_party_type`.\n\n- A new `type-declaration` mark is added when a share that is type-locked, first-party and has an observed grant disagrees with, or cannot be checked against, the locally known capabilities or type lock.\n\n**Why**\n\nA share that claims to come from a first-party type, when Claude Code cannot confirm that on your machine, now gets flagged instead of being taken at its word.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}