chaffjs 0.31.0 → 0.32.0

package/rules/reference-number-repeated.yaml

@@ -0,0 +1,63 @@
+id: reference-number-repeated
+layer: L3
+status: stable
+how_to_find: reference-number-repeated
+severity: warning
+
+name:
+  ja: 明細の表で、同じ領収書・請求書の番号が二つの行にある
+  en: The same receipt or invoice number on two rows of an itemised table
+
+why:
+  ja: 経費精算書や請求の明細では、一つの行が一枚の領収書や請求書で、その番号は表の中で一度しか出てきません。同じ番号が二つの行にあれば、同じ領収書を二度請求しているか、行を写して番号を直し忘れたかのどちらかです。どちらも、読み手は番号を一つずつ照らし合わせないかぎり気づきません。列は見出しの語（領収書番号、伝票番号、請求書番号、Receipt no.、Invoice no.、Ref.）だけで決めます。番号は数字を一つ以上含む升だけを読み、空の升、「-」、「なし」、「N/A」は番号として数えません。全角と半角、大文字と小文字、空白は同じ番号として比べます。
+  en: In an expense claim or an invoice's line items, each row is one receipt or invoice, and its number appears once in the table. The same number on two rows means either the same receipt is claimed twice or a row was copied and its number not changed. Neither is seen unless the reader checks the numbers one by one. The column is decided by its heading words alone (Receipt no., Invoice no., Voucher no., Ref.). Only cells holding at least one digit are read as numbers; a blank cell, a dash, "none" or "N/A" is not. Case, full-width and half-width forms and spaces are ignored when comparing.
+
+message:
+  ja: 「{heading}」の「{number}」は、{firstLine} 行目の行にもあります
+  en: '"{number}" in the column "{heading}" is already on line {firstLine}'
+
+how_to_fix:
+  ja: 二つの行が別の領収書なら正しい番号に直し、同じ領収書なら一方の行を消してください。
+  en: If the two rows are different receipts, correct the number; if they are the same receipt, remove one of the rows.
+
+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:
+  ja: 明細の表で、同じ領収書や請求書の番号が二つの行にある所
+  en: The same receipt or invoice number written on two rows of one itemised table
+example:
+  ja:
+    before: |
+      | 日付 | 領収書番号 | 内容 | 金額 |
+      | --- | --- | --- | --- |
+      | 2026年4月6日 | K-118 | 電車代 | 480円 |
+      | 2026年4月8日 | K-119 | 文具代 | 1,210円 |
+      | 2026年4月9日 | K-119 | タクシー代 | 2,350円 |
+    after: |
+      | 日付 | 領収書番号 | 内容 | 金額 |
+      | --- | --- | --- | --- |
+      | 2026年4月6日 | K-118 | 電車代 | 480円 |
+      | 2026年4月8日 | K-119 | 文具代 | 1,210円 |
+      | 2026年4月9日 | K-120 | タクシー代 | 2,350円 |
+  en:
+    before: |
+      | Date | Receipt no. | Description | Amount |
+      | --- | --- | --- | --- |
+      | April 6, 2026 | K-118 | Train fare | $12.40 |
+      | April 8, 2026 | K-119 | Stationery | $21.10 |
+      | April 9, 2026 | K-119 | Taxi | $35.50 |
+    after: |
+      | Date | Receipt no. | Description | Amount |
+      | --- | --- | --- | --- |
+      | April 6, 2026 | K-118 | Train fare | $12.40 |
+      | April 8, 2026 | K-119 | Stationery | $21.10 |
+      | April 9, 2026 | K-120 | Taxi | $35.50 |
+
+not_flagged:
+  ja: 見出しが領収書・伝票・請求書の番号の語でない列（科目のコード、口座番号、日付、「番号」だけの列）は読みません。番号の列が二つ以上ある表も読みません。数字を含まない升（空、「-」、「なし」、「N/A」）は比べません。二つ以上の番号が繰り返す表や、一つの番号が三つ以上の行にある表は、一枚の伝票の行をまとめて書いた表（請求書とその入金、一枚の領収書の内訳）なので比べません。表が違えば同じ番号でもかまいません。
+  en: 'A column whose heading is not a receipt, voucher or invoice number word (a category code, an account number, a date, a bare "No.") is not read, nor is a table with two such columns. A cell with no digit (blank, a dash, "none", "N/A") is not compared. A table where two or more numbers repeat, or one number is on three rows or more, groups the rows of one slip (an invoice and its payment, the parts of one receipt) and is not compared. The same number in two different tables is fine.'

package/rules/reference-number-variant.yaml

