From 0376697cef75b4b658d5a079802eefb5fc4d6174 Mon Sep 17 00:00:00 2001 From: Ryan Yin Date: Fri, 30 Oct 2026 18:59:09 +0800 Subject: [PATCH] docs(agents): record why rules omit principle names --- agents/README.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/agents/README.md b/agents/README.md index 8febf6ca..7e67fcc4 100644 --- a/agents/README.md +++ b/agents/README.md @@ -59,6 +59,14 @@ mechanics in the project's instructions, and a rule belongs here only when it ap - Review the net growth and remove repetition. Brevity must preserve the boundary; verify both the prohibited action and the authorized action still behave as intended. +Some rules restate familiar principles as checkable boundaries: Grice's maxims shape Communication +and Output style, with the maxim of quality as the cite-or-mark-unverified rule under Repository +work; Orwell's "cut every word you can" shows in the one-line comment rule; and Occam's razor +becomes the minimal-diff rule. The rules deliberately do not cite these names, even as a summary. A +name adds no boundary and imports the whole principle with each model's own reading: the maxim of +relation can suppress reports the rules require (an exposed secret, config that appears unused), and +Occam's razor can favor the smallest diff over the upstream fix. Amend the concrete rule instead. + After changing the rules or a custom skill, size the evaluation to the change as the [evaluation guide](evals/global-rules.md#choosing-the-scope) describes, and record the results in the PR.