chaffjs 0.32.0 → 0.34.0

package/rules/number-without-unit.yaml

@@ -65,8 +65,8 @@ example:
       | Taxi | $100 |
 
 not_flagged:
-  ja: ほかの値に二つ以上、同じ一つの単位が付いているときだけ指します。単位の無い値のほうが多い列、単位が混ざる列（分と時間）、数でない値（未定）は見ません。表の見出しの単位（「金額（円）」）は読みません。
-  en: Reported only when at least two other values carry one and the same unit. A column where bare numbers are the majority, one that mixes units (minutes and hours), and values that are not numbers (TBD) are not checked. A unit written in the header ("Amount ($)") is not read.
+  ja: ほかの値に二つ以上、同じ一つの単位が付いているときだけ指します。単位の無い値のほうが多い列、単位が混ざる列（分と時間）、数でない値（未定）は見ません。表の見出しの単位（「金額（円）」）は読みません。数量の列で、ほかの値が借りる期間（4日、2泊）のとき、単位の無い整数（チャイルドシート 1）は個数なので指しません。
+  en: Reported only when at least two other values carry one and the same unit. A column where bare numbers are the majority, one that mixes units (minutes and hours), and values that are not numbers (TBD) are not checked. A unit written in the header ("Amount ($)") is not read. In a Quantity column whose other values are a hired period (4 days, 2 nights), a bare whole number (Child seat | 1) is a count of pieces and is not reported.
 rewrite:
   depth: light
   ja:

package/rules/orthographic-variant.yaml

@@ -4,7 +4,7 @@ status: stable
 how_to_find: orthographic-variant
 # 語の一覧は持たない。文書の中の語を、日本語は辞書の形の読み（出来る・できる はどちらもデキル）で、カタカナ語は小さい字と「ー」を
 # ならした形で、英字は大文字小文字とハイフンを外した形で束ね、同じ語の書き方が二つあれば少ないほうを指す。
-# 読みが同じで意味の違う語（成る・なる）は lang-ja の orthographic-variant-distinct に並べて外す。
+# 読みが同じで意味の違う語（成る・なる）は lang-ja の orthographic-variant-distinct に並べて外す。genres を付けた語はそのジャンルだけで外す。
 uses: [pos]
 severity: info
 
@@ -56,8 +56,8 @@ example:
       Send the form by email. We answer every email within a day. Attach the receipt to the email.
 
 not_flagged:
-  ja: 読みが同じでも漢字の違う語（書く・描く）、補助動詞・形式名詞と本来の使い方の書き分け（見て下さい・資料を下さい）、書き分けが意味の違いになる語（成る・なる、言う・いう）、語末の「ー」だけの違い（katakana-long-vowel が見ます）、鉤括弧や引用符の中、語の直後のふりがなの括弧の中（HTTP（えいちてぃーてぃーぴー））、chaff.yaml の names に書いた名前は見ません。名詞に続けて書いたかなの名詞（全員ぶん）と慣用句の動詞（気をつける）は、同じ読みの語（文、名札を付ける）と別に比べます。英字は、頭の字の大文字小文字（Email と email）と、大文字だけの語（強調や略語）、大文字の名前に語尾が付いた語（関数名の SENDs）、同じ文の略語の字を示した語（CLIPER と並ぶ CLImatology）を書き方の違いにしません（HBase のような名前の大文字は比べます）。少ないほうが三分の一を超えるときも言いません。文学のジャンルでは既定で止めています（その時代の書き方のため）。
-  en: The case of a word's first letter (Email, email; Long-Term, long-term) is not a spelling, nor is a word in capitals only (emphasis or an acronym), nor a name in capitals with an ending (SENDs, OPENed), nor the letters of an acronym picked out beside it (CLImatology next to CLIPER). A name spelled with capitals (HBase) is still compared. Hyphenated words that are another word (re-sign, resign), part of an address (github.com), anything in quotation marks, a Japanese reading in brackets right after a word (HTTP（えいちてぃーてぃーぴー）) and the team's names are not compared. Nothing is reported when the minority is more than a third. The literature preset turns it off, since old spelling belongs to its time.
+  ja: 読みが同じでも漢字の違う語（書く・描く）、補助動詞・形式名詞と本来の使い方の書き分け（見て下さい・資料を下さい）、書き分けが意味の違いになる語（成る・なる、言う・いう。法務のジャンルでは、法令の書き方で書き分ける 時・とき と 物・もの も）、語末の「ー」だけの違い（katakana-long-vowel が見ます）、鉤括弧や引用符の中、語の直後のふりがなの括弧の中（HTTP（えいちてぃーてぃーぴー））、chaff.yaml の names に書いた名前は見ません。名詞に続けて書いたかなの名詞（全員ぶん）と慣用句の動詞（気をつける）は、同じ読みの語（文、名札を付ける）と別に比べます。英字は、頭の字の大文字小文字（Email と email）と、大文字だけの語（強調や略語）、大文字の名前に語尾が付いた語（関数名の SENDs）、同じ文の略語の字を示した語（CLIPER と並ぶ CLImatology）を書き方の違いにしません（HBase のような名前の大文字は比べます）。少ないほうが三分の一を超えるときも言いません。文学のジャンルでは既定で止めています（その時代の書き方のため）。
+  en: The case of a word's first letter (Email, email; Long-Term, long-term) is not a spelling, nor is a word in capitals only (emphasis or an acronym), nor a name in capitals with an ending (SENDs, OPENed), nor the letters of an acronym picked out beside it (CLImatology next to CLIPER). A name spelled with capitals (HBase) is still compared. In Japanese, words whose kanji and kana forms mean different things (成る and なる) are not compared, and in the legal genres neither are 時 and とき or 物 and もの, which legal drafting writes apart. Hyphenated words that are another word (re-sign, resign), part of an address (github.com), anything in quotation marks, a Japanese reading in brackets right after a word (HTTP（えいちてぃーてぃーぴー）) and the team's names are not compared. Nothing is reported when the minority is more than a third. The literature preset turns it off, since old spelling belongs to its time.
 level_meaning:
   ja: 少ないほうが語の {limit}% 以下のとき指摘
   en: reported when the minority spelling is {limit}% of the word's uses or less

package/rules/reference-number-variant.yaml

@@ -34,7 +34,7 @@ levels: { strict: error, normal: warning, relaxed: warning }
 options:
   listed_kinds:
     kind: words
-    default: [item]
+    default: [item, model]
     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
@@ -77,5 +77,5 @@ example:
       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)."