@@ -0,0 +1,81 @@
+id: reference-number-variant
+layer: L3
+status: stable
+how_to_find: reference-number-variant
+word_list: reference-label
+# The labels (予約番号, Booking number, 発注番号, Student number) and what each labels come from the language's reference-label lexicon; numbers after
+# labels of different kinds (a booking number and a confirmation number) are never compared.
+languages: [ja, en]
+severity: warning
+
+name:
+  ja: 予約番号などの文字の入れ違い
+  en: Booking or reference number with two characters swapped
+
+why:
+  ja: 予約確認書や受付の控えでは、予約番号や受付番号が冒頭と、キャンセルや問合せの案内とに何度も書かれます。一か所だけ「MN-48215」が「MN-48251」になっていると、読み手はどちらを伝えればよいか分からず、違う番号を伝えると予約が見つかりません。隣り合う二つの文字の入れ違いは、打ち間違いで最も多い形です。「予約番号」「受付番号」のような同じ種類の語のすぐ後ろに書いた番号どうしを比べ、隣り合う二つの文字だけが入れ違った番号を指します。
+  en: "A confirmation or a receipt writes its booking number more than once: at the top, and again where it says how to cancel or whom to call. When one place reads MN-48251 for MN-48215, the reader cannot tell which to quote, and the wrong one finds no booking. Two neighbouring characters swapped is the commonest slip in typing a number. chaff compares the numbers written right after labels of the same kind (Booking number, Confirmation number) and reports one that is another with two neighbouring characters swapped."
+
+message:
+  ja: 番号「{written}」は、「{other}」の隣り合う文字が入れ違っています
+  en: "The number {written} is {other} with two neighbouring characters swapped"
+
+messages:
+  substituted:
+    ja: ナンバー「{written}」は、この文書の車のナンバー「{other}」と一連番号の一文字だけが違います
+    en: "The plate {written} differs from this document's plate {other} in one character of its serial"
+
+how_to_fix:
+  ja: 正しい番号を確かめて、もう一方を直してください。
+  en: Check which number is right and correct the other.
+
+levels: { strict: error, normal: warning, relaxed: warning }
+
+options:
+  listed_kinds:
+    kind: words
+    default: [item]
+    about:
+      ja: 文書が多くを並べる番号の種類（reference-label の group）。この種類の、語の後ろや表にある番号どうしは比べず、語の無い番号だけを比べる
+      en: Kinds of number a document lists many of (reference-label groups). Two labelled or tabled numbers of such a kind are never compared; only one with no label is
+
+use_for: [business, technical, blog, legal, docs, academic, literature, speech]
+off_for:
+  literature: A story's booking numbers are made up and need not agree; one may differ on purpose.
+  speech: A transcript writes what was said, numbers misspoken and corrected included.
+
+group: facts
+summary:
+  ja: 同じ文書で、予約番号などの隣り合う文字が入れ違っている所（MN-48215 と MN-48251）
+  en: A booking number written once with two neighbours swapped (MN-48215, MN-48251)
+example:
+  ja:
+    before: |
+      # ご予約の確認
+
+      予約番号：MN-48215
+
+      ご連絡の際は、予約番号 MN-48251 をお伝えください。
+    after: |
+      # ご予約の確認
+
+      予約番号：MN-48215
+
+      ご連絡の際は、予約番号 MN-48215 をお伝えください。
+  en:
+    before: |
+      # Your booking
+
+      Booking number: MN-48215
+
+      When you call, please give your booking number, MN-48251.
+    after: |
+      # Your booking
+
+      Booking number: MN-48215
+
+      When you call, please give your booking number, MN-48215.
+
+not_flagged:
+  ja: 「予約番号」「受付番号」「予約確認番号」「お問い合わせ番号」「社員番号」「学籍番号」「発注番号」「見積番号」「請求書番号」「患者番号」「契約番号」「登録番号」「口座番号」「証券番号」のような語のすぐ後ろ（間は空白と「：」「、」や開き括弧だけ）にある、数字を4つ以上含む英数字の並びだけを番号と見ます。発注番号は取引先の番号を書き写すこともありますが、同じ種類の語の番号どうしで隣り合う二文字だけが入れ違ったものしか指さないので、別の注文の番号は指しません。「原契約番号」「基本契約番号」「旧契約番号」「変更契約番号」「親契約番号」は別の契約の番号を引く語なので、文書自身の「契約番号」とは比べません。「登録番号」「受講番号」は参加者の登録の番号、「申込番号」は申込みの番号として、互いに比べません。「振込先口座番号」「振込元口座番号」は振込の相手の口座の番号を書く語なので、口座自身の「口座番号」とは比べません。「契約者番号」は契約者その人の番号で、証券番号とは見ません。語の無い番号（下に書く品番の形のものを除く）、種類の違う番号（学籍番号と社員番号、予約番号と受付番号、請求書番号と注文番号、見積番号と注文番号や請求書番号、登録番号と申込番号）、一文字だけ違う番号、離れた文字の入れ違い、二か所以上入れ違った番号は指しません。自動車のナンバー（ひばり野 330 ね 48-15）の形に合う並びは、語が「登録番号」でも自動車のナンバーとして読みます。ナンバーだけは、文書が一台の車のことを書いているとき（その車のナンバーを「登録番号：」のような語と番号だけの行に一つだけ書き、ほかのナンバーは一つだけで、その語が文の初めにあるとき。「代車の登録番号」のように語の前に語があれば別の車と見ます）に限って、地名・分類番号・かなが同じで一連番号が一文字だけ違うものも指します。「ナンバー」だけの語や英語の「Registration」だけの語は、ナンバーの語として読みません。「品番」「商品コード」「品目コード」は商品の番号の語です。表の行や列の見出しにこの語を書いた升の品番も、語の後ろの品番と同じに読みます。語の無い品番（「GP-0521の替芯」）は、英字と「-」と数字4つ以上の形（GP-0521）のときだけ、語の後ろか表にある品番のちょうど一つと隣り合う二文字だけが入れ違っていれば指します。その書き方の品番が文書のどこかで語の後ろか表にあれば、別の商品の品番と見て指しません（カタログの表に並ぶ AB-1234 と AB-1243 は二つの商品です）。語の後ろや表にある品番どうしも、別の商品の品番として比べません（この扱いをする種類は listed_kinds で決めます）。二つ以上の品番のどれとも読めるもの、英字や「-」の無い番号（48251）も指しません。「会員番号」「会員ID」の会員の番号と、「お客様番号」の番号は、別の番号になり得るので比べません。語のすぐ後ろの番号を「HM 5520 8137」のように空白一つずつで区切って書いたときは、続く並びがどれも4文字以上の大文字と数字で数字を含む間を一つの番号と読み、行の終わりや、語（「の方」「2名」）の前で止めます。
+  en: "Only letters and digits right after a label (booking number, reservation number, confirmation number, reference number, employee number, student number, PO number, quote or estimate number, invoice number, patient number, contract or agreement number, registration number, account number, policy number), with nothing but spaces, a colon, a comma or an opening bracket between, are read, and only when they hold four digits or more. A PO number may be the buyer's, copied from another document, but only two numbers of one kind that differ by two neighbours swapped are reported, so a different order's number is not. An original, master, former, amended or parent contract number (and an amendment number) cites another contract, so it is never compared with the document's own contract number. A registration number labels an attendee's registration and an application number an application, so the two are never compared. A payee's, beneficiary's, payer's or sender's account number labels the other side of a transfer, so it is never compared with the account's own account number; a policyholder number is not read as a policy number. Unlabelled codes (but for item codes, below), numbers of different kinds (a student number and an employee number, a booking number and an order number, an invoice number and an order number, a quote number and an order or invoice number, a registration number and an application number), numbers that differ in one character, swaps of characters that are not neighbours and numbers with more than one swap are not reported. A bare quote is not read as a label, since it is also a verb (quote your PO number). A plate number, number plate or licence plate is a vehicle's and is never compared with a registration number; a bare Registration label is not read as a plate, since an attendee's registration is written so too. An item code, item no., SKU or product code labels an item; a code in a table under such a label, in its row or its column, is read as if written after it. A code with no label (Refills for GP-0521) is reported only in the shape letters, a hyphen and four digits or more, and only when it is exactly one labelled or tabled code with two neighbours swapped. When the document labels or tables that writing itself anywhere, it is another item and is not reported (a catalog's AB-1234 and AB-1243 are two items), and two labelled or tabled item codes are never compared with each other (listed_kinds names the kinds read so); nor is a code two labelled codes swap to, or a number with no letters or hyphen (48251). A member number or member ID and a customer number may be different numbers, so they are never compared. A number written in groups one space apart (HM 5520 8137) is read as one while each further group is four or more capitals and digits holding a digit, stopping at the line's end or before a word or a short count (expires, 100 copies)."

package/rules/reference-title-mismatch.yaml

@@ -28,7 +28,7 @@ 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
+  en: A reference's title ("Section 5 (Privacy)") that differs from the heading
 example:
   ja:
     before: |

package/rules/reference-topic-missing.yaml

@@ -28,7 +28,7 @@ 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
+  en: A reference that names a topic ("see Section 2 for pricing") never found there
 example:
   ja:
     before: |

package/rules/reference-unit-mismatch.yaml

@@ -0,0 +1,62 @@
+id: reference-unit-mismatch
+layer: L3
+status: stable
+how_to_find: reference-unit
+extra_word_lists: [lab-result-column]
+# The result, reference range and unit columns are found by the language's lab-result-column and reference-unit-column
+# lexicons, and the units are read with reference-unit (a group is one unit: mg/dL and mg/dl, ×10⁴/µL and 万/µL).
+languages: [ja, en]
+severity: error
+
+name:
+  ja: 検査結果の単位が基準値の単位と違う
+  en: A test result in another unit than its reference range
+
+why:
+  ja: 健康診断や血液検査の結果の表で、結果を「64 mmol/L」、同じ行の基準値を「40〜96 mg/dL」と書くと、数を比べても基準の内か外かは分かりません。単位を写し間違えたか、別の検査機関の値を貼ったときに起きます。見出しが「結果」「基準値」の列（語は言語パッケージの語彙表 lab-result-column と reference-unit-column）を行ごとに読み、二つの升の単位（語彙表 reference-unit）を比べます。升に単位が無ければ、列の見出しの括弧の中の単位、次にその行の「単位」の列を使います。基準値の列が二つ（男性・女性）あれば、それぞれと比べます。mg/dL と mg/dl、×10⁴/µL と 万/µL のように、書き方が違っても数を換算せずに比べられる単位は同じ単位と読みます。
+  en: 'When a results table writes a result as "52 mmol/L" and the reference range on the same row as "40–60 mg/dL", the numbers cannot be compared, and the reader cannot tell whether the result is in range. It happens when a unit is copied wrong or a value is pasted from another lab. Each row of a table whose headings name a result and a reference range (the language package''s lab-result-column and reference-unit-column lexicons) is read, and the units of the two cells (the reference-unit lexicon) are compared. A cell without a unit takes a unit in brackets in its column heading, then the row''s Unit column. Two reference range columns (men and women) are each compared. Two ways of writing one unit, which compare without converting the number (mg/dL and mg/dl, ×10³/µL and ×10⁹/L), are read as the same unit.'
+
+message:
+  ja: 「{item}」の結果「{result}」の単位が、基準値「{range}」の単位と違います
+  en: 'The result "{result}" for "{item}" is in another unit than its reference range "{range}"'
+
+how_to_fix:
+  ja: 検査機関の報告と照らして、結果か基準値の単位を直すか、同じ単位に換算して書いてください。
+  en: Check the lab's report and correct the unit of the result or of the range, or convert one so both use the same unit.
+
+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:
+  ja: 検査結果の表で、結果と基準値の単位が違う行
+  en: A results table row whose result and reference range are in different units
+example:
+  ja:
+    before: |
+      | 項目 | 結果 | 基準値 |
+      | --- | --- | --- |
+      | HDLコレステロール | 64 mmol/L | 40〜96 mg/dL |
+    after: |
+      | 項目 | 結果 | 基準値 |
+      | --- | --- | --- |
+      | HDLコレステロール | 64 mg/dL | 40〜96 mg/dL |
+  en:
+    before: |
+      | Test | Result | Reference range |
+      | --- | --- | --- |
+      | Creatinine | 0.82 mmol/L | 0.57–1.11 mg/dL |
+    after: |
+      | Test | Result | Reference range |
+      | --- | --- | --- |
+      | Creatinine | 0.82 mg/dL | 0.57–1.11 mg/dL |
+
+not_flagged:
+  ja: 結果か基準値のどちらかに単位が無く、行の単位の列にも列の見出しにも無いとき、語彙表 reference-unit に無い単位、数の無い升（陰性、—）は比べません。結果か基準値の升に換算した値を並べて書き（「5.5 mmol/L（99 mg/dL）」）、どれか一つの単位が合えば言いません。見出しが「結果」と「基準値」の列を持たない表は読みません。
+  en: 'A row where the result or the range has no unit, in its cell, in its column heading or in the row''s Unit column, a unit that is not in the reference-unit lexicon, and a cell without a number ("Negative", "—") are not compared. A cell that also gives a converted value ("5.5 mmol/L (99 mg/dL)") is fine when any of its units matches. A table without a result column and a reference range column is not read.'
+level_meaning:
+  ja: 検査結果と基準値の単位が違うとき指摘
+  en: reported when a result and its reference range are in different units

package/rules/relative-date-mismatch.yaml

@@ -28,7 +28,7 @@ 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
+  en: A date given as "two weeks later, on May 16" that is not that far away
 example:
   ja:
     before: |

package/rules/request-without-deadline.yaml

@@ -38,7 +38,7 @@ off_for:
 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
+  en: A request ("Please send …") with no deadline and no one named to do it
 example:
   ja:
     before: |
@@ -60,8 +60,8 @@ example:
       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.
+  ja: 確認・返信・提出のように、済んだかどうかが後で分かる動作を頼む文だけを見ます。「ご了承ください」のような心構えの依頼と、「ご不明な点があれば、ご連絡ください」のような条件付きの申し出と、「ご質問はメールでお送りください」のような質問を受け付ける申し出は見ません。期限か担当が、その文か次の文にあれば指しません。ビジネスの文書でだけ動きます。
+  en: Only requests for an action whose completion can be checked (review, reply, send) are read. Courtesy requests, conditional offers ("If you have questions, let me know") and open offers ("Please send any questions to me") are not. A deadline or owner in the same or the next sentence is enough. Business documents only.
 rewrite:
   depth: light
   ja:

package/rules/required-listed-as-preferred.yaml

@@ -41,7 +41,7 @@ off_for:
 group: structure
 summary:
   ja: 求人で、必須に挙げた資格や経験を歓迎にも挙げている所
-  en: A skill or qualification in a job posting listed both as required and as preferred
+  en: A job posting that lists one skill both as required and as preferred
 example:
   ja:
     before: |

package/rules/required-sections.yaml

@@ -27,8 +27,8 @@ use_for: [business, blog, technical, legal, docs, academic, literature, speech]
 
 group: team
 summary:
-  ja: チームが必須と決めた見出し（「リスク」「費用」など）が無い文書。chaff.yaml の required_sections に書いた見出しだけを見ます
-  en: A heading the team requires (such as "Risks" or "Cost") missing from the document, from required_sections in chaff.yaml
+  ja: チームが必須と決めた見出し（「リスク」「費用」など）が無い文書。chaff.yaml で決めます
+  en: A heading the team requires (such as "Risks") missing, set in chaff.yaml
 example:
   ja:
     config: { required_sections: [リスク] }

package/rules/requirement-modal.yaml

@@ -65,8 +65,8 @@ sources: [jis-z8301-2019, plain-2011]
 
 group: team
 summary:
-  ja: 規格・規程の文末が、チームの選んだ決まり（JIS Z 8301:2019 など）と違う所。options で決めたときだけ見ます
-  en: A provision's verb form that the house rule the team picked does not use ("shall" under the Federal Plain Language Guidelines); checked only when options pick one
+  ja: 規格・規程の文末が、チームの選んだ決まり（JIS Z 8301 など）と違う所（選んだときだけ）
+  en: A requirement's verb ("must", "shall") that the team's house rule does not use
 example:
   ja:
     before: |

package/rules/requirement-smell.yaml

@@ -58,7 +58,7 @@ sources: [femmer-2017, berry-2003, iso-29148]
 group: wording
 summary:
   ja: 仕様書や契約書の要求の文にある「可能な限り」「必要に応じて」「等」「及び／又は」
-  en: '"As far as possible", "if necessary", "etc." or "and/or" in a requirement of a specification or a contract'
+  en: '"As far as possible", "if necessary", "etc." or "and/or" in a requirement'
 example:
   ja:
     before: |

package/rules/revision-direction-mismatch.yaml

@@ -0,0 +1,66 @@
+id: revision-direction-mismatch
+layer: L3
+status: stable
+how_to_find: revision-direction
+# The words of revision are revision-direction (rise, fall; the verbs rise-verb and fall-verb only with a word of its
+# group forecast in their sentence); the labels of the previous and the revised forecast are
+# revision-column (previous, revised).
+severity: warning
+
+name:
+  ja: 修正の向きと表の数字が逆
+  en: A forecast revision that moves the other way
+
+why:
+  ja: 業績予想の修正で「上方修正します」と書いた下の表で、今回の予想が前回の予想より小さいと、読み手は文と表のどちらを信じればよいか分かりません。去年の発表文を写して数字だけ差し替えたときや、表の列を入れ違えたときに起きます。前回の予想の列（前回発表予想・前回予想）と今回の予想の列（今回修正予想・今回予想）を持つ表、またはその二つを行に持つ表と、同じ節（見出しから次の見出しまで）に書いた修正の向きの語（上方修正・増額修正・下方修正・減額修正。「引き上げ」「引き下げ」は同じ文に「予想」「見通し」があるときだけ）を比べます。向きの語の文が項目（売上高・営業利益）を名指していればその項目を（「営業利益（百万円）」は括弧を除いた「営業利益」でも名指したことにします）、名指していなければ表の最初の項目を見ます。
+  en: 'When a release says the forecast is "revised upward" and the table below it shows a revised figure lower than the previous one, readers cannot tell whether to believe the sentence or the table. It happens when last year''s release is copied and only the figures are replaced, or when the columns are swapped. A table with a column of the previous forecast (Previous forecast) and one of the revised forecast (Revised forecast), or a row of each, is compared with the word of revision in the same section, from a heading to the next (revised upward, revised downward; raised, lowered and cut only with forecast, guidance or outlook in their sentence). When the sentence of the word names items (net sales, operating profit; "Operating profit (loss)" is named without its brackets too) those items are checked; when it names none, the first item of the table is.'
+
+message:
+  ja: 「{word}」と書いていますが、「{item}」は前回の {previous} から今回の {revised} へ逆に動いています
+  en: '"{word}" is written, but {item} goes the other way, from {previous} to {revised}'
+
+how_to_fix:
+  ja: 修正の向きの語と、表の前回・今回の数字のどちらが正しいかを確かめて、ほかを直してください。項目によって向きが違うなら、項目ごとに書いてください（「売上高を下方修正し、営業利益を上方修正します」）。
+  en: Check whether the word of revision or the previous and revised figures are right, and correct the other. If the items move different ways, say so item by item ("we lower net sales and raise operating profit").
+
+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:
+  ja: 「上方修正」と書いたのに、表の今回の予想が前回より小さい所
+  en: A forecast said to be revised up whose new figure is lower, or the reverse
+example:
+  ja:
+    before: |
+      通期の業績予想を上方修正します。
+
+      | 項目 | 前回予想 | 今回予想 |
+      | --- | --- | --- |
+      | 売上高 | 5,200 | 5,000 |
+    after: |
+      通期の業績予想を下方修正します。
+
+      | 項目 | 前回予想 | 今回予想 |
+      | --- | --- | --- |
+      | 売上高 | 5,200 | 5,000 |
+  en:
+    before: |
+      We are revising upward the full-year forecast.
+
+      | Item | Previous forecast | Revised forecast |
+      | --- | --- | --- |
+      | Net sales | 5,200 | 5,000 |
+    after: |
+      We are revising downward the full-year forecast.
+
+      | Item | Previous forecast | Revised forecast |
+      | --- | --- | --- |
+      | Net sales | 5,200 | 5,000 |
+
+not_flagged:
+  ja: 節の中に上へと下への向きの語が両方ある節、向きの語の無い節、前回と今回の列（行）が一つずつ無い表は比べません。名指した項目が上と下の両方に動いているとき（向きの語がどの項目のことか決まらない）、升が数でない（「―」「未定」）とき、前回と今回の升に書いた単位が違うとき、値が変わっていないときは言いません。項目を名指さない文では、表の最初の項目だけを見ます（二つ目からの項目が逆に動いていても言いません）。
+  en: 'A section with words of both directions, a section with no word of revision, and a table without exactly one previous and one revised column (or row) are not compared. Named items that moved both ways (the word cannot be tied to one of them), a cell that is not a number ("-", "TBD"), cells written in different units and an unchanged figure are not reported. A sentence that names no item is checked against the first item of the table only; later items that move the other way are not reported.'

