{"version":"2.1.247","anchor":"the-memory-file-warnings-are-written-as-repair-instructions","canonical_anchor":"the-memory-file-warnings-are-written-as-repair-instructions","heading":"The memory-file warnings are written as repair instructions","tier":"internal","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/the-memory-file-warnings-are-written-as-repair-instructions","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### The memory-file warnings are written as repair instructions\n\nMemory file warnings are phrased as instructions so Claude can fix the file immediately.\n\n**What**\n\nEach warning tells the model what to do rather than just what is wrong, so Claude can fix the file in the same turn. It sits behind the same memory-directory condition as the check itself.\n\n**Details**\n\n- Missing description: says recall cannot reliably select the file and asks for a frontmatter block with name, description and metadata.type.\n- Continuation file: explains that recall only reads the first stretch of each file, so chained `-2` parts are rarely found.\n- Over the size cap: phrased as an error saying the write succeeded but content past the limit is invisible to recall.\n\n**Evidence**\n\n`This memory file has no frontmatter `description`, so recall cannot reliably select it for future sessions. Add the frontmatter block (name, description, metadata.type) at the top.`\n\n- Area: Memory\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}