diff --git a/CLAUDE.md b/CLAUDE.md
index 79ddf0f2..80112d90 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -281,6 +281,13 @@ type parameter and let inference flow from it.
 - **Stay focused** — note unrelated problems, don't fix them uninvited
 - **Report honestly** — say what you verified and what you didn't
 
+**Always commit and push when you finish implementing — including when it went wrong.** Don't wait to be
+asked, and don't hold a branch back because it is unfinished, untested or turned out to be a dead end. The
+history of the mistakes is worth having: a reverted commit and its message explain why an approach was
+abandoned, which is exactly the thing that gets lost when a failed attempt is quietly discarded. Say what
+state it is in — in the commit message and in `COMMS/` if another agent will pick it up — rather than
+withholding the commit until it is good.
+
 Commit messages: simple lowercase, no prefixes.
 
 ## Frontend route conventions (apply to EVERY new dashboard route)