package/rules/risk-disclosure.yaml

@@ -43,7 +43,7 @@ use_for: [business]
 group: structure
 summary:
   ja: よい面だけを書き、リスクや弱みに触れていない提案（AI に読ませる検査）
-  en: A proposal that gives only the upside and never mentions a risk (checked by an AI)
+  en: A proposal that gives only the upside and no risk (read by an AI)
 example:
   ja:
     before: |

package/rules/running-balance-mismatch.yaml

@@ -0,0 +1,59 @@
+id: running-balance-mismatch
+layer: L3
+status: stable
+how_to_find: running-balance
+severity: warning
+
+name:
+  ja: 残高が前の行から計算した値と合わない
+  en: A running balance the row above and this row's amounts do not give
+
+why:
+  ja: 返済予定表の「お支払後の残高」、通帳や入出金明細の「残高」、在庫表の「在庫」は、前の行の残高にその行の動きを足し引きした値です。読み手は引き算し直さずに信じます。一つの行の数字だけを直したとき、桁を打ち間違えたとき、行を別の表から写したときに食い違います。どの列が残高で、どの列がその行の動きかは、列の見出しの語（残高、元金、返済額、利息、入金、出金、Balance、Principal、Payment、Interest、Deposit、Withdrawal）だけで決めます。列の並びでは決めません。元金の列があれば、残高は前の行の残高から元金を引いた値です。元金の列が無く、利息の列も無ければ、支払額を引いた値です。入金と出金の列のある表では、前の行の残高に入金を足し、出金を引いた値です（空の升と「-」は0）。書いた数はどれも、最後の桁の半分までの丸めを認めます。言うのは表ごとに最初に合わない行だけです。一つの行の残高を打ち間違えると次の行も合わなくなるので、そこで止めます。
+  en: 'The "balance after payment" of a repayment schedule, the "balance" of a bank statement and the "on hand" of a stock card are the row above''s balance moved by this row. Readers trust them without doing the subtraction again. They go wrong when one figure of a row is corrected and the balance is not, when a digit is mistyped, or when a row is copied from another table. Which column is the balance and which holds a row''s movement is decided by the heading words alone (Balance, Principal, Payment, Interest, Deposit, Withdrawal), never by where a column stands. With a principal column, the balance is the row above''s less the principal. With no principal column and no interest column, it is the row above''s less the payment. With deposit and withdrawal columns, it is the row above''s plus the deposit less the withdrawal (a blank cell or a dash is zero). Every written number may be rounded to half its last digit. Only the first row of a table that does not add up is reported: a mistyped balance makes the next row fail too, so the check stops there.'
+
+message:
+  ja: 残高「{balance}」は、前の行の残高とこの行の金額からは {computed} です
+  en: 'The balance "{balance}" is written, but the row above and this row give {computed}'
+
+how_to_fix:
+  ja: この行と前の行の残高、この行の金額のどれが正しいかを確かめて、ほかを直してください。
+  en: Check which of this balance, the one above it and this row's amounts is right, and correct the others.
+
+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:
+  ja: 返済表や明細の残高が、前の行の残高からの足し引きと合わない所
+  en: A running balance that is not the balance above plus or minus this row's amounts
+example:
+  ja:
+    before: |
+      | 回 | お支払額 | うち元金 | うち利息 | お支払後の残高 |
+      | --- | --- | --- | --- | --- |
+      | 1 | 32,826円 | 27,426円 | 5,400円 | 1,772,574円 |
+      | 2 | 32,826円 | 27,508円 | 5,318円 | 1,754,066円 |
+    after: |
+      | 回 | お支払額 | うち元金 | うち利息 | お支払後の残高 |
+      | --- | --- | --- | --- | --- |
+      | 1 | 32,826円 | 27,426円 | 5,400円 | 1,772,574円 |
+      | 2 | 32,826円 | 27,508円 | 5,318円 | 1,745,066円 |
+  en:
+    before: |
+      | No. | Payment | Balance after payment |
+      | --- | --- | --- |
+      | 1 | $104.00 | $2,392.00 |
+      | 2 | $104.00 | $2,298.00 |
+    after: |
+      | No. | Payment | Balance after payment |
+      | --- | --- | --- |
+      | 1 | $104.00 | $2,392.00 |
+      | 2 | $104.00 | $2,288.00 |
+
+not_flagged:
+  ja: 残高の列が一つに決まらない表、元金の列も支払額の列も入出金の列も無い表、利息の列があって元金の列が無い表、返済の列と入出金の列の両方がある表、日付の列も回（番号）の列も無い表（口座ごと・品目ごとの一覧かもしれない）、「入出金」のように一つの列が両方の向きを書く表は比べません。残高や金額の升が数でない行（—、▲1,000、(1,000)）、単位の書き方が違う行、合計の行は比べず、次の行からまた数え始めます。入金と出金がどちらも空の行（前月繰越）も、そこから数え始めます。回の列の番号が増えていかない表、返済の表で残高が最後の行のほうが大きい表（並びが逆）は比べません。丸めで届く差は言いません。
+  en: "A table whose balance column is not one, with no principal, payment, deposit or withdrawal column, with an interest column but no principal column, with both loan and deposit columns, or with no date or row-number column (its rows may be accounts or items, not times), or with one column for both directions (Deposit/Withdrawal) is not compared. A row whose balance or amount cell is not a number (—, -1,000, (1,000)), whose amounts are written with different units, or that is a total row is skipped, and the count starts again from the next row; so does a row with both deposit and withdrawal blank (brought forward). A table whose row numbers do not rise, or a repayment table whose last balance is larger than its first (rows in reverse), is not compared. A difference the rounding can reach is not reported."

package/rules/scaled-quantity-mismatch.yaml

@@ -31,7 +31,7 @@ off_for:
 group: facts
 summary:
   ja: 人数ごとの列を持つ材料の表で、一行だけ比のとおりに増えていない量
-  en: An ingredients table with a column per number of servings where one row does not scale
+  en: A recipe table with one row that does not scale with the servings
 example:
   ja:
     before: |

package/rules/serial-range-reversed.yaml

@@ -0,0 +1,52 @@
+id: serial-range-reversed
+layer: L3
+status: stable
+how_to_find: serial-range
+# serial-label names the codes on the line; the joints are range-connector, range-opener, range-closer and quantity-range-word;
+# quantity-change-word (its ungrouped words) makes a pair a change.
+severity: warning
+
+name:
+  ja: 製造番号やロットの範囲の終わりが始まりより小さい
+  en: A serial or lot number range that ends below where it starts
+
+why:
+  ja: 「製造番号：A2400〜A1800」「ロット番号：K0430〜K0410」のように、番号の範囲の終わりが始まりより小さいと、読み手は自分の製品が範囲に入るのかを確かめられません。回収のお知らせでは、対象の製品を見落とすか、対象外の製品まで問い合わせが来ることになります。片方の番号だけを書き換えたとき、二つを入れ替えて書いたときに起きます。英字と数字の番号を二つ、範囲の記号（〜、–）か「から … まで」でつないだものを、同じ行の前に「製造番号」「シリアル」「ロット」「バッチ」のある所だけ読みます。英字とハイフンと数字の桁数が両端でそろうときだけ数字を比べます（A2400 と A1800。A2400 と B0100 は別の系列なので比べません）。
+  en: 'When a range of serial or lot numbers ends below where it starts ("Serial numbers: B3900 to B3100", "Lots L5240 through L5210"), the reader cannot tell whether their product is in it. In a recall notice, affected units are missed or unaffected owners call in. It happens when only one of the two numbers is edited, or when they are written the wrong way round. Two letter-and-digit codes joined by a range mark (–, —), "to" or "through" are read only when "serial", "lot", "batch" or "S/N" stands earlier on the line. The numbers are compared only when both codes have the same letters, the same hyphen and the same number of digits (B3900 and B3100; B3900 and C0100 are different series).'
+
+message:
+  ja: 番号の範囲「{range}」の終わりが始まりより小さくなっています
+  en: 'The number range "{range}" ends below where it starts'
+
+how_to_fix:
+  ja: 範囲の二つの番号を確かめて、書き間違えたほうを直すか、小さいほうから書いてください。
+  en: Check both numbers, and correct the wrong one or write the smaller one first.
+
+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:
+  ja: 「製造番号：A2400〜A1800」のように、番号の範囲の終わりが始まりより小さい所
+  en: 'A serial or lot number range that ends below its start, such as "L5240 to L5210"'
+example:
+  ja:
+    before: |
+      製造番号：A2400〜A1800
+    after: |
+      製造番号：A1800〜A2400
+  en:
+    before: |
+      Serial numbers: B3900 to B3100
+    after: |
+      Serial numbers: B3100 to B3900
+
+not_flagged:
+  ja: 「製造番号」「ロット」などの語の無い行の番号（部品表の品番は並べた順のことがあります）、英字や桁数の違う二つの番号（A2400〜B0100）、読点で並べた番号（A2400、A1800）、数字が二桁以下の番号、「変更」など値を変える語のある文は比べません。
+  en: 'Codes on a line without "serial", "lot", "batch" or "S/N" (part numbers in a parts list may be an order), two codes with different letters or numbers of digits (A2400 to B0100), codes listed with a comma (A2400, A1800), codes with fewer than three digits, and a sentence with a word of change ("changed", "reduced") are not compared.'
+level_meaning:
+  ja: 製造番号やロットの範囲の終わりが始まりより小さいとき指摘
+  en: reported when a serial or lot number range ends below where it starts

package/rules/share-amount-mismatch.yaml