+  ja: 「予約番号」「受付番号」「予約確認番号」「お問い合わせ番号」「社員番号」「学籍番号」「発注番号」「見積番号」「請求書番号」「患者番号」「契約番号」「登録番号」「口座番号」「証券番号」のような語のすぐ後ろ（間は空白と「：」「、」や開き括弧だけ）にある、数字を4つ以上含む英数字の並びだけを番号と見ます。発注番号は取引先の番号を書き写すこともありますが、同じ種類の語の番号どうしで隣り合う二文字だけが入れ違ったものしか指さないので、別の注文の番号は指しません。「原契約番号」「基本契約番号」「旧契約番号」「変更契約番号」「親契約番号」は別の契約の番号を引く語なので、文書自身の「契約番号」とは比べません。「登録番号」「受講番号」は参加者の登録の番号、「申込番号」は申込みの番号として、互いに比べません。「振込先口座番号」「振込元口座番号」は振込の相手の口座の番号を書く語なので、口座自身の「口座番号」とは比べません。「契約者番号」は契約者その人の番号で、証券番号とは見ません。語の無い番号（下に書く品番の形のものを除く）、種類の違う番号（学籍番号と社員番号、予約番号と受付番号、請求書番号と注文番号、見積番号と注文番号や請求書番号、登録番号と申込番号）、一文字だけ違う番号、離れた文字の入れ違い、二か所以上入れ違った番号は指しません。自動車のナンバー（ひばり野 330 ね 48-15）の形に合う並びは、語が「登録番号」でも自動車のナンバーとして読みます。ナンバーだけは、文書が一台の車のことを書いているとき（その車のナンバーを「登録番号：」のような語と番号だけの行に一つだけ書き、ほかのナンバーは一つだけで、その語が文の初めにあるとき。「代車の登録番号」のように語の前に語があれば別の車と見ます）に限って、地名・分類番号・かなが同じで一連番号が一文字だけ違うものも指します。「ナンバー」だけの語や英語の「Registration」だけの語は、ナンバーの語として読みません。「品番」「商品コード」「品目コード」は商品の番号の語です。表の行や列の見出しにこの語を書いた升の品番も、語の後ろの品番と同じに読みます。語の無い品番（「GP-0521の替芯」）は、英字と「-」と数字4つ以上の形（GP-0521）のときだけ、語の後ろか表にある品番のちょうど一つと隣り合う二文字だけが入れ違っていれば指します。その書き方の品番が文書のどこかで語の後ろか表にあれば、別の商品の品番と見て指しません（カタログの表に並ぶ AB-1234 と AB-1243 は二つの商品です）。語の後ろや表にある品番どうしも、別の商品の品番として比べません（この扱いをする種類は listed_kinds で決めます）。二つ以上の品番のどれとも読めるもの、英字や「-」の無い番号（48251）も指しません。「会員番号」「会員ID」の会員の番号と、「お客様番号」の番号は、別の番号になり得るので比べません。語のすぐ後ろの番号を「HM 5520 8137」のように空白一つずつで区切って書いたときは、続く並びがどれも4文字以上の大文字と数字で数字を含む間を一つの番号と読み、行の終わりや、語（「の方」「2名」）の前で止めます。「型番」は製品の型番の語で、品番と同じく、語の後ろや表にある型番どうしは比べません。製品の文書（回収のお知らせや保証書）が自分の製品として名指す番号（題名にある番号、「型番：」「商品コード：」のような語と番号だけの行の番号、表で型番や品番の語を書いた升の番号）がちょうど一つのときに限り、「-」の前に英字が二つ以上あり、数字が二つ以上の短い番号（NH-805、FT-38）も読み、文書に一度だけ書いた、その番号の隣り合う二文字が入れ違った番号（NH-850）を指します。そう名指す番号が二つ以上ある文書（カタログ）、表にある番号、二度以上書いた番号、その番号と同じ行にある番号（「NH-805 と NH-850」）、「予約番号」のような別の種類の語の後ろの番号、英字一つの番号（A-12）は指しません。
+  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). A model, model number or model no. labels a product's model, and, as with item codes, two labelled or tabled models are never compared. When a product document (a recall, a warranty) names exactly one code as its own (in its title, on a line holding only a model or item label and the code, as Model: SH-710, or in a table under such a label), a shorter code is read too (two letters or more before a hyphen, and two digits or more: SH-710, FT-38), and a code written once that is that code with two neighbours swapped (SH-701) is reported. Not when the document names two codes so (a catalog), nor a code in a table, one written twice or more, one on a line that also names the document's code (the SH-710 replaces the SH-701), one after a label of another kind (booking number), or one with a single letter (A-12)."

package/rules/toki-as-condition.yaml

@@ -0,0 +1,71 @@
+id: toki-as-condition
+layer: L3
+status: stable
+how_to_find: condition-toki
+word_list: condition-toki
+extra_word_lists: [condition-follower]
+requires: [pos]
+languages: [ja]
+severity: info
+
+name:
+  ja: 条件を言う「時」
+  en: 時 written for a condition (法令用語の「とき」)
+
+why:
+  ja: 法令の文では、「時」は時点（相続開始の時から）、「とき」は条件（認定を受けたときは）を言います。「認定を受けた時は」と書くと、読み手は「受けた時点で」の意味か「受けた場合に」の意味かを考えます。契約書や規程は法令の書き方にそろえるので、同じ使い分けをします。動詞や助動詞で終わる節の後ろの「時」に、「は」「には」「も」が続くときだけ指します。
+  en: Japanese legal drafting writes 時 for a point in time (相続開始の時から, "from the time the succession opens") and とき for a condition (認定を受けたときは, "if the approval is given"). With 認定を受けた時は the reader has to decide whether a moment or a condition is meant. Contracts and internal rules follow the statutes' usage. chaff reports 時 only after a clause that ends in a verb or an auxiliary and before は, には or も.
+
+message:
+  ja: 条件を言うなら「{matched}」は「{preferred}」と書きます
+  en: 'For a condition, legal Japanese writes "{matched}" as "{preferred}"'
+
+how_to_fix:
+  ja: 条件なら「とき」にしてください（認定を受けた時は → 認定を受けたときは）。時点を言うなら「時から」「時に」のように書けば、時点と読めます。
+  en: For a condition, write とき (認定を受けた時は → 認定を受けたときは). For a point in time, write 時から or 時に so that it reads as one.
+
+placeholders:
+  matched:
+    ja: 見つけた語
+    en: the word found
+  preferred:
+    ja: 条件を言う書き方
+    en: the word for a condition
+
+levels: { strict: warning, normal: info, relaxed: info }
+
+use_for: [legal, docs, academic, literature, speech]
+off_for:
+  docs: "The 時 / とき split is a convention of legal drafting: outside it, 時は for a condition is not a slip."
+  academic: "The 時 / とき split is a convention of legal drafting: outside it, 時は for a condition is not a slip."
+  literature: "The 時 / とき split is a convention of legal drafting: outside it, 時は for a condition is not a slip."
+  speech: "The 時 / とき split is a convention of legal drafting: outside it, 時は for a condition is not a slip."
+
+group: wording
+summary:
+  ja: 「認定を受けた時は」のように、条件を「とき」でなく「時」で書いた所
+  en: 時 written for a condition (受けた時は) where legal Japanese writes とき
+example:
+  ja:
+    config: { genre: legal/contract }
+    before: |
+      第5条　乙は、許可の取消しを受けた時は、直ちに甲に通知しなければならない。
+    after: |
+      第5条　乙は、許可の取消しを受けたときは、直ちに甲に通知しなければならない。
+
+not_flagged:
+  ja: 時点を言う「時」（相続開始の時から、死亡した時に、契約の終了の時まで）、名詞や「その」「ある」の後ろの「時」（事故の時は、その時は）、「時効」「時間」「同時」「随時」「臨時」「当時」「時点」「時期」のような語、鉤括弧で引いた中は指しません。法務のジャンルだけで動きます。
+  en: 時 for a point in time (相続開始の時から, 死亡した時に, 契約の終了の時まで), 時 after a noun or after その and ある (事故の時は, その時は), words such as 時効, 時間, 同時, 随時, 臨時, 当時, 時点 and 時期, and anything quoted in 「」 are not reported. Only the legal genres run this rule.
+rewrite:
+  depth: light
+  ja:
+    direction: 条件を言う「時」を「とき」に替えてください。替えるのはその一語だけです。
+    pairs:
+      - before: 乙は、許可の取消しを受けた時は、直ちに甲に通知しなければならない。
+        after: 乙は、許可の取消しを受けたときは、直ちに甲に通知しなければならない。
+      - before: 支払期日を過ぎる時には、年三パーセントの遅延損害金を支払う。
+        after: 支払期日を過ぎるときには、年三パーセントの遅延損害金を支払う。
+    keep:
+      - 条の番号と中身
+    avoid:
+      - 時点を言う「時」（時から、時まで、時に）まで替える

package/rules/total-mismatch.yaml

@@ -10,8 +10,8 @@ name:
   en: A total that is not the sum of its items
 
 why:
-  ja: 見積や請求の「合計」が、上に並べた金額の和と合わないと、読み手はどちらが正しいのかを計算し直すことになります。行を足したり消したりしたあとに、合計だけ直し忘れると起きます。箇条書きか表で、合計の語（合計・小計）で始まる行を、同じ単位で同じ列の金額の和と比べます。表の最初の列の見出しか、合計の行が数を書いた列の見出しが名指す語を付けた合計（見出しが「控除項目」の表の「控除合計」、「単位数」の列の「修得単位合計」）も合計の行と読みます。合計が足す期間を頭に付けた合計（年間合計、年計、通年合計）も合計の行と読みます。見出しが「項目」の表でも、最後の行の差引合計・控除合計は、上に合計のような行が無く金額の列が一つなら合計の行と読みます。契約書のように一つの文に書いた合計（「保守費60,000円、運用費30,000円とし、合計100,000円とする」「月額150,000円（内訳：…）」）も、その文に並べた同じ単位の金額の和と比べます。小計のあとの総計のように、足し方が何通りかあるときは、どの足し方でも合わないときだけ指します。
-  en: When the total of a quote or an invoice is not the sum of the amounts listed above it, the reader has to add them up again to find out which is right. It happens when a line is added or removed and the total is not updated. In a list or a table, a line starting with a total word (Total, Subtotal) is compared with the sum of the amounts in the same unit and column above it. A total with a word that the header of the table's first column, or of the column the total holds its number in, names ("Total deductions" under "Deduction", "Total credits earned" in the "Credits" column) is read as a total line too, and so is a total naming the span it covers ("Total for the year", "Year total", "Annual total"). Under a header that names nothing ("Item"), a "Total deductions" on the table's last row is read too, when no row above it is a total or a gross or net amount and the table has one column of amounts. A total written in a sentence, as contracts do ("$6,000 for hosting and $3,000 for support, for a total of $9,000", "$8 per month, made up of …"), is compared with the amounts in the same unit listed in that sentence. When there is more than one way to add them up, such as a grand total after a subtotal and tax, it is pointed out only when none of them matches.
+  ja: 見積や請求の「合計」が、上に並べた金額の和と合わないと、読み手はどちらが正しいのかを計算し直すことになります。行を足したり消したりしたあとに、合計だけ直し忘れると起きます。箇条書きか表で、合計の語（合計・小計）で始まる行を、同じ単位で同じ列の金額の和と比べます。表の最初の列の見出しか、合計の行が数を書いた列の見出しが名指す語を付けた合計（見出しが「控除項目」の表の「控除合計」、「単位数」の列の「修得単位合計」）も合計の行と読みます。合計が足す期間を頭に付けた合計（年間合計、年計、通年合計）も合計の行と読みます。見出しが「項目」の表でも、最後の行の差引合計・控除合計は、上に合計のような行が無く金額の列が一つなら合計の行と読みます。契約書のように一つの文に書いた合計（「保守費60,000円、運用費30,000円とし、合計100,000円とする」「月額150,000円（内訳：…）」「総額12,000円：設計5,000円、開発6,000円」）も、その文に並べた同じ単位の金額の和と比べます。合計で終わる文の次の文が「内訳は」で始まるときは、その文の金額と比べます。小計のあとの総計のように、足し方が何通りかあるときは、どの足し方でも合わないときだけ指します。
+  en: When the total of a quote or an invoice is not the sum of the amounts listed above it, the reader has to add them up again to find out which is right. It happens when a line is added or removed and the total is not updated. In a list or a table, a line starting with a total word (Total, Subtotal) is compared with the sum of the amounts in the same unit and column above it. A total with a word that the header of the table's first column, or of the column the total holds its number in, names ("Total deductions" under "Deduction", "Total credits earned" in the "Credits" column) is read as a total line too, and so is a total naming the span it covers ("Total for the year", "Year total", "Annual total"). Under a header that names nothing ("Item"), a "Total deductions" on the table's last row is read too, when no row above it is a total or a gross or net amount and the table has one column of amounts. A total written in a sentence, as contracts do ("$6,000 for hosting and $3,000 for support, for a total of $9,000", "$8 per month, made up of …", "a total of $12,000 — $5,000 for design and $6,000 for development"), is compared with the amounts in the same unit listed in that sentence, and with the amounts of the next sentence when it opens with a breakdown phrase ("This consists of …"). When there is more than one way to add them up, such as a grand total after a subtotal and tax, it is pointed out only when none of them matches.
 
 message:
   ja: 合計「{written}」が、内訳の金額の和（{sum}）と合いません
@@ -61,5 +61,5 @@ example:
       | Total | $8,000 |
 
 not_flagged:
-  ja: 単位や列の違う金額は足しません。合計の語に表の見出しが名指さない語を付けた行（見出しが「項目」の表の「消費税合計」）は、別の種類の合計かもしれないので比べません。差引合計・控除合計も、表の最後の行でないとき、上に合計の行や総支給額・支給合計の行があるとき、金額の列が二つ以上あるときは比べず、下から続けた行の和か、その上の行の和からそれを引いた額と合えば指しません。面積のように、上の行の和とは限らない量の合計（面積合計）も比べません。前の期間の合計（前年合計）は読まず、期間を付けた合計が内訳の和を一年に直した額（ちょうど4倍・12倍・52倍。月額の内訳に年間合計）なら比べません。重さ・容量・長さ（mg、g、mL、L、cm、km）は、列のどの行も同じ種類の量なら換算して足します（500mg と 0.5g は 1g）。何あたりかを書いた量（300mg/錠）、目安の量（約300mg）、範囲（300〜400mg）がある列は足しません。足し方が何通りもあるとき（小計と税のあとの総計など）は、どれとも合わないときだけ指します。文の中では、合計の語（合計・総額）のすぐ後ろの金額か内訳の語（内訳は）のすぐ前の金額だけを合計と読み、内訳の金額が二つ以上あるときだけ比べます。並びの一部（単価や上限など、合計の語から離れた金額を除いた並び）の和か、一つを引いた額（値引き）と合えば指しません。
-  en: Amounts in another unit or column are not added. A total with a word the table's header does not name ("Total tax" under "Item") is not compared, as it may be a total of another kind, nor is a total of a quantity that need not be the sum of the rows (Total area). Under such a header, "Total deductions" is not compared when it is not the last row, when a total or a gross or net amount (Gross pay) is above it, or when the table has two columns of amounts; it is not reported when it matches the last few rows, or the rows above those less them. A total for another span ("Prior-year total") is not read, and a total naming its span that is the items scaled to a year (exactly 4, 12 or 52 times their sum, as monthly items under an annual total) is not compared. Mass, volume and length (mg, g, mL, L, cm, km) are converted and added when every row of the column is the same kind of measure (500 mg and 0.5 g make 1 g); a column with an amount per something (300 mg/tablet), a rough amount (about 300 mg) or a range (300-400 mg) is not added. Where there is more than one way to add them up, it is reported only when none matches. In a sentence, only the amount right after a total phrase (a total of) or right before a breakdown phrase (made up of) is read as a total, and only when two or more items in its unit are listed. It is not reported when the items nearest the phrase add up to it, or when it matches with one item taken away (a discount).
+  ja: 単位や列の違う金額は足しません。合計の語に表の見出しが名指さない語を付けた行（見出しが「項目」の表の「消費税合計」）は、別の種類の合計かもしれないので比べません。差引合計・控除合計も、表の最後の行でないとき、上に合計の行や総支給額・支給合計の行があるとき、金額の列が二つ以上あるときは比べず、下から続けた行の和か、その上の行の和からそれを引いた額と合えば指しません。面積のように、上の行の和とは限らない量の合計（面積合計）も比べません。前の期間の合計（前年合計）は読まず、期間を付けた合計が内訳の和を一年に直した額（ちょうど4倍・12倍・52倍。月額の内訳に年間合計）なら比べません。重さ・容量・長さ（mg、g、mL、L、cm、km）は、列のどの行も同じ種類の量なら換算して足します（500mg と 0.5g は 1g）。何あたりかを書いた量（300mg/錠）、目安の量（約300mg）、範囲（300〜400mg）がある列は足しません。足し方が何通りもあるとき（小計と税のあとの総計など）は、どれとも合わないときだけ指します。文の中では、合計の語（合計・総額）のすぐ後ろの金額か内訳の語（内訳は）のすぐ前の金額だけを合計と読み、内訳の金額が二つ以上あるときだけ比べます。並びの一部（単価や上限など、合計の語から離れた金額を除いた並び）の和か、一つを引いた額（値引き）と合えば指しません。合計のすぐ後ろの「：」から続く内訳は、「うち」「または」「最大」のように内訳のすべてとは限らない語があるとき、ほかの単位の金額や割合を並べたときは比べません。
+  en: Amounts in another unit or column are not added. A total with a word the table's header does not name ("Total tax" under "Item") is not compared, as it may be a total of another kind, nor is a total of a quantity that need not be the sum of the rows (Total area). Under such a header, "Total deductions" is not compared when it is not the last row, when a total or a gross or net amount (Gross pay) is above it, or when the table has two columns of amounts; it is not reported when it matches the last few rows, or the rows above those less them. A total for another span ("Prior-year total") is not read, and a total naming its span that is the items scaled to a year (exactly 4, 12 or 52 times their sum, as monthly items under an annual total) is not compared. Mass, volume and length (mg, g, mL, L, cm, km) are converted and added when every row of the column is the same kind of measure (500 mg and 0.5 g make 1 g); a column with an amount per something (300 mg/tablet), a rough amount (about 300 mg) or a range (300-400 mg) is not added. Where there is more than one way to add them up, it is reported only when none matches. In a sentence, only the amount right after a total phrase (a total of) or right before a breakdown phrase (made up of) is read as a total, and only when two or more items in its unit are listed. It is not reported when the items nearest the phrase add up to it, or when it matches with one item taken away (a discount). Items after a colon or a dash right after a total are not compared when "including", "or" or "up to" shows they may not be every item, when one of them is in another unit, or when they are percentages.

package/rules/unknown-word.yaml

@@ -47,8 +47,8 @@ example:
       The report is attached to this email.
 
 not_flagged:
