chaffjs 0.20.0 → 0.21.0

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-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

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: