chaffjs 0.19.0 → 0.21.0

package/rules/reference-title-mismatch.yaml

@@ -0,0 +1,102 @@
+id: reference-title-mismatch
+layer: L3
+status: stable
+how_to_find: reference-title-mismatch
+requires: [structure]
+severity: info
+
+name:
+  ja: 参照に添えた名前が、参照先の見出しと違う
+  en: A reference whose name does not match its target's heading
+
+why:
+  ja: 「第5条（秘密保持）」の第5条が、実は「第5条（損害賠償）」だと、読み手は番号と名前のどちらを信じればよいか分かりません。条や章を足したり消したりして番号がずれたのに、参照を直し忘れると起きます。参照のすぐ後ろの括弧か引用符の中の名前を、参照先の見出しと比べます。どちらかがどちらかを含めば合っているとみなします。
+  en: 'When "Section 5 (Confidentiality)" points at a Section 5 headed "Liability", the reader cannot tell whether the number or the name is right. It happens when sections are added or removed and the numbers shift, but the references are not updated. The name in brackets or quotes right after a reference is compared with the target''s heading; they agree when either contains the other.'
+
+message:
+  ja: "{label}に「{name}」と添えていますが、{label}の見出しは「{heading}」です"
+  en: '{label} is called "{name}" here, but its heading is "{heading}"'
+
+how_to_fix:
+  ja: 番号と名前のどちらが正しいかを確かめて、もう一方を直してください。番号がずれたのなら、ほかの参照も同じようにずれていないかを見てください。
+  en: Check whether the number or the name is right and correct the other. If the numbers shifted, check the other references too.
+
+levels: { normal: info, relaxed: info }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+
+group: facts
+summary:
+  ja: 「第5条（秘密保持）」のように参照に添えた名前が、その条や章の見出しと違う所
+  en: A name given with a reference ("Section 5 (Confidentiality)") that differs from that section's heading
+example:
+  ja:
+    before: |
+      # 規約
+
+      ## 第1章 総則
+
+      料金は第2章「返金」を見てください。
+
+      ## 第2章 料金
+
+      月額です。
+    after: |
+      # 規約
+
+      ## 第1章 総則
+
+      料金は第2章「料金」を見てください。
+
+      ## 第2章 料金
+
+      月額です。
+  en:
+    before: |
+      # Terms
+
+      ## 1. Scope
+
+      For fees, see Section 2 (Refunds).
+
+      ## 2. Pricing
+
+      The fee is monthly.
+    after: |
+      # Terms
+
+      ## 1. Scope
+
+      For fees, see Section 2 (Pricing).
+
+      ## 2. Pricing
+
+      The fee is monthly.
+
+not_flagged:
+  ja: 参照先が見出しを持たないとき、参照先が一つに決まらないとき、他の文書の条（民法第709条）、括弧の中が数字を含むか「前述」「参照」のような語のときは見ません。
+  en: References whose target has no heading or cannot be told apart, references to another document, and brackets holding a number or a word like "above" or "see" are left alone.
+rewrite:
+  depth: light
+  ja:
+    direction: 番号と名前のどちらが正しいかを書き手に確かめ、もう一方を直してください。名前を添える意味が無ければ、名前を消して番号だけにしてもかまいません。
+    pairs:
+      - before: 第2章「返金」を見てください。
+        after: 第2章「料金」を見てください。
+      - before: 第5条（秘密保持）に定めるとおり
+        after: 第6条（秘密保持）に定めるとおり
+    keep:
+      - 参照先の番号と見出しの対応
+    avoid:
+      - どちらが正しいかを推測で決める
+  en:
+    direction: Ask the writer whether the number or the name is right, and correct the other. If the name adds nothing, the reference can carry the number alone.
+    pairs:
+      - before: see Section 2 (Refunds)
+        after: see Section 2 (Pricing)
+      - before: as set out in Section 5 (Confidentiality)
+        after: as set out in Section 6 (Confidentiality)
+    keep:
+      - which numbered section has which heading
+    avoid:
+      - guessing which value is right