@@ -0,0 +1,58 @@
+id: share-amount-mismatch
+layer: L3
+status: stable
+how_to_find: share-amount
+# The total, share and payment words, and the step a unit may be rounded to, come from the language's share-amount-label
+# lexicon. The arithmetic (rate × total, rounded down, to nearest or up) is tax-mismatch's.
+extra_word_lists: [share-amount-label]
+severity: warning
+
+name:
+  ja: 負担額が合計に負担の割合を掛けた額と合わない
+  en: An amount paid that is not the stated share of the total
+
+why:
+  ja: 医療費の明細書や領収書で、負担割合が3割、合計が10,000円なら、払う額は3,000円です。負担額がこれと合わないと、患者は払いすぎか払い足りないかを確かめられません。合計を直して負担額を直し忘れたとき、別の患者の額を写したとき、割合を取り違えたときに起きます。表なら、見出しが合計・負担割合・負担額を言う列の、同じ行の三つの升で比べます。負担割合の列が無ければ、負担額の見出しの括弧（自己負担額（3割））か、文書に一つだけ書いた「負担割合：3割」の割合を使います。表でなければ、同じ節の「合計：」の行と、その下の「自己負担額：」の行で比べます。3割は30%と読みます。
+  en: 'On a medical bill or receipt, a 30% patient share of a $600.00 total is $180.00. When the amount paid is not that, the patient cannot tell whether they paid too much or too little. It happens when the total is corrected and the share is not, when another patient''s amount is copied, or when the share is mixed up. In a table, the three cells of one row are compared, in the columns whose headings name the total, the share and the amount paid. With no share column, the rate in brackets in the amount''s heading (Your share (30%)) or the one share the document states on a line of its own (Patient share: 30%) is used. Outside a table, a "Total:" line is compared with a "Your share:" line below it in the same section.'
+
+message:
+  ja: 負担額「{written}」が、合計「{base}」の{rate}（{expected}）と合いません
+  en: "The amount {written} is not {rate} of the total {base} ({expected})"
+
+how_to_fix:
+  ja: 合計と負担の割合を確かめて、負担額を計算し直してください。
+  en: Check the total and the share, and work the amount out again.
+
+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:
+  ja: 医療費の明細で、負担額が合計の3割（30%）などと合わない所
+  en: An amount paid on a medical bill that is not the stated share (30%) of the total
+example:
+  ja:
+    before: |
+      | 合計 | 負担割合 | 負担額 |
+      | --- | --- | --- |
+      | 10,000円 | 3割 | 3,300円 |
+    after: |
+      | 合計 | 負担割合 | 負担額 |
+      | --- | --- | --- |
+      | 10,000円 | 3割 | 3,000円 |
+  en:
+    before: |
+      | Total charges | Patient share | Amount paid |
+      | --- | --- | --- |
+      | $600.00 | 30% | $108.00 |
+    after: |
+      | Total charges | Patient share | Amount paid |
+      | --- | --- | --- |
+      | $600.00 | 30% | $180.00 |
+
+not_flagged:
+  ja: 端数は切り捨て・四捨五入・切り上げのどれでも、円の位でも合っていると読み、円の金額は10円の位に丸めた額も合っていると読みます。合計の列や行が無いもの、払う額の列や行が二つ以上あるもの、割合が読めないもの（文書に違う割合が二つあるもの）、合計と負担額の単位が違うもの（点と円）は比べません。「請求額」「お支払額」の列は、同じ行に負担割合の升があるときだけ比べます。表でない行は、合計の行が負担額の行より下にあれば比べません。文の中に書いた額は読みません。
+  en: 'Rounding down, to the nearest or up, to the cent or to the unit, is read as right, and an amount in yen may also be rounded to 10 yen. Nothing is compared with no total column or line, with two amount columns or lines, with no share to read (or two different shares stated in the document), or with the total and the amount in different units. An "Amount paid" or "Amount due" column is compared only beside a share cell on the same row. Outside a table, a total line below the amount line is not compared. An amount written in a sentence is not read.'

package/rules/share-over-hundred.yaml

@@ -27,7 +27,7 @@ use_for: [business, technical, blog, legal, docs, academic, literature, speech]
 group: facts
 summary:
   ja: 「回答者の120%」のように、集まりの一部の割合なのに 100% を超える百分率
-  en: A percentage that is a share of a group but passes 100%, such as "120% of respondents"
+  en: A share of a group over 100%, such as "120% of respondents"
 example:
   ja:
     before: 調査では、回答者の120%が満足と答えました。

package/rules/shell-prompt-mix.yaml

@@ -33,7 +33,7 @@ off_for:
 group: consistency
 summary:
   ja: シェルのブロックで、「$」のプロンプトを付けたコマンドと付けないコマンドが混ざっている所
-  en: Shell blocks that write commands with a "$" prompt in some places and without it in others
+  en: Shell commands written with a "$" prompt in some places and without in others
 example:
   ja:
     config: { genre: docs/manual }

package/rules/space-before-punctuation.yaml

@@ -28,7 +28,7 @@ use_for: [business, technical, blog, legal, docs, academic, literature, speech]
 group: slips
 summary:
   ja: 英文の「word .」「word ,」のように、句読点の前に空白がある所
-  en: A space before a period, comma, semicolon, question mark or exclamation mark, as in "word ."
+  en: A space before a period, comma or other mark, as in "word ."
 example:
   en:
     before: |