{"version":"2.1.269","anchor":"db-read-now-flags-results-from-documents-owned-by-someone-el","canonical_anchor":"db-read-now-flags-results-from-documents-owned-by-someone-el","heading":"Read results now flag content owned by someone else as 'foreign'","tier":"notice","area":"Database Tools","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/db-read-now-flags-results-from-documents-owned-by-someone-el","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Read results now flag content owned by someone else as 'foreign'\n\nDatabase reads and artifact\/asset tools now mark results as foreign when they belong to another user's workshop or session\n\n**What**\n\n- `db_read` results now include a `foreign: true` field when the document was authored by someone else, the collection is access-controlled, or the caller isn't the document's owner.\n\n- The artifact tool's `read_asset` action similarly flags results as `foreign: true` when the asset's page is a workshop page or otherwise not the caller's own; `delete_asset` now also returns a `written: { url }` object on successful deletion.\n\n- The artifact tool's `verify`, `list_files`, and `read_file` actions now add `foreign: true` when the artifact or file belongs to another workshop\/session (detected via workshop-page recording or, for `read_file`, a workshop-decisions marker in the HTML).\n\n- New schemas back this: a `written` object (url) and a `verify` object (url, ver, state, entries, truncated, dropped, waited, and the new optional `foreign` flag).\n\n**Why** Surfacing ownership this way helps Claude Code (and anyone reviewing its actions) tell apart content it owns from content that belongs to someone else's workshop or session, which matters for deciding whether it's safe to edit or delete.\n\n- Area: Database Tools\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}