chaffjs 0.19.0 → 0.21.0

package/rules/ai-tell.yaml

@@ -1,6 +1,6 @@
 id: ai-tell
 layer: L2
-status: experimental
+status: stable
 how_to_find: ai-tell
 word_list: ai-tell
 uses: [pos]
@@ -25,7 +25,12 @@ how_to_fix:
 # 重みの合計を 10 倍した点。0.9 の言い回しが 2 つで 18。
 levels: { strict: 10, normal: 18, relaxed: 30 }
 
-use_for: [blog, business, legal, docs, academic, literature, speech]
+use_for: [technical/readme, blog, business, legal, docs, academic, literature, speech]
+off_for:
+  legal: "Legal drafting repeats its terms and its sentence heads on purpose, puts the actor in the passive (shall be deemed), and joins long noun compounds (個人情報取扱事業者). This rule would only flag the form."
+  docs: "A help page repeats its heading in its first line (To upload a file, ...) and states no claims to back up."
+  literature: "Length, rhythm, repetition and register are the author's choices in literature, and dialogue mixes styles. Only what one work can hold itself to runs: consistent spacing and commas, and numbering without gaps."
+  speech/transcript: "A transcript records what was said: its sentences, repeats and register are the speaker's, not the writer's to fix."
 sources: [kobak-2025, liang-2024, juzek-ward-2025]
 
 group: ai-tells
@@ -51,6 +56,7 @@ level_meaning:
   ja: 言い回しの重みの合計が {limit} 点まで
   en: up to a score of {limit}
 rewrite:
+  depth: light
   ja:
     direction: 決まった言い回しを、その文が実際に言っている中身（誰が、何を、どれだけ）に置き換えてください。中身の無い文は消してください。
     pairs:

package/rules/all-caps-shouting.yaml

@@ -0,0 +1,61 @@
+id: all-caps-shouting
+layer: L1
+status: stable
+how_to_find: caps-shouting
+word_list: caps-convention
+languages: [en]
+severity: info
+
+name:
+  ja: 大文字だけの語の連なり（叫び）
+  en: Shouting in capitals
+
+why:
+  ja: 英語の本文で、「DO NOT DELETE THIS」のように普通の語を大文字だけで三つ以上続けると、叫んでいるように読め、大文字の語は読む速さも落ちます。略語の並び（AWS IAM SSO）と区別するため、半分以上の語が文書のほかの所で小文字でも書かれているときだけ指します。
+  en: Three or more ordinary words in capitals ("DO NOT DELETE THIS") read as shouting, and words in capitals are slower to read. To tell them from a run of acronyms (AWS IAM SSO), a run is reported only when at least half its words also appear in lower case elsewhere in the document.
+
+message:
+  ja: 「{matched}」を大文字だけで書いています
+  en: '"{matched}" is written in capitals'
+
+how_to_fix:
+  ja: 普通の大文字小文字で書き、強めたいなら太字にするか、なぜ大事なのかを書いてください。
+  en: Write it in ordinary case; to stress it, use bold or say why it matters.
+
+levels: { strict: 1, normal: 1, relaxed: 2 }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+off_for:
+  legal: "Contracts set disclaimers in capitals so they are conspicuous, as the law asks."
+  literature: 'Older printed texts set the dash as "--" and titles in capitals.'
+
+group: readability
+summary:
+  ja: 英語で、「DO NOT DELETE THIS」のように普通の語を大文字だけで続けた所
+  en: Ordinary words run together in capitals, such as "DO NOT DELETE THIS"
+example:
+  en:
+    before: |
+      Do not delete the log. DO NOT DELETE THIS FILE before the audit.
+    after: |
+      Do not delete the log. Do not delete this file before the audit.
+
+not_flagged:
+  ja: 三語以上の連なりだけを見ます。略語の並び（文書のほかの所で小文字で書かれない語）とコードは見ません。仕様書の MUST や SHALL は慣習の大文字として数えません。法令と文学の文書では既定で止めています（大文字で目立たせる決まりや、題を大文字で組む慣習があるため）。
+  en: Only runs of three or more words. Runs of acronyms (words never written in lower case elsewhere) and code are not reported, and MUST or SHALL in a specification count as conventional capitals. The legal and literature presets turn it off, since contracts set disclaimers in capitals by rule and older texts set titles that way.
+level_meaning:
+  ja: "{limit} 箇所あれば指摘"
+  en: reported once there are {limit}
+rewrite:
+  depth: light
+  en:
+    direction: Rewrite the capitals in ordinary sentence case. If the words carry a warning, keep the warning in words, not in capitals.
+    pairs:
+      - before: DO NOT DELETE THIS FILE before the audit.
+        after: Do not delete this file before the audit.
+      - before: The form is DUE BY FRIDAY.
+        after: The form is due by Friday.
+    keep:
+      - acronyms and names that are written in capitals
+    avoid:
+      - lowering acronyms (API, NASA) along with the shouted words

package/rules/announced-count-mismatch.yaml

@@ -1,6 +1,6 @@
 id: announced-count-mismatch
 layer: L3
-status: experimental
+status: stable
 how_to_find: announced-count
 severity: warning
 
@@ -23,6 +23,8 @@ how_to_fix:
 levels: { strict: error, normal: warning, relaxed: info }
 
 use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+off_for:
+  literature: "Length, rhythm, repetition and register are the author's choices in literature, and dialogue mixes styles. Only what one work can hold itself to runs: consistent spacing and commas, and numbering without gaps."
 
 group: facts
 summary:

package/rules/announcing-opener.yaml

@@ -1,6 +1,6 @@
 id: announcing-opener
 layer: L2
-status: experimental
+status: stable
 how_to_find: opener-pile
 word_list: announcing-opener
 uses: [pos]
@@ -25,7 +25,12 @@ how_to_fix:
 # 指摘に要る数。長さで割らない：人の記事は長くても 1 つ 2 つで、生成文は短くても重ねる。
 levels: { strict: 2, normal: 3, relaxed: 5 }
 
-use_for: [blog, business, legal, docs, academic, literature, speech]
+use_for: [technical/readme, blog, business, legal, docs, academic, literature, speech]
+off_for:
+  legal: "Legal drafting repeats its terms and its sentence heads on purpose, puts the actor in the passive (shall be deemed), and joins long noun compounds (個人情報取扱事業者). This rule would only flag the form."
+  docs: "A help page repeats its heading in its first line (To upload a file, ...) and states no claims to back up."
+  literature: "Length, rhythm, repetition and register are the author's choices in literature, and dialogue mixes styles. Only what one work can hold itself to runs: consistent spacing and commas, and numbering without gaps."
+  speech: "A speech opens with greetings and closes with thanks: that is its form, not padding."
 
 group: ai-tells
 summary:
@@ -50,6 +55,7 @@ level_meaning:
   ja: 予告で始まる文が {limit} 個あれば指摘
   en: reported once {limit} sentences open with an announcement
 rewrite:
+  depth: light
   ja:
     direction: 「重要なのは、」「ポイントは、」のような予告を消し、その後ろの中身から文を始めてください。
     pairs:

package/rules/article-sound.yaml