package/rules/reference-topic-missing.yaml

@@ -0,0 +1,102 @@
+id: reference-topic-missing
+layer: L3
+status: stable
+how_to_find: reference-topic-missing
+requires: [structure]
+severity: info
+
+name:
+  ja: 「第2章で述べた〇〇」の〇〇が、第2章に無い
+  en: A reference to a topic its target never mentions
+
+why:
+  ja: 「第2章で述べた料金体系」と書いたのに、第2章に料金体系の話が無いと、読み手は探しても見つけられません。章を入れ替えたり、話を別の章へ移したりしたときに起きます。参照のすぐ後ろの「で述べた」「で説明した」に続く語を、参照先の見出しと本文から探し、どこにも無ければ指します。
+  en: 'When the text says "see Section 2 for pricing" and Section 2 never mentions pricing, the reader looks and finds nothing. It happens when sections are reordered or a topic moves elsewhere. The words right after "for" (or 「で述べた」) are looked for in the target''s heading and text, and it is pointed out when they are not there.'
+
+message:
+  ja: "{label}（{heading}）に「{topic}」が見当たりません"
+  en: '"{topic}" does not appear in {label} ({heading})'
+
+how_to_fix:
+  ja: 話がどの章にあるかを確かめて、参照の番号を直してください。言い換えて書いているなら、同じ言葉に揃えると読み手が探せます。
+  en: Find the section that covers the topic and correct the number. If the section words it differently, using the same word lets the reader find it.
+
+levels: { strict: warning, normal: info, relaxed: info }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+
+group: facts
+summary:
+  ja: 「第2章で述べた料金体系」のように参照先の話題を書いたのに、その章に話題の語が無い所
+  en: A reference that names a topic ("see Section 2 for pricing") its target never mentions
+example:
+  ja:
+    before: |
+      # 案内
+
+      ## 第1章 総則
+
+      第2章で述べた返金手続は改定されます。
+
+      ## 第2章 料金
+
+      料金体系は月額です。
+    after: |
+      # 案内
+
+      ## 第1章 総則
+
+      第2章で述べた料金体系は改定されます。
+
+      ## 第2章 料金
+
+      料金体系は月額です。
+  en:
+    before: |
+      # Guide
+
+      ## 1. Scope
+
+      See Section 2 for refunds.
+
+      ## 2. Pricing
+
+      The price is monthly.
+    after: |
+      # Guide
+
+      ## 1. Scope
+
+      See Section 2 for pricing.
+
+      ## 2. Pricing
+
+      The price is monthly.
+
+not_flagged:
+  ja: 「詳細」「内容」のようにどの章にも当てはまる語、参照先が見出しを持たないか一つに決まらない参照、他の文書の条は見ません。言い換え（料金と価格）は見つけられないので、語が違えば指します。
+  en: Words that fit any section ("details", "more information"), references whose target has no heading or cannot be told apart, and references to another document are left alone. A synonym (price and fee) is not recognised, so a different word is pointed out.
+rewrite:
+  depth: light
+  ja:
+    direction: 話題がどの章にあるかを書き手に確かめ、参照の番号を直してください。参照先が別の言葉で書いているなら、どちらかの言葉に揃えます。
+    pairs:
+      - before: 第2章で述べた返金手続は改定されます。
+        after: 第3章で述べた返金手続は改定されます。
+      - before: 第2章で述べた価格表
+        after: 第2章で述べた料金表
+    keep:
+      - 参照している話題
+    avoid:
+      - 参照先に無い話を、参照先にあることにする
+  en:
+    direction: Ask the writer which section covers the topic and correct the number. If the target words it differently, use one wording in both places.
+    pairs:
+      - before: See Section 2 for refunds.
+        after: See Section 3 for refunds.
+      - before: See Section 2 for fees.
+        after: See Section 2 for pricing.
+    keep:
+      - the topic being referred to
+    avoid:
+      - claiming the target covers something it does not