-  ja: 大文字を含む語、四字より短い語、コード・URL・メールアドレスの中の語、強調や角括弧で頭の字を分けた語の残り（**G**lobally の lobally、[e]xpressions の xpressions）、文書で二度以上使う語、一字違いの辞書の語が無い語、chaff.yaml の names に並べた語、語彙表 known-misspelling が別に言う語は指しません。
-  en: Words with a capital letter, words shorter than four letters, words in code, URLs and email addresses, the rest of a word whose first letter is set apart by emphasis or brackets (lobally in **G**lobally, xpressions in [e]xpressions), words used twice or more in the document, words with no dictionary word one letter away, words listed under names in chaff.yaml, and the misspellings known-misspelling reports are not reported.
+  ja: 大文字を含む語、四字より短い語、コード・URL・メールアドレスの中の語、強調や角括弧で頭の字を分けた語の残り（**G**lobally の lobally、[e]xpressions の xpressions）、文書で二度以上使う語、一字違いの辞書の語が無い語、chaff.yaml の names に並べた語、語彙表 known-misspelling が別に言う語は指しません。同じ文書がコード（`tidyq check` やコードの区画）にも書いた語も、その文書の名前なので指しません。
+  en: Words with a capital letter, words shorter than four letters, words in code, URLs and email addresses, the rest of a word whose first letter is set apart by emphasis or brackets (lobally in **G**lobally, xpressions in [e]xpressions), words used twice or more in the document, words with no dictionary word one letter away, words listed under names in chaff.yaml, and the misspellings known-misspelling reports are not reported. Nor is a word the document also writes in code (`tidyq check`, a code block), since it is a name the document uses.
 rewrite:
   depth: light
   en:

package/rules/use-before-definition.yaml

@@ -50,8 +50,8 @@ example:
       This agreement is between Harbour Ltd (the "Seller") and Hill Ltd (the "Buyer"). The Seller ships within five days.
 
 not_flagged:
-  ja: 定義の条（「X」とは…をいう）で定義した語は、前で使っても言いません。定義の条は文書の頭にも終わりにも置く書き方があるためです。規約やポリシーの丁寧な形（以下「X」といいます）も、法令の形と同じに読みます。見出しの行（章・節の行、条の前の「（買主の義務）」のような見出し）の語と、漢字で終わる語にさらに漢字が続く長い語（「監査委員会」の「監査委員」）と、定義の括弧の前の長い名前をそのまま書いた所（「…作成の手引き（以下「手引き」という。）」より前の「…作成の手引き」）は、使った所に数えません。最初の一か所だけを指します。
-  en: Terms defined in a definitions clause ("X" means ...) are not checked, since a definitions clause may come first or last. A heading line (a chapter or section line, or the caption above an article) does not count as a use, nor does a longer word that runs on in kanji past a term ending in kanji, nor an earlier copy of the long name written just before the definition's bracket. The polite Japanese form (以下「X」といいます) is read like the statute form. Only the first early use is pointed at.
+  ja: 定義の条（「X」とは…をいう）で定義した語は、前で使っても言いません。定義の条は文書の頭にも終わりにも置く書き方があるためです。規約やポリシーの丁寧な形（以下「X」といいます）も、法令の形と同じに読みます。見出しの行（章・節の行、条の前の「（買主の義務）」のような見出し）の語と、漢字で終わる語にさらに漢字が続く長い語（「監査委員会」の「監査委員」）と、定義の括弧の前の長い名前をそのまま書いた所（「…作成の手引き（以下「手引き」という。）」より前の「…作成の手引き」）は、使った所に数えません。最初の一か所だけを指します。別の語を定義する括弧の前の名前の中（This Services Agreement (this "Agreement") の Services、本サービス利用契約（以下「本契約」という。）の本サービス）も、使った所に数えません。
+  en: Terms defined in a definitions clause ("X" means ...) are not checked, since a definitions clause may come first or last. A heading line (a chapter or section line, or the caption above an article) does not count as a use, nor does a longer word that runs on in kanji past a term ending in kanji, nor an earlier copy of the long name written just before the definition's bracket. The polite Japanese form (以下「X」といいます) is read like the statute form. Only the first early use is pointed at. A word inside the name written right before another term's defining bracket (Services in This Services Agreement (this "Agreement")) is not a use either.
 rewrite:
   depth: structure
   ja:

package/src/api.ts

