diff --git a/.claude/memory/feedback_rmm_dev_is_mike.md b/.claude/memory/feedback_rmm_dev_is_mike.md
index 9eec55f..e54a3c9 100644
--- a/.claude/memory/feedback_rmm_dev_is_mike.md
+++ b/.claude/memory/feedback_rmm_dev_is_mike.md
@@ -11,4 +11,5 @@ GuruRMM development — code, bugs, the roadmap, architecture — is **Mike's**
 **How to apply:**
 - RMM bug/dev/roadmap item → it's Mike's. Since Mike is usually the user, just surface it to him directly; don't send a coord note to anyone (a note to yourself is pointless, and Howard isn't the owner).
 - **GuruScan** (`projects/msp-tools/guru-scan/`) IS Howard's project — coord notes about GuruScan correctly go to Howard. Don't conflate GuruScan with GuruRMM just because the names rhyme or GuruScan may integrate with RMM.
+- **Leave GuruScan alone until Howard asks.** Do NOT proactively review, audit, or modify its code — even after a sync pulls in big GuruScan changes. Wait for Howard to explicitly request a review. (Mike, 2026-05-27, after I offered to review Howard's GuruScan.psm1 refactor unprompted.)
 - Before sending any coord note to a teammate, check whose domain the work actually sits in. See [[user_howard]].