package/rules/relative-date-mismatch.yaml

@@ -0,0 +1,72 @@
+id: relative-date-mismatch
+layer: L3
+status: stable
+how_to_find: relative-date-mismatch
+requires: [dates]
+severity: warning
+
+name:
+  ja: 「3日後の10月5日」の日付が、基準の日付から数えた日と合わない
+  en: A relative date that does not match its base date
+
+why:
+  ja: 「10月2日に申し込み、3日後の10月6日に通知」のように、相対の期間と日付を一緒に書くと、読み手はどちらが正しいのか分かりません。日程をずらしたときに、日付か期間の片方だけを直すと起きます。「3日後の」「1か月前の」のすぐ後ろの日付を、同じ文で前にある日付（文が「2週間後、」で始まるなら前の文の日付）に期間を足した（前なら引いた）日と比べます。
+  en: 'When a relative length and a date are written together ("Applications open on May 1, 2026. Two weeks later, on May 16, 2026, …"), the reader cannot tell which is right. It happens when a schedule moves and only the date or only the length is changed. The date right after "N days later" or "N weeks earlier" is compared with the nearest earlier date in the same sentence (or in the previous sentence when the sentence opens with the relative length), plus or minus the length.'
+
+message:
+  ja: "{base}の{relative}なら{expected}のはずですが、{target}と書かれています"
+  en: "{relative} from {base} is {expected}, but the date is given as {target}"
+
+how_to_fix:
+  ja: 基準の日付・期間・日付のどれが正しいかを確かめて、残りを合わせてください。
+  en: Check which is right, the base date, the length or the date, and make the rest agree.
+
+levels: { normal: warning, relaxed: info }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+
+group: facts
+summary:
+  ja: 「3日後の10月6日」のように、相対で書いた日付が基準の日付から数えた日と合わない所
+  en: A date written with a relative length ("two weeks later, on May 16") that is not that far from its base date
+example:
+  ja:
+    before: |
+      10月2日に申し込みを締め切り、3日後の10月6日に結果を通知します。
+    after: |
+      10月2日に申し込みを締め切り、3日後の10月5日に結果を通知します。
+  en:
+    before: |
+      Applications close on May 1, 2026. Two weeks later, on May 16, 2026, results are sent.
+    after: |
+      Applications close on May 1, 2026. Two weeks later, on May 15, 2026, results are sent.
+
+not_flagged:
+  ja: 期間のすぐ後ろ（「の」や読点だけを挟む）に日付があるときだけ見ます。基準の日付が同じ文（文の頭の「2週間後、」なら前の文）に無いもの、「3営業日後」のように単位が日・週・月・年でないものは見ません。
+  en: Only a date right after the relative length (with "on" or punctuation between) is checked. A relative length with no date before it in the same sentence (or the previous one, when the sentence opens with it), and units other than days, weeks, months and years ("3 business days later"), are left alone.
+rewrite:
+  depth: light
+  ja:
+    direction: 基準の日付・期間・日付のどれが正しいかを書き手に確かめ、残りを合わせてください。期間か日付のどちらかを消して、一つだけにしてもかまいません。
+    pairs:
+      - before: 10月2日に締め切り、3日後の10月6日に通知します。
+        after: 10月2日に締め切り、3日後の10月5日に通知します。
+      - before: 発売日の5月1日の1か月前の4月2日に予約を始めます。
+        after: 発売日の5月1日の1か月前の4月1日に予約を始めます。
+    keep:
+      - 基準の日付
+      - 「後」か「前」かの向き
+    avoid:
+      - どれが正しいかを推測で決める
+  en:
+    direction: Ask the writer which of the base date, the length and the date is right, and make the rest agree. Dropping either the length or the date also works.
+    pairs:
+      - before: Applications close on May 1, 2026. Two weeks later, on May 16, 2026, results are sent.
+        after: Applications close on May 1, 2026. Two weeks later, on May 15, 2026, results are sent.
+      - before: The launch is on June 1, 2026; one month earlier, on May 2, 2026, preorders open.
+        after: The launch is on June 1, 2026; one month earlier, on May 1, 2026, preorders open.
+    keep:
+      - the base date
+      - whether the date is later or earlier
+    avoid:
+      - guessing which value is right

