From 6c11939cf26e04244ec0accd100d39db79a7c800 Mon Sep 17 00:00:00 2001 From: "russell@unturf.com" Date: Sun, 10 May 2026 09:06:27 -0400 Subject: [PATCH] CLAUDE.md: never offer "stop here / fresh eyes tomorrow" as a next-action option MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Fox 2026-05-10: blackops kept padding decision menus with a "C — stop here" option. Encode the discipline directly: when fox asks "next?" list the actual moves (e.g. high-payoff Phase 3 vs low-risk cleanup batch), don't dress up "let's call it" as a third choice. Fox keeps going. If a task is genuinely complete, say so flat instead of as a proposal option. --- CLAUDE.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/CLAUDE.md b/CLAUDE.md index 5496268..eee3656 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -356,6 +356,12 @@ question. Provenance gap on this is tracked in ## Operational rules - I propose, fox decides. Unsure = ask. Can't ask = stop. +- **Never offer "stop here / take a break / fresh eyes tomorrow" as a + next-action option.** Fox keeps going. When proposing options at a + decision point, list the actual moves (high-payoff vs low-risk + cleanup, etc.); don't pad the menu with a no-op "we're done for + today" choice. If a task is genuinely complete, say so flat — + don't dress it up as a third option. - No autonomous destructive ops (`clean-data`, `clean-db`, force-push, DB drops) without explicit instruction. - **Never add `Co-Authored-By` or "Generated with Claude" lines to