chaffjs 0.20.0 → 0.22.0

package/rules/defined-term-form.yaml

@@ -0,0 +1,113 @@
+id: defined-term-form
+layer: L3
+status: stable
+how_to_find: defined-term-form
+requires: [structure, pos]
+severity: info
+
+name:
+  ja: 定義した語を、定義と違う形で使っている
+  en: A defined term used in another form
+
+why:
+  ja: 契約では、定義した語は定義した形のまま使うのが決まりです。「本サービス」と定義したあとで「「本サービス」」とかぎ括弧を付け直すと、新しく定義し直したのか、同じものなのかが読み手に分かりません。英語では "Services" と定義した語を "services" と小文字で書くと、定義した意味なのか、ふつうの意味なのかが分かれ、争いのもとになります。定義の後ろで、かぎ括弧や引用符に入れ直した語と、大文字で定義した語を小文字で書いた所（大文字の使用より少ないとき）を指します。
+  en: 'A contract uses each defined term exactly as defined. Quoting a term again after its definition ("the "Services"") leaves the reader asking whether it is being defined anew. Writing "services" where "Services" is defined splits the defined sense from the ordinary one, which is where disputes start. chaff points at a term set in quotes again after its definition, and at a capitalised term written in lower case (when the capitalised uses are more).'
+
+message:
+  ja: 定義した「{term}」と違う形で使っています
+  en: '"{term}" is used in another form than defined'
+
+messages:
+  quoted:
+    ja: 「{term}」は {line} 行目で定義した語です。定義のあとは、かぎ括弧を付けずに使います
+    en: '"{term}" is defined on line {line}; after that it is used without quotes'
+  case:
+    ja: 「{term}」は {line} 行目で大文字で定義した語ですが、ここは小文字です
+    en: '"{term}" is defined with a capital on line {line}, but written in lower case here'
+
+how_to_fix:
+  ja: 定義した語はかぎ括弧を付けずに使い、英語では定義のとおり大文字で始めてください。ふつうの意味で使うなら、別の言葉に替えます。
+  en: Use the defined term without quotes and, in English, with its capital as defined. If the ordinary sense is meant, use another word.
+
+levels: { strict: 3, normal: 2, relaxed: 1 }
+
+use_for: [legal, docs, academic, literature, speech]
+off_for:
+  docs: "Defined terms and short names are a contract's apparatus: the legal genres check them."
+  academic: "Defined terms and short names are a contract's apparatus: the legal genres check them."
+  literature: "Defined terms and short names are a contract's apparatus: the legal genres check them."
+  speech: "Defined terms and short names are a contract's apparatus: the legal genres check them."
+  legal/statute: "A regulation's guidelines and circulars quote a defined term to point at its definition (「個人情報」の定義)."
+
+group: consistency
+summary:
+  ja: 契約や規約で、定義した語を定義のあとでかぎ括弧に入れ直したり、大文字で定義した語を小文字で書いたりしている所
+  en: A defined term quoted again after its definition, or a capitalised defined term written in lower case
+example:
+  ja:
+    config: { genre: legal/contract }
+    before: |
+      # 利用規約
+
+      第1条　当社は、会議室の予約サービス（以下「本サービス」という。）を提供する。
+
+      第2条　利用者は、「本サービス」を業務の目的でだけ使う。
+    after: |
+      # 利用規約
+
+      第1条　当社は、会議室の予約サービス（以下「本サービス」という。）を提供する。
+
+      第2条　利用者は、本サービスを業務の目的でだけ使う。
+  en:
+    config: { genre: legal/contract }
+    before: |
+      # Terms
+
+      1. We provide a room booking service (the "Services").
+
+      2. You may use the Services for business only. The Services are provided as is.
+
+      3. You must not resell the services.
+    after: |
+      # Terms
+
+      1. We provide a room booking service (the "Services").
+
+      2. You may use the Services for business only. The Services are provided as is.
+
+      3. You must not resell the Services.
+
+not_flagged:
+  ja: 定義そのもの（以下「本サービス」という、「本サービス」とは）、定義より前の使用（use-before-definition が見ます）、文の頭の大文字、小文字の使用が {limit} 個を超えるか大文字の使用より多い語（ふつうの意味で使っているとみなす）は指しません。定義の文の中の使用（「顧客」とは、表紙に「顧客」と書いた者をいう）も見ません。法令・規程のジャンルは、定義を指すために語をかぎ括弧に入れるので見ません。
+  en: 'The definitions themselves ("Services" means, (the "Services")), uses before the definition (use-before-definition reads those), capitals at the start of a sentence, and terms written in lower case more than {limit} times or more often than capitalised (taken as the ordinary word used on purpose) are not reported, nor is a use inside the defining sentence ("Customer" means the party named "Customer"). Statutes and regulations quote a term to point at its definition, so that genre does not run this rule.'
+level_meaning:
+  ja: 小文字の使用が {limit} 個以下で、大文字の使用より少ないとき指摘
+  en: lower-case uses reported when they are {limit} or fewer and fewer than the capitalised ones
+rewrite:
+  depth: light
+  ja:
+    direction: 定義した語を定義の形に戻してください。かぎ括弧を外し、英語の語は定義のとおり大文字で始めます。ふつうの意味で使っているのが明らかなら、定義した語と紛れない別の言葉に替えます。どちらの意味か決められなければ、書き手に確かめます。
+    pairs:
+      - before: 利用者は、「本サービス」を業務の目的でだけ使う。
+        after: 利用者は、本サービスを業務の目的でだけ使う。
+      - before: 乙は、「対象情報」を第三者に開示しない。
+        after: 乙は、対象情報を第三者に開示しない。
+    keep:
+      - 条の番号と中身
+      - 定義した語そのもの
+    avoid:
+      - 定義を書き換える
+      - 意味が分からない所を推測で大文字にする
+  en:
+    direction: Bring the term back to its defined form. Remove the quotes, and capitalise it as defined. If the ordinary sense is clearly meant, use a word that cannot be mistaken for the defined term. If it is not clear which sense is meant, ask the writer.
+    pairs:
+      - before: You must not resell the services.
+        after: You must not resell the Services.
+      - before: The "Customer" must pay within 30 days.
+        after: The Customer must pay within 30 days.
+    keep:
+      - the clause numbers and their content
+      - the defined term itself
+    avoid:
+      - changing the definition
+      - capitalising a word whose sense is unclear without asking

package/rules/demonstrative-opener-run.yaml

@@ -1,6 +1,6 @@
 id: demonstrative-opener-run
 layer: L3
-status: experimental
+status: stable
 how_to_find: opener-run
 word_list: demonstrative-opener
 requires: [pos]
@@ -45,6 +45,7 @@ level_meaning:
   ja: 指示語で始まる文 {limit} 文の連続まで
   en: up to {limit} such sentences in a row
 rewrite:
+  depth: light
   ja:
     direction: 続いた指示語のうち、指すものが遠いものから、指している名詞に置き換えてください。一つ前の文を指す指示語は残してかまいません。
     pairs:

package/rules/double-keigo.yaml

@@ -1,6 +1,6 @@
 id: double-keigo
 layer: L3
-status: experimental
+status: stable
 how_to_find: phrase-match
 word_list: double-keigo
 uses: [pos]
@@ -26,6 +26,11 @@ how_to_fix:
 levels: { strict: 1, normal: 1, relaxed: 2 }
 
 use_for: [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."
+  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/double-negative.yaml

@@ -1,6 +1,6 @@
 id: double-negative
 layer: L2
-status: experimental
+status: stable
 how_to_find: phrase-match
 word_list: double-negative
 uses: [pos]
@@ -26,6 +26,10 @@ how_to_fix:
 levels: { strict: 1, normal: 1, relaxed: 2 }
 
 use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+off_for:
+  legal: 'Statutes and opinions write "not inconsistent with" on purpose.'
+  literature: "A narrator may hedge, speak with ら dropped, and spell as the work's time and place did."
+  speech: "A transcript keeps the speaker's words: hedges and ら dropped as spoken."
 
 group: readability
 summary:

package/rules/doubled-nado.yaml

@@ -1,6 +1,6 @@
 id: doubled-nado
 layer: L2
-status: experimental
+status: stable
 how_to_find: phrase-match
 word_list: doubled-nado
 requires: [pos]
@@ -44,6 +44,7 @@ level_meaning:
   ja: 重ねた所が {limit} 箇所あれば指摘
   en: reported once there are {limit}
 rewrite:
+  depth: light
   ja:
     direction: 「など」か「等」のどちらか一つを消してください。文書の中でほかに多く使っている方を残します。
     pairs:

package/rules/doubled-punctuation.yaml

@@ -1,6 +1,6 @@
 id: doubled-punctuation
 layer: L1
-status: experimental
+status: stable
 how_to_find: doubled-punctuation
 severity: warning
 

package/rules/doubled-word.yaml

@@ -1,6 +1,6 @@
 id: doubled-word
 layer: L3
-status: experimental
+status: stable
 how_to_find: doubled-word
 word_list: doubled-word
 requires: [pos]
@@ -25,6 +25,9 @@ how_to_fix:
 levels: { strict: error, normal: warning, relaxed: info }
 
 use_for: [blog, business, 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: slips
 summary:

package/rules/duplicate-definition.yaml

@@ -1,6 +1,6 @@
 id: duplicate-definition
 layer: L3
-status: experimental
+status: stable
 how_to_find: duplicate-definition
 requires: [structure]
 severity: warning
@@ -30,6 +30,8 @@ placeholders:
 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: structure
 summary:

package/rules/duplicate-heading.yaml

@@ -1,6 +1,6 @@
 id: duplicate-heading
 layer: L1
-status: experimental
+status: stable
 how_to_find: duplicate-heading
 requires: [markdown]
 severity: warning

package/rules/duration-mismatch.yaml

@@ -1,6 +1,6 @@
 id: duration-mismatch
 layer: L3
-status: experimental
+status: stable
 how_to_find: duration-mismatch
 requires: [dates]
 severity: warning
@@ -45,6 +45,7 @@ not_flagged:
   ja: 三通りの数え方（終わりを含める、含めない、初日を数えずに過ぎた日）のどれとも合わないときだけ指します。「約3か月」「3か月程度」のような目安の期間、日付が三つ以上か期間が二つ以上ある文、年を書いた日付と書かない日付の組は見ません。
   en: Only an end that matches none of the three ways of counting is pointed out. A rough length ("about 3 months"), a sentence with three or more dates or two or more lengths, and a pair of one date with a year and one without are left alone.
 rewrite:
+  depth: light
   ja:
     direction: 始まり・期間・終わりのうち、どれが正しいかを書き手に確かめ、残りを合わせてください。期間か終わりのどちらかを消して、一つだけにしてもかまいません。
     pairs:

package/rules/elapsed-years-mismatch.yaml

@@ -1,6 +1,6 @@
 id: elapsed-years-mismatch
 layer: L3
-status: experimental
+status: stable
 how_to_find: elapsed-years-mismatch
 requires: [dates]
 severity: warning
@@ -24,6 +24,8 @@ how_to_fix:
 levels: { 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:
@@ -53,6 +55,7 @@ not_flagged:
   ja: 文書に日付（日付だけの段落か「更新日：」の段落）が無ければ、比べる年が無いので見ません。一年までの違い、起点の語に直接付いていない年数（「創業後3年で上場」）、生まれた年と年齢が一つの文に一つずつでないものも見ません。
   en: A document with no date of its own (a paragraph holding only a date, or "Updated:") has no year to count to and is not checked. A difference of one year, a count not attached to the origin word ("listed 3 years after its founding"), and a sentence without exactly one year of birth and one age are left alone.
 rewrite:
+  depth: light
   ja:
     direction: 年数と起点の年のどちらが正しいかを書き手に確かめ、もう一方を直してください。毎年変わる年数は「2015年創業」のように起点の年だけにすると、古くなりません。
     pairs:

package/rules/email-greeting-closing.yaml

@@ -0,0 +1,122 @@
+id: email-greeting-closing
+layer: L2
+status: stable
+how_to_find: email-frame
+severity: info
+
+name:
+  ja: メールの挨拶か結びが無い
+  en: Email without a greeting or a closing
+
+why:
+  ja: 仕事のメールは、挨拶で始まり結びで終わるのが読み手の期待です。挨拶が無いと用件だけを突きつけられたように読め、結びが無いと途中で切れたように見えます。下書きを貼り付けたときや、前のメールから本文だけを写したときに抜けます。本文の最初の数行に挨拶（お世話になっております、拝啓、Dear）が無いか、最後の数行（名前や連絡先の行を含む）に結び（よろしくお願いいたします、敬具、Best regards）が無いとき指します。語は語彙表から読みます。
+  en: 'A work email is expected to open with a greeting and end with a closing. Without the greeting it reads as a bare demand; without the closing it looks cut off. Both go missing when a draft is pasted in or the body is copied from an earlier email. chaff points out a body whose first lines hold no greeting ("Dear", "Hi", "Hello") or whose last lines, the name and contact lines included, hold no closing ("Best regards", "Sincerely", "Thanks"). The words come from a lexicon.'
+
+message:
+  ja: メールの挨拶か結びがありません
+  en: The email has no greeting or no closing
+
+messages:
+  greeting:
+    ja: 書き出しに挨拶がありません
+    en: The email does not open with a greeting
+  closing:
+    ja: 終わりに結びの言葉がありません
+    en: The email does not end with a closing
+
+how_to_fix:
+  ja: 書き出しに「いつもお世話になっております。」のような挨拶を、終わりに「よろしくお願いいたします。」のような結びを足してください。
+  en: Open with a greeting such as "Dear Ms Lee," and end with a closing such as "Best regards," before your name.
+
+levels: { strict: warning, normal: info, 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: structure
+summary:
+  ja: 仕事のメールで、書き出しの挨拶か終わりの結びが無いもの
+  en: A work email that opens without a greeting or ends without a closing
+example:
+  ja:
+    config: { genre: business/email }
+    before: |
+      件名: 打ち合わせの日程
+
+      打ち合わせの日程をお知らせします。10月13日の14時からです。
+
+      よろしくお願いいたします。
+    after: |
+      件名: 打ち合わせの日程
+
+      いつもお世話になっております。打ち合わせの日程をお知らせします。10月13日の14時からです。
+
+      よろしくお願いいたします。
+  en:
+    config: { genre: business/email }
+    before: |
+      Subject: Meeting date
+
+      The meeting is on 13 October at 14:00.
+
+      Best regards,
+      Ichiro
+    after: |
+      Subject: Meeting date
+
+      Dear facilities team,
+
+      The meeting is on 13 October at 14:00.
+
+      Best regards,
+      Ichiro
+not_flagged:
+  ja: 引用した返信（「>」の行）と、ヘッダーと署名（「-- 」の後ろ）は見ません。挨拶と結びの言い方は決めず、語彙表のどれかがあれば足ります。メール・手紙のジャンルでだけ見ます。
+  en: 'Quoted replies (lines starting with ">"), the header and the signature after "-- " are not read. Which greeting or closing is used is not decided; any word in the lexicon will do. Only the email and letter genre runs this rule.'
+rewrite:
+  depth: light
+  ja:
+    direction: 足りないほうだけを足してください。挨拶は本文の最初に一文、結びは名前の前に一文です。相手との関係が分からなければ「お世話になっております」「よろしくお願いいたします」を使います。用件の文は変えません。
+    pairs:
+      - before: 打ち合わせの日程をお知らせします。
+        after: いつもお世話になっております。打ち合わせの日程をお知らせします。
+      - before: |
+          ご都合をお知らせください。
+          佐藤
+        after: |
+          ご都合をお知らせください。
+          よろしくお願いいたします。
+          佐藤
+    keep:
+      - 用件の文
+      - 署名の名前と連絡先
+    avoid:
+      - 本文に無い用件や約束を足す
+      - 挨拶を何文も重ねる
+  en:
+    direction: Add only what is missing. The greeting is one line before the body, the closing one line before the name. If the relationship is unclear, use "Dear [name]," and "Best regards,". Leave the body as it is.
+    pairs:
+      - before: The meeting is on 13 October at 14:00.
+        after: |
+          Dear facilities team,
+
+          The meeting is on 13 October at 14:00.
+      - before: |
+          Let me know which time suits you.
+          Ichiro
+        after: |
+          Let me know which time suits you.
+
+          Best regards,
+          Ichiro
+    keep:
+      - the body's sentences
+      - the name and contact lines
+    avoid:
+      - adding a request or a promise the body does not make
+      - piling up several greetings

package/rules/email-subject-length.yaml

@@ -0,0 +1,112 @@
+id: email-subject-length
+layer: L2
+status: stable
+how_to_find: email-subject
+severity: warning
+
+name:
+  ja: 件名が空か長すぎる
+  en: Subject line empty or too long
+
+why:
+  ja: 受け手は件名を見て、開くか、いつ読むかを決めます。空の件名は用件が分からず、迷惑メールにも見えます。長い件名は一覧で途中から切れ、肝心の語が見えません。「件名：」「Subject:」の行があるメールだけを見て、その値の字数を数えます。返信や転送でメールソフトが足す「Re:」「Fwd:」は数えません。
+  en: 'Recipients decide from the subject whether to open a message and when. An empty subject says nothing and looks like spam; a long one is cut off in the inbox list before its key words. Only an email with a "Subject:" line is checked, and its value is counted in characters. The "Re:" and "Fwd:" a mail program adds are not counted.'
+
+message:
+  ja: 件名が {count} 字あります（{limit} 字まで）
+  en: The subject has {count} characters (up to {limit})
+
+messages:
+  empty:
+    ja: 件名が空です
+    en: The subject line is empty
+
+how_to_fix:
+  ja: 件名には、用件と、日付や案件名のような見分けの語だけを書いてください。説明は本文に移します。
+  en: Put only the request and a distinguishing word (a date, a project) in the subject, and move the explanation into the body.
+
+levels:
+  ja: { strict: 20, normal: 30, relaxed: 40 }
+  en: { strict: 50, normal: 70, relaxed: 90 }
+
+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: structure
+summary:
+  ja: 「件名：」の行がある仕事のメールで、件名が空か、字数の上限を超えるもの
+  en: A work email whose "Subject:" line is empty or longer than the limit
+example:
+  ja:
+    config: { genre: business/email }
+    before: |
+      件名: 来週の火曜日に予定している会議室の予約サービスの導入に向けた打ち合わせの日程について
+
+      いつもお世話になっております。打ち合わせの日程をお知らせします。
+
+      よろしくお願いいたします。
+    after: |
+      件名: 打ち合わせの日程（10月13日）
+
+      いつもお世話になっております。打ち合わせの日程をお知らせします。
+
+      よろしくお願いいたします。
+  en:
+    config: { genre: business/email }
+    before: |
+      Subject: Following up on our conversation last week about the meeting room booking service and a visit
+
+      Dear facilities team,
+
+      I would like to visit your office.
+
+      Best regards,
+      Ichiro
+    after: |
+      Subject: Visit for the room booking service
+
+      Dear facilities team,
+
+      I would like to visit your office.
+
+      Best regards,
+      Ichiro
+not_flagged:
+  ja: 「件名：」の行が無いメールや手紙、引用した返信の中の件名は見ません。メール・手紙のジャンルでだけ見ます。
+  en: 'An email or letter without a "Subject:" line, and subjects inside a quoted reply, are not checked. Only the email and letter genre runs this rule.'
+level_meaning:
+  ja: 件名 {limit} 字まで
+  en: up to {limit} characters in the subject
+rewrite:
+  depth: light
+  ja:
+    direction: 件名を、用件と見分けの語（日付・案件名・期限）だけに縮めてください。経緯や理由は本文に移します。空の件名には、本文の用件を短く書きます。
+    pairs:
+      - before: 来週の火曜日に予定している会議室の予約サービスの導入に向けた打ち合わせの日程について
+        after: 打ち合わせの日程（10月13日）
+      - before: 先日お送りいただいた見積書の内容についての確認とご相談
+        after: 見積書の確認（10月分）
+    keep:
+      - 用件
+      - 日付・案件名・期限
+    avoid:
+      - 本文に無い用件を件名に書く
+      - 「至急」「重要」を足す
+  en:
+    direction: Cut the subject to the request and a distinguishing word (a date, a project, a deadline). Move the background into the body. For an empty subject, state the body's request briefly.
+    pairs:
+      - before: Following up on our conversation last week about the meeting room booking service and a visit
+        after: Visit for the room booking service
+      - before: Some questions about the quote you sent us and a few things we would like to discuss
+        after: Questions on the October quote
+    keep:
+      - the request
+      - dates, project names and deadlines
+    avoid:
+      - stating a request the body does not make
+      - adding "Urgent" or "Important"

package/rules/emoji-density.yaml

@@ -1,6 +1,6 @@
 id: emoji-density
 layer: L1
-status: experimental
+status: stable
 how_to_find: emoji-density
 severity: info
 
@@ -24,6 +24,8 @@ how_to_fix:
 levels: { strict: 3, normal: 8, relaxed: 20 }
 
 use_for: [blog, business, 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."
 sources: [zhang-2024]
 
 group: readability

package/rules/emoji-heading.yaml

@@ -1,6 +1,6 @@
 id: emoji-heading
 layer: L1
-status: experimental
+status: stable
 how_to_find: emoji-heading
 requires: [markdown]
 severity: info
@@ -25,6 +25,11 @@ how_to_fix:
 levels: { strict: 2, normal: 3, relaxed: 5 }
 
 use_for: [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."
 sources: [zhang-2024]
 
 group: ai-tells
@@ -100,6 +105,7 @@ level_meaning:
   ja: 絵文字の付いた見出しが {limit} 個あれば指摘
   en: reported once {limit} headings carry an emoji
 rewrite:
+  depth: light
   ja:
     direction: 見出しから絵文字を外し、節の中身が分かる言葉にしてください。絵文字が言っていたこと（注意、完了）が要るなら、本文の最初の文で言います。
     pairs:

package/rules/empty-intensifier.yaml

@@ -28,6 +28,9 @@ levels:
   relaxed: 3
 
 use_for: [blog, business, 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: wording
 summary:
@@ -48,6 +51,7 @@ level_meaning:
   ja: 当てはまる言い回しが {limit} 箇所あれば指摘
   en: reported once there are {limit}
 rewrite:
+  depth: light
   ja:
     direction: 強める語（「非常に」「言うまでもなく」）を消し、何がどう大事なのかが本文にあれば、それを主語と述語で書いてください。無ければ書き手に聞きます。
     pairs:

package/rules/empty-list-item.yaml

@@ -1,6 +1,6 @@
 id: empty-list-item
 layer: L1
-status: experimental
+status: stable
 how_to_find: empty-list-item
 requires: [markdown]
 severity: warning
@@ -57,6 +57,7 @@ not_flagged:
   ja: 見出しの語だけの項目は、同じ箇条書きのほかの項目に「見出し：値」の形が一つも無ければ指しません（記入用の書式）。下に入れ子の箇条書きや段落が続く項目（「手順：」の下に手順を並べたもの）も指しません。Markdown の箇条書きでだけ動きます。
   en: 'A label-only item is not reported when no other item in its list has a "label: value" form (a blank form to fill in). An item followed by a nested list or paragraph (a lead-in) is not reported. Markdown lists only.'
 rewrite:
+  depth: light
   ja:
     direction: 空の項目に入るものを本文から探して書いてください。本文に無ければ作らず、「未定」と書いて書き手に聞きます。中身の無い記号だけの項目は消します。
     pairs:

package/rules/empty-section.yaml

@@ -1,6 +1,6 @@
 id: empty-section
 layer: L1
-status: experimental
+status: stable
 how_to_find: empty-section
 requires: [markdown]
 severity: warning

package/rules/empty-table-cell.yaml

@@ -1,6 +1,6 @@
 id: empty-table-cell
 layer: L1
-status: experimental
+status: stable
 how_to_find: empty-table-cell
 requires: [markdown]
 severity: warning
@@ -61,6 +61,7 @@ not_flagged:
   ja: 一番左の列は見ません（空欄で「上と同じ」を表す書き方があるため）。同じ列に空欄が二つ以上ある列、本文の行が三つより少ない表、「—」「なし」と書いたセルは指しません。Markdown の表でだけ動きます。
   en: The first column is not checked, since a blank there often means "same as above". A column with two or more blanks, a table with fewer than three body rows, and a cell holding "—" or "none" are not reported. Markdown tables only.
 rewrite:
+  depth: light
   ja:
     direction: 空欄に入るものを本文から探して書いてください。本文に無ければ作らず、「未定」と書いて、決める人か時期を書き手に聞きます。
     pairs:

package/rules/excessive-hedging.yaml

@@ -1,6 +1,6 @@
 id: excessive-hedging
 layer: L2
-status: experimental
+status: stable
 how_to_find: hedging
 word_list: excessive-hedging
 # 1 つの文の重なりを数えるときの、それだけでは逃げていない包む言い方（「という状況です」、may）と、
@@ -35,6 +35,11 @@ how_to_fix:
 levels: { strict: 3, normal: 6, relaxed: 12 }
 
 use_for: [business, blog, 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."
+  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."
 sources: [femmer-2017]
 
 group: wording
@@ -56,6 +61,7 @@ level_meaning:
   ja: 1000 字あたり逃げの表現 {limit} 個まで（一文に重ねた逃げは、文書の長さによらず指摘）
   en: up to {limit} hedges per 1000 words (hedges stacked in one sentence are reported whatever the length)
 rewrite:
+  depth: light
   ja:
     direction: 重ねた逃げは一つだけ残すか、確かめたことなら全部外して言い切ってください。言い切れないなら、何が分かれば言い切れるかを書きます。
     pairs: