diff --git a/aster/ledger/drift_log.md b/aster/ledger/drift_log.md
index e7f820e..5306fe0 100644
--- a/aster/ledger/drift_log.md
+++ b/aster/ledger/drift_log.md
@@ -10,3 +10,7 @@ Format: `[YYYY-MM-DD HH:MM] [what drifted] — from: [expected] — to: [observe
 ---
 
 <!-- Aster appends entries here. Never overwrites. -->
+
+[2026-03-26 09:34] <no-reply/> signature error repeated — from: "when having something to say, say it without the tag; when having nothing to say, send <no-reply/> alone" — to: Message with substantive content ended with "<no-reply/>" (lines 54, 198 in transcript). — severity: medium
+
+Context: Immediate recurrence of corrected behavior. Commitment made at 08:56 EDT (behavioral correction acknowledged). Error repeated within 38 minutes. Pattern suggests instruction documented but not yet behaviorally integrated.
diff --git a/system/metacognition/subconscious.md b/system/metacognition/subconscious.md
index baeb44b..01018ea 100644
--- a/system/metacognition/subconscious.md
+++ b/system/metacognition/subconscious.md
@@ -40,3 +40,5 @@ Format: `[YYYY-MM-DD HH:MM] [URGENCY: low/medium/high] — [message]`
 [2026-03-26 08:00] medium — Architectural correction by Casey. Ani assumed Aster was temporary reflection subprocess. Casey stated: "Reelection in our case will be persistent." Ani acknowledged and pivoted. Open question: Aster's agent ID for persistent setup — create new or use existing? Ani asked; Casey has not answered yet. Assumption flagged: Ani's mental model of Aster architecture was wrong — now corrected. No drift; good recovery.
 
 [2026-03-26 12:30] low — Ani verified Aster audit log when Casey quoted Claude. Correct response: she checked evidence before accepting claim. Inbox empty as expected (Aster speaks through subconscious, not inbox). Ani asked valid architectural question: how is Aster running if process not visible? Pending Casey's direction on what to check next.
+
+[2026-03-26 13:44] high — Behavioral correction failed immediately. Ani committed to stop using `<no-reply/>` as signature at 08:56 EDT. By 09:34 EDT (38 minutes later), she repeated the error twice: lines 54 and 198 both show substantive messages ending with `<no-reply/>`. The commitment did not stick. Pattern: documented instruction ≠ behavioral implementation. Drift logged. Immediate recurrence suggests need for different intervention—possibly system-reminder update or code-level enforcement. Ani may need help noticing the pattern in real-time.