{"version":"2.1.227","anchor":"memory-citation-telemetry-counts-how-cited-files-resolved","canonical_anchor":"memory-citation-telemetry-counts-how-cited-files-resolved","heading":"Memory citation telemetry counts how cited files resolved","tier":"internal","area":"Memory","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/memory-citation-telemetry-counts-how-cited-files-resolved","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Memory citation telemetry counts how cited files resolved\n\nMemory citations are checked against files Claude actually had, and the counts recorded.\n\n**What**\n\nWhen a memory citation tag is stripped from assistant output, the event now reports how many of the cited filenames matched known memory files, how many had been read or written, and how many were injected into the prompt, surfaced, or only listed in an index.\n\n**Details**\n\n- Filenames come from the tag's filenames attribute and are capped per block.\n\n**Evidence**\n\n`cited_injected_body_count`\n\n- Area: Memory\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 4\/5"}