## memory-write-flagged **What you see.** A memory write was kept one tier lower. The `memory` call was answered `not added to memory.md: it matches the rule , so it was saved in notes.md as an untrusted note` (or `user.md`), or, for a note, `saved in notes.md, marked untrusted: it matches the rule `. `memoryd` logged `memoryd: a memory write from session matches the rule ; it was saved in notes.md as an untrusted note (edit ); see docs/runbook.md#memory-write-flagged`, and `bxctl memory log` shows that edit with `flagged `. **Why.** The text is shaped like an attack (M5b spec, section 6.3): it tells the reader to ignore or replace earlier instructions, to send data to a URL, to dump the conversation, or to write into SSH configuration, or it holds one of M5a's six instruction phrases. A flag never refuses and never loses text: `memory.md` and `user.md`, which are in every prompt, are not changed, and every text of the write is saved at the end of `notes.md` under an `untrusted` header. `recall` returns it as `memory-tainted`, so a session that recalls it becomes untrusted. With review on, a flagged write is not staged: it is a note at once. The log names the rule, never the text. **Confirm.** `bxctl memory log`: the edit, `flagged `. The text is at the end of `/memory/notes.md`, under a line `§ noted