{"version":"2.1.236","anchor":"the-first-artifact-database-write-names-the-local-file-it-re","canonical_anchor":"the-first-artifact-database-write-names-the-local-file-it-re","heading":"The first artifact database write names the local file it reads from","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/the-first-artifact-database-write-names-the-local-file-it-re","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### The first artifact database write names the local file it reads from\n\nThe first artifact database write shows which local file it reads and why approval is manual.\n\n**What**\n\nThe approval prompt for an artifact database write now shows the local file the document comes from, and lists reasons the automatic permission classifier cannot approve it: a path whose spelling can name a different file, a path resolving outside the allowed read paths, and a hard-linked source.\n\n**Details**\n\n- The prompt no longer promises session-wide coverage when the write is not one that can be covered for the session.\n\n**Evidence**\n\n`the path\\u2019s spelling can name a different file than it appears to \\u2014 approval must come from the user, not the auto-permission classifier`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}