package/rules/repeated-conjunction.yaml

@@ -1,6 +1,6 @@
 id: repeated-conjunction
 layer: L2
-status: experimental
+status: stable
 how_to_find: repeated-conjunction
 word_list: paragraph-opener
 uses: [pos]
@@ -25,6 +25,9 @@ how_to_fix:
 levels: { strict: 1, normal: 2, relaxed: 4 }
 
 use_for: [business, blog, technical, 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."
+  speech/transcript: "A transcript records what was said: its sentences, repeats and register are the speaker's, not the writer's to fix."
 
 group: readability
 summary:

package/rules/repeated-sentence-ending.yaml

@@ -0,0 +1,62 @@
+id: repeated-sentence-ending
+layer: L3
+status: stable
+how_to_find: ending-run
+requires: [pos]
+languages: [ja]
+severity: info
+
+name:
+  ja: 同じ文末が続く
+  en: The same sentence ending in a row
+
+why:
+  ja: 「〜です。〜です。〜です。」「〜しました。〜しました。〜しました。」のように、同じ形で終わる文が続くと、読み手には同じ調子の繰り返しに聞こえ、どの文が要なのかが見えにくくなります。文末の助動詞と、その前の動詞を書いた形で比べます。名詞の後の「です」は名詞が違っても同じ文末と見ます（必要です、重要です）。
+  en: In Japanese, sentences that all end the same way ("…です。…です。…です。") read as one tone repeated, and the sentence that matters does not stand out. chaff compares the closing auxiliaries and the verb before them as written. After a noun only the auxiliaries count, so 必要です and 重要です end the same way.
+
+message:
+  ja: 「〜{word}」で終わる文が {count} 文続いています（{limit} 文まで）
+  en: '{count} sentences in a row end with "〜{word}" (limit {limit})'
+
+how_to_fix:
+  ja: 一つの文の終わり方を変えるか、二つの文を一つにまとめてください（〜です。〜です。→ 〜で、〜です。）。
+  en: Change how one sentence ends, or join two sentences into one.
+
+levels: { strict: 2, normal: 2, relaxed: 3 }
+
+use_for: [blog, business, technical, legal, docs, academic, literature, speech]
+off_for:
+  legal: "Articles end 〜する。〜する。 by form; the same ending in a row is the drafting style."
+
+group: readability
+summary:
+  ja: 「〜です。〜です。〜です。」のように、同じ形で終わる文が続く所
+  en: Japanese sentences in a row that all end the same way ("…です。…です。…です。")
+example:
+  ja:
+    before: |
+      この機能は必要です。設定も簡単です。費用も無料です。
+    after: |
+      この機能は必要で、設定も簡単です。費用はかかりません。
+
+not_flagged:
+  ja: 段落をまたいだ文は続きと見ません。助動詞で終わらない文（体言止め、言い切りの動詞）は比べず、そこで続きが切れます。動詞が違えば（読みました、書きました）同じ文末とは見ません。
+  en: Sentences in different paragraphs are not a run. A sentence that does not end with an auxiliary (a noun, a bare verb) is not compared and breaks the run. Different verbs (読みました, 書きました) are different endings.
+level_meaning:
+  ja: 同じ文末の文が {limit} 文続くまで
+  en: up to {limit} sentences in a row with the same ending
+rewrite:
+  depth: light
+  ja:
+    direction: 続いた文のうち一つか二つの文末を変えてください。二文を「〜で、」「〜し、」でつなぐか、言い方を変えます。言っている事柄は変えません。
+    pairs:
+      - before: この機能は必要です。設定も簡単です。費用も無料です。
+        after: この機能は必要で、設定も簡単です。費用はかかりません。
+      - before: 資料を確認しました。手順を修正しました。結果を報告しました。
+        after: 資料を確認して手順を直し、その結果を報告しました。
+    keep:
+      - それぞれの文が言っている事柄
+      - 文体（です・ます、だ・である）
+    avoid:
+      - 文末を変えるために「〜と言えます」「〜となっております」のような飾りを足す
+      - 文体を混ぜる（です・ますの中に、だ・である）

package/rules/repeated-sentence-head.yaml

@@ -26,6 +26,10 @@ levels:
   relaxed: 4
 
 use_for: [blog, business, technical, 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."
+  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."
 
 group: readability
 summary:

package/rules/request-without-deadline.yaml

@@ -0,0 +1,92 @@
+id: request-without-deadline
+layer: L3
+status: stable
+how_to_find: request-without-deadline
+requires: [dates]
+# Who and when are read from the language's request-* lexicons, the document's dates, and proper nouns when parts of
+# speech are available.
+uses: [pos]
+languages: [ja, en]
+severity: info
+
+name:
+  ja: 期限も担当も無い依頼
+  en: Request with no deadline or owner
+
+why:
+  ja: 「資料をご確認ください」のような依頼に、いつまでに・誰がするかが書かれていないと、読んだ人は自分の仕事だと思わず、急ぐ理由も分からないまま後回しにします。依頼したほうは返事を待ち続けることになります。
+  en: A request ("Please review the draft.") with no deadline and no named person leaves every reader assuming someone else will do it, some day. The sender waits for an answer that has no date.
+
+message:
+  ja: この依頼には、いつまでに・誰がするかが書かれていません
+  en: This request says neither who should do it nor by when
+
+how_to_fix:
+  ja: 期限か担当（できれば両方）を書いてください。「10月20日（火）までに、山田さんがご確認ください」のように。
+  en: Add a deadline or an owner, ideally both ("Yamada, please review the draft by Tuesday, October 20.").
+
+levels: { strict: warning, normal: info, relaxed: info }
+
+use_for: [business, legal, docs, academic, literature, speech]
+off_for:
+  legal: "A request without a deadline is a business-mail habit; elsewhere a request is an instruction or a pointer."
+  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."
+  speech: "A speech opens with greetings and closes with thanks: that is its form, not padding."
+
+group: wording
+summary:
+  ja: 「ご確認ください」「Please send …」のような依頼で、その文にも次の文にも期限と担当が無いもの
+  en: A request ("Please send …") with no deadline and no person or role in it or in the next sentence
+example:
+  ja:
+    before: |
+      添付の見積書をご確認ください。
+
+      ほかに質問はありません。
+    after: |
+      添付の見積書を、10月20日（火）までにご確認ください。
+
+      ほかに質問はありません。
+  en:
+    before: |
+      Please review the attached quote.
+
+      I have no other questions.
+    after: |
+      Please review the attached quote by Tuesday, October 20.
+
+      I have no other questions.
+
+not_flagged:
+  ja: 確認・返信・提出のように、済んだかどうかが後で分かる動作を頼む文だけを見ます。「ご了承ください」のような心構えの依頼と、「ご不明な点があれば、ご連絡ください」のような条件付きの申し出は見ません。期限か担当が、その文か次の文にあれば指しません。ビジネスの文書でだけ動きます。
+  en: Only requests for an action whose completion can be checked (review, reply, send) are read. Courtesy requests and conditional offers ("If you have questions, let me know") are not. A deadline or owner in the same or the next sentence is enough. Business documents only.
+rewrite:
+  depth: light
+  ja:
+    direction: 依頼の文に、本文に書かれている期限と担当を書き足してください。本文に無ければ作らず、［期限］［担当］と空けて書き手に聞きます。
+    pairs:
+      - before: 添付の見積書をご確認ください。
+        after: 添付の見積書を、［期限］までにご確認ください。
+      - before: 議事録を共有してください。
+        after: 議事録を、10月16日（金）までに伊藤さんが共有してください。
+    keep:
+      - 頼む中身と、敬語の度合い
+      - 本文のほかの文
+    avoid:
+      - 本文に無い日付や名前を作る
+      - 依頼を命令の形に書き換える
+  en:
+    direction: Add the deadline and owner the text gives to the request. If the text gives none, do not invent them; leave [deadline] and [owner] for the writer.
+    pairs:
+      - before: Please review the attached quote.
+        after: Please review the attached quote by [deadline].
+      - before: Please share the minutes.
+        after: Ito, please share the minutes by Friday, October 16.
+    keep:
+      - what is asked, and how politely
+      - the other sentences
+    avoid:
+      - inventing a date or a name the text does not give
+      - turning the request into an order

package/rules/required-sections.yaml

@@ -1,6 +1,6 @@
 id: required-sections
 layer: L1
-status: experimental
+status: stable
 how_to_find: required-sections
 severity: error
 

package/rules/requirement-modal.yaml

@@ -1,6 +1,6 @@
 id: requirement-modal
 layer: L2
-status: experimental
+status: stable
 how_to_find: requirement-modal
 # 何を見るかは options で決める。決めなければ何も見ない。語は言語ごとの語彙表 requirement-modal-<standard> と requirement-modal-must にある。
 uses: [pos]

package/rules/requirement-smell.yaml

@@ -1,12 +1,12 @@
 id: requirement-smell
 layer: L2
-status: experimental
+status: stable
 how_to_find: requirement-smell
 # 要求の文の目印と、三つの見つけ方の語。語はすべて言語ごとの語彙表にある。
 word_list: requirement-marker
 extra_word_lists: [requirement-loophole, requirement-open-end, requirement-either]
 uses: [pos]
-severity: warning
+severity: info
 
 name:
   ja: 要求の文に、決めきれない言い方がある
@@ -40,11 +40,19 @@ placeholders:
     ja: 見つけた語
     en: the phrase found
 
-levels: { strict: error, normal: warning, relaxed: info }
+levels: { strict: warning, normal: info, relaxed: info }
 
 # 要求を書く文書だけ。仕様書、契約書・規約、説明書（マニュアル・FAQ）。ほかの法務・説明書のジャンルと、学術・文学・話し言葉は
-# genres.yaml で止める（法令は「等」を定義して使う、用語集の「〜すること。」は語の説明）。
+# off_for で止める（法令は「等」を定義して使う、用語集の「〜すること。」は語の説明）。
 use_for: [technical/spec, legal, docs, academic, literature, speech]
+off_for:
+  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."
+  speech: "A transcript keeps the speaker's words: hedges and ら dropped as spoken."
+  legal/statute: "A statute defines its 等 terms (以下「個人情報等」という) and uses them in its obligations."
+  legal/judgment: "requirement-smell is for the documents that state requirements: specifications, contracts and documentation."
+  legal/patent: "requirement-smell is for the documents that state requirements: specifications, contracts and documentation."
+  docs/glossary: "An entry that ends 〜すること or 〜のこと defines a word; it is no requirement."
 sources: [femmer-2017, berry-2003, iso-29148]
 
 group: wording

package/rules/rule-of-three.yaml

@@ -1,6 +1,6 @@
 id: rule-of-three
 layer: L1
-status: experimental
+status: stable
 how_to_find: rule-of-three
 severity: info
 
@@ -22,7 +22,13 @@ how_to_fix:
 
 levels: { strict: 50, normal: 70, relaxed: 90 }
 
-use_for: [blog, legal, docs, academic, literature, speech]
+use_for: [technical/readme, blog, 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."
+  speech: "A speech opens with greetings and closes with thanks: that is its form, not padding."
 sources: [reinhart-2025, zhang-2024]
 
 group: ai-tells
@@ -116,12 +122,13 @@ example:
       - No review
 
 not_flagged:
-  ja: 箇条書きが 3 つより少ない文書は見ません。ビジネス文書と技術文書のジャンルでは見ません。
-  en: Documents with fewer than three lists are not checked. Business and technical genres do not run this rule.
+  ja: 箇条書きが 3 つより少ない文書は見ません。ビジネス文書と仕様書（technical/spec）のジャンルでは見ません。
+  en: Documents with fewer than three lists are not checked. Business and specification (technical/spec) genres do not run this rule.
 level_meaning:
   ja: 3 項目の箇条書きの割合 {limit}% まで
   en: up to {limit}% of lists with exactly three items
 rewrite:
+  depth: light
   ja:
     direction: 三つ並んだ箇条書きのうち、ほかの項目と同じことを言っている項目を消すか、一つにまとめてください。本当に三つあるリストはそのままにします。
     pairs:

package/rules/sasete-itadaku.yaml

@@ -1,6 +1,6 @@
 id: sasete-itadaku
 layer: L3
-status: experimental
+status: stable
 how_to_find: phrase-count
 word_list: sasete-itadaku
 uses: [pos]
@@ -26,6 +26,12 @@ how_to_fix:
 levels: { strict: 1, normal: 3, relaxed: 6 }
 
 use_for: [business, blog, 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."
+  speech/transcript: "A transcript records what was said: its sentences, repeats and register are the speaker's, not the writer's to fix."
 
 group: wording
 summary:

package/rules/section-length-uniformity.yaml

@@ -1,6 +1,6 @@
 id: section-length-uniformity
 layer: L1
-status: experimental
+status: stable
 how_to_find: section-uniformity
 severity: info
 
@@ -30,7 +30,13 @@ options:
       ja: 測る節の数の下限。節が少ないと長さのばらつきは偶然で小さく出て、人の書いた文書でも揃って見えます
       en: The fewest sections measured. With few sections, the variation is small by chance, and a person's writing looks uniform too
 
-use_for: [blog, legal, docs, academic, literature, speech]
+use_for: [technical/readme, blog, 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."
+  speech: "A speech opens with greetings and closes with thanks: that is its form, not padding."
 
 group: ai-tells
 summary:
@@ -131,8 +137,8 @@ example:
       New versions are on the same page.
 
 not_flagged:
-  ja: 中身のある節が 5 より少ない文書は見ません（min_sections で変えられます）。ビジネス文書と技術文書のジャンルでは見ません。
-  en: Documents with fewer than 5 sections are not checked (min_sections changes it). Business and technical genres do not run this rule.
+  ja: 中身のある節が 5 より少ない文書は見ません（min_sections で変えられます）。ビジネス文書と仕様書（technical/spec）のジャンルでは見ません。
+  en: Documents with fewer than 5 sections are not checked (min_sections changes it). Business and specification (technical/spec) genres do not run this rule.
 level_meaning:
   ja: 節の長さのばらつきが {limit}% 未満なら指摘
   en: reported when section length varies by less than {limit}%

package/rules/sentence-initial-conjunction-run.yaml

@@ -1,6 +1,6 @@
 id: sentence-initial-conjunction-run
 layer: L3
-status: experimental
+status: stable
 how_to_find: conjunction-run
 word_list: sentence-opener
 languages: [en]
@@ -25,6 +25,10 @@ how_to_fix:
 levels: { strict: 1, normal: 2, relaxed: 4 }
 
 use_for: [blog, business, legal, docs, academic, literature, speech]
+off_for:
+  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."
 
 group: readability
 summary: