chaffjs 0.20.0 → 0.22.0

package/rules/colon-lead-in.yaml

@@ -1,6 +1,6 @@
 id: colon-lead-in
 layer: L1
-status: experimental
+status: stable
 how_to_find: colon-lead-in
 # English human writing hands off to a list after a colon as a matter of course: two in a short self-written English
 # document already passed any limit that the generated-style samples reached. Japanese only until a limit separates them.
@@ -27,6 +27,11 @@ how_to_fix:
 levels: { strict: 1, normal: 2, relaxed: 4 }
 
 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:
@@ -58,6 +63,7 @@ level_meaning:
   ja: コロンで箇条書きへ渡す文が 1000 字あたり {limit} 個まで
   en: "colon lead-ins to lists: up to {limit} per 1000 characters"
 rewrite:
+  depth: structure
   ja:
     direction: コロンで箇条書きへ渡す所のうち、項目が二つか三つで互いに繋がっているものを文に戻してください。手順や部品の一覧は箇条書きのままにします。
     pairs:

package/rules/concrete-evidence-density.yaml

@@ -25,6 +25,12 @@ how_to_fix:
 levels: { strict: 1, normal: 3, relaxed: 6 }
 
 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."
+  speech: "A speech opens with greetings and closes with thanks: that is its form, not padding."
 
 group: structure
 summary:

package/rules/contraction-consistency.yaml

@@ -1,6 +1,6 @@
 id: contraction-consistency
 layer: L2
-status: experimental
+status: stable
 how_to_find: contraction-mix
 word_list: contraction
 languages: [en]
@@ -26,6 +26,9 @@ how_to_fix:
 levels: { strict: 4, normal: 2, relaxed: 1 }
 
 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: consistency
 summary:

package/rules/contrast-framing.yaml

@@ -1,6 +1,6 @@
 id: contrast-framing
 layer: L2
-status: experimental
+status: stable
 how_to_find: contrast-framing
 word_list: contrast-frame
 # 打ち消し（it's not）と、それを返す語（it's、but）。後ろに返しが来たときだけ対比の枠になる。
@@ -30,6 +30,11 @@ levels:
   en: { strict: 2, normal: 3, relaxed: 6 }
 
 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:
@@ -56,6 +61,7 @@ level_meaning:
   ja: 1000 字あたり対比の枠 {limit} 個まで
   en: up to {limit} contrast frames per 1000 words
 rewrite:
+  depth: light
   ja:
     direction: 打ち消している側（X）を消し、言いたい側（Y）を普通の文で書いてください。X が誰かの実際の誤解なら、その誤解を書いたうえで一度だけ打ち消してください。
     pairs:

package/rules/cross-doc-duplicate-definition.yaml

@@ -0,0 +1,70 @@
+id: cross-doc-duplicate-definition
+layer: L3
+status: experimental
+how_to_find: cross-doc-duplicate-definition
+# documents: compares the files of one run, so it runs only when chaff is given two or more files, or a folder.
+requires: [structure, documents]
+# The words that make a sentence a definition (をいう, means), per language.
+extra_word_lists: [definition-statement]
+severity: warning
+
+name:
+  ja: ファイルによって違う定義
+  en: One term defined differently in different files
+
+why:
+  ja: 契約書の束や説明書では、同じ語をいくつものファイルで定義することがあります（本契約と別紙、用語集と各ページ）。後から一方だけを直すと、ファイルによって定義が食い違い、どちらの意味で読めばよいか分からなくなります。一度に渡したファイルどうしで、同じ語の定義（「『X』とは、…をいう」"X" means …）の、語の後ろの言葉を比べ、多くのファイルと違う言葉で定義したファイルを指します。全角半角、空白、両端の句読点の違いは問いません。言葉が違っても意味が同じかは機械では決まらないので、確かめる場所を示すだけです。
+  en: 'A bundle of contracts or a manual often defines the same term in several files (the agreement and its schedule, the glossary and the pages). When one is changed later and the other is not, the files disagree on what the term means. Across the files given together, the words after the term in each definition ("X" means …, 「X」とは、…をいう) are compared, and a file that defines the term in other words than most files do is pointed out. Width, spaces and the punctuation at either end do not count. Whether two wordings mean the same is not something a machine can decide, so chaff only shows where to look.'
+
+message:
+  ja: 「{term}」を、一緒に見たほかの {count} ファイルと違う言葉で定義しています（例：{example}）
+  en: '"{term}" is defined in other words than in {count} other {count|file|files} checked with it (as in {example})'
+
+how_to_fix:
+  ja: 定義を一か所（用語集や本契約）にまとめ、ほかのファイルからはそこを参照してください。意味を変えているなら、別の語にします。
+  en: Keep the definition in one place (the glossary, the main agreement) and refer to it from the other files. If the meaning is meant to differ, use a different term.
+
+placeholders:
+  term:
+    ja: 〇〇
+    en: the term
+
+levels: { strict: error, normal: warning, relaxed: info }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+
+group: structure
+summary:
+  ja: 同じ語を、ファイルによって違う言葉で定義している所
+  en: The same term defined in other words in different files
+example:
+  ja:
+    other: |
+      # 用語集
+
+      「メンバー」とは、ワークスペースに招かれた人のことです。
+    before: |
+      # はじめに
+
+      「メンバー」とは、料金を払った人のことです。
+    after: |
+      # はじめに
+
+      「メンバー」とは、ワークスペースに招かれた人のことです。
+  en:
+    other: |
+      # Glossary
+
+      "Member" means a person invited to a workspace.
+    before: |
+      # Getting started
+
+      "Member" means a person who pays the fee.
+    after: |
+      # Getting started
+
+      "Member" means a person invited to a workspace.
+
+not_flagged:
+  ja: 範囲を限った定義（「この条において『X』とは」）と、語の後ろに意味を書かない定義（「以下『X』という。」）は比べません。一つのファイルの中で二度定義した語は、最初の定義で比べます（二度目は duplicate-definition が見ます）。全角半角、空白、両端の句読点だけが違う定義は同じとみなします。
+  en: Definitions limited to a part ("In this section, X means") and those that give the meaning before the term ('(the "Vendor")') are not compared. A file that defines a term twice is compared by its first definition (duplicate-definition reports the second). Definitions that differ only in width, spaces or the punctuation at either end are taken as the same.

package/rules/cross-doc-fact-conflict.yaml

@@ -0,0 +1,64 @@
+id: cross-doc-fact-conflict
+layer: L3
+status: experimental
+how_to_find: cross-doc-fact-conflict
+# documents: compares the files of one run, so it runs only when chaff is given two or more files, or a folder.
+requires: [quantities, documents]
+uses: [pos]
+severity: warning
+
+name:
+  ja: ファイルによって違う値が書いてある項目
+  en: One item given different values in different files
+
+why:
+  ja: 説明書や文書の束では、料金・版・締切・問い合わせ先のような同じ項目を、いくつものページに書きます。値を直したときに一つのページだけ直し忘れると、ページによって値が食い違い、読み手はどれを信じればよいか分かりません。一度に渡したファイルどうしで、「項目：値」「項目は値です」と書いた所と表の升を読み、同じ項目名（全角半角、大文字小文字は揃えて比べます）に、同じ単位で違う値を書いたファイルを指します。メールアドレスと、三つ以上に区切った版（2.4.1、v3）も値として読みます。どちらが正しいかは決めず、その値を書いたファイルの少ないほうを指します。
+  en: 'A manual or a bundle of documents repeats the same items, such as a fee, a version, a deadline or a contact address, on page after page. When a value changes and one page is missed, the pages disagree and the reader cannot tell which to trust. Across the files given together, values written as "Item: value" or "The item is value", and table cells, are read; a file that gives the same item name (case and width aside) a different value in the same unit is pointed out. Email addresses and versions of three parts or more (2.4.1, v3) are read as values too. chaff does not decide which is right; it points at the value fewer files give.'
+
+message:
+  ja: 「{label}」が {value} と書かれていますが、一緒に見たほかの {count} ファイルでは {other} です（例：{example}）
+  en: '"{label}" is {value} here, but {other} in {count} other {count|file|files} checked with it (as in {example})'
+
+how_to_fix:
+  ja: どちらの値が正しいかを確かめて、違うほうを直してください。別のもの（別のプラン、別の版）の値なら、項目名にそれを書き分けてください（「プロプランの月額料金」）。
+  en: Check which value is right and correct the other. If they are values of different things (another plan, another release), say so in the item name ("Pro plan monthly fee").
+
+levels: { normal: warning, relaxed: info }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+
+group: facts
+summary:
+  ja: 同じ項目（料金、版、締切、問い合わせ先）に、ファイルによって違う値を書いた所
+  en: The same item (a fee, a version, a deadline, a contact address) given different values in different files
+example:
+  ja:
+    other: |
+      # 料金
+
+      月額料金：1,200円
+    before: |
+      # よくある質問
+
+      月額料金：1,500円
+    after: |
+      # よくある質問
+
+      月額料金：1,200円
+  en:
+    other: |
+      # Pricing
+
+      Monthly fee: $12
+    before: |
+      # Questions
+
+      Monthly fee: $15
+    after: |
+      # Questions
+
+      Monthly fee: $12
+
+not_flagged:
+  ja: 一つのファイルの中で同じ項目に二つ以上の値を書いたファイルは数えません（プランごとの料金のような一覧か、ファイルの中の食い違いで、そちらは fact-conflict が見ます）。ファイルどうしで値が三通り以上に分かれる項目も、一覧と読んで何も言いません。単位の違う値、記録の欄（同じ名前が行の頭に何度も出る欄）、値の後ろに条件が続くもの（「1,200円から」）も比べません。
+  en: A file that gives an item two or more values is not counted (it is a list, such as a fee per plan, or a conflict within the file, which fact-conflict reports). An item whose values split three or more ways across the files is read as a list and left alone. Values in different units, record fields (the same name at the start of many lines), and values followed by a condition ("$12 per seat") are not compared.

package/rules/currency-notation-consistency.yaml

@@ -0,0 +1,77 @@
+id: currency-notation-consistency
+layer: L2
+status: stable
+how_to_find: currency-notation
+severity: info
+
+name:
+  ja: 通貨の書き方が混ざっている
+  en: A currency written two ways
+
+why:
+  ja: 同じ通貨の金額を「1,000円」と「¥1,000」、「$20」と「USD 20」のように二通りに書くと、読み手は別の通貨か、別の扱いの金額かと迷います。見積もりや資料を寄せ集めたときに起きます。どの書き方が正しいかは決めず、通貨ごとに文書の中で少ないほうを指します。
+  en: When one currency is written two ways in one document ("$20" and "USD 20", "1,000円" and "¥1,000"), the reader wonders whether a different currency or a different kind of amount is meant. It happens when quotes and notes are pasted together. chaff does not decide which way is right; for each currency it points at the way the document uses less.
+
+message:
+  ja: 「{written}」と書いています（この文書はこの通貨をふつう「{usual}」のように書きます。{of} 箇所のうち {count} 箇所が違う）
+  en: '"{written}" here, where the document usually writes this currency like "{usual}" ({count} of {of})'
+
+how_to_fix:
+  ja: 文書の多いほうの書き方に合わせてください。チームで決めているなら、STYLE.md に書いておくと迷いません。
+  en: Match the way the rest of the document writes the currency. If the team has decided, write it in the style guide.
+
+# 少ないほうが、その通貨の金額の何パーセントまでなら「混ざっている」と見るか。これを超えたら、文書が使い分けている。
+levels: { strict: 49, normal: 34, relaxed: 20 }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+
+group: consistency
+summary:
+  ja: 「1,000円」と「¥1,000」、「$20」と「USD 20」のように、一つの文書で同じ通貨の金額を二通りに書いている所
+  en: One currency written two ways in one document, such as "$20" and "USD 20", or "1,000円" and "¥1,000"
+example:
+  ja:
+    before: |
+      基本料金は 3,000円、追加料金は 500円、送料は 800円 です。割引は ¥200 です。
+    after: |
+      基本料金は 3,000円、追加料金は 500円、送料は 800円 です。割引は 200円 です。
+  en:
+    before: |
+      The base fee is $300, the add-on is $50 and shipping is $20. The discount is USD 10.
+    after: |
+      The base fee is $300, the add-on is $50 and shipping is $20. The discount is $10.
+
+not_flagged:
+  ja: 通貨ごとに比べるので、円とドルが並ぶのは混ざりではありません。少ないほうがその通貨の金額の三分の一を超える文書は、使い分けている（表は USD、本文は $）と読んで言いません。二つの書き方が同じ数のときも言いません。コードの中は読みません。
+  en: Each currency is compared with itself, so dollars beside yen is not a mix. When the less common way is over a third of that currency's amounts, the document is read as using both on purpose (USD in tables, $ in prose) and nothing is reported; nor when the two ways are equally common. Code is not read.
+level_meaning:
+  ja: 少ないほうの書き方が、その通貨の金額の {limit}% 以下のとき指摘
+  en: reported when the less common way is {limit}% of that currency's amounts or less
+
+rewrite:
+  ja:
+    direction: その通貨の金額を、文書で多いほうの書き方にそろえてください。数と桁はそのまま残します。
+    pairs:
+      - before: 送料は 800円 です。割引は ¥200 です。
+        after: 送料は 800円 です。割引は 200円 です。
+      - before: 月額 $20、年額 USD 200 です。
+        after: 月額 $20、年額 $200 です。
+    keep:
+      - 金額の数と桁
+      - どの通貨か
+    avoid:
+      - 別の通貨に換算してしまう
+      - 表の通貨の書き方まで本文に合わせて崩す
+  en:
+    direction: Write the currency's amounts the way the document mostly does. Keep the numbers as they are.
+    pairs:
+      - before: Shipping is $20. The discount is USD 10.
+        after: Shipping is $20. The discount is $10.
+      - before: The fee is 500 yen, or ¥450 if paid early.
+        after: The fee is 500 yen, or 450 yen if paid early.
+    keep:
+      - the numbers and their magnitude
+      - which currency each amount is in
+    avoid:
+      - converting an amount to another currency
+      - changing the way a table writes it to match the prose

package/rules/cushion-phrase-density.yaml

@@ -1,6 +1,6 @@
 id: cushion-phrase-density
 layer: L2
-status: experimental
+status: stable
 how_to_find: cushion-density
 word_list: cushion-phrase
 uses: [pos]
@@ -25,6 +25,12 @@ how_to_fix:
 levels: { strict: 2, normal: 5, relaxed: 10 }
 
 use_for: [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."
+  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:
@@ -51,6 +57,7 @@ level_meaning:
   ja: 1000 字あたりクッション言葉 {limit} 個まで
   en: up to {limit} softeners per 1000 words
 rewrite:
+  depth: light
   ja:
     direction: クッション言葉は最初の一つだけ残し、あとは用件（何を、いつまでに）から書いてください。敬語の丁寧さは変えません。
     pairs:

package/rules/dangling-figure-reference.yaml

@@ -1,6 +1,6 @@
 id: dangling-figure-reference
 layer: L3
-status: experimental
+status: stable
 how_to_find: dangling-figure
 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/dangling-participle.yaml

@@ -0,0 +1,58 @@
+id: dangling-participle
+layer: L3
+status: stable
+how_to_find: dangling-opener
+requires: [pos]
+languages: [en]
+severity: info
+
+name:
+  ja: 主語の無い分詞の句
+  en: Dangling participle
+
+why:
+  ja: 英語で分詞の句から始めた文（Having reviewed the code, …）は、句の動作をしたのが文の主語だと読まれます。主語が形だけの it や there だと（Having reviewed the code, it is ready.）、コードを見たのが誰なのか文に書かれていません。読み手は一瞬つまずき、意味を補って読むことになります。-ing の分詞の句の直後の主語が it か there で、be が続く形だけを指します。
+  en: 'A sentence that opens with a participle phrase ("Having reviewed the code, …") is read as if the subject did that action. When the subject is an empty "it" or "there" ("Having reviewed the code, it is ready."), the sentence never says who reviewed the code, and the reader has to supply it. Only an opening "-ing" phrase followed by "it" or "there" and a form of "be" is reported.'
+
+message:
+  ja: 「{opener}」の動作をしたのが誰か、文に書かれていません（主語が「{subject}」）
+  en: '"{opener}" has no one to attach to; the subject is an empty "{subject}"'
+
+how_to_fix:
+  ja: 動作をした人を主語にするか（Having reviewed the code, we think it is ready.）、句を節にしてください（After we reviewed the code, it was ready.）。
+  en: Make whoever did the action the subject ("Having reviewed the code, we consider it ready."), or turn the phrase into a clause ("After we reviewed the code, it was ready.").
+
+levels: { strict: warning, normal: info, relaxed: info }
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+off_for:
+  literature: "A narrator and a character speak as they speak, and loose openings are part of a voice."
+  speech: "A transcript keeps the speaker's words."
+
+group: wording
+summary:
+  ja: 英語で、「Having reviewed the code, it is ready.」のように、分詞の句の後ろの主語が形だけの it や there の文
+  en: 'A participle phrase followed by an empty "it" or "there", as in "Having reviewed the code, it is ready."'
+
+example:
+  en:
+    before: Having reviewed the logs, it is clear that the job failed twice.
+    after: Having reviewed the logs, we found that the job failed twice.
+
+not_flagged:
+  ja: 主語が人や物の名詞の文（Having reviewed the code, the team approved it.）、過去分詞で始めた句（Configured with SSO, it is ready.。it そのものを言うことが多い）、決まった言い方として読む句（Given、Based on、Generally speaking、Having said that）、挿入句の it is（Testing it, it is worth noting, requires …）、分詞の句が長く読点の位置が当てにならない文は指しません。英語の文だけを読みます。
+  en: 'A sentence whose subject is a person or a thing ("Having reviewed the code, the team approved it."), an opening past participle ("Configured with SSO, it is ready.", which usually describes "it" itself), openings read as fixed phrases ("Given", "Based on", "Generally speaking", "Having said that"), a parenthetical "it is" ("Testing it, it is worth noting, requires …"), and long openings where the comma cannot be trusted are not reported. Only English sentences are read.'
+
+rewrite:
+  depth: light
+  en:
+    direction: Give the participle phrase a subject that did its action, or turn the phrase into a clause with its own subject. Keep what the sentence says.
+    pairs:
+      - before: Having reviewed the logs, it is clear that the job failed twice.
+        after: Having reviewed the logs, we found that the job failed twice.
+      - before: Looking at the totals, there is a gap of 40 hours.
+        after: Looking at the totals, we see a gap of 40 hours.
+    keep:
+      - what the sentence says and its figures
+    avoid:
+      - inventing who did the action when the document does not say

package/rules/dangling-reference.yaml

@@ -1,6 +1,6 @@
 id: dangling-reference
 layer: L3
-status: experimental
+status: stable
 how_to_find: dangling-reference
 requires: [structure]
 severity: error
@@ -25,6 +25,8 @@ how_to_fix:
 levels: { normal: error, relaxed: warning }
 
 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."
 sources: [jis-z8301-2019, femmer-2017]
 
 group: structure

package/rules/date-format-consistency.yaml

@@ -1,8 +1,8 @@
 id: date-format-consistency
 layer: L1
-status: experimental
+status: stable
 how_to_find: date-format
-severity: warning
+severity: info
 
 name:
   ja: 日付の書き方が揃っていない
@@ -59,6 +59,7 @@ level_meaning:
   ja: 少ないほうの書き方の日付が全体の {limit}% 以下なら指摘
   en: reported while the minority style is {limit}% of the dates or less
 rewrite:
+  depth: light
   ja:
     direction: 指された日付を、文書の多いほうの書き方（指摘が例に引く日付の書き方）に書き直してください。日付そのもの（年・月・日）は変えません。
     pairs:

package/rules/date-order.yaml

@@ -1,6 +1,6 @@
 id: date-order
 layer: L3
-status: experimental
+status: stable
 how_to_find: date-order
 requires: [dates]
 severity: warning
@@ -24,6 +24,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."
 sources: [de-marneffe-2008]
 
 group: facts

package/rules/date-range-reversed.yaml

@@ -1,6 +1,6 @@
 id: date-range-reversed
 layer: L3
-status: experimental
+status: stable
 how_to_find: date-range-reversed
 requires: [dates]
 severity: warning
@@ -24,6 +24,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/date-weekday-mismatch.yaml

@@ -1,6 +1,6 @@
 id: date-weekday-mismatch
 layer: L3
-status: experimental
+status: stable
 how_to_find: date-weekday-mismatch
 requires: [dates]
 severity: error
@@ -24,6 +24,8 @@ how_to_fix:
 levels: { normal: error, relaxed: warning }
 
 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/date-without-year.yaml

@@ -1,12 +1,12 @@
 id: date-without-year
 layer: L1
-status: experimental
+status: stable
 how_to_find: date-without-year
 requires: [dates]
 # The dates come from the language package's date reader. English does not read a date written without its year yet,
 # so the rule checks Japanese only until it does.
 languages: [ja]
-severity: warning
+severity: info
 
 name:
   ja: 年の無い日付
@@ -28,7 +28,7 @@ how_to_fix:
   ja: 年を書いてください（2027年1月15日）。
   en: Write the year (January 15, 2027).
 
-levels: { strict: error, normal: warning, relaxed: info }
+levels: { strict: warning, normal: info, relaxed: info }
 
 use_for: [business, technical, blog, legal, docs, academic, literature, speech]
 
@@ -55,6 +55,7 @@ not_flagged:
   ja: 年を一度だけ書いて、あとの日付は月と日だけで書く文書（年の無い日付のほうが多い文書）は、書き方の選び方として指しません。ただしその場合も、年をまたぐ日付は指します。月だけ・年だけの日付は見ません。
   en: A document that writes the year once and the rest as month and day (more yearless dates than dated ones) is a style, and not reported, except for a date across the turn of a year. Month-only and year-only dates are not checked.
 rewrite:
+  depth: light
   ja:
     direction: 指摘された日付に年を書き足してください。年は本文のほかの日付と、曜日から確かめます。決められなければ、作らずに［年］と空けて書き手に聞きます。
     pairs:

package/rules/defined-name-repeated.yaml

@@ -0,0 +1,97 @@
+id: defined-name-repeated
+layer: L3
+status: stable
+how_to_find: defined-name-repeated
+requires: [structure, pos]
+severity: info
+
+name:
+  ja: 短い呼び名を定めた名前を、あとで正式の名前のまま書いている
+  en: A long name used again after its short name was defined
+
+why:
+  ja: 「株式会社みなと製作所（以下「甲」という。）」と定めたら、そのあとは「甲」と書くのが決まりです。途中で「株式会社みなと製作所」と書き戻すと、読み手は甲と同じ会社なのか、別の立場の同じ会社なのかを確かめることになります。文の途中で括弧に入れて短い呼び名を定めた所の、括弧のすぐ前の名前（名詞と固有名詞の並び）を正式の名前とし、定義より後でその名前が出てくる所を指します。署名欄のように、呼び名と並べて書いた行や名前だけの行は見ません。
+  en: 'Once a contract says "Harbour Works Ltd (the "Supplier")", it refers to the Supplier as "the Supplier". Writing "Harbour Works Ltd" again later makes the reader check whether it is the same party in the same role. chaff takes the name right before an inline definition''s bracket (a run of nouns and names) as the long name, and points at each later use of it. Lines that give the short name too, or little more than the name (a signature block), are not read.'
+
+message:
+  ja: 「{name}」は {line} 行目で「{term}」と呼ぶと定めた名前です
+  en: '"{name}" was given the short name "{term}" on line {line}'
+
+how_to_fix:
+  ja: 定めた呼び名で書いてください。正式の名前が要る所（署名欄、別の会社と並べる所）なら、そのままにします。
+  en: Use the short name the contract defined. Where the full name is needed (a signature block, a list beside other companies), leave it.
+
+levels: { strict: warning, normal: info, relaxed: info }
+
+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."
+
+group: consistency
+summary:
+  ja: 「株式会社みなと製作所（以下「甲」という。）」のあとで、甲を正式の名前のまま書いている所
+  en: A party or a thing given a short name ("the Supplier") and later written out in full again
+example:
+  ja:
+    config: { genre: legal/contract }
+    before: |
+      # 業務委託契約書
+
+      株式会社みなと製作所（以下「甲」という。）と北浜商事株式会社（以下「乙」という。）は、次のとおり契約を結ぶ。
+
+      第1条　乙は、株式会社みなと製作所の会議室の予約を代わりに行う。
+    after: |
+      # 業務委託契約書
+
+      株式会社みなと製作所（以下「甲」という。）と北浜商事株式会社（以下「乙」という。）は、次のとおり契約を結ぶ。
+
+      第1条　乙は、甲の会議室の予約を代わりに行う。
+  en:
+    config: { genre: legal/contract }
+    before: |
+      # Services Agreement
+
+      This agreement is between Harbour Works Ltd (the "Supplier") and North Trading Inc (the "Customer").
+
+      1. The Customer pays Harbour Works Ltd within thirty days of each invoice.
+    after: |
+      # Services Agreement
+
+      This agreement is between Harbour Works Ltd (the "Supplier") and North Trading Inc (the "Customer").
+
+      1. The Customer pays the Supplier within thirty days of each invoice.
+
+not_flagged:
+  ja: 短い呼び名を定める前の使用、呼び名と同じ行にある使用、名前だけの行（署名欄）、四字に満たない名前（「法律」）、一語の英語の名前、呼び名が名前を含むもの（「本サービス」）、前の語が絞り込む名前（「妊娠中の女性従業員」「本利用規約」）、それ自体が定義した語である名前、長い語の一部（「株式会社みなと製作所大阪支店」）は見ません。法務のジャンルで見ます。
+  en: 'Uses before the short name is defined, uses on a line that also gives the short name, lines holding little more than the name (a signature block), names shorter than four characters, one-word English names, short names that contain the long one, names narrowed by the word before them ("the Beta Preview"), names that are defined terms themselves, and a name inside a longer word are not reported. The legal genres run this rule.'
+rewrite:
+  depth: light
+  ja:
+    direction: 正式の名前を、定めた呼び名に置き換えてください。署名欄や、ほかの会社と並べて正式の名前が要る所はそのままにします。どちらの立場の名前か分からなければ、書き手に確かめます。
+    pairs:
+      - before: 乙は、株式会社みなと製作所の会議室の予約を代わりに行う。
+        after: 乙は、甲の会議室の予約を代わりに行う。
+      - before: 個人情報の保護に関する法律に従って扱う。
+        after: 個人情報保護法に従って扱う。
+    keep:
+      - 条の番号と中身
+      - 署名欄の正式の名前
+    avoid:
+      - 甲と乙を取り違える
+      - 署名欄の名前を呼び名に変える
+  en:
+    direction: Replace the full name with the short name the contract defined. Leave it where the full name is needed, such as a signature block or a list beside other companies. If it is not clear which party is meant, ask the writer.
+    pairs:
+      - before: The Customer pays Harbour Works Ltd within thirty days.
+        after: The Customer pays the Supplier within thirty days.
+      - before: North Trading Inc may end this agreement on notice.
+        after: The Customer may end this agreement on notice.
+    keep:
+      - the clause numbers and their content
+      - the full names in the signature block
+    avoid:
+      - swapping the parties
+      - turning a signature block's name into the short name