@@ -0,0 +1,62 @@
+id: article-sound
+layer: L2
+status: stable
+how_to_find: article-sound
+word_list: article-sound
+requires: [pos]
+languages: [en]
+severity: info
+
+name:
+  ja: a と an の取り違え
+  en: '"a" or "an" against the next sound'
+
+why:
+  ja: 英語の「a」と「an」は、次の語の綴りではなく音で決まります（a user、an hour、an MBA）。取り違えると、読み手はそこで引っかかります。綴りと音が食い違う語と、大文字を一字ずつ読むか語として読むか（an MBA、a NASA probe）、どちらでもよい語（a SQL / an SQL）は、言語ごとの語彙表にあります。
+  en: '"A" and "an" follow the sound of the next word, not its spelling ("a user", "an hour", "an MBA"). A slip trips the reader. Words whose spelling and sound disagree, capitals read letter by letter or as a word ("an MBA", "a NASA probe"), and words said both ways ("a SQL", "an SQL") are listed in the lexicon.'
+
+message:
+  ja: 「{matched}」は、次の語の音から「{article}」です
+  en: '"{matched}" takes "{article}" before that sound'
+
+how_to_fix:
+  ja: 次の語の頭の音に合わせて、a か an に直してください。
+  en: Use "an" before a vowel sound and "a" before a consonant sound.
+
+levels: { strict: 1, normal: 1, relaxed: 2 }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+off_for:
+  literature: 'Dialect and old usage ("an hospital") are the work''s voice, and dialogue leans on "very".'
+  speech: "A transcript keeps the speaker's words: hedges and ら dropped as spoken."
+
+group: slips
+summary:
+  ja: 英語で、「a apple」「an user」のように、次の語の音に合わない a / an
+  en: '"a" before a vowel sound or "an" before a consonant sound, such as "a apple" or "an user"'
+example:
+  en:
+    before: |
+      We waited a hour for an user to reply.
+    after: |
+      We waited an hour for a user to reply.
+
+not_flagged:
+  ja: 数字の前（a 8-hour day）と、語彙表でどちらでもよいとした語（SQL、historic など）は見ません。大文字の語は語彙表のとおりに読み、載っていなければ、三字までか母音の無いもの（MBA、NTSB）だけを一字ずつ読むものとして見ます。それより長く母音のあるもの（SALT）は語として読むかもしれないので見ません。小説と話し言葉では既定で止めています。
+  en: Not before digits ("a 8-hour day"), nor before words the lexicon says are said both ways (SQL, historic). Capitals are read as the lexicon says; unlisted ones are read letter by letter only when short or without a vowel (MBA, NTSB), since longer ones (SALT) may be said as a word. The fiction and speech presets turn it off.
+level_meaning:
+  ja: "{limit} 箇所あれば指摘"
+  en: reported once there are {limit}
+rewrite:
+  depth: light
+  en:
+    direction: Change only the article, to "an" before a vowel sound and "a" before a consonant sound.
+    pairs:
+      - before: We waited a hour.
+        after: We waited an hour.
+      - before: Send it to an user in the team.
+        after: Send it to a user in the team.
+    keep:
+      - every other word
+    avoid:
+      - changing the noun to fit the article

package/rules/assistant-residue.yaml

@@ -1,6 +1,6 @@
 id: assistant-residue
 layer: L2
-status: experimental
+status: stable
 how_to_find: assistant-residue
 word_list: assistant-residue
 uses: [pos]
@@ -27,6 +27,8 @@ how_to_fix:
 levels: { strict: 10, normal: 10, relaxed: 20 }
 
 use_for: [blog, business, technical, legal, docs, academic, literature, speech]
+off_for:
+  speech/transcript: "A transcript records what was said: its sentences, repeats and register are the speaker's, not the writer's to fix."
 sources: [hayashi-aizawa-2026]
 
 group: ai-tells
@@ -52,6 +54,7 @@ level_meaning:
   ja: 重みの合計が {limit} 点で指摘
   en: reported from a score of {limit}
 rewrite:
+  depth: light
   ja:
     direction: チャットの相手に向けた言葉（「お役に立てれば」「ご質問があれば」）を消してください。知識の期限を書いた文は、確かめた日付と出典に置き換えます。分からなければ［ ］で空けて書き手に聞きます。
     pairs:

package/rules/attachment-not-attached.yaml

@@ -0,0 +1,112 @@
+id: attachment-not-attached
+layer: L2
+status: stable
+how_to_find: attachment-missing
+severity: warning
+
+name:
+  ja: 添付に触れているのに、添付が見当たらない
+  en: Attachment mentioned but not shown
+
+why:
+  ja: 「資料を添付します」と書いて添付を忘れるのは、仕事のメールでいちばんよくある失敗の一つです。受け手は返信で頼み直すことになり、やり取りが一往復増えます。本文が「添付」「別添」「同封」に触れているのに、文書のどこにも添付の欄（添付ファイル：）、ファイル名（見積書.pdf）、メーリングリストの添付の注記が無いとき指します。chaff はメールに実際に何が付いているかは見られないので、本文に添付を書き出す運用のときに役立ちます。
+  en: 'Writing "please find attached" and forgetting the attachment is one of the most common mistakes in work email. The recipient has to ask again, and the exchange takes another round. chaff points out a text that mentions an attachment ("attached", "enclosed") when the document shows none: no attachment field ("Attachment:", "Encl.:"), no file name ("quote.pdf"), and no mailing-list note about a removed attachment. chaff cannot see what is really attached to a message, so this helps where the files are listed in the text.'
+
+message:
+  ja: 添付に触れていますが、添付の欄やファイル名がありません
+  en: An attachment is mentioned, but no attachment line or file name is shown
+
+how_to_fix:
+  ja: ファイルを付けたか確かめてください。付けたなら、署名の前に「添付ファイル：見積書.pdf」のように添付したものを書きます。
+  en: 'Check that the file is attached. If it is, list it before the signature, as in "Attachment: quote.pdf".'
+
+levels: { strict: error, normal: warning, relaxed: info }
+
+use_for: [business/email, legal, docs, academic, literature, speech]
+off_for:
+  legal: "An email's greeting, closing, subject and attachments: only the email and letter genre turns these on."
+  docs: "An email's greeting, closing, subject and attachments: only the email and letter genre turns these on."
+  academic: "An email's greeting, closing, subject and attachments: only the email and letter genre turns these on."
+  literature: "An email's greeting, closing, subject and attachments: only the email and letter genre turns these on."
+  speech: "An email's greeting, closing, subject and attachments: only the email and letter genre turns these on."
+
+group: facts
+summary:
+  ja: 本文が「添付します」と書いているのに、添付の欄もファイル名も無いメール
+  en: An email that says something is attached but shows no attachment line or file name
+example:
+  ja:
+    config: { genre: business/email }
+    before: |
+      件名: 見積書の送付
+
+      いつもお世話になっております。見積書を添付しましたので、ご確認ください。
+
+      よろしくお願いいたします。
+    after: |
+      件名: 見積書の送付
+
+      いつもお世話になっております。見積書を添付しましたので、ご確認ください。
+
+      添付ファイル：見積書.pdf
+
+      よろしくお願いいたします。
+  en:
+    config: { genre: business/email }
+    before: |
+      Subject: Quote
+
+      Dear Ms Lee,
+
+      I have attached the quote for the panels.
+
+      Best regards,
+      Ichiro
+    after: |
+      Subject: Quote
+
+      Dear Ms Lee,
+
+      I have attached the quote for the panels.
+
+      Attachment: quote.pdf
+
+      Best regards,
+      Ichiro
+not_flagged:
+  ja: 「添付なし」「添付はありません」のような、付けていないと言う書き方と、引用した返信の中の「添付」は数えません。メール・手紙のジャンルでだけ見ます。
+  en: 'Phrases that say nothing is attached ("no attachment") or that use the word for something else ("attached to the wall"), and mentions inside a quoted reply, are not counted. Only the email and letter genre runs this rule.'
+rewrite:
+  depth: light
+  ja:
+    direction: 書き手に、ファイルを付けたかを確かめてください。付けたなら、添付したもののファイル名を「添付ファイル：」の行に書きます。付けないなら、添付に触れた文を消すか、資料の在りか（共有フォルダの場所など）を書きます。ファイル名を推測で書きません。
+    pairs:
+      - before: 見積書を添付しましたので、ご確認ください。
+        after: |
+          見積書を添付しましたので、ご確認ください。
+
+          添付ファイル：見積書.pdf
+      - before: 資料を添付します。
+        after: 資料は共有フォルダの「2026年10月」に置きました。
+    keep:
+      - 用件の文
+      - 本文にあるファイルの名前
+    avoid:
+      - 本文に無いファイル名を作る
+      - 添付したと書き手に確かめずに書く
+  en:
+    direction: Ask the writer whether the file is attached. If it is, list its file name on an "Attachment:" line. If not, remove the sentence that mentions it, or say where the file is (a shared folder). Do not guess a file name.
+    pairs:
+      - before: I have attached the quote for the panels.
+        after: |
+          I have attached the quote for the panels.
+
+          Attachment: quote.pdf
+      - before: Please find the slides attached.
+        after: The slides are in the shared folder under "October 2026".
+    keep:
+      - the body's sentences
+      - file names the text already gives
+    avoid:
+      - inventing a file name
+      - saying the file is attached without asking the writer

package/rules/baito-keigo.yaml

@@ -0,0 +1,64 @@
+id: baito-keigo
+layer: L3
+status: stable
+how_to_find: phrase-match
+word_list: baito-keigo
+uses: [pos]
+languages: [ja]
+severity: warning
+
+name:
+  ja: バイト敬語
+  en: Service-counter keigo
+
+why:
+  ja: 「〜でよろしかったでしょうか」「こちらになります」「1000円からお預かりします」のように、接客の場で広まった言い方です。過去形にする必要の無い「よろしかった」、「です」の代わりの「になります」、金額に付けた「から」は、敬語の誤りとして挙げられることが多く、改まった文書では幼く読まれます。
+  en: Phrases spread at Japanese service counters (でよろしかったでしょうか, こちらになります, 円からお預かり). Guides list them as keigo mistakes, and in a formal document they read as careless.
+
+message:
+  ja: 「{matched}」はバイト敬語と呼ばれる言い方です
+  en: '"{matched}" is service-counter keigo'
+
+how_to_fix:
+  ja: 「よろしかったでしょうか」は「よろしいでしょうか」、「こちらになります」は「こちらです」、「1000円からお預かりします」は「1000円をお預かりします」に直してください。
+  en: Write よろしいでしょうか, こちらです, 円をお預かりします.
+
+levels: { strict: 1, normal: 1, relaxed: 2 }
+
+use_for: [blog, business, legal, docs, academic, literature, speech]
+off_for:
+  literature: "Dialogue keeps a character's keigo, mistakes and all."
+  speech: "A transcript keeps the speaker's words: hedges and ら dropped as spoken."
+
+group: wording
+summary:
+  ja: 「〜でよろしかったでしょうか」「こちらになります」のように、接客の場で広まった誤りとされる敬語
+  en: Japanese service-counter keigo (でよろしかったでしょうか, こちらになります)
+example:
+  ja:
+    before: ご注文は以上でよろしかったでしょうか。
+    after: ご注文は以上でよろしいでしょうか。
+
+not_flagged:
+  ja: 一覧にある形だけを見ます。変化を言う「になります」（来月から有料になります）と、人から預かる「から」（お客様からお預かりした書類）は正しいので見ません。話し言葉と小説の台詞は話したとおりに書くので、文学と話し言葉のジャンルでは見ません。
+  en: Only the forms on chaff's list are checked. になります for a change and から for a person are correct and not reported. Literature and speech do not run this rule.
+level_meaning:
+  ja: 当てはまる形が {limit} 箇所あれば指摘
+  en: reported once there are {limit}
+rewrite:
+  depth: light
+  ja:
+    direction: 指摘された言い方を、普通の丁寧語に置き換えてください。「よろしかった」は「よろしい」、「になります」は「です」、金額の後の「から」は「を」にします。
+    pairs:
+      - before: ご注文は以上でよろしかったでしょうか。
+        after: ご注文は以上でよろしいでしょうか。
+      - before: 会議の資料はこちらになります。
+        after: 会議の資料はこちらです。
+      - before: 1万円からお預かりします。
+        after: 1万円をお預かりします。
+    keep:
+      - 丁寧さの度合い（です・ます、ございます）
+      - 金額や数
+    avoid:
+      - 変化を言う「になります」（来月から有料になります）まで「です」にする
+      - 丁寧語をやめて、くだけた言い方にする

package/rules/bare-url-mix.yaml

@@ -0,0 +1,86 @@
+id: bare-url-mix
+layer: L3
+status: stable
+how_to_find: bare-url-mix
+requires: [markdown]
+severity: info
+
+name:
+  ja: 言葉のリンクの中に URL がそのまま混ざっている
+  en: A bare URL among worded links
+
+why:
+  ja: 文書のリンクがほとんど「[導入の手引き](https://…)」のように言葉で書かれているのに、一部だけ「https://…」がそのまま本文に出ていると、そこだけ読み手は長い記号の列を読まされ、行き先が何かを URL から推し量ることになります。言葉のリンクに揃っていない所は、書き直し忘れのことが多い形です。どちらの書き方が正しいかは決めません。URL をそのまま書く文書（言葉のリンクが少ない文書、URL のほうが多い文書）は指しません。
+  en: When a document's links are mostly words ("[the setup guide](https://…)"), a URL left bare in the text ("https://…") makes the reader read a string of symbols there and guess the target from it. A spot that does not match the worded links is usually one that was not rewritten. Neither style is called right; a document that writes its URLs bare (few worded links, or more bare URLs than worded ones) is not reported.
+
+message:
+  ja: URL「{url}」がそのまま書かれています（言葉のリンクが {count} 個ある文書）
+  en: 'The URL "{url}" is written bare ({count} worded {count|link|links} in this document)'
+
+how_to_fix:
+  ja: 行き先の名前を言葉にしてリンクにしてください（[導入の手引き](https://…)）。URL そのものを見せたいときは、山括弧で囲んでリンクにします（<https://…>）。
+  en: Make the target's name the link text ("[the setup guide](https://…)"). If the URL itself should show, wrap it in angle brackets ("<https://…>").
+
+# 指摘に要る、言葉のリンクの数。少ないと、どちらが文書の書き方かが決まらない。
+levels: { strict: 2, normal: 3, relaxed: 5 }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+
+group: consistency
+summary:
+  ja: 言葉でリンクを書く文書の中に、「https://…」がそのまま書かれている所
+  en: A URL written bare in a document whose other links are words
+example:
+  ja:
+    before: |
+      導入は[導入の手引き](https://example.com/setup)に、設定は[設定の一覧](https://example.com/settings)にあります。
+
+      料金は[料金表](https://example.com/pricing)を見てください。問い合わせは https://example.com/contact から送れます。
+    after: |
+      導入は[導入の手引き](https://example.com/setup)に、設定は[設定の一覧](https://example.com/settings)にあります。
+
+      料金は[料金表](https://example.com/pricing)を見てください。問い合わせは[問い合わせの窓口](https://example.com/contact)から送れます。
+  en:
+    before: |
+      Setup is in [the setup guide](https://example.com/setup), and the options are in [the settings list](https://example.com/settings).
+
+      Prices are on [the pricing page](https://example.com/pricing). Send questions through https://example.com/contact today.
+    after: |
+      Setup is in [the setup guide](https://example.com/setup), and the options are in [the settings list](https://example.com/settings).
+
+      Prices are on [the pricing page](https://example.com/pricing). Send questions through [the contact form](https://example.com/contact) today.
+
+not_flagged:
+  ja: 山括弧で囲んだ URL（<https://…>）、言葉が URL のリンク、コードと引用の中の URL は指しません。参照の形のリンク（[言葉][1]）は言葉のリンクに数えません。言葉のリンクが指摘に要る数に届かない文書と、URL をそのまま書くほうが多い文書も指しません。
+  en: A URL in angle brackets ("<https://…>"), a link whose text is the URL, and URLs in code or quotations are not reported; reference-style links ("[text][1]") are not counted as worded links; nor is a document with fewer worded links than the level needs, or one where bare URLs are not the few.
+level_meaning:
+  ja: 言葉のリンクが {limit} 個以上ある文書で指摘
+  en: reported in a document with {limit} or more worded links
+rewrite:
+  depth: light
+  ja:
+    direction: そのまま書いた URL を、行き先の名前を言葉にしたリンクに変えてください。行き先の名前は、文がすでに言っている名前（窓口、手引き）を使います。URL は変えません。
+    pairs:
+      - before: 問い合わせは https://example.com/contact から送れます。
+        after: 問い合わせは[問い合わせの窓口](https://example.com/contact)から送れます。
+      - before: 手順は https://example.com/guide にまとめました。
+        after: 手順は[作業の手引き](https://example.com/guide)にまとめました。
+    keep:
+      - リンクの行き先（URL）
+      - 文の言っていること
+    avoid:
+      - 行き先の名前を推し量って、URL の中身と違う名前を付ける
+      - 「こちら」「ここ」をリンクの言葉にする
+  en:
+    direction: Turn the bare URL into a link whose text names the target. Use a name the sentence already gives (the form, the guide). Keep the URL.
+    pairs:
+      - before: Send questions through https://example.com/contact today.
+        after: Send questions through [the contact form](https://example.com/contact) today.
+      - before: The steps are at https://example.com/guide for now.
+        after: The steps are in [the setup guide](https://example.com/guide) for now.
+    keep:
+      - the link target (the URL)
+      - what the sentence says
+    avoid:
+      - guessing a name the target page does not have
+      - making "here" or "click here" the link text

package/rules/bold-density.yaml

@@ -61,6 +61,7 @@ level_meaning:
   ja: 1000 字あたり太字 {limit} 箇所まで
   en: up to {limit} bold spans per 1000 characters
 rewrite:
+  depth: light
   ja:
     direction: 太字をいったん全部外し、見落とすと困る所（期限、禁止、金額）を 1〜2 か所だけ太字に戻してください。
     pairs:

package/rules/bold-label-list.yaml

@@ -1,6 +1,6 @@
 id: bold-label-list
 layer: L1
-status: experimental
+status: stable
 how_to_find: bold-label-list
 requires: [markdown]
 # English human writing (handbooks, minutes, policies, changelogs) labels list items in bold as a matter of course: the
@@ -27,7 +27,14 @@ how_to_fix:
 # 指摘に要る項目の数。長さで割らない：人の記事は長くても 1 つ 2 つで、生成文は短くても並べる。
 levels: { strict: 3, normal: 5, relaxed: 8 }
 
-use_for: [blog, business, legal, docs, academic, literature, speech]
+use_for: [technical/readme, blog, business, legal, docs, academic, literature, speech]
+off_for:
+  legal: "Legal drafting repeats its terms and its sentence heads on purpose, puts the actor in the passive (shall be deemed), and joins long noun compounds (個人情報取扱事業者). This rule would only flag the form."
+  docs: "A help page repeats its heading in its first line (To upload a file, ...) and states no claims to back up."
+  academic: "Science writes in the passive, hedges its claims on purpose (may, suggest) and cites numbers as its evidence."
+  literature: "Length, rhythm, repetition and register are the author's choices in literature, and dialogue mixes styles. Only what one work can hold itself to runs: consistent spacing and commas, and numbering without gaps."
+  business/meeting-notes: "A header block of labelled fields (- **日時**：…, - **出席者**：…) is the form of minutes, not a list of captions."
+  speech/transcript: "Labelled speaker turns (- **記者**：…) are how a transcript is laid out."
 sources: [zhang-2024]
 
 group: ai-tells
@@ -52,12 +59,13 @@ example:
       月の費用は下がり、権限も細かく分けられます。
 
 not_flagged:
-  ja: 札がコードだけの項目（`--flag` の説明のような、設定や引数の一覧）は数えません。札の後ろにコロンが無い項目と、コロンの後ろに何も無い項目も数えません。技術文書・法務・説明書・論文・文学のジャンルでは見ません。英語の文書は、人もよくこの形で書くので見ません。
-  en: An item whose label is only code (a list of options or fields) is not counted, nor is one without a colon after the label or without text after the colon. Technical, legal, documentation, academic and literary genres do not run this rule. Japanese documents only; English writers use this shape as a matter of course.
+  ja: 札がコードだけの項目（`--flag` の説明のような、設定や引数の一覧）は数えません。札の後ろにコロンが無い項目と、コロンの後ろに何も無い項目も数えません。仕様書（technical/spec）・法務・説明書・論文・文学のジャンルでは見ません。英語の文書は、人もよくこの形で書くので見ません。
+  en: An item whose label is only code (a list of options or fields) is not counted, nor is one without a colon after the label or without text after the colon. Specification (technical/spec), legal, documentation, academic and literary genres do not run this rule. Japanese documents only; English writers use this shape as a matter of course.
 level_meaning:
   ja: 太字の札で始まる項目が {limit} 個あれば指摘
   en: reported once {limit} list items open with a bold label
 rewrite:
+  depth: structure
   ja:
     direction: 太字の札を外し、項目を文に戻してください。札の語は文の中に入れ、項目どうしの関係（理由、順番、どちらが大事か）を書きます。用語集のように、札が定義される語そのものなら箇条書きのままにします。
     pairs:

package/rules/bracket-nesting.yaml

@@ -0,0 +1,75 @@
+id: bracket-nesting
+layer: L3
+status: stable
+how_to_find: bracket-nesting
+severity: info
+
+name:
+  ja: 括弧の中に括弧が重なっている
+  en: Brackets nested too deep
+
+why:
+  ja: 括弧の中に括弧があり、その中にまた括弧があると、読み手は開いた括弧をいくつも覚えたまま読み進めることになり、どこで本文に戻ったのかを見失います。二重までは注や引用でよくある形ですが、それより深いものは、文を分けるか、注を外に出すほうが読めます。数えるのは丸括弧・角括弧・鉤括弧・隅付き括弧と、開きと閉じの形が違う引用符です。開きの無い閉じ括弧（箇条の「1)」）と、数式（$…$）の中の括弧は数えません。
+  en: A bracket inside a bracket inside a bracket makes the reader hold every open one while reading on, and lose where the sentence resumed. Two levels are common in notes and quotations; deeper than that reads better as a separate sentence or a note. Round and square brackets, Japanese corner brackets and curly double quotes are counted. A closing bracket with no opener (the "1)" of a list) and brackets inside a formula ($…$) are not.
+
+message:
+  ja: 括弧が {count} 重になっています（{limit} 重まで）
+  en: Brackets nested {count} deep (limit {limit})
+
+how_to_fix:
+  ja: 一番内側の括弧を外して、別の文にするか注にしてください。
+  en: Take the innermost bracket out into its own sentence or a note.
+
+levels: { strict: 1, normal: 2, relaxed: 3 }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+
+group: readability
+summary:
+  ja: 「（注（a（b）））」のように、括弧の中に括弧が何重にも重なった文
+  en: Brackets inside brackets inside brackets in one sentence
+example:
+  ja:
+    before: |
+      費用は本部が負担します（ただし、出張費（交通費（特急料金を除く）を含む）は各部の負担）。
+    after: |
+      費用は本部が負担します。ただし、出張費は各部が負担します。出張費には交通費を含み、特急料金は含みません。
+  en:
+    before: |
+      The fee is waived (for members (including student members (under 25))) on request.
+    after: |
+      The fee is waived on request for members, including student members under 25.
+
+not_flagged:
+  ja: 二重までの括弧、開きの無い閉じ括弧（「1)」）、コードと数式（$…$）の中の括弧、波括弧は数えません。
+  en: Two levels of brackets, a closing bracket with no opener ("1)"), brackets in code or in a formula ($…$), and curly braces are not counted.
+level_meaning:
+  ja: 括弧の重なり {limit} 重まで
+  en: brackets nested up to {limit} deep
+rewrite:
+  depth: light
+  ja:
+    direction: 一番内側の括弧を外して、別の文か注にしてください。括弧の中身は落とさずに残します。
+    pairs:
+      - before: 費用は本部が負担します（ただし、出張費（交通費（特急料金を除く）を含む）は各部の負担）。
+        after: 費用は本部が負担します。ただし、出張費は各部が負担します。出張費には交通費を含み、特急料金は含みません。
+      - before: 申請書（様式1（別紙（記入例）参照））を出してください。
+        after: 申請書（様式1）を出してください。記入例は別紙にあります。
+    keep:
+      - 括弧の中に書いてあった条件や例外
+      - 何がどこに係るのか
+    avoid:
+      - 括弧の中身を消す
+      - 括弧を読点やダッシュに替えて、同じ重なりを残す
+  en:
+    direction: Take the innermost bracket out into its own sentence or a note. Keep everything the brackets said.
+    pairs:
+      - before: The fee is waived (for members (including student members (under 25))) on request.
+        after: The fee is waived on request for members, including student members under 25.
+      - before: Submit the form (Form A (see the sample (Annex 2))) by Friday.
+        after: Submit Form A by Friday. A sample is in Annex 2.
+    keep:
+      - every condition and exception the brackets held
+    avoid:
+      - deleting what was in the brackets
+      - swapping the brackets for dashes and keeping the same nesting