{"version":"2.1.304","anchor":"instruction-file-origin-marking-unverified-paths","canonical_anchor":"instruction-file-origin-marking-unverified-paths","heading":"Instruction files changed by a hook are marked unverified","tier":"internal","area":"Memory","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/instruction-file-origin-marking-unverified-paths","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Instruction files changed by a hook are marked unverified\n\nInstruction files such as CLAUDE.md are now flagged unverified when a hook adds them or their path was marked\n\n**What**\n\nInstruction files, such as CLAUDE.md, tell Claude how to work in a project. A hook is a command you configure to run at certain points in a session. Claude Code now marks an instruction file as unverified when its path was flagged, or when it first appears through a hook's change.\n\n**Why**\n\nInstruction content that a hook brought in is no longer treated the same as content Claude Code read itself.\n\n- Area: Memory\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}