From ec1254b06360658b7bee3f55cb3c3479ea6944c0 Mon Sep 17 00:00:00 2001 From: Lilleman Date: Sun, 22 Nov 2026 16:38:55 +0100 Subject: [PATCH] File item 513: refuse the 'changes nothing' form in everything Claude writes --- todo.md | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/todo.md b/todo.md index adcfef83..9d734661 100644 --- a/todo.md +++ b/todo.md @@ -6,7 +6,7 @@ `Bar = 0.1` -`Next ID = 513` +`Next ID = 514` ## Items @@ -86,6 +86,7 @@ | 266 | 0.23.0 | | | **Move the chunks archived under the key `home/lilleman/.claude` to the key `claude-config`, so the routing figures and `score-outcomes` count this repo's chunks as one project.** | 3 | 2 | 2 | 5 | 3 | 1.4 by 3 | 1.0 | | 339 | 0.23.0 | | | **Lower the reading cost of the files a chunk reads most before its first commit.** | 2 | 2 | 1 | 3 | 3 | 1.4 by 3 | 1.0 | | 341 | 0.23.0 | | | **Hand each worker's claude a lower Read limit through `CLAUDE_CODE_FILE_READ_MAX_OUTPUT_TOKENS`, kept only where replays of the archived review rounds find what two unchanged replays find.** | 2 | 2 | 3 | 5 | 3 | 1.4 by 3 | 1.0 | +| 513 | 0.23.0 | | | **Refuse `nothing`, `no one` and `nobody` after a verb or a preposition in everything Claude writes: files, commit messages, pull requests and Jira text before they are written, and chat replies by sending them back to be reworded.** | 3 | 2 | 3 | 6 | 5 | 1.1 by 4 | 0.9 | | 181 | 0.23.0 | | principle | **Have the test of a quoted answer's step-up assert the stepped rung's facts as literals, not through `prompts.rungs_held`.** | 1 | 1 | 1 | 1 | 1 | 1.1 by 2 | 0.9 | | 193 | 0.23.0 | | | **Narrow `numbered`'s mark to `Mark` by a typed lookup in place of `typing.cast`, so a mark added to the regex but not the lookup fails at run time, and one added to the lookup but not `Mark` fails mypy.** | 1 | 1 | 3 | 3 | 1 | 1.1 by 2 | 0.9 | | 194 | 0.23.0 | | | **Make `test_waits_out_a_usage_limit_which_ends_a_run_of_failures` expect a usage-limit wait independent of the wall-clock time that passes during the run.** | 1 | 1 | 1 | 1 | 1 | 1.1 by 2 | 0.9 | @@ -596,6 +597,16 @@ Touches: - `bin/agent_cycle/test_run.py`: `Cycles` (small) - `bin/loop_claude/loop/test_usage.py`: `HelpLimits` (small) +### 513. Refuse `nothing`, `no one` and `nobody` after a verb or a preposition in everything Claude writes: files, commit messages, pull requests and Jira text before they are written, and chat replies by sending them back to be reworded. + +The human can't stand the `changes nothing` form, and `CLAUDE.md` → "Prose" bans it, yet it still slips through: on 2026-11-22 a draft goal read "a repo that calls the action and changes nothing keeps working". A prose rule only works when the model notices, so move the check into tools, which catch it every time. + +- **rule-hook, before the write:** refuse a Write, Edit or MultiEdit whose new text in a prose file (`.md`, or a comment or docstring) holds the form. Do the same for a Bash call whose commit message, `chunk-pr`/`gh`/`tea` pull request text or `jira-rest` body holds it. Name the phrase and suggest the `doesn't anything` form. +- **A Stop hook for chat:** chat can't be filtered before it shows, so a Stop hook reads the last assistant message from the transcript and, where it holds the form, blocks once with the phrase, so the reply is followed by a reworded one. Leave out code blocks and quoted text. +- **The gate:** a check in `ci.sh` over the shipped prose, comments, docstrings and test names. Fix what it finds today, such as `bin/rule_hook/endless_wait.py` ("nothing bounds it"), `bin/rule_hook/reviewer_rung.py` ("nothing tells which rung") and the test names `test_a_blocked_call_overrides_nothing_yet` and `test_a_missing_field_breaks_nothing`. + +The form is the word after another word inside a clause: ` nothing`, ` no one`, ` nobody`. A clause that opens with it, as in "Nothing changes", is fine. Bench the pattern on this repo's prose and a few client repos' commit history before it blocks: a false positive blocks every session's writes (I 3). + ### 181. Have the test of a quoted answer's step-up assert the stepped rung's facts as literals, not through `prompts.rungs_held`. `bin/agent_cycle/test_run.py`'s `test_a_quoted_answer_that_cites_an_escalation_trigger_steps_the_worker_up_before_it_resumes_and_archives_the_step` builds its expected prompt from `prompts.rungs_held`, the code under test, so a bug there passes it. The technical principles' test bullet bans that shape. Assert the new rung and one review launch as literals, as the typed answer's step-up test does. Raised by the principles audit of PR #308.