@@ -31,8 +31,17 @@ export type Section = { readonly depth: number; readonly heading: string; readon
 /** One bulleted or numbered list, with the length of each item in characters. */
 export type List = { readonly span: Span; readonly itemLengths: readonly number[] };
 
-/** One entry of a word list. instead_of is another way to write the same thing, for rules that check a document is consistent. */
-export type LexiconEntry = { readonly pattern: string; readonly instead_of?: string };
+/**
+ * One entry of a word list. instead_of is another way to write the same thing, for rules that check a document is
+ * consistent; rewrite, how to rewrite this phrase. genres: the genres or groups it holds in (legal, blog/tech); without
+ * them, every genre. options.lexicon and doc.lexicons hold only the entries for the document's genre.
+ */
+export type LexiconEntry = {
+  readonly pattern: string;
+  readonly instead_of?: string;
+  readonly rewrite?: string;
+  readonly genres?: readonly string[];
+};
 
 export type Lexicon = readonly LexiconEntry[];
 

package/src/cli-text.ts

@@ -49,9 +49,10 @@ const USAGE_JA = `chaff — 文章の読みにくいところを見つけます
   chaff ai-score <file>... [--format text|json] [--json] [--compact]
                                  AI らしさの簡易判定（低・中・高）。生成文に多い目印を、同じジャンルの人の文書と比べる（書いたのが AI かは判定しない）
                                  --json は --format json と同じ。--compact はファイルごとに 1 行
-  chaff grade <items.jsonl> [--out <results.jsonl>] [--baseline <前の results.jsonl>] [--allow-stamp-mismatch]
+  chaff grade <items.jsonl> [--rubric <rubric.yaml|.json>] [--out <results.jsonl>] [--baseline <前の results.jsonl>] [--allow-stamp-mismatch]
               [--variant-key <欄>] [--format text|json|markdown] [--json] [--compact]
                                  AI の出力を JSONL でまとめて採点する（指摘の率・事実・引用・合否。何も送らない）
+                                 --rubric はその回だけ chaff.yaml の grade: の代わりにそのファイル（grade: と同じ形の YAML か JSON）で採点する
                                  --allow-stamp-mismatch はルールか設定が前の回と違っても比べる（そのことを先に出す）
                                  --variant-key は variant の欄の代わりにその欄で出力を分けて並べる。--json は --format json と同じ。markdown は PR のコメント向け
   chaff fix-plan <file> [--depth light|structure|register] [--json]
@@ -67,7 +68,7 @@ const USAGE_JA = `chaff — 文章の読みにくいところを見つけます
   chaff feedback <file> --rule <rule> [--line N] | --missed --line N
                                  誤った指摘・見逃しの報告の下書きを作る（何も送らない。--with-config で chaff.yaml 全体も載せる）
 
-  --compact         エンジニア向けの 1 行形式
+  --compact         エンジニア向けの短い形式。指摘 1 件を 2 行で出す（位置・重さ・説明、その下に rule の id）
   --no-guide        ジャンルを決めたときに最初に出す、そのジャンルの指針を出さない
   --experimental    試験中の rule も動かす
   --genre <ジャンル>  この実行だけジャンルを決める（chaff.yaml より優先）
@@ -108,9 +109,10 @@ const USAGE_EN = `chaff — finds what makes writing hard to read. It never rewr
   chaff ai-score <file>... [--format text|json] [--json] [--compact]
                                  quick AI-likeness score (low, medium, high): signs common in generated text against human documents of the genre (not a verdict on who wrote it)
                                  --json is --format json; --compact prints one line per file
-  chaff grade <items.jsonl> [--out <results.jsonl>] [--baseline <earlier results.jsonl>] [--allow-stamp-mismatch]
+  chaff grade <items.jsonl> [--rubric <rubric.yaml|.json>] [--out <results.jsonl>] [--baseline <earlier results.jsonl>] [--allow-stamp-mismatch]
               [--variant-key <field>] [--format text|json|markdown] [--json] [--compact]
                                  grade a JSONL file of model outputs (finding rates, facts, quotations, pass or fail; sends nothing)
+                                 --rubric grades by that file (YAML or JSON, shaped like grade:) instead of chaff.yaml's grade: for this run
                                  --allow-stamp-mismatch compares with the baseline even when its rules or settings differ, saying so first
                                  --variant-key splits the outputs by that field instead of variant; --json is --format json; markdown is for a PR comment
   chaff fix-plan <file> [--depth light|structure|register] [--json]
@@ -126,7 +128,7 @@ const USAGE_EN = `chaff — finds what makes writing hard to read. It never rewr
   chaff feedback <file> --rule <rule> [--line N] | --missed --line N
                                  draft a report of a wrong or missed finding (sends nothing; --with-config adds all of chaff.yaml)
 
-  --compact         one line per finding, for engineers
+  --compact         a short form for engineers: two lines per finding (position, severity, message; the rule id below)
   --no-guide        leave out the genre's guide, which comes first when the genre is set
   --experimental    run the experimental rules too
   --genre <genre>   the genre for this run only (wins over chaff.yaml)

package/src/commands/grade.ts

@@ -1,10 +1,11 @@
-import { mkdirSync, writeFileSync } from "node:fs";
+import { mkdirSync, readFileSync, writeFileSync } from "node:fs";
 import { dirname } from "node:path";
 import { packageFor } from "../adapter-load.ts";
 import type { Config } from "../config/load.ts";
 import { readDocumentFile } from "../files.ts";
 import { GENRES } from "../genre.ts";
 import { gradeItem, type GradeSetup } from "../grade/grade-item.ts";
+import { expectProblems } from "../grade/expect-read.ts";
 import { DEFAULT_VARIANT_FIELD, ITEM_FIELDS, parseItems, type GradeItem, type VariantField } from "../grade/item.ts";
 import { renderMarkdown } from "../grade/render-markdown.ts";
 import { renderVariants, renderVariantsCompact } from "../grade/render-variants.ts";
@@ -14,6 +15,8 @@ import { renderCompact, renderSummary } from "../grade/render.ts";
 import type { GradeResult } from "../grade/result.ts";
 import { gradeSetup } from "../grade/setup.ts";
 import { parseRubric, type Rubric } from "../grade/rubric.ts";
+import { parseRubricFile, type RubricFileProblem } from "../grade/rubric-file.ts";
+import { rubricRuleEntries, taskNamesOf, taskRuleIds } from "../grade/task-rubric.ts";
 import { rulesOf } from "../custom/load.ts";
 import { summaryOf } from "../grade/summary.ts";
 import { GRADE_TEXT, type GradeText } from "../grade/text.ts";
@@ -26,7 +29,7 @@ import { chooseBaseline } from "./grade-baseline.ts";
 /** Exit codes (spec §29.3). 2 keeps "the grader did not run" apart from "an output is bad" at a CI gate. */
 export const GRADE_EXIT = { passed: 0, failed: 1, unreadable: 2 } as const;
 
-const VALUED: ReadonlySet<string> = new Set(["--out", "--genre", "--baseline", "--format", "--variant-key"]);
+const VALUED: ReadonlySet<string> = new Set(["--out", "--genre", "--baseline", "--format", "--variant-key", "--rubric"]);
 
 const FORMATS = ["text", "json", "markdown"] as const;
 
@@ -56,11 +59,13 @@ export type GradeContext = {
   readonly ui: UiLanguage;
 };
 
-const readItems = async (path: string, variantField: VariantField, text: GradeText): Promise<readonly GradeItem[] | undefined> => {
+type ReadItems = { readonly items: readonly GradeItem[]; readonly lines: readonly number[] };
+
+const readItems = async (path: string, variantField: VariantField, tasks: readonly string[], text: GradeText): Promise<ReadItems | undefined> => {
   try {
-    const vocabulary = { isLanguage: (language: string) => packageFor(language) !== undefined, genres: GENRES };
+    const vocabulary = { isLanguage: (language: string) => packageFor(language) !== undefined, genres: GENRES, tasks };
     const parsed = parseItems(await readDocumentFile(path), vocabulary, variantField);
-    if ("items" in parsed) return parsed.items;
+    if ("items" in parsed) return parsed;
     parsed.problems.forEach((problem) => console.error(`${path}: ${text.problem(problem)}`));
   } catch (error) {
     console.error(text.unreadable(path, error instanceof Error ? error.message : String(error)));
@@ -68,39 +73,75 @@ const readItems = async (path: string, variantField: VariantField, text: GradeTe
   return undefined;
 };
 
-/** The `grade:` rubric, or undefined after saying what is wrong with it. `rubric: undefined` is a run with no rubric. */
-const readRubric = (config: Config, text: GradeText): { readonly rubric: Rubric | undefined } | undefined => {
+/** The rubric a run grades by, and the --rubric file it came from when it came from one. */
+type RubricRead = { readonly rubric: Rubric | undefined; readonly file?: { readonly path: string; readonly digest: string } | undefined };
+
+/** chaff.yaml's `grade:` rubric, or undefined after saying what is wrong with it. `rubric: undefined` is a run with no rubric. */
+const readConfigRubric = (config: Config, text: GradeText): RubricRead | undefined => {
   const parsed = parseRubric(config.grade);
   if ("rubric" in parsed) return parsed;
   parsed.problems.forEach((problem) => console.error(`chaff: ${text.rubricProblem(problem)}`));
   return undefined;
 };
 
-/** A rule id under grade.rules that chaff does not know. Said once here; each result also lists it as not run. */
-const warnUnknownRules = (rubric: Rubric | undefined, config: Config, text: GradeText): void => {
+const fileProblemText = (path: string, problem: RubricFileProblem, text: GradeText): string => {
+  if (problem.kind === "format") return text.rubricFormat(path);
+  if (problem.kind === "syntax") return text.rubricSyntax(path, problem.why);
+  return text.rubricProblem(problem.problem, path);
+};
+
+/** A --rubric file's rubric, which replaces chaff.yaml's `grade:`, or undefined after saying why it cannot be read. */
+const readRubricFile = (path: string, text: GradeText): RubricRead | undefined => {
+  try {
+    const parsed = parseRubricFile(path, readFileSync(path, "utf8"));
+    if ("rubric" in parsed) return { rubric: parsed.rubric, file: { path, digest: parsed.digest } };
+    parsed.problems.forEach((problem) => console.error(fileProblemText(path, problem, text)));
+  } catch (error) {
+    console.error(text.unreadable(path, error instanceof Error ? error.message : String(error)));
+  }
+  return undefined;
+};
+
+const readRubric = (rubricPath: string | undefined, config: Config, text: GradeText): RubricRead | undefined =>
+  rubricPath === undefined ? readConfigRubric(config, text) : readRubricFile(rubricPath, text);
+
+/** A rule id under the rubric's rules that chaff does not know. Said once here; each result also lists it as not run. */
+const warnUnknownRules = (rubric: RubricRead, config: Config, text: GradeText): void => {
   const known = new Set(rulesOf(config.language ?? "en", config).map((rule) => rule.id));
-  Object.keys(rubric?.rules ?? {})
-    .filter((id) => !known.has(id))
-    .forEach((id) => console.error(`chaff: grade.rules.${id}: ${text.unknownRule}`));
+  const where = rubric.file === undefined ? "chaff: grade." : `${rubric.file.path}: `;
+  rubricRuleEntries(rubric.rubric)
+    .filter((entry) => !known.has(entry.id))
+    .forEach((entry) => console.error(`${where}${entry.path}.${entry.id}: ${text.unknownRule}`));
 };
 
 const setupFor = async (
   items: readonly GradeItem[],
-  rubric: Rubric | undefined,
+  rubric: RubricRead,
   argv: readonly string[],
   context: GradeContext,
   text: GradeText,
 ): Promise<GradeSetup | undefined> => {
   const languages = items.flatMap((item) => (item.language === undefined ? [] : [item.language]));
-  const run = { experimental: context.config.experimental || argv.includes("--experimental"), genre: context.flag(argv, "--genre") };
+  const run = {
+    experimental: context.config.experimental || argv.includes("--experimental"),
+    genre: context.flag(argv, "--genre"),
+    rubricFile: rubric.file?.digest,
+  };
   try {
-    return await gradeSetup(context.config, run, languages, rubric);
+    return await gradeSetup(context.config, run, languages, rubric.rubric);
   } catch (error) {
     console.error(text.cannotLoad(error instanceof Error ? error.message : String(error)));
     return undefined;
   }
 };
 
+/** Whether every expect entry is one fact; else says which are not, on their lines, before anything is graded. */
+const expectReadable = async (path: string, read: ReadItems, setup: GradeSetup, text: GradeText): Promise<boolean> => {
+  const problems = (await Promise.all(read.items.map((item, index) => expectProblems(item, read.lines[index] ?? 0, setup)))).flat();
+  problems.forEach((problem) => console.error(`${path}: ${text.problem(problem)}`));
+  return problems.length === 0;
+};
+
 /** One output after another, in the file's order: the results file lines up with the input. */
 const gradeInOrder = (items: readonly GradeItem[], setup: GradeSetup): Promise<GradeResult[]> =>
   items.reduce<Promise<GradeResult[]>>(async (previous, item) => [...(await previous), await gradeItem(item, setup)], Promise.resolve([]));
@@ -144,14 +185,24 @@ const printSummary = (path: string, results: readonly GradeResult[], compared: C
   } else printText(path, results, variants, compared, printing);
 };
 
-type RunOptions = { readonly path: string; readonly format: Format; readonly variantField: VariantField };
+type RunOptions = { readonly path: string; readonly format: Format; readonly variantField: VariantField; readonly rubric: string | undefined };
+
+/** --rubric's file: undefined when not given, null when given without one (a usage error, not a quiet fall back to chaff.yaml). */
+const rubricPathOf = (argv: readonly string[], context: GradeContext): string | undefined | null => {
+  if (!argv.includes("--rubric")) return undefined;
+  const path = context.flag(argv, "--rubric");
+  return path === undefined || path === "" || path.startsWith("--") ? null : path;
+};
 
 /** The file to grade and how to read and print it, or undefined after printing the usage. */
 const runOptionsOf = (argv: readonly string[], context: GradeContext): RunOptions | undefined => {
   const [path, ...extra] = gradeTargets(argv);
   const format = formatOf(argv, context);
   const variantField = variantFieldOf(argv, context);
-  if (path !== undefined && extra.length === 0 && format !== undefined && variantField !== undefined) return { path, format, variantField };
+  const rubric = rubricPathOf(argv, context);
+  if (path !== undefined && extra.length === 0 && format !== undefined && variantField !== undefined && rubric !== null) {
+    return { path, format, variantField, rubric };
+  }
   console.error(GRADE_TEXT[context.ui].usage);
   return undefined;
 };
@@ -171,16 +222,17 @@ export const runGrade = async (argv: readonly string[], context: GradeContext):
   const options = runOptionsOf(argv, context);
   if (options === undefined) return GRADE_EXIT.unreadable;
   const { path } = options;
-  const rubric = readRubric(context.config, host);
-  const items = rubric === undefined ? undefined : await readItems(path, options.variantField, host);
-  const setup = items === undefined || rubric === undefined ? undefined : await setupFor(items, rubric.rubric, argv, context, host);
-  if (setup === undefined || items === undefined) return GRADE_EXIT.unreadable;
+  const rubric = readRubric(options.rubric, context.config, host);
+  const read = rubric === undefined ? undefined : await readItems(path, options.variantField, taskNamesOf(rubric.rubric), host);
+  const setup = read === undefined || rubric === undefined ? undefined : await setupFor(read.items, rubric, argv, context, host);
+  if (setup === undefined || read === undefined || rubric === undefined || !(await expectReadable(path, read, setup, host))) return GRADE_EXIT.unreadable;
+  const { items } = read;
   const baseline = await chooseBaseline(context.flag(argv, "--baseline"), setup.stamp, argv.includes("--allow-stamp-mismatch"), context.ui);
   if (baseline.kind === "stop") return GRADE_EXIT.unreadable;
-  warnUnknownRules(setup.rubric, context.config, host);
+  warnUnknownRules(rubric, context.config, host);
   const results = await gradeInOrder(items, setup);
   writeResults(context.flag(argv, "--out"), results, host);
-  const rubricRules = new Set(Object.keys(setup.rubric?.rules ?? {}));
+  const rubricRules = (result: GradeResult): ReadonlySet<string> => taskRuleIds(setup.rubric, result.task);
   const compared = baseline.kind === "compare" ? { path: baseline.path, comparison: compareRuns(baseline.before, results, rubricRules) } : undefined;
   const ui = sharedLanguage(
     results.map((result) => result.language),

package/src/company-kana-spelling.ts

@@ -42,7 +42,26 @@ export const kanjiReadingOf = (
 const baseStartOf = (mention: CompanyMention): number =>
   mention.position === "after" ? mention.offset : mention.offset + mention.surface.length - mention.base.length;
 
-/** 会社の名前の、漢字一字をその読みのひらがなかカタカナで書いた形（みどりの生命保険株式会社、みどりノ生命保険株式会社）。 */
+/** 濁る頭の音（カ行、サ行、タ行、ハ行）。 */
+const VOICEABLE = /^[カキクケコサシスセソタチツテトハヒフヘホ]/u;
+const VOICED_MARK = "゙";
+
+/** 名前の中ほどの字の読みは、頭の音を濁らせて書くことがある（こむぎ畑 ハタケ を こむぎばたけ）。頭の音が濁らない読みには無い。 */
+export const voicedReadingOf = (reading: string): string | undefined => {
+  const first = VOICEABLE.exec(reading)?.[0];
+  return first === undefined ? undefined : `${(first + VOICED_MARK).normalize("NFC")}${reading.slice(first.length)}`;
+};
+
+/** 名前の字の読みの、かなの書き方。名前の頭でない字は、頭の音を濁らせた読みも。 */
+const readingsAt = (reading: string, inside: boolean): string[] => {
+  const voiced = inside ? voicedReadingOf(reading) : undefined;
+  return voiced === undefined ? [reading] : [reading, voiced];
+};
+
+/**
+ * 会社の名前の、漢字一字をその読みのひらがなかカタカナで書いた形（みどりの生命保険株式会社、みどりノ生命保険株式会社）。
+ * 名前の頭でない字は、頭の音を濁らせた読みでも（こむぎばたけベーカリー）。
+ */
 export const kanaSpellingsOf = (mention: CompanyMention, words: readonly ReadWord[]): string[] => {
   const baseStart = baseStartOf(mention);
   const baseEnd = baseStart + mention.base.length;
@@ -53,7 +72,8 @@ export const kanaSpellingsOf = (mention: CompanyMention, words: readonly ReadWor
       if (read === undefined) return [];
       const at = word.start - mention.offset + read.index;
       const [before, after] = [mention.surface.slice(0, at), mention.surface.slice(at + read.kanji.length)];
-      return [toHiragana(read.reading), read.reading].map((kana) => `${before}${kana}${after}`);
+      const inside = word.start + read.index > baseStart;
+      return readingsAt(read.reading, inside).flatMap((reading) => [toHiragana(reading), reading].map((kana) => `${before}${kana}${after}`));
     });
 };
 

package/src/company-name-ending.ts

@@ -0,0 +1,50 @@
+// 会社の名前の一語の終わりだけの違い。長い語の終わりの二字まで（Brightmoor と Brightmore、Lumenvale と Lumenvail）と、最後の語の
+// 単数と複数（Water Utility と Water Utilities）。名前のほかの語は同じもの。
+
+const LATIN_WORD = /^[a-z]+$/u;
+
+/** 終わりの二字の違いを見る語の長さ。短い語（Alpha と Alpine）は別の名前のことが多い。 */
+const MIN_ENDING_WORD_LENGTH = 8;
+/** 頭からそろった字の後ろに残る字の数。 */
+const MAX_ENDING_LENGTH = 2;
+
+const wordsOf = (base: string): string[] =>
+  base
+    .toLowerCase()
+    .split(/\s+/u)
+    .filter((word) => word !== "");
+
+/** 二つの名前の語の数が同じで、違うのが一語だけなら、その語の組と位置。 */
+const differingWord = (left: string, right: string): { readonly pair: readonly [string, string]; readonly last: boolean } | undefined => {
+  const [leftWords, rightWords] = [wordsOf(left), wordsOf(right)];
+  const differing = leftWords.flatMap((word, index) => (word === rightWords[index] ? [] : [index]));
+  const [at] = differing;
+  const [leftWord, rightWord] = [leftWords[at ?? -1], rightWords[at ?? -1]];
+  if (leftWords.length !== rightWords.length || differing.length !== 1 || leftWord === undefined || rightWord === undefined) return undefined;
+  return { pair: [leftWord, rightWord], last: at === leftWords.length - 1 };
+};
+
+const sharedPrefix = (left: string, right: string): number => {
+  const differ = [...left].findIndex((char, index) => char !== right.charAt(index));
+  return differ < 0 ? left.length : differ;
+};
+
+/** 八字以上の英字の語の、頭がそろい、終わりの二字までだけが違うか（moor と more）。 */
+export const isEndingApart = (left: string, right: string): boolean => {
+  if (left === right || !LATIN_WORD.test(left) || !LATIN_WORD.test(right) || Math.min(left.length, right.length) < MIN_ENDING_WORD_LENGTH) return false;
+  const prefix = sharedPrefix(left, right);
+  return left.length - prefix <= MAX_ENDING_LENGTH && right.length - prefix <= MAX_ENDING_LENGTH;
+};
+
+/** 片方が他方の複数の形か（Tool と Tools、Box と Boxes、Utility と Utilities）。 */
+export const isPluralOf = (singular: string, plural: string): boolean =>
+  LATIN_WORD.test(singular) &&
+  (plural === `${singular}s` || plural === `${singular}es` || (singular.endsWith("y") && plural === `${singular.slice(0, -1)}ies`));
+
+/** 二つの会社の名前の部分が、一語の終わりだけ違うか。長い語の終わりの二字までか、最後の語の単数と複数。 */
+export const isNameEndingSlip = (left: string, right: string): boolean => {
+  const differing = differingWord(left, right);
+  if (differing === undefined) return false;
+  const [leftWord, rightWord] = differing.pair;
+  return isEndingApart(leftWord, rightWord) || (differing.last && (isPluralOf(leftWord, rightWord) || isPluralOf(rightWord, leftWord